On Tue, Apr 14, 2026 at 02:41:41PM +0300, Eli Zaretskii wrote: > > In texi2any and Texinfo TeX, to select the right translated strings in > > output and to select the right lang attributes in output formats. > > But this is only possible if there are *.po files for the script, > right? Is it likely that there will be such a .po file?
It is already the case, for serbian, we have translations both in cyrillic (for texi2any) and in latin scripts (for Texinfo TeX). But we do not need to have an actual case to design a feature for the long-term of the Texinfo language. > > More generally, it is probably useful when translating manuals from > > one language + script to another for the process of translation > > itself when there are multiple possible scripts for a language. > > I'm not sure I understand how this would be useful in that case. The > source manual is already written, so whatever script it used is > "stated" de-facto by the document itself, no? Or what am I missing? If translation is always from english, it is mainly for the destination manual. If the source is not english, it could also be relevant for the source manual. If there are multiple scripts, a translation framework such as po4a needs to distinguish the script among the destination manuals and emit the correct commands. For example, if the destination language is sr-Latn, the output should not be in the same po files as sr (currently, in sr@latin po files as far as I can tell), and the po4a parser used should output the right @-commands in the result file, for example @documentlanguage sr @documentscript Latn and not simply @documentlanguage sr -- Pat
