From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Gavin Smith Newsgroups: gmane.comp.tex.texinfo.general,gmane.emacs.devel Subject: Re: @dircategory (Re: Translating Emacs manuals is of strategic importance) Date: Sat, 6 Jan 2024 19:27:15 +0000 Message-ID: References: <8734vda9kz.fsf@yahoo.com> <5EC9A02F-DB34-48B6-BD2D-CB9E89A385D0@traductaire-libre.org> <83r0iwuek9.fsf@gnu.org> <837cknvkrx.fsf@gnu.org> <83r0iuuacz.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="16053"; mail-complaints-to="usenet@ciao.gmane.io" Cc: Eli Zaretskii , Stefan Kangas , Vincent =?iso-8859-1?Q?Bela=EFche?= , emacs-devel@gnu.org, rms@gnu.org, help-texinfo@gnu.org To: Jean-Christophe Helary Original-X-From: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Sat Jan 06 20:27:30 2024 Return-path: Envelope-to: gnu-help-texinfo2@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 1rMCKP-0003wx-Qe for gnu-help-texinfo2@m.gmane-mx.org; Sat, 06 Jan 2024 20:27:29 +0100 Original-Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rMCKK-0003Ul-1L; Sat, 06 Jan 2024 14:27:24 -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 1rMCKH-0003Pq-OM; Sat, 06 Jan 2024 14:27:21 -0500 Original-Received: from mail-qk1-x730.google.com ([2607:f8b0:4864:20::730]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.90_1) (envelope-from ) id 1rMCKG-0006uC-34; Sat, 06 Jan 2024 14:27:21 -0500 Original-Received: by mail-qk1-x730.google.com with SMTP id af79cd13be357-78101108e3fso76759685a.1; Sat, 06 Jan 2024 11:27:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1704569238; x=1705174038; darn=gnu.org; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:date:from:from:to :cc:subject:date:message-id:reply-to; bh=uxF1uhwEQLmS/Pfgh++Vyk0FPfwsG55/gGADm1Y8mgs=; b=A8etLdo//wXUtBjp4NHgp73llPOuHdpkBUg2YYTslChwILFli5W0aF1gaSVF4rcn9O d9fIFyzs7UALaxmxdsHLvtcEvKJKvw8t1P1LEOM2zndf+U5kQ6ieaketyxgGG2uANvvt 8+BBP/V66V5n3RcywLdBBkq4Rxw5SH2UtghYFPKRPd9CodBeKbcaXxVSz0o1Szx/kCKg Q04JnPDS1XKCyC9V270BJ48HHQ1xqFJkcNgPq+Grl5s+BfX/S8kkQJ452ObRpV02cdPn 5Q/SOTWmqPDfA7ekzDKQFteH3t13gRU8vAHoX2V04LVNfC4ND1Yxuy6kB1DJBYV80VAk xVuw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1704569238; x=1705174038; h=in-reply-to:content-transfer-encoding:content-disposition :mime-version:references:message-id:subject:cc:to:date:from :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=uxF1uhwEQLmS/Pfgh++Vyk0FPfwsG55/gGADm1Y8mgs=; b=BrZZ6hxFLZNEh0Y4uq0QpImHZzaC9pVoJsdBIB3NZh09fEGm/6jA+SU33qeGNt2Od6 v2BVRlQ0L5w8RnlSnnrs8Mb34BRKB+DNfyHGZDc0B1tjiFd9WOdPLgcuhuScPpONdQ9G p0HDEwS3oNcJ0Eg8NqoKOwahwtJp67LGaZi5EhRxC3F2EFl8OqzSARVsqkdDRIYHzorT X/CsXp9sKrWdgBljkeDaVrb9QAT5oVwx6t7VDpYlsp76/AIf1TFDZBDWXObvDwA+EMy9 KqX+5x6fszJUzC3AuzJ/FLD7RW6j++6LhjnDITiP2zfva6ifyiXUbhY0LO8HT4EjZBMZ DOsg== X-Gm-Message-State: AOJu0Yx7dxitJlo2k3C0V4v4pLTAj8S6WYRDZeff8/eqjesMj1NrF5xw W2OXB2QUR+UlO5N8jtcVtSw= X-Google-Smtp-Source: AGHT+IFBooH4CL9RXOp5Omhuvq7JZkbl8onfe+C/IwZif3HjTx5HgL4BQj7ioboasQI81WiDPhRsmA== X-Received: by 2002:a37:de1a:0:b0:783:518:282a with SMTP id h26-20020a37de1a000000b007830518282amr1417508qkj.36.1704569237857; Sat, 06 Jan 2024 11:27:17 -0800 (PST) Original-Received: from localhost ([2a02:c7f:c29:b00:cd5c:ff9c:7813:a266]) by smtp.gmail.com with ESMTPSA id bi15-20020a05620a318f00b0078314f2144bsm351802qkb.44.2024.01.06.11.27.17 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 06 Jan 2024 11:27:17 -0800 (PST) X-Google-Original-From: Gavin Smith Content-Disposition: inline In-Reply-To: Received-SPF: pass client-ip=2607:f8b0:4864:20::730; envelope-from=gavinsmith0123@gmail.com; helo=mail-qk1-x730.google.com X-Spam_score_int: -18 X-Spam_score: -1.9 X-Spam_bar: - X-Spam_report: (-1.9 / 5.0 requ) BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-texinfo@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Users list for the Texinfo documentation system List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Original-Sender: help-texinfo-bounces+gnu-help-texinfo2=m.gmane-mx.org@gnu.org Xref: news.gmane.io gmane.comp.tex.texinfo.general:3384 gmane.emacs.devel:314647 Archived-At: On Sat, Jan 06, 2024 at 09:37:03AM +0000, Jean-Christophe Helary wrote: > >> Also, we will have to translate @node, because they appear in the > >> Section index. I see that they were kept in English in the SES manual. > > > > If we translate @node names, links from the doc strings and > > cross-manual links will not work. > > They will if they are translated in the other manuals. That’s what I’m > doing in the Emacs manuals at the moment. > > > But, for such links to work, we > > need a facility to tell the Info reader that when a link goes to a > > manual named FOO.info, it should visit FOO-LANG.info instead. Again, > > something that involves a change in Texinfo and in all Info readers. > > What are the practical cases where translating nodes would be a problem? > > 1. I read a manual in English, there is a link with a node in English, > it directs to the other English manual. > > It’s the expected behaviour. > > 2. I read a manual in French, there is a link with a node in English, > it directs to the other English manual. > > If the other manual exists in French, it is not the proper behaviour. One option to account for this is use multiple infodirs, one for each language. Each of the infodirs would be on the INFOPATH, in order of language preference. Node names would not be translated, so that links to translated nodes would work, if they became available. Alternatively, the English node name could be provided as an @anchor in addition to a non-English node name. > > 3. I read a manual in French, there is a link with a node in French, it > directs to the other French manual. > > If the other manual exists in French, it is the proper behaviour. > > If it does not, we should have an error message that informs the reader > that the manual is not translated. > > > So instead of a complex look up system, just an error message for links > that don’t work should be sufficient. Don’t you think? That word "just" implies it's easy and straightforward to implement, which is a risky assumption. One difficulty that comes to mind is how you tell the difference between a manual that has not been translated yet, and one which just isn't installed or or doesn't exist. > > One issue seems to be that nodes have natural language IDs that also > appear in the manual. If nodes were just arbitrary IDs associated to a > string, like “2.1.2.fr” associated to “Ma section”, while “2.1.2.en” is > “My section”, it would be easier to do the lookup and the manual would > print the correct string. > > In my current work on the Emacs manual, every time I find a node, I > look for it in all the other chapters/manuals and adapt its translation. >