From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Marcin Borkowski Newsgroups: gmane.emacs.help Subject: Re: Emacs as a translator's tool Date: Thu, 04 Jun 2020 21:47:33 +0200 Message-ID: <877dwmoboq.fsf@mbork.pl> References: <871rn35lqc.fsf@mbork.pl> <87zh9r45ad.fsf@mbork.pl> <87h7vz2m5g.fsf@ebih.ebihd> <87d06k4rmg.fsf@mbork.pl> <87eeqzmanl.fsf@ebih.ebihd> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="53459"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: mu4e 1.1.0; emacs 27.0.50 Cc: help-gnu-emacs@gnu.org To: Emanuel Berg Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Thu Jun 04 21:48:13 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 1jgvqX-000DgR-Jw for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 04 Jun 2020 21:48:13 +0200 Original-Received: from localhost ([::1]:54938 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jgvqW-0007JW-M7 for geh-help-gnu-emacs@m.gmane-mx.org; Thu, 04 Jun 2020 15:48:12 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:46262) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jgvqE-0007IJ-1i for help-gnu-emacs@gnu.org; Thu, 04 Jun 2020 15:47:54 -0400 Original-Received: from mail.mojserwer.eu ([195.110.48.8]:54548) by eggs.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jgvq6-0006t8-FG for help-gnu-emacs@gnu.org; Thu, 04 Jun 2020 15:47:53 -0400 Original-Received: from localhost (localhost [127.0.0.1]) by mail.mojserwer.eu (Postfix) with ESMTP id DC7BBE6DAE; Thu, 4 Jun 2020 21:47:40 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at mail.mojserwer.eu Original-Received: from mail.mojserwer.eu ([127.0.0.1]) by localhost (mail.mojserwer.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uS-YU4ZQJYfr; Thu, 4 Jun 2020 21:47:37 +0200 (CEST) Original-Received: from localhost (jeden09-dwa27.echostar.pl [213.156.109.227]) by mail.mojserwer.eu (Postfix) with ESMTPSA id 48D37E6CB0; Thu, 4 Jun 2020 21:47:37 +0200 (CEST) In-reply-to: <87eeqzmanl.fsf@ebih.ebihd> Received-SPF: pass client-ip=195.110.48.8; envelope-from=mbork@mbork.pl; helo=mail.mojserwer.eu X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/04 15:47:41 X-ACL-Warn: Detected OS = Linux 3.11 and newer [fuzzy] X-Spam_score_int: -25 X-Spam_score: -2.6 X-Spam_bar: -- X-Spam_report: (-2.6 / 5.0 requ) BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, T_SPF_HELO_TEMPERROR=0.01, URIBL_BLOCKED=0.001 autolearn=_AUTOLEARN 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:123227 Archived-At: On 2020-06-01, at 10:51, Emanuel Berg via Users list for the GNU Emacs text= editor wrote: > Marcin Borkowski wrote: > >>> Can't you do ecat-highlight-next-sentence and >>> ecat-highlight-previous-sentence by just moving >>> point to the next sentence and then do >>> ecat-highlight-this-sentence? Feels more >>> natural... >> >> That would completely defeat the purpose. All CAT >> stuff (as many people already told) is about >> efficiency. One of the main points of my (very >> simple) code is that I do not have to move >> point anywhere. > > Because its inefficient? ... you are a fast > translator :) It's not the question of speed, but of distractions. Annoying workflow full of distractions (like moving the point in the other window manually) is very inefficient. > but ... OK. > > Only it still looks wierd with the same code two > extra times. > >> Well, you already got your answers, but let me >> stress that one of the important points is >> extracting text from some strange formats and >> putting the translation back into it. Think Word >> documents with complex formatting, or HTML with >> many tags/attributes. If you are to translate >> things like >> >>

Click the > class=3D"dancing-elephants">big red button to >> launch the nuke

>> >> and all the markup has to be there in the >> translation, you really don't want to type it by >> hand - it's time-consuming and error-prone. > > Well, that's a task for a parser rather to convert > between one format to another... very mechanical > and easy. Have you ever done a real-world translation like this...? > >>> Some idiomatic phrases are pitfalls tho. >>> For example the English "more or less" looks like >>> the Swedish "mer eller mindre" (which means >>> "correct but with room for fine details") but the >>> way native speakers use it seems to be more (?) >>> "b=C3=A5de och" which means discussion can go both >>> (disparate) ways and BOTH are correct! So perhaps >>> one could have a list of these "trap phrases" so >>> when they turn up in the text, they are >>> highlighted to indicate "watch out! we are not >>> just piling words here!" Who'd compile that list >>> is another matter... >> >> I guess this is a very minor problem... > > It depends how many there are... should be systemized > just as everything unusual is in any trade. > Easy thing to do with huge gain and possible to build > on and extend... As I said - you're right, but this is definitely not a major issue. Best, --=20 Marcin Borkowski http://mbork.pl