unknown
1970-01-01 00:00:00 UTC
Thanks for that.
routine which currently converts the input to XML-safe strings to replace the
entities back to something that LaTeX can grok. Most of the work is to compile
a table that defines the required translations.
regards,
Markus
There's something else. You may recall some time ago all the trouble
taken to ensure entities such as — and & are preserved in
database reference entries and subsequently then preserved throughout
DocBook processing. Many of my references include entities in document
titles. Well, those entities are now appearing in the bibtex entries
created by runbib. As you noted, the raw ampersands choke LaTeX. Is
there any way of converting those xml-safe entities to LaTeX equivalents
as runbib exports them? In the case of '—' that would be '---'.
I don't think this is too hard. I'll have to adapt the character replacementtaken to ensure entities such as — and & are preserved in
database reference entries and subsequently then preserved throughout
DocBook processing. Many of my references include entities in document
titles. Well, those entities are now appearing in the bibtex entries
created by runbib. As you noted, the raw ampersands choke LaTeX. Is
there any way of converting those xml-safe entities to LaTeX equivalents
as runbib exports them? In the case of '—' that would be '---'.
routine which currently converts the input to XML-safe strings to replace the
entities back to something that LaTeX can grok. Most of the work is to compile
a table that defines the required translations.
regards,
Markus
--
Markus Hoenicka
***@cats.de
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de
Markus Hoenicka
***@cats.de
(Spam-protected email: replace the quadrupeds with "mhoenicka")
http://www.mhoenicka.de