From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Where to contribute manual translations ? Date: Thu, 28 Dec 2023 18:04:48 +0200 Message-ID: <83jzoy71pb.fsf@gnu.org> References: <837cky94rm.fsf@gnu.org> <83v88i77ui.fsf@gnu.org> Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="19169"; mail-complaints-to="usenet@ciao.gmane.io" Cc: vincent.b.1@hotmail.fr, emacs-devel@gnu.org To: Stefan Kangas Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Thu Dec 28 17:05:16 2023 Return-path: Envelope-to: ged-emacs-devel@m.gmane-mx.org Original-Received: from lists.gnu.org ([209.51.188.17]) by ciao.gmane.io with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1rIssm-0004oD-6I for ged-emacs-devel@m.gmane-mx.org; Thu, 28 Dec 2023 17:05:16 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rIssb-0000pe-BJ; Thu, 28 Dec 2023 11:05:05 -0500 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rIssZ-0000mu-DM for emacs-devel@gnu.org; Thu, 28 Dec 2023 11:05:03 -0500 Original-Received: from fencepost.gnu.org ([2001:470:142:3::e]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rIssY-0006eU-Fq; Thu, 28 Dec 2023 11:05:02 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=References:Subject:In-Reply-To:To:From:Date: mime-version; bh=SzCGCJn94iTR2dCZonVusLdQkBlviHeZO26PvxuKFAo=; b=W+9GlRXib0dN WujSRiuxjgEGRQdBlQCf1uK0eb3syqruurLoBiCh0Udru0EI/Q9AeUAFBdp7hpB7CCvYWnA1iRS49 jKN8LbFbQbvgobAA8SFEG+nYVPV9cg9yvbidrPdRwd3rwzwKonlUY7YOsOs+JvjaQmgtMtKp7qh/D HdlOeB3M4jd2aKCfJxNdPFCIh6gc6lJDzNCXvc0uoQbPf73NN5O4hoEF5KvyyATyfFjr+YVbP7wYk xhEadp0TY+/eaTx1oClET9yj66OvOZKP8bq0bGElRhSL/a0TCnsiEp/1G4F6eO4lX2QEswccY+DLW 6W+M8Bx8LcVnptF+Zq33xg==; In-Reply-To: (message from Stefan Kangas on Thu, 28 Dec 2023 07:32:08 -0800) X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.emacs.devel:314286 Archived-At: > From: Stefan Kangas > 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.