My feedback on PGTEI is too long for email, so I posted it here: http://Classicosm.com/xml/feedbackonpgtei.html Sections include: PGTEI Vocabulary PGTEI Examples PGTEI Documentation Generated HTML Default CSS Generated PDF Generated Text PGText to PGTEI I also put together a (rough draft!) Quick Reference table, including a comparison to XHTML http://Classicosm.com/xml/pgteiquickreference.html To help explore alternatives to TEI, I critique a side-by-side comparison to a dedicated vocabulary for plays: http://Classicosm.com/xml/tei-vs-play.html Feedback welcome!!! -- Cheers, Scott S. Lawton http://Classicosm.com/ - Classic Books http://ProductArchitect.com/ - consulting
Scott Lawton wrote:
Section 18: I strongly recommend omitting the requirement that TEX and NROFF characters must be escaped. (As far as I can tell, that's not part of TEI.) It may well be a useful optional feature; perhaps it could be turned on by including a specific processing instruction.
That limitation will go away once XSLT can handle entities or until I rewrite the XSLT transform into perl.
quote is used in an example but apparently isn't part of TEI Lite (it's not in link_outAppendix A). What's the story?
<quote> is to be used when you quote some written source, <q> when you quote direct speech.
q: in cases where the quotation marks don't balance, it may be difficult to automatically convert quotation marks to the appropriate q.../q form, and time consuming to manually proof. Accordingly, I suggest this step be left as optional.
It is optional. Using <q> will debug your quotes automatically, something that is near impossible to program any other way. Using <q> will also get the most pretty quote signs the output format can display.
langUsage: I suggest the standard should be to omit the content of the tag (e.g. "British", which is probably more useful as "British English" or "English (British)"). This information should be generated to ensure consistency. (They appear in the generated PGTEI and in alice.tei, but not in lmiss.tei.)
You have to include only the languages you actually use in the text. The converter includes some more because it is easier to delete than to add and if you declare too many it doesn't hurt.
pgHeader looks like it's contains information that should be described in teiHeader (though I'm new to TEI so may be wrong). alice.tei and lmiss.tei both contain pgHeader; the generated PGTEI does not. PGTEI Examples
pgHeader is a hack that can be removed once we agree on how to insert all that information in the teiHeader.
Having separate index tags for TOC, PDF and PDB strikes me as unnecessary and prone to error. Shouldn't the TOC one suffice for all?
Some formats have limitations. eg. PamlDoc bookmarks have a maximum of 16 characters. PDF bookmarks have to use iso-8859-1 chars. Moreover you don't always want the full <head> to appear in the contents.
In the documentation, why is "Versprich mir, Heinrich" repeated in the output, the second time in white?
Because there is no other way to properly indent a continuation line in HTML. If you can figure out one (that does not use tables or javascript!) I'd like to hear.
Are the heuristics from things like GutenMark included? That would seem to be quite valuable.
No. Its just a quick perl hack. Better take GutenMark and make it output TEI instead of HTML. But that is a job for the author of GutenMark. Better bug him :-) -- Marcello Perathoner webmaster@gutenberg.org
participants (2)
-
Marcello Perathoner -
Scott Lawton