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 15:02:09 +0200 Message-ID: <83plygue5q.fsf@gnu.org> References: <91D00B9D-0057-4748-8C83-50E749FE3961@traductaire-libre.org> <835y0b29rk.fsf@gnu.org> <87r0iz3lx0.fsf@yahoo.com> <877ckqa6m5.fsf@yahoo.com> <71CE52FF-41E1-400F-8B2E-06570F6199EC@traductaire-libre.org> <88006F20-3C13-4E70-BD64-653D896F1DBD@traductaire-libre.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="19336"; 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 14:03:28 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 1rLjrE-0004m4-IE for ged-emacs-devel@m.gmane-mx.org; Fri, 05 Jan 2024 14:03:28 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rLjqJ-0004NF-6j; Fri, 05 Jan 2024 08:02:31 -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 1rLjqH-0004Ml-0l for emacs-devel@gnu.org; Fri, 05 Jan 2024 08:02:29 -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 1rLjqF-0002zo-Ru; Fri, 05 Jan 2024 08:02:27 -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=WJLe7O/mHhrmy7MtSbqaIzP+/b1/hpuaj4xO/PGSfVQ=; b=okYxO731NOLXOyB179yk AQaUnpmxkEFIuO4O1iNGDsrFgb8ZGb/GhwGqBUceEZ+84TGQFLvxAsf2YirzdD45kae1sMTUxj3UT 8Vw2P0VERRHwimGi1sMtCdHvsZh0mBkf+I7tdVw1Ko0CylN8bY9ZW6QcNU+H2XBEAguPZ7IRQ0R5c T3KtnlD1Spuqz+dxD/p/D9PcPWHKDtKJvUfVYVBLh1DVSs15/vqQS7EOHuxy445U2VqidgR2ZnpjH mdvWZypxXxrKQceZI5V/UTg+P8YZLU8XBPOjzOB/B/STOOhRSRPW7X5O3Dwja5tm9MYDk6GY/RGeh AABqQOPAx4ctRg==; In-Reply-To: <88006F20-3C13-4E70-BD64-653D896F1DBD@traductaire-libre.org> (message from Jean-Christophe Helary on Fri, 05 Jan 2024 08:20:51 +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:314566 Archived-At: > Date: Fri, 05 Jan 2024 08:20:51 +0000 > From: Jean-Christophe Helary > Cc: Po Lu , Eli Zaretskii , Vincent Belaïche , emacs-devel@gnu.org, rms@gnu.org > > * translation and proofreading/validation > > 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. > * version numbers > > We’d need to have somewhere in the translation the base commit number > of the English original, so that when the file is in > emacs/doc/lang/[lg] people know how recent the document is. You assume the translations will be mostly outdated. I'm not so sure, but if that indeed happens, we'll think of something. I don't think this is a hard problem to solve. > * reduction of redundant work > > To make sure people don’t translate documents that are already worked > on, we’d need a matrix where the files are assigned, and willing > contributors could check the matrix and would also announce their > willingness to work on such and such chapter here (pretty much like the > W3C does for its translation process), for ex: I'd worry about this when we have more than a couple translations. Also, the translation matrix is maintained by TP, and I'm not sure we should have our own copy; we could simply rely on TP in this aspect. > * technical requirements > > An extra step would be a technical requirement that the file was > properly checked for spelling/grammar with the tools that Emacs > provides and that it properly builds on the various systems where it > was handled, to ensure that the lead does not have to do too much grunt > work on the deliverables. Every piece of documentation submitted to Emacs is expected to be spell-checked, and Emacs supports spell-checking of every language for which the available spell-checkers have dictionaries. So I don't see any special problem here. > * information > > We’d need a readme file to make all that explicit. Yes. Feel free to submit it. > * publication > > 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. 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.