From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.blaine.gmane.org!not-for-mail From: Eric Abrahamsen Newsgroups: gmane.emacs.help Subject: Re: Emacs as a translator's tool Date: Thu, 17 Sep 2020 08:16:44 -0700 Message-ID: <87h7rwtov7.fsf@ericabrahamsen.net> References: <871rn35lqc.fsf@mbork.pl> <87zh9r45ad.fsf@mbork.pl> <87h7vz2m5g.fsf@ebih.ebihd> <87zh9qr67n.fsf@ericabrahamsen.net> <3DBA2692-28A0-4AC3-B884-78763A9C7B16@traduction-libre.org> <87tuzyr474.fsf@ericabrahamsen.net> Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="blaine.gmane.org:116.202.254.214"; logging-data="37520"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/28.0.50 (gnu/linux) Cc: help-gnu-emacs , Emanuel Berg , Yuri Khan To: Jean-Christophe Helary Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Sep 17 17:29:38 2020 Return-path: Envelope-to: geh-help-gnu-emacs@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 1kIvqs-0009bk-JD for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 17 Sep 2020 17:29:38 +0200 Original-Received: from localhost ([::1]:51274 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1kIvqr-0001v5-JQ for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 17 Sep 2020 11:29:37 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:59026) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kIveW-0006ML-Gz for help-gnu-emacs@gnu.org; Thu, 17 Sep 2020 11:16:52 -0400 Original-Received: from ericabrahamsen.net ([52.70.2.18]:39282 helo=mail.ericabrahamsen.net) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1kIveU-0003ru-3O for help-gnu-emacs@gnu.org; Thu, 17 Sep 2020 11:16:52 -0400 Original-Received: from localhost (c-73-254-86-141.hsd1.wa.comcast.net [73.254.86.141]) (Authenticated sender: eric@ericabrahamsen.net) by mail.ericabrahamsen.net (Postfix) with ESMTPSA id EE601FA095; Thu, 17 Sep 2020 15:16:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericabrahamsen.net; s=mail; t=1600355806; bh=SjxnDfGqNpC2tYxWpWC9sMHAAzwbGpZM+M2KNKZI/C8=; h=From:To:Cc:Subject:References:Date:In-Reply-To:From; b=aeKW84ylCPHS5BwMSQJUKdy7y6fZ5EEcOZpU1I2o7dnO936KAeXkuTAEe6yARUJq8 +nCaY41F/pNzz2rzeq/i8T6gjWyWfPULaJzWUcvLzU8zGGgR6KHva12ktOg2eHwFM5 J5yTlxEAX8qDzgQpFLXJEqlH5l4v+OQgcW/6A8Ak= In-Reply-To: <87tuzyr474.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Fri, 29 May 2020 11:22:55 -0700") Received-SPF: pass client-ip=52.70.2.18; envelope-from=eric@ericabrahamsen.net; helo=mail.ericabrahamsen.net X-detected-operating-system: by eggs.gnu.org: First seen = 2020/09/17 11:00:39 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -43 X-Spam_score: -4.4 X-Spam_bar: ---- X-Spam_report: (-4.4 / 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, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, SPF_PASS=-0.001 autolearn=ham autolearn_force=no X-Spam_action: no action X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Original-Sender: "help-gnu-emacs" Xref: news.gmane.io gmane.emacs.help:124071 Archived-At: Eric Abrahamsen writes: > Jean-Christophe Helary [...] >>> 2. Link terms in the translation to a glossary pulled from the original. >>> This would be character names, places, special terms, etc. They might >>> not always be translated the same way, but I need to know how I've >>> handled them earlier in the document. Glossary terms would be >>> highlighted in the source text, and when you came to the equivalent >>> spot in the translation, you'd use a command like >>> insert-translation-term that would prompt for the translation, >>> offering completion on earlier translations, and then insert that >>> term into the translated text with a link to the original in the >>> glossary. There would also be two multi-occur commands: one that >>> prompted for a translation and showed all the places in the source >>> text where it came from, and another that did the opposite: prompted >>> for an original glossary term and showed all the places in the >>> translation where it was translated. >> >> Very nice ideas. > > Maybe this will inspire me to write some code! The nice thing about the > glossary is that it wouldn't have to just be vocabulary. You could just > as easily use it for "every time the car crash is referenced", or > something like that. You'd just have to manually mark the passage in the > original, rather than automated marking by text search. Okay, I've finally implemented this, and pushed a version 0 of a package called org-translate to ELPA. You can see the code here: https://git.savannah.gnu.org/gitweb/?p=emacs/elpa.git;a=blob_plain;f=packages/org-translate/org-translate.el;hb=HEAD I'm going to fool with it a bit longer, then make a real release. It basically does what I was describing up-thread: basic segmentation, tracking of correspondences between source and translation text, and maintenance of a glossary for automatic translation. Comments very welcome! I hope it will eventually be used by more people than just me :) Eric