Just to react to this comment : I fully agree that a translation should keep exactly the same anchor & node names. So that switching the language is just a matter of replacing en by de, fr, ru, jp etc.
Emacs info viewer inserts the word « see », even in French, before links, fortunately « see » does not mean anything wrong in French, but still, this is a hassle. I wonder why this was done this way. Also, a module like Calc finds function / command doc in the manual relying on some search, so this way of doing should be generalized, and made language independant if for other module than Calc people want to proceed this way, and if they want have translation of the manual. V. ________________________________ De : Gavin Smith <gavinsmith0...@gmail.com> Envoyé : jeudi 11 janvier 2024 21:37 À : Eli Zaretskii <e...@gnu.org> Cc : pertu...@free.fr <pertu...@free.fr>; jean.christophe.hel...@traductaire-libre.org <jean.christophe.hel...@traductaire-libre.org>; stefankan...@gmail.com <stefankan...@gmail.com>; vincent....@hotmail.fr <vincent....@hotmail.fr>; emacs-de...@gnu.org <emacs-de...@gnu.org>; r...@gnu.org <r...@gnu.org>; help-texinfo@gnu.org <help-texinfo@gnu.org> Objet : Re: @dircategory (Re: Translating Emacs manuals is of strategic importance) On Thu, Jan 11, 2024 at 10:03:29PM +0200, Eli Zaretskii wrote: > > From: Gavin Smith <gavinsmith0...@gmail.com> > > Date: Thu, 11 Jan 2024 19:46:30 +0000 > > Cc: pertu...@free.fr, jean.christophe.hel...@traductaire-libre.org, > > stefankan...@gmail.com, vincent....@hotmail.fr, emacs-de...@gnu.org, > > r...@gnu.org, help-texinfo@gnu.org > > > > > > 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.
