Re: Texinfo translation error, texinfo_document domain

2022-11-01 Thread Gavin Smith
On Tue, Nov 01, 2022 at 12:47:17PM +0100, Patrice Dumas wrote: > On Tue, Nov 01, 2022 at 01:26:49AM +0100, Bruno Haible wrote: > > With this, most of the confusion should be gone. Thanks!! > > I tried to be clearer in the following commit (which may need to be > revised): >

Re: Texinfo translation error, texinfo_document domain

2022-11-01 Thread Patrice Dumas
On Tue, Nov 01, 2022 at 01:26:49AM +0100, Bruno Haible wrote: > With this, most of the confusion should be gone. Thanks!! I tried to be clearer in the following commit (which may need to be revised): https://git.savannah.gnu.org/cgit/texinfo.git/commit/?id=dd02e93ab701f7d7c9d2dcb9783241af9307afa5

Re: Texinfo translation error, texinfo_document domain

2022-10-31 Thread Bruno Haible
Patrice Dumas wrote: > Beware that this has changed in the forthcoming release in which UTF-8 > is considered as preferred. Cool! > > 3) "For maximum portability of Texinfo documents across the many different > > user > > environments in the world, we recommend sticking to 7-bit ASCII in the >

Re: Texinfo translation error, texinfo_document domain

2022-10-31 Thread Patrice Dumas
On Tue, Nov 01, 2022 at 12:47:22AM +0100, Bruno Haible wrote: > Hi Patrice, > > Patrice Dumas wrote: > > > My complaint was only about the (apparent / confused) need to use TeXinfo > > > syntax *for non-ASCII characters*. > > > > It should only be required for non-ASCII characters if the

Re: Texinfo translation error, texinfo_document domain

2022-10-31 Thread Bruno Haible
Hi Patrice, Patrice Dumas wrote: > > My complaint was only about the (apparent / confused) need to use TeXinfo > > syntax *for non-ASCII characters*. > > It should only be required for non-ASCII characters if the encoding of the > po file is us-ascii, for example in pt_BR.us-ascii.po the

Re: Texinfo translation error, texinfo_document domain

2022-10-30 Thread Patrice Dumas
On Sat, Oct 29, 2022 at 05:23:25PM +0200, Bruno Haible wrote: > My complaint was only about the (apparent / confused) need to use TeXinfo > syntax *for non-ASCII characters*. It should only be required for non-ASCII characters if the encoding of the po file is us-ascii, for example in

Re: Texinfo translation error, texinfo_document domain

2022-10-29 Thread 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

Re: Texinfo translation error, texinfo_document domain

2022-10-29 Thread Bruno Haible
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

Re: Texinfo translation error, texinfo_document domain

2022-10-29 Thread Gavin Smith
(trimming mailing list that you cannot post to if not subscribed) On Sat, Oct 29, 2022 at 04:39:32PM +0200, Bruno Haible wrote: > 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)

Re: Texinfo translation error, texinfo_document domain

2022-10-29 Thread Bruno Haible
Hi TeXinfo maintainers, This exchange is from the French translators mailing list: Jean-Charles Malahieude wrote: > Le 28/10/2022 à 19:42, Gavin Smith a écrit : > > In the translations for 'texinfo_document', fr.po: > > > > [...] > > #: tp/Texinfo/Transformations.pm:597 > > msgid " --- The