Clarification: English is the default default language. That is, the
fallback language is set in the stylesheet parameter
l10n.gentext.default.language, which is set to 'en' by default in the
distribution.
Bob Stayton
Sagehill Enterprises
b...@sagehill.net
On 11/30/2017 9:19 PM, Bob Stayton
Regarding the XSLT language code, the template for quote eventually
calls the utility template named l10n.language, which uses the current
element () as the context and scans ancestor-or-self for the
closest xml:lang attribute to determine the language, and falling back
to the default language
Thanks to you and Ron for your ideas about how to deal with this issue.
Wow, I didn't even know that the quote element even existed. Both
solutions are interesting:
richard: I notice that QUOTE will surround the sentence with span tags and
then presumably insert the language-appropriate version
I use entities to separate open an close single and double quotes, 's
etc. Conversion can be of 'straight' quotes can done to about the 90%
level by looking at the environment of 'straight' quotes in a regex
search throughout a set of files.
e.g.
On
Hi Robert,
I avoid the issue entirely by using the DocBook element.
The element gives you language appropriate quotation marks, and it will
also handle quotes within quotes, which is a nice touch.
I don’t know of any automated smart quote processing in the DocBook stylesheets
(in fact, I’m
Up to now I've avoided dealing with the issue of smart quotes (curly
quotes) by simply dealing with straight quotes in my docbook source.
About 75% of my source comes from MS Word, and I then find some way to
paste or convert into Docbook XML.
Another 25% comes from .txt or from content I
