Hi Matthew,
On 30 Nov 96, 12:29, Matthew Johnson wrote to Auke Reitsma
 AR>> Personally I'm using WP5.1 for HTML work. A bunch of styles
 AR>> for each tag and a bunch of macros for each 'problem'. Most
 AR>> of it is still experimental. Just about every session I add
 AR>> or change something ...
 MJ> I'd like to see it when you're finished.
Ok. But it'll be some time ... Remind me next year or so ...
 MJ> ... I'm considering doing
 MJ> the HTML by hand. I think that in the long run it will probably
 MJ> be easier to take advantage of extensions.
The way I do it is basically by using styles. E.g: the pair of tags  and 
 are a perfect match for a 'closed' style and  is perfect for an 
'open' style. In this way you can setup styles for al basic types of HTML 
tags.
And you van do something similar with 'simple' WP codes like [LARGE][large] 
etc, using  etc.
This is the way I started doing it.
A problem with this method is that a number of tags have parameters. Like in 
the above example with . For this reason I have a second set of styles 
in which all tags are closed styles so the parameters can be put inside.
The macros are mainly for converting and validating. Many are based on the 
following fragment:
    {style}9Stylename{Enter}1
which looks for the style Stylename and activates it. Ultimately a WP file
which is to be saves as ascii only contains plain ascii characters, a LOT of 
styles and a few loose hard and soft returns.
The only problem which I can't solve is that when I scan with a macro through 
a file and detect an open style I can't find out _which_ open style that is. 
For closed styles the good old {system}29~ works perfectly but for open 
styles that does not work :-(
Greetings from
 _____
 /_|__|  Auke Reitsma, Delft, The Netherlands.
/  | \  --------------------------------------
email: Auke.Reitsma@net.HCC.nl
--- GEcho 1.00
---------------