Languages on HTML interface elements

16 views
Skip to first unread message

Rob Beezer

unread,
Sep 2, 2026, 6:05:24 PMSep 2
to prete...@googlegroups.com
Suppose you write a text in French and you want to use the GFDL license (OK, a
bit contrived, I know).

The license should not be changed/edited except in very precise ways, the
license says that. The French quote marks you would get could be considered a
violation of the license. Stay with me. So, as suggested very recently, you
mark the GFDL appendix as in the "en-US" language. Good. English quote marks.

But now many of the interface elements (various buttons, navigation, tool tips,
etc) are in English when you open the GFDL appendix page, and not in French like
the whole rest of the document/pages.

I guess we can debate what should be the best behavior, *in this instance*, but
I really do not plan to change anything right now.

Instead, I think it would be better if this was one more argument to split out
translating things like "Chapter" and "Theorem" from things like "Previous" and
"Calculator". The former could stay in XSL (for content in all conversions) and
the latter could be a Javascript/CSS thing for HTML formats.

Rob

Andrew Scholer

unread,
Sep 5, 2026, 2:38:03 PM (13 days ago) Sep 5
to prete...@googlegroups.com
100% agree that translating content strings that are universal across all formats should be in XSL while HTML specific UI elements should be translated in JS.

For the hypothetical, if the goal is to leave the text as is, wouldn't it be better to use the literal characters in the license text instead of turning " into <q> and then trying to force it to render in the right language?


--
You received this message because you are subscribed to the Google Groups "PreTeXt development" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-dev...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-dev/MTAwMDAzSG9KbGRoS1M.1788386721%40pnsh.

Rob Beezer

unread,
Sep 5, 2026, 5:19:03 PM (13 days ago) Sep 5
to prete...@googlegroups.com
On 9/5/26 11:37, Andrew Scholer wrote:
> wouldn't it be better to use the literal characters in the license text
You would think so, wouldn't you? But quotes in LaTeX are goofy, and the ASCII
" is going to be a right curly quote when typeset, whether or not it begins or
ends the quoted phrase. That was some of the motivation for #q, which was one
of the earliest intra-sentence markup we developed.

I think a fully marked up GFDL and a "en-US" tag might be the path of least
resistance, such is the state of all these markup languages we deal with. Be
glad we started *another* markup language?

Rob


Reply all
Reply to author
Forward
0 new messages