Special operations in eWriter


Next — in an Editor’s System Menu

The Next and Prev commands in the system menus of child windows in the Windows Multiple document Interface applications are pretty useless. Next skims through the z-order stack by sending the front window to the back. Prev brings the bottom window to the top. Once the load order has been shuffled, these bring up random windows. In eWriter, starting with 0.9x, Next, ^F6, brings up the window immediately under the top one. If you have a number of windows open but want to jump back and forth between two, bring them to the top and then use ^F6 to move back and forth. I have not yet found a use for the Shift+^F6. It still brings up the bottom window.


eWriter and the European typist

eWriter began as my 21st century etypewriter. My horizon stretched out just past the neighborhood pizza palace. It's plain text for writing email content. Plain text means 7-bit characters (the 0 to 127 byte values). That's why tagging methods like RTF and HTML exist. Attachments go through a MIME coding-decoding pair of processes to get the text into plain text form. And I guess modern mailers run their own text through the process to catch 8-bit chars.

If you just open an editor in eWriter and start typing, you will find that the chars 128 through 254 do not seem to work. Actually, you can make them work either of two ways. Look on the Edit menu. There are two items:

     Enable high one-byte chars as text
     Enable high one-byte chars as HTML/XML codes

You can check only one of these, and while it is checked the 8-bit ANSI characters will go into your text as the characters you expect to see or as HTML/XML "escape" codes for showing the characters in a browser viewed text.

From my early days of protecting the American English writer from his or her special case typing in a plain text setting, I did not keep those two settings across sessions in ewriter.ini. This means that to type Spanish or German you must pull down the Edit menu and click the pertinent item each time you open eWriter. Of course, you may be moving back and forth during the session, anyway.


I’m not sure what I mean by “special operations,” but I know what my first topic will be. It has to do with the emailing of what I’ve referred to as an eletter. My first thought about eWriter, and the 16 bit Pocketpad I did earlier, was as “everyone’s etypewriter.” The paper would roll into a text editor and roll out of a web browser. Both were free and ubiquitous. The two were connected by the cyberspace wormhole of email with its seven-bit plain text.

The single drawback, was the HTML “tag” as the writer’s punctuation marks. The simplest is three characters. And in the simplest cases two are required. Obviously, the etypewriter for the 21st century would have to have some souped up keys. The result is eWriter as you see it.

eLetters and mail programs that export HTML

The “special operation” I have in mind has to do with the new mailers which are also using HTML as a way of exporting text when sending it. If you do not have one of those mailers to export and received HTML tagged messages, you see the text message and then below it the HTML tagged version of the message. One of these mailers will not read my tags in an eletter and will, as I intend, present the eletter as plain text. The recipient selects everything between <HTML> and </HTML>, moves it to a text editor, and saves it into an .htm or .html file. The recipient reads the manuscript in the mailer or text editor and the typeset or word processor copy in a browser, from which a paper copy may be printed.

The problem comes when these new mailers are used both to send and receive an eletter. The solution lies with the sender. The problem is that the HTML tagged version of the sent message puts its tags around all those tags in the text. I understand, from a new friend who has tried sending eletters to his friends, that what is read by his friends’ mailers is ...confused.

To send eletters, or anything you don’t want to arrive in a (usually pointless) HTML wrapper, you have to turn off your mailer's HTML export. I’ve installed Outlook Express in order to see how this is done. I assume other mailers will have pretty much the same Options setup.

On the Menu: Tools/Options... Send (Tab). Check “Plain Text”. OK the dialog. To make your mailer’s Compose editor “look and feel” like a text editor, not a word processor, click on the read tab and make your Proportional Font, like the non-Proportional font, Courier or Courier New. You may already have seen my suggestions for eletters.

To make them easy to read “as text” in the mailer, I usually tab in eight spaces to write text. I use Shift+Enter to hold that indent in subsequent lines as I type paragraphs. This way, I can put <P> and other non-inline tags in a gutter and, by using white space, make the text paragraphs very easy to read as plain text.


Add your own “special operations.” Pull speclops.htm into an editor, put in a line (Ctrl+NumPad#4), and type in how you do a complex task involving interior and exterior setup. Put in another line at the end. If you get a number of these, you might want to put in headings. you might even put in anchors and a jump table at the top.