I use jEdit with the XML plugin installed. I find it helps me find
problems fairly easily.
Daniel
On 09/20/2012 05:26 PM, Greg Hellings wrote:
There are a number of pieces of software out there that will
pretty-print the XML for you, with indenting and whatnot. Overly
indented for what you wou
I seldomly create OSIS from scratch, but usually create an USFM text, which I
then import with known tools.
This means that all corrections happen not in OSIS, which indeed can become a
bit of a nightmare, but in USFM, which is easy and nice.
Most Bible translation projects also appreciate rec
There are a number of pieces of software out there that will
pretty-print the XML for you, with indenting and whatnot. Overly
indented for what you would want in production but decent for
debugging mismatching nesting and the like.
For example, 'xmllint --format' will properly indent the file, etc
Andrew Thule writes:
> One of my least favour things is finding mismatched tags in OSIS.xml files
> Has anyone successfully climbed this summit?
XEmacs and xml-mode (and font-lock-mode). M-C-f and M-C-b execute
sgml-forward-element and -backward-. That is, sitting at the beginning
of , M-C-f (
One of my least favour things is finding mismatched tags in OSIS.xml
files (and solving other related xmllint/osis2mod errors); because I
don't currently have an efficient way of doing it.
My methodology is nearly all the command line. I have very little
reliance on gui based tools. I edit in vi,
