Re: @dircategory (Re: Translating Emacs manuals is of strategic importance)

[Eli Zaretskii <eliz@gnu.org>]

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Sat, 6 Jan 2024 03:57:24 -0800
> Cc: vincent.b.1@hotmail.fr, emacs-devel@gnu.org, rms@gnu.org, 
> 	help-texinfo@gnu.org
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> >> If that’s the case, what about using “Translated manuals” for now,
> >> since the number of translated manuals is very low?
> >
> > I'd say the other way around: as long as we have very few
> > translations, keeping them together with the English version is
> > better.
> 
> I'm concerned that they'd get in the way, even if there are only few of
> them.

How can a couple of manuals get in the way?  I think they will be
hardly even noticed.

> How about using something like `Info-streamline-headings' for this:
> 
> - Put manuals under "Translated manuals" for English locales.
> 
> - Move those relevant to the current locale to "Emacs".
> 
> I'd probably take it a step further and completely hide translations (by
> default at least) outside of relevant locales.  We already do basically
> that for the tutorial.

We could do something like that, indeed, but I tend to think this is a
matter of user preferences rather than the locale.  Why would we
assume that only users running in a French locale want to be able to
read the French translation?

In any case, my proposal was to do something simple as the first step.
IMO we should postpone more complicated stuff, like user preferences
and locale-dependent magic to later, when the way of handling
translations of the manuals is based on discussions and decisions that
are not private to Emacs.  I feel we are putting the cart ahead of the
horses by designing solutions for this at this time.