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: Infrastructure proposal (Re: Translating Emacs manuals is of strategic importance) Date: Fri, 05 Jan 2024 16:30:51 +0200 Message-ID: <83cyufvomc.fsf@gnu.org> References: <87r0iz3lx0.fsf@yahoo.com> <877ckqa6m5.fsf@yahoo.com> <71CE52FF-41E1-400F-8B2E-06570F6199EC@traductaire-libre.org> <88006F20-3C13-4E70-BD64-653D896F1DBD@traductaire-libre.org> <83plygue5q.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="4238"; mail-complaints-to="usenet@ciao.gmane.io" Cc: stefankangas@gmail.com, luangruo@yahoo.com, vincent.b.1@hotmail.fr, emacs-devel@gnu.org, rms@gnu.org To: Jean-Christophe Helary Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane-mx.org@gnu.org Fri Jan 05 15:32:29 2024 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 1rLlFM-0000ur-CL for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Jan 2024 15:32:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rLlEH-0002DH-HF; Fri, 05 Jan 2024 09:31:21 -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 1rLlE8-0002C8-AV for emacs-devel@gnu.org; Fri, 05 Jan 2024 09:31:12 -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 1rLlE6-00025F-2d; Fri, 05 Jan 2024 09:31:10 -0500 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=gnu.org; s=fencepost-gnu-org; h=MIME-version:References:Subject:In-Reply-To:To:From: Date; bh=vDgrdM4OAoWkoxyt1XurXYl+J5lbQldm4OzTsMiHh4A=; b=CcIjNp7QYU1sv8N4mWkW 1YglPd4ArZyHwe+f2SVrlGYO+FUxflZ3t/bzUDNIjE9+AnNZFmJf0pPWuJ5mgcJgLWCeLio0YVvQK ZCr25T0ZT5MVbCSidcAGgy04HwAWzIdiBUN8Nq8TECh917wZGmIPoF3m3nmCjR90323YY0azKpUHL dVC3uMvqS2GF8LFMPmq3b7TEO2dgxLiiymAzekU2rqN8unfVIGVx9C+ArNqr8HITpnkL2Wc+9IGwy IY9cezxdJcGoZ3r6TYB3NkT8JHDmdqDzRUekiYi85ie+CainRVkYtCGnvqn3spnp66mcbcqP71gT4 7Jdie8Wlw5hIwA==; In-Reply-To: (message from Jean-Christophe Helary on Fri, 05 Jan 2024 14:07:12 +0000) 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:314570 Archived-At: > Date: Fri, 05 Jan 2024 14:07:12 +0000 > From: Jean-Christophe Helary > Cc: Stefan Kangas , Po Lu , Vincent Belaïche , emacs-devel@gnu.org, rms@gnu.org > > >> Now that we have emacs/doc/lang/[lg], what do you think of having > >> something like emacs/doc/lang/drafts/[lg], where people would commit > >> draughts to be proofread/validated? > > > > I prefer to use special Git branches for that. This is how we handle > > any changes that are not yet ready to be landed on the master branch, > > and I see no reason to invent special conventions for manual > > translations. > > What would be the best way to name the branch? It would be nice to have > a standard way of naming branches that include documents that require > proofreading, because it is less easy to find a branch than to find a > folder. I don't care much about the names of these branches. We could have all of them under origin/translations/, for example, if that would help. The important thing is that the people who contribute know the name and/or publish it when they need others to take a look. Not everything needs to be codified in advance and rigidly. > >> For each emacs release, the texi files would be compiled into > >> appropriate formats (minimally info) so that people can easily install > >> them. > > > > That's part of the release procedure, so there's no reason to consider > > it specially. > > Maybe, but it’s a good thing that it is on paper so that translators > understand how their work is handled. We can’t expect translators to > understand the fine aspects of the Emacs release process. It isn't a job for translators, it's a job for the Emacs maintainers. And it's already "on paper": see admin/make-tarball.txt. > > We already have translated reference cards, for example > > (see etc/refcards/ in the Emacs tree), from which we generate PDF when > > a release tarball is prepared. > > Do you suggest that the manuals could also be published as PDF? No, I just gave an example how portions of the documentation that are not in English are organically incorporated into the Emacs release process.