Hello,
since Help+Manual 10, I have noticed that some build-in builds are labeled differently, namely:
- eWriter - This adds the EBOOK build.
- Webhelp - This adds the HTML build.
It is a little confusing. Can you unify the builds labeling? I would expect to add "HTML" or "EBOOK". Now I must think about what I am adding, because the naming is not transparent. Al least keep the old name in brackets: "eWriter (EBOOK)", "Webhelp (HTML)".
Confusing built-in build names
Moderators: Alexander Halser, Tim Green
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Confusing built-in build names
Hi Peter,
These are actually not new, that has always been the case.
In the case of eWriter, it has historical reasons: The first experimental version of what became eWriter was referred to simply as a "Windows eBook", and the rather ungainly build solution was to activate both eBook and HTML for it. This has now become so established that our developers didn't want to change it because it could have caused errors in existing projects.
WebHelp used to be called "browser-based help", because there was some concern that it was a proprietary term from Adobe. Instead of calling the build something odd like BBHELP we chose to use just HTML, which was easily distinguished from CHM for CHM files. In retrospect, that has proved to be a little problematic as well, because all the output formats except Word and PDF are actually HTML-based. And Microsoft also caused endless confusion by referring to CHM as "HTML Help" to distinguish it from the former RTF-based WinHelp in Windows 3. Now, many people assume that "HTML Help" means WebHelp, and so the confusion continues.
For the moment we're stuck with these tags, even though they aren't perfect.
These are actually not new, that has always been the case.
In the case of eWriter, it has historical reasons: The first experimental version of what became eWriter was referred to simply as a "Windows eBook", and the rather ungainly build solution was to activate both eBook and HTML for it. This has now become so established that our developers didn't want to change it because it could have caused errors in existing projects.
WebHelp used to be called "browser-based help", because there was some concern that it was a proprietary term from Adobe. Instead of calling the build something odd like BBHELP we chose to use just HTML, which was easily distinguished from CHM for CHM files. In retrospect, that has proved to be a little problematic as well, because all the output formats except Word and PDF are actually HTML-based. And Microsoft also caused endless confusion by referring to CHM as "HTML Help" to distinguish it from the former RTF-based WinHelp in Windows 3. Now, many people assume that "HTML Help" means WebHelp, and so the confusion continues.
For the moment we're stuck with these tags, even though they aren't perfect.
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
-
Peter_J_user
- Posts: 8
- Joined: Thu Dec 16, 2021 4:20 pm
Re: Confusing built-in build names
Hi Tim,
thanks for your response. I understand that the builds cannot be changed for backwards compatibility (which I want to keep, too).
I wonder if the UI strings when selecting the builds can be updated - please see attached:
For example: eWriter > eWriter (EBOOK)
thanks for your response. I understand that the builds cannot be changed for backwards compatibility (which I want to keep, too).
I wonder if the UI strings when selecting the builds can be updated - please see attached:
For example: eWriter > eWriter (EBOOK)
You do not have the required permissions to view the files attached to this post.
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Confusing built-in build names
No, because we want to actively get away from the word "eBook" in connection with eWriter, because that limits it too much and many people then misunderstand what it's for. It's now a full, interactive and context-sensitive help format. So it's official name is now eWriter Help, or eWriter in the short form.I wonder if the UI strings when selecting the builds can be updated - please see attached:
For example: eWriter > eWriter (EBOOK)
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Re: Confusing built-in build names
Excelent reasons! The ewriter format is so powerful!
Are you considering to make these changes also within eviewer itself? There are still references to the word ebook.

Are you considering to make these changes also within eviewer itself? There are still references to the word ebook.
You do not have the required permissions to view the files attached to this post.
- Tim Green
- Site Admin
- Posts: 7818
- Joined: Mon Jun 24, 2002 9:11 am
- Location: Bruehl, Germany
- Contact:
Re: Confusing built-in build names
Thanks, noted. 
Regards,
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.
Tim (EC Software Documentation & User Support)
Private support:
Please do not email or PM me with private support requests -- post to the forum directly.