Re: normalization problem with `@anchor` targets

2025-03-11 Thread pertusus
On Tue, Mar 11, 2025 at 09:22:55PM +, Gavin Smith wrote: > On Tue, Mar 11, 2025 at 10:02:25AM +0100, pertu...@free.fr wrote: > > On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote: > > > Isn't that changing the purpose of --transliterate-file-names? > > > > > > Before: "texi2any --tra

Re: normalization problem with `@anchor` targets

2025-03-11 Thread Gavin Smith
On Tue, Mar 11, 2025 at 10:02:25AM +0100, pertu...@free.fr wrote: > On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote: > > Isn't that changing the purpose of --transliterate-file-names? > > > > Before: "texi2any --transliterate-file-names" means to output files > > with transliterated fi

Re: Texinfo documentation (gettextization)

2025-03-11 Thread Patrice Dumas
On Tue, Mar 11, 2025 at 10:30:18AM -0300, Jamenson Espindula wrote: > Hi all. > > I am working on the 7.1 edition of the Texinfo Manual (documentation > only) (gettextization of the strings). > > I am using "po4a" to generate a Portable Object (PO) file containing > the translated strings. Howeve

Re: Texinfo documentation (gettextization)

2025-03-11 Thread Gavin Smith
On Tue, Mar 11, 2025 at 10:30:18AM -0300, Jamenson Espindula wrote: > Hi all. > > I am working on the 7.1 edition of the Texinfo Manual (documentation > only) (gettextization of the strings). > > I am using "po4a" to generate a Portable Object (PO) file containing > the translated strings. Howeve

Re: use heading like sectioning commands with USE_NEXT_HEADING_FOR_LONE_NODE

2025-03-11 Thread pertusus
On Sun, Mar 02, 2025 at 09:48:26AM +, Gavin Smith wrote: > as if the following were done instead: > > @node Chapter > @chapter Chapter > > @subsubheading Topic > > @node Section > @section Section > > Here, the @subsubheading is just producing output (just like regular > parag

Re: normalization problem with `@anchor` targets

2025-03-11 Thread pertusus
On Sun, Mar 09, 2025 at 12:33:40PM +, Gavin Smith wrote: > > > > What I plan to do is: > > * name for links to external nodes is the default one independently of > > customization variables. If users ask for it, we can add to htmlxref > > hello type translit > > * name for redirecti

Re: normalization problem with `@anchor` targets

2025-03-11 Thread Gavin Smith
On Thu, Mar 06, 2025 at 10:17:30AM +0100, pertu...@free.fr wrote: > On Mon, Mar 03, 2025 at 08:11:29PM +, Gavin Smith wrote: > > > I don't reproduce that, I think that the issue is probably that a file > > > is read twice, rather than warnings being emitted twice per file. > > > Where/how/what

Texinfo documentation (gettextization)

2025-03-11 Thread Jamenson Espindula
Hi all. I am working on the 7.1 edition of the Texinfo Manual (documentation only) (gettextization of the strings). I am using "po4a" to generate a Portable Object (PO) file containing the translated strings. However, when I attempt to generate the PO file, there is an error: texinfo/translated/

Re: normalization problem with `@anchor` targets

2025-03-11 Thread pertusus
On Mon, Mar 10, 2025 at 07:28:54PM +, Gavin Smith wrote: > On Mon, Mar 10, 2025 at 02:33:40PM +0100, pertu...@free.fr wrote: > > On Sun, Mar 09, 2025 at 12:33:40PM +, Gavin Smith wrote: > > > > > > > > What I plan to do is: > > > > * name for links to external nodes is the default one inde