emacs-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Where to contribute manual translations ?


From: Eli Zaretskii
Subject: Re: Where to contribute manual translations ?
Date: Thu, 28 Dec 2023 18:04:48 +0200

> From: Stefan Kangas <stefankangas@gmail.com>
> Date: Thu, 28 Dec 2023 07:32:08 -0800
> Cc: emacs-devel@gnu.org
> 
> > Stefan, do you think doc/LANG, where LANG is a language name, is okay
> > for keeping translations of manuals to language LANG?
> 
> I'd probably prefer to keep them in a subdirectory like
> 
>     doc/translations/<...>
> 
> My main concern with adding new files [with similar names] is ease of
> autocompleting, both inside the doc/ directory, and when using
> `project-find-file' together with flexible matching styles.
> 
> For the latter case especially, I find that having duplicate file names
> under version control often causes conflicts.  Thus, I'd rather we avoid
> that if possible.
> 
> I'd suggest something like
> 
>     doc/translations/$SECTION/$LANG-$MANUAL.texi
> 
> so that we end up with
> 
>     doc/translations/misc/fr-ses.texi
> 
> .
> 
> I also considered something like
> 
>     doc/translations/$LANG/$SECTION/$MANUAL
> 
> so that in this case we end up with
> 
>     doc/translations/fr/misc/ses.texi
> 
> but that has the same problem that we end up with duplicate file names.
> It's also perhaps somewhat overblown given that we only expect to have a
> very small number of translated manuals for the foreseeable future.[1]
> 
> WDYT?

If we are going to call the source files of the translations of
manuals as MANUAL-LANG.texi, then we don't need a separate directory,
we could instead put them all in the same directories.  That is, we
could have doc/misc/ses.texi and doc/mist/ses-fr.texi.  This would be
simpler, I think?

> > Another question is what would be the file name of the corresponding
> > Info file, and in what directory should it be generated by makeinfo?
> 
> I'm less concerned with autocompleting in this directory, and it's not
> under version control.  So it should be easier to change the structure
> later, I think.
> 
> Perhaps for now something like
> 
>     info/$LANG/$MANUAL
> 
> is okay?

Why not info/$MANUAL-$LANG.info ?

And I think we should look at what other projects do, if we find such
projects.



reply via email to

[Prev in Thread] Current Thread [Next in Thread]