Re: Texinfo translation error, texinfo_document domain

[Gavin Smith]

On Sat, Oct 29, 2022 at 05:23:25PM +0200, Bruno Haible wrote:
> Hi Gavin,
> 
> > > It sounds wrong to expect translators to use TeXinfo syntax for
> > > non-ASCII characters, for three reasons:
> > > 
> > > 1) Translator tools support the common (state-free) charset encodings,
> > >    namely UTF-8, ISO-8859-*, and so on. Not TeX with \, not TeXinfo with
> > >    @, not ISO-2022-*. PO files that expect TeXinfo syntax deny translators
> > >    from the ability to use their native input methods.
> > > 
> > >    I guess this is the reason why you don't see Chinese, Hindi, 
> > > Vietnamese,
> > >    Armenian, etc. translations for texinfo/po_document/*.po.
> > 
> > UTF-8 is allowed and works.  See e.g. po_document/uk.po.
> 
> Good, that's better than I thought. Then, why are there no Chinese, Hindi,
> etc. translations of this POT file? Karl [1] suggested that "there is
> confusion in both directions among the translators". Maybe it's as simple
> as sending a mail to these translation teams and clarifying to them that they
> can submit normal UTF-8 PO files for this domain?

I'd assumed because there was little interest in these language
communities for providing translations.  You can see how much
activity there is in different teams at
https://translationproject.org/team/index.html.  Now if everything
was being translated except for Texinfo, that might indicate a problem
on our end.