On Thu, Jan 11, 2024 at 10:03:29PM +0200, Eli Zaretskii wrote: > > From: Gavin Smith <[email protected]> > > Date: Thu, 11 Jan 2024 19:46:30 +0000 > > Cc: [email protected], [email protected], > > [email protected], [email protected], [email protected], > > [email protected], [email protected] > > > > > > Although it's not ideal, using cross-reference labels may be the best > > > > solution. It would be a temporary solution if the targetted manual > > > > obtained an English translation later. Once that is the case, the > > > > first manual could be updated with the translated node name, so > > > > "*note Choisir Tampon:(emacs)Select Buffer." becomes > > > > "*note (emacs)Choisir Tampon::", eliminating the English. > > > > > > You mean, the Info reader should do that? It would mean that the Info > > > reader will need to access all its cross-manual links in a node before > > > it can display the node with or without the English node names. > > > > I meant that the maintainers of the translated document would update it. > > That'd mean whenever a new translated manual is released, the > translators will need to update all the manuals that cross-reference > to the newly-released one, and users will then need to update their > manuals. Should be possible, of course, but quite a hassle, IMO.
Well, they wouldn't *need* to update the manuals. The links to the English node names would still work as long as the translated manual has the @anchor commands with those node names.
