On Sun, Mar 09, 2025 at 10:05:52PM +0100, Patrice Dumas wrote:
> On Sun, Mar 09, 2025 at 05:18:28PM +0000, Gavin Smith wrote:
> > Updating the test results changed "erreur" to "error". This was for
> > the change that introduced _cache_node_names to bulk convert all the
> > node names in one go. I assumed this was because the documentlanguage
> > wasn't set at the time the node names were converted.
>
> Indeed, and I think that it is bad. Caching the converted node name is
> good, but it should be more dynamical, converted node names should be
> invalidated when documentlanguage changes. This is what is done in HTML
> for instance, and I think that it should be the same for Plaintext/Info.
I will try to work out how to do this but it seems like a unlikely case
to have @error{} in a node name. Can you think of any other commands
that would be documentlanguage dependent?
If @error{} is translated to "erreur" in a node name in a French Info
file, then it is not possible to link to that node from another
Info manual using @error{} in the node name unless that Info file
was also generated with French documentlanguage. You would have
to explicity "erreur" in the node name, not @error{}. (Again, this is
a very minor problem.)
