On 7/14/2025 4:14 PM, Pablo Rodriguez via ntg-context wrote:
On 7/14/25 10:09, Hans Hagen via ntg-context wrote:
Hi, […] % pablo will check the other languages and also the % kind of language tags we want to end up in the pdf
As far as I can remember, ConTeXt differs from ISO 639 with ancient Greek.
What ConTeXt considers `agr` is `grc` for ISO 639.
As for other languages, which is the file that has the complete list of languages and its tagging values?
That file never made it to a stable so it's on my machine but in the meantiem we can use llg files (language goodies) so we can for instance make lang-agr.llg return { name = "ancient greek", version = "1.00", comment = "Some old greek stuff", author = "Hans Hagen", options = { -- none so far }, tags = { pdf = "grc", } } which I can then load. We only need these for outliers. I'll add that possibility (assuming that you will check the relevant pdf tags). It can then in due time also replace the never really used language association feature.
Well, I can check that indirectly (not by Acrobat reading it aloud, but with https://ngpdf.com).
I happily leave that you you to test.
so, the question is 'selective' or 'everywhere'
I think the selective implementation would make more sense, especially when the selection could later include more items (as required/needed by users).
this is more a feature in the category of style and color and we can consider it also a bit natural to structure things like a description (alt) are more obscure and specific so these should be very selective (irr we have some wrapper that actually sets that property in pdf but it might not be hooked into tagging); i tend to see tagging completely decoupled from pdf and couldn't motivate myself to deal with it otherwise (just like in mkii we had decoupled backends which is why we always had kind of generic backend interfaces in context, not that it matters much today because dvi adn its special variants have gone out of scope)
BTW, besides alternative and actual text we need to implement `/E` (expansion of acronyms and abbreviations).
i remember seeing that and wondering why that was useful ... if acronyms are a problem then they should not be used; one can have a list of meanings anyway
If we already have `\definesynonyms`, it may be only adding proper taggig for it (even when no `\placelist[synonyms]` is invoked in the document).
this has nothing to do with tagging, there could be some rollover feature but those features have always been unreliable; it's in the same ballpark as this automatic url recognition it is not that hard to implement (although one has to render the meaning into something useful than is pure text, so basically like bookmarks) but there is no need to show off here for "the sake of it can be done" Hans ----------------------------------------------------------------- Hans Hagen | PRAGMA ADE Ridderstraat 27 | 8061 GH Hasselt | The Netherlands tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl -----------------------------------------------------------------