Thanks for your interest in OrthoXML mode.
"Editing your xml files, I notice there are lots of funny characters
in it. as if there was some sort of encoding translation that was to an
"What's wrong with UTF-8?"
Windows does not support UTF-8 well so I 'go with the flow' and use their
favored encoding, CP1252 which is effectively identical to ISO-8859-1
(Western Eurpean). [I would very much like to use UTF-8 so I could exploit
the 2800+ glyphs of Consolas, my favorite font. But I have found encodings
to be fraught with difficulties, and not just with jEdit. If only someone
would write an "Encoding Wizard" plugin :) ]
I would guess that you have to use the 'FILE/Reload with encoding' command
to load the files with ISO-8859-1 encoding.
"Have you tried opening these xml files in jEdit with the XML plugin?
They don't validate."
I don't know a thing about the XML plugin or what 'validation' implies.
OrthoXML.xml confines itself to just one issue: coloring jEdit mode syntax,
which as the PDF examples indicate, it apparently does. I say 'apparently'
because I am its only tester so far. I have no difficulty incorporating it
in CATALOG and loading and using it.
Of course, as it stands, OrthoXML.xml is not a viable replacement for
xml.xml because it ignores certain XML forms. It looks to me like it can
pretty easily be combined with xml.xml to produce a mode that has all the
capabilities of both. But the first order of business is to gain some
confidence in its correctness and I can't do that by myself.
If you want to experiment with it, and its incorrect handling of other
forms of XML is a problem, you can insert temporary entries in CATALOG to
make it the handler for .xml. I have included .jedit-scheme files so you
can duplicate what you see in the PDFs.
I hope you will continue experimenting and report any issues. I'd also
like to know if anyone has difficulties displaying the PDFs and their
"One can live magnificently in this world if one knows how to work and how
to love." -- Leo Tolstoy