lee said:
Edit the .xml file with a simple text editor (beware Microsoft tools!) to add the line: ?xml-stylesheet href="persistent.css" type="text/css"? You can experiment by adding new styles to 'persistent.css' (don't forget to save the file and reload your browser after adding rules). For example, add "p { display:block; text-indent: 3em }" and all of a sudden you will get distinct, indented paragraphs (and some non-paragraphs will also become distinct and indented). Add "teiHeader { display: none }" and all the Gutenberg legal cruft, together with the metadata which is typically only of interest to archivers, will disappear (it's still there, it's just not "in your face" anymore).
that is, in other words, if i tell it to use a stylesheet, and then go and create that stylesheet, it will work. :+) i knew that anyway, but i guess it's good to be reminded. ;+) *** jeroen said:
You can render XML, using XSLT + CSS in Firefox and IE, for a small demo, look at http://www.gutenberg.org/files/11335/11335-x/11335-x.xml.
yes, i should have mentioned jeroen's files work in firefox... (not in safari. but in firefox.)
Some have argued (with valid reasons) that the entire idea of TEI markup is broken, and have proposed systems in which the mark-up is separated from the text (stream of characters), in such a way that multiple, parallel systems of mark-up can exist. Think of a separate (part of a) file, saying characters 21 to 34 are italics, and so on. This may sound odd, but it is the way the old Macintosh wordprocessor MacWrite worked.
actually, that's the way the underlying _editfield_ of the (classic) mac operating system is structured. -bowerbird