> Date: Thu, 6 Feb 2025 21:33:31 +0100
> From: pertu...@free.fr
> Cc: bug-texinfo@gnu.org
>
> On Thu, Feb 06, 2025 at 07:53:06PM +, Werner LEMBERG wrote:
> >
> > OK, so let me recapitulate: If I want to support Texinfo manuals with
> > HTML output that could have both `@anchor{o}` and `@ancho
[texinfo.tex 2025-02-06.22]
> Yes, it was a bug. I've committed a fix in version 2025-02-06.22,
> and rethought how the space trimming works for macro arguments and
> hopefully made the implementation in texinfo.tex a bit simpler.
> Thanks for the report.
Thanks for the quick fix!
> > > This
On Thu, Feb 06, 2025 at 08:42:38PM +, Gavin Smith wrote:
> Well, I checked the sources of Texinfo 4.13 and transliterate_file_names
> appears to be off by default:
>
> I checked Texinfo 5.2 (September 2013) and it was on by default for that
> release, with 'TRANSLITERATE_FILE_NAMES' => 1 in %d
On Thu, Feb 06, 2025 at 04:32:35PM +0100, Patrice Dumas wrote:
> On Thu, Feb 06, 2025 at 07:02:20AM +, Werner LEMBERG wrote:
> >
> > Interestingly, the translated strings were there from the very
> > beginning (i.e., since 2016) – I guess this has worked then, and later
> > on Texinfo was modi
On Thu, Feb 06, 2025 at 06:40:31AM +, Werner LEMBERG wrote:
> Looks like a bug, since we actually have something similar in
> LilyPond, and it works! My guess is that a combination of other
> Texinfo commands 'fixes' this...
Yes, it was a bug. I've committed a fix in version 2025-02-06.22,
a
On Thu, Feb 06, 2025 at 07:38:58PM +0100, pertu...@free.fr wrote:
> On Thu, Feb 06, 2025 at 05:19:17PM +, Gavin Smith wrote:
> > >
> > > To handle such cases, texi2any offers the
> > > --transliterate-file-names command line option. This option enables
> > > transliteration of node
Hello,
This was reported in Debian:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1012612
The pod2texi @direntry is
* pod2texi: (pod2texi)Invoking pod2texi.
But there is no pod2texi manual as it is included in the texinfo manual.
It could be
* pod2texi: (texinfo)Invoking pod2texi.
or
* p
On Thu, Feb 06, 2025 at 07:53:06PM +, Werner LEMBERG wrote:
>
> > To handle such cases, texi2any offers the
> > --transliterate-file-names command line option. [...]
> >
> > This is the default.
>
> Well, it is customary to always show the opposite option of the
> default in the `-
> To handle such cases, texi2any offers the
> --transliterate-file-names command line option. [...]
>
> This is the default.
Well, it is customary to always show the opposite option of the
default in the `--help` screen. For file name transliteration,
however, this is not the case: Th
On Thu, Feb 06, 2025 at 05:19:17PM +, Gavin Smith wrote:
> >
> > To handle such cases, texi2any offers the
> > --transliterate-file-names command line option. This option enables
> > transliteration of node names into ASCII characters for the purposes of
> > file name creation and
On Thu, Feb 06, 2025 at 05:02:30PM +, Werner LEMBERG wrote:
>
> I don't understand. How gets 'ö' mapped to 'o'? It is not NFC, but
> it can't be transliteration either, can it? I thought that the idea
> of transliteration is to map non-ASCII characters to ASCII strings
> unambiguously,
No,
On Thu, Feb 06, 2025 at 05:36:10PM +0100, pertu...@free.fr wrote:
> On Thu, Feb 06, 2025 at 04:05:36PM +, Werner LEMBERG wrote:
> >
> > > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/HTML-Xref-8_002dbit-Character-Expansion.html
> >
> > Thanks, but I don't think this is a vali
>> 'o' is definitely *not* the NFC of 'ö'! AFAICS, the above warning
>> message points to a bug in `texi2any`.
>
> Not the part about the regular rules, but about transliteration for file
> names:
>
> To handle such cases, texi2any offers the
> --transliterate-file-names command line o
On Thu, Feb 06, 2025 at 04:05:36PM +, Werner LEMBERG wrote:
>
> > https://www.gnu.org/software/texinfo/manual/texinfo/html_node/HTML-Xref-8_002dbit-Character-Expansion.html
>
> Thanks, but I don't think this is a valid explanation. 'o' is
> definitely *not* the NFC of 'ö'! AFAICS, the above
>> [texinfo.tex 2025-02-03.17]
>> [texi2any 7.2]
>>
>> ```
>> bogen.texinfo:17: warning: @anchor `Bögen' file Bogen.html for redirection
>> exists
>> bogen.texinfo:10: warning: conflict with @anchor `Bogen' redirection file
>> ```
>>
>> And indeed, a redirection file for 'Bögen' is missing, AFA
On Thu, Feb 06, 2025 at 03:46:41PM +, Werner LEMBERG wrote:
> > I would be quite surprised that this worked with texi2any since the
> > 5.0 release of GNU Texinfo. Maybe there was no error message, but
> > the result was probably unexpected. It could have worked with
> > makeinfo in C pre 5.0
>> Interestingly, the translated strings were there from the very
>> beginning (i.e., since 2016) – I guess this has worked then, and
>> later on Texinfo was modified somehow, and updating the PO file was
>> forgotten.
>
> I would be quite surprised that this worked with texi2any since the
> 5.0 r
On Thu, Feb 06, 2025 at 08:06:19AM +, Werner LEMBERG wrote:
>
> [texinfo.tex 2025-02-03.17]
> [texi2any 7.2]
>
> ```
> bogen.texinfo:17: warning: @anchor `Bögen' file Bogen.html for redirection
> exists
> bogen.texinfo:10: warning: conflict with @anchor `Bogen' redirection file
> ```
>
> An
On Thu, Feb 06, 2025 at 07:02:20AM +, Werner LEMBERG wrote:
>
> Interestingly, the translated strings were there from the very
> beginning (i.e., since 2016) – I guess this has worked then, and later
> on Texinfo was modified somehow, and updating the PO file was
> forgotten.
I would be quite
[texinfo.tex 2025-02-03.17]
[texi2any 7.2]
Consider the following input file `bogen.texinfo`. The German word
'Bögen' is the plural of 'Bogen' – in music, this is 'slur'
vs. 'slurs'.
```
\input texinfo
@node Top
@top Top
top
@node Foo
@chapter Foo
@anchor{Bogen}Bogen
@page
@node Bar
@chapt
20 matches
Mail list logo
