On Fri, Aug 04, 2023 at 04:06:47PM -0700, Raymond Toy wrote:
> With texinfo 7.0.2 (which comes with Fedora 38), I get warnings like:
>
> |warning: @ref node name should not contain `:' |
>
> The offending ref is “@ref{ext:encapsulate}”, and corresponding anchor is
> “ext:encapsulate”. I didn’t se
>>> In the particular manual, there are lots of anchors that contain
>>> colons but most of them are not referenced via @ref. (For whatever
>>> reason.)
>>
>> How curious!
>>
> Yeah, I don't really know the history of this. It's a document that
> was, possibly, in Scribe, that was later converte
On 8/4/23 4:56 PM, Gavin Smith wrote:
On Fri, Aug 04, 2023 at 04:06:47PM -0700, Raymond Toy wrote:
With texinfo 7.0.2 (which comes with Fedora 38), I get warnings like:
|warning: @ref node name should not contain `:' |
The offending ref is “@ref{ext:encapsulate}”, and corresponding anchor is
On Fri, Aug 04, 2023 at 04:06:47PM -0700, Raymond Toy wrote:
> With texinfo 7.0.2 (which comes with Fedora 38), I get warnings like:
>
> |warning: @ref node name should not contain `:' |
>
> The offending ref is “@ref{ext:encapsulate}”, and corresponding anchor is
> “ext:encapsulate”. I didn’t se
On Tue, Jul 11, 2023 at 01:49:32PM +0100, Gavin Smith wrote:
> On Thu, Jun 22, 2023 at 06:07:20PM +0200, Bruno Haible wrote:
> It might be a good idea to show some of the warnings by default but
> not all of them. I agree that the warning you identified as the essential
> one.
>
> If I disable th
With texinfo 7.0.2 (which comes with Fedora 38), I get warnings like:
|warning: @ref node name should not contain `:' |
The offending ref is “@ref{ext:encapsulate}”, and corresponding anchor
is “ext:encapsulate”. I didn’t see anything in the manual about this
constraint, but I didn’t look too
On Fri, Aug 04, 2023 at 01:16:27PM +0100, Gavin Smith wrote:
> On Fri, Aug 04, 2023 at 11:15:56AM +0100, Gavin Smith wrote:
> > > There is already code for that in Texinfo::Transformations,
> > > new_master_menu
> > > creates a detailmenu, and regenerate_master_menu regenerate the Top node
> > > m
On Fri, Aug 04, 2023 at 11:15:56AM +0100, Gavin Smith wrote:
> > There is already code for that in Texinfo::Transformations, new_master_menu
> > creates a detailmenu, and regenerate_master_menu regenerate the Top node
> > master menu, replacing the first detailmenu in Top node menus or
> > appendin
> It was the functional change. I re-reverted, fixed, merged the two
> changes in one commit and reapplied in
> 1a21355dd1b50a796e35d9fc55c76b94424b126e
It works now, thanks.
Werner
On Fri, Aug 04, 2023 at 08:25:22AM +0200, Patrice Dumas wrote:
> On Thu, Aug 03, 2023 at 11:17:06PM +0100, Gavin Smith wrote:
> > I've changed texinfo.texi not to use explicit @menu blocks in most cases,
> > using the new @nodedescription command for the information that was
> > previously in the @
On Fri, Aug 04, 2023 at 11:33:38AM +0200, Patrice Dumas wrote:
> > Perhaps it will be easier to split this change into a functional change
> > and a change just to move code around. Then it will be more possible to
> > understand which part of it caused the problem.
>
> It was the functional chan
On Fri, Aug 04, 2023 at 10:03:22AM +0100, Gavin Smith wrote:
> On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
> > After a standard compilation and installation on my openSUSE GNU/Linux
> > box I see latin1-encoded strings on my UTF-8 console.
>
> > Bisecting leads to the following
On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
> After a standard compilation and installation on my openSUSE GNU/Linux
> box I see latin1-encoded strings on my UTF-8 console.
> Bisecting leads to the following commit:
>
> ```
> afca9f95f8dcca047ad9637b1abe9e4117111e8c is the fir
Hello,
Thanks for the report and analysis. It is due to a missing shift of
set_translations_encoding argument...
Gavin reverted it, I will reapply with the fix.
On Fri, Aug 04, 2023 at 08:06:44AM +, Werner LEMBERG wrote:
>
> [1bc5824f2c4aa1d633d62210f1bc7daa210f620c]
>
> [LANG=en_US.UTF-8
[1bc5824f2c4aa1d633d62210f1bc7daa210f620c]
[LANG=en_US.UTF-8
LANGUAGE=de]
[perl v5.26.1]
After a standard compilation and installation on my openSUSE GNU/Linux
box I see latin1-encoded strings on my UTF-8 console.
```
> makeinfo --help
Aufruf: makeinfo [OPTION]⦠TEXINFO-DATEIâ¦
Ãbersetzt T
15 matches
Mail list logo
