> the characters that
> WP9 can translate into Unicode show up in red, the rest in black.
I'm hoping your points are going to get me to the solution. I've also
discovered a few more things about WP9's symbol dialog box (ctrl-w) which
may be helpful to others working with WP. It looks like what characters are
shown in red as characters translateable to unicode or as the dialog puts it
to "SGML" depends on what the declared character set of the current file is.
If I am in a non SGML/XML file in other words a plain WP document as is the
case with where we are starting from, as you noted, no characters are shown
in red. If I start a new docbook document using one of WP's precompiled
DTDs, maybe most characters are show in red. If I am in one of our own GLAH
documents, which has a declared character set of isolat1, much fewer
characters are shown in red. If I open a new HTML document as SGML, using
either the precomplied WP HTML DTD or my own additions, the red characters
are close to those of the GLAH document.
Our problem arises when going from a WP document to HTML. If one used the
color guide shown when in a WP document, one might assume that no special
characters would be appropriately handled. However, some do translate to
appropriate isolat1 values and some do translate to appropriate ISO
entities. I'm hoping that the color coding shown when in an HTML document
will correlate with what happens when "saving as" HTML from a WP document.
>P9 does not restrict one
> to UTF-8 -- one can also use UTF-16 Big Endian or UTF-16 Little
Yes, but it doesn't have an option to use XML with isolat1 which is what we
want to do.