From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.io!.POSTED.ciao.gmane.io!not-for-mail From: Emanuel Berg via Users list for the GNU Emacs text editor Newsgroups: gmane.emacs.help Subject: Re: Emacs as a translator's tool Date: Wed, 10 Jun 2020 23:28:21 +0200 Message-ID: <87r1um391m.fsf@ebih.ebihd> References: <871rn35lqc.fsf@mbork.pl> <87zh9r45ad.fsf@mbork.pl> <87h7vz2m5g.fsf@ebih.ebihd> <87d06k4rmg.fsf@mbork.pl> <87eeqzmanl.fsf@ebih.ebihd> <877dwmoboq.fsf@mbork.pl> <87bllypckg.fsf@ebih.ebihd> <87tuzpmnuo.fsf@mbork.pl> <87bllu4lx0.fsf@ebih.ebihd> <87blluxfcq.fsf@mbork.pl> <1rmqrrvn.fsf@ebih.ebihd> <87sgf5xry2.fsf@mbork.pl> <87ftb5qodp.fsf@ebih.ebihd> <87ftb4xcf4.fsf@mbork.pl> <87h7vkklij.fsf@ebih.ebihd> <87r1umwsff.fsf@mbork.pl> Reply-To: Emanuel Berg Mime-Version: 1.0 Content-Type: text/plain Injection-Info: ciao.gmane.io; posting-host="ciao.gmane.io:159.69.161.202"; logging-data="4995"; mail-complaints-to="usenet@ciao.gmane.io" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux) To: help-gnu-emacs@gnu.org Cancel-Lock: sha1:LB/MAMri/lOb45+AbXc/0SSAr6k= Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane-mx.org@gnu.org Wed Jun 10 23:29:01 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 1jj8HL-00018z-WE for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 10 Jun 2020 23:29:00 +0200 Original-Received: from localhost ([::1]:36594 helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1jj8HL-00078d-0j for geh-help-gnu-emacs@m.gmane-mx.org; Wed, 10 Jun 2020 17:28:59 -0400 Original-Received: from eggs.gnu.org ([2001:470:142:3::10]:58422) by lists.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jj8Gt-00078F-P6 for help-gnu-emacs@gnu.org; Wed, 10 Jun 2020 17:28:31 -0400 Original-Received: from ciao.gmane.io ([159.69.161.202]:56252) by eggs.gnu.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1jj8Gs-0000Hp-Ky for help-gnu-emacs@gnu.org; Wed, 10 Jun 2020 17:28:31 -0400 Original-Received: from list by ciao.gmane.io with local (Exim 4.92) (envelope-from ) id 1jj8Gp-0000UO-T5 for help-gnu-emacs@gnu.org; Wed, 10 Jun 2020 23:28:27 +0200 X-Injected-Via-Gmane: http://gmane.org/ Mail-Followup-To: help-gnu-emacs@gnu.org Mail-Copies-To: never Received-SPF: pass client-ip=159.69.161.202; envelope-from=geh-help-gnu-emacs@m.gmane-mx.org; helo=ciao.gmane.io X-detected-operating-system: by eggs.gnu.org: First seen = 2020/06/10 17:28:28 X-ACL-Warn: Detected OS = Linux 2.2.x-3.x [generic] [fuzzy] X-Spam_score_int: -8 X-Spam_score: -0.9 X-Spam_bar: / X-Spam_report: (-0.9 / 5.0 requ) BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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:123317 Archived-At: Marcin Borkowski wrote: >> Right, but I think its a good idea to keep them >> apart. And then have different modes... > > It depends. How about preapring a LaTeX file with two > language versions typeset side-by-side? Better to use the translation tool somewhere else, when its done one can do whatever with the material including typesetting. LaTeX mode and markup will just complicate everything. Do it all in one buffer in general: DNC >> Still, one can do that as well... with a variable >> instead of point to keep track of it the overlay. >> Maybe editing screws it up. Its just better to >> have different buffers for different purposes, >> then people can also rearrange stuff visually more >> easily, and many other advantages... > > But my solution, in which I only use the overlay > itself (no point, no markers, no variables pointing > to buffers) seems to cover all such cases, and in > quite an elegant way. There is only one variable and that holds the overlay. Moving point I consider a good thing, only perhaps one should keep two sets of functions, to make it more clear what happens and when, and make it more versatile. As for your solution, I have only seen one version, the first you posted here... -- underground experts united http://user.it.uu.se/~embe8573 https://dataswamp.org/~incal