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: Translation of manuals (was: SES manual French translation) Date: Tue, 02 Jan 2024 15:35:39 +0200 Message-ID: <83ttnvzwlw.fsf@gnu.org> References: <831qb45fog.fsf@gnu.org> <50A7AFED-DA37-4212-9ED1-7D906C34B6B2@traductaire-libre.org> <83o7e51bws.fsf@gnu.org> <83mstp11sz.fsf@gnu.org> <91D00B9D-0057-4748-8C83-50E749FE3961@traductaire-libre.org> <835y0b29rk.fsf@gnu.org> <8A22A273-11F5-449C-A2A4-2E8C68CCF1FE@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="34266"; mail-complaints-to="usenet@ciao.gmane.io" Cc: vincent.b.1@hotmail.fr, stefankangas@gmail.com, 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 Tue Jan 02 14:37:05 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 1rKex5-0008bs-6u for ged-emacs-devel@m.gmane-mx.org; Tue, 02 Jan 2024 14:37:03 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rKewI-0006Nv-Rf; Tue, 02 Jan 2024 08:36:14 -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 1rKewC-0006Lr-Fz for emacs-devel@gnu.org; Tue, 02 Jan 2024 08:36:08 -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 1rKewB-0001rR-2t; Tue, 02 Jan 2024 08:36:07 -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=6YehlLi7xUwCro2hWHUAO6YwpyCgU09g9PSnFFuD8vQ=; b=ZnIcRwhE/4WaFSjo/Wre U1Nfn0RwX4RDagMVV9dbN8E7UV3OE6uF+tfWAFWaVrsdJMnEsYBre3zVLWFR7Ess5fT82vZbQc0Yr fcrUuQdy9ZOsGIcRBtZxvNfRSop3U/G85OB9f5Bauhvda0esMnDTOcx0cUbmAXmpApgAbuohqge0B zDtIKSJOt+b276eHRB456oysA77qEEf7jzn6WqErVgl+QNBUq8yanclpIzRofKV1tofHT45Ziil12 Qhh4Bu/AMIYNyjGqVcloKzS5QdDSEpEwCNJ8SSUc76v7ZiS8wF3YKXqowivh8l/wIPD13BBTSsfJE Mu3+Tilppuprfg==; In-Reply-To: <8A22A273-11F5-449C-A2A4-2E8C68CCF1FE@traductaire-libre.org> (message from Jean-Christophe Helary on Tue, 02 Jan 2024 13:16:53 +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:314455 Archived-At: > Date: Tue, 02 Jan 2024 13:16:53 +0000 > From: Jean-Christophe Helary > Cc: Vincent Belaïche , stefankangas@gmail.com, emacs-devel@gnu.org, rms@gnu.org > > > Not at the moment, no. And I'm not even sure this is our > > Emacs-specific problem to solve. If the GNU Project is going to > > support translations of the manuals, the ways of doing that should be > > discussed project-wide, probably on then Texinfo mailing list or at > > least with the participation of the Texinfo developers. > > The GNU project is already supporting translation of documentation. > > https://translationproject.org/extra/matrix.html > > (TexInfo is there too) AFAIK, that matrix shows the state of translation of message catalogs of each project, which is not what we are talking about here. If I'm wrong, would you mind pointing me at the translated Info manuals of the projects in the matrix? > >> If we were not to use an intermediate format and directly use texi, > >> we’d need a translation reference format, like TMX, but it could be > >> translated PO files, since they share a similar structure. The > >> translators would translate chunk by chunk and need a tool that > >> identifies already translated chunks from the reference format and use > >> them instead. > > > > We could for starters invent some simple technique of our own, like > > markers within the Texinfo sources that identify small enough chunks > > of text, or something similar. > > Markers are already here (TexInfo commands, end of sentence markers, > etc.). I meant markers specifically for translators, so that it would be easy to detect chunk(s) of text that was/were modified, and update their translations. > Some commands in TexInfo have translatable contents, others do not. I didn't mean Texinfo commands, I meant mainly the plain text which is 85% of any Texinfo manual. > Honestly, the easiest way to handle the translation of Emacs documents > would be to contact the TP project manager and to discuss what’s the > best way to do that, while thinking of what kind of infrastructure we > want on the emacs side to handle how to store/build all the translations. That could also be a good idea. Although TP is AFAIK mainly busy with translating short messages, not large manuals of the kind we have in Emacs.