Re: XyWrite for Windows vs XyWrite for DOS

["..." yesss@xxxxxxxx]

Hi, Craig Triplett. If your writer does in fact submit
xyWrite 3 files with {mdXX} coding, here's a bit of arcana
that may be totally useless to you or might come in handy
in a xyW3/xyWin situation to make {mdnm} specific to what
it's undoing. (I use it where xyW meets html.) While {md+XX}
and {md-XX} choke v3 bigtime, you can *append* to v3 {mdXX}
codes freely for annotation or any other purpose:

	{mdbr+it}Guide to the Haffenreffer-Herreshoff Collection
	at M.I.T.{mdnm-it}

v3 renders the code as intended and retains such suffixes
through stores and reopenings. You can see how you could
convert {mdbr+it} to {md+it} and {mdnm-it} to {md-it}
by simply clearing the CMline, typing, and executing:
	ci br+ +
	ci nm- -
And of course {md+it} to {mdbr+it} and {md-it} to {mdnm-it}:
	ci +it br+it
	ci -it nm-it

Conversions in v3 must be done with codes exposed
since md+ and md- give it fits even when d bi=1 (that
invaluable undocumented neutralizer Tim Baehr bestowed
on us). I've never checked to see what xyWin and winNB
do with annotated {mdXX}es (and couldn't check xyDos4
since I long ago erased mine). If not done by ci
commands, annotations must be inserted manually--i.e., a
	md br+it
command inserts only {mdbr}. ... Ciao. 		--a

======================================= adpFisher  nyc
	xyWrite 3 supplements !xyWise and !xyWiz +
	Wolfgang Bechstein's seafaring adventures:
http://www.escape.com/~yesss/ ========================================