Re: email-style italics: MARKUP.PM

[Jon Pareles xywrite4@xxxxxxxx]

Robert--

On MARKUP.PM

Thanks to you, I now have stunningly symmetrical right and left double-quotes. I got them using the
nn=R1R4R7 and nn=R1R4R8 in the my .kbd file.

Trying to input B=147 and E=148 (from the number keys) in MARKUP.DAT turned "quoted
text" into 147quotedtext148 (in Wordpad). Perhaps I needed a carriage return or other
character in MARKUP.DAT to do it that way?

The double quotes are now saved as the default.
But if you are still tweaking MARKUP.PM, my ideal would be to have another pre-existing MARKUP.DAT
available with single-quotes, so I don't have to remember where I stashed the ANSI characters in my
.kbd file each time.

I assume the emailers who started the whole thing would also love to have a handful of regularly
used substitutions available to MARKUP.PM if it could somehow recall more than one previously used
set.

In the meantime, I'm going to save a couple of .DAT files as MARKUPDQ.DAT and MARKUPSQ.DAT and
re-save them as MARKUP.DAT as I need them.

Even if you never get around to that tweak, I'll be using MARKUP.PM daily, with gratitude.

Jon Pareles

> - you can SAve a default markup tag set (all four tags)
> after one complete run; if the set has been previously
> saved, you are asked if you want to use it
> Reactions? Suggestions?
>
> > What do I input at the prompts to get actual left and
> > right quotes, and left and right single quotes?
>
> That depends. If you're going to port your text to
> ANSI
> (i.e. to Windows apps), then you want to change " and
> " to o
> (char 147) and oe (148). Change `' to ae 145 and AE
> 146. If
> you're staying in the XyWrite world, ""
> becomes 264 and 265, `' becomes 266 and 267. Now, you canNOT use the number
> pad
> (e.g. 1-4-7) to enter these keys! You need to have the
> replacement keys assigned to keys on your KBD, and
> moreover, > in the case of chars over 255 (three-byte XyWrite charset chars), you need to assign them in the KBD file using R1
> through R9 functions, thus:
>  nn=R2R6R4
> for char 264. Don't use commas (do NOT say
> "nn=R2,R6,R4") -- string the funcs
> together! It's
> super-tricky to capture those three byters, and this is the
> only way it works.
>
> Another way to handle these odd characters is to put them in the MARKUP.DAT file -- do a run with simple characters (asingle pair is enough) to learn how the MARKUP.DAT file is organized.
> THEN you CAN use the number pad to enter the keys you want. SAve MARKUP.DAT when you're done.
>