You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The TEI format is very flexible and is customized in various ways by different editors and for different uses. Right now, the TEI writer does not seem to have a lot of customization available.
My use case is to produce input suitable for the Lodel CMS. I can easily write a custom XML template to get the right structure for metadata but the body text produced by Pandoc produces markup which differs from the expected schema. For instance <p> and <head> may require attributes but the TEI writer does not seem to be able to produce them. I guess that part of the work could be achieved with filters, but precise tag production seems to require adjustments to the writer.
What would be the best way to adapt the TEI writer to the specifics of a particular publisher ? Defining a custom writer seems to be a lot of duplicate work. A possibility would be to extend the existing writer and use writer-specific variables for customization, but it requires some thought.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello,
The TEI format is very flexible and is customized in various ways by different editors and for different uses. Right now, the TEI writer does not seem to have a lot of customization available.
My use case is to produce input suitable for the Lodel CMS. I can easily write a custom XML template to get the right structure for metadata but the body text produced by Pandoc produces markup which differs from the expected schema. For instance
<p>
and<head>
may require attributes but the TEI writer does not seem to be able to produce them. I guess that part of the work could be achieved with filters, but precise tag production seems to require adjustments to the writer.What would be the best way to adapt the TEI writer to the specifics of a particular publisher ? Defining a custom writer seems to be a lot of duplicate work. A possibility would be to extend the existing writer and use writer-specific variables for customization, but it requires some thought.
Thanks for any feedback !
Beta Was this translation helpful? Give feedback.
All reactions