From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mp1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by ms8.migadu.com with LMTPS id aC0LHl1L1mWWVAAA62LTzQ:P1 (envelope-from ) for ; Wed, 21 Feb 2024 20:13:33 +0100 Received: from aspmx1.migadu.com ([2001:41d0:403:4876::]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) by mp1.migadu.com with LMTPS id aC0LHl1L1mWWVAAA62LTzQ (envelope-from ) for ; Wed, 21 Feb 2024 20:13:33 +0100 X-Envelope-To: larch@yhetil.org Authentication-Results: aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=p+Bi5R2O; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=yhetil.org; s=key1; t=1708530103; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:list-id:list-help: list-unsubscribe:list-subscribe:list-post:dkim-signature; bh=O6v0pOOAowaBZaKu1ybxIPu2fYC3ehDGxhP3Hu0nkXU=; b=Zno8KwR9hHdnGFf5gVWm4LUL0d5NOMS4G6BP+tNDUHEAzfnLt+JAdWl+aSjAHndAGR9dvP iaOStFBS1wfhRndZEfnWJGXHHuVnRNFkNpJq+jg9LcIkny+6ChIBxy/w8NxdMjSoMcgtdd ASZwdJrKIHj36C2Ui9Zxg6JMeJIcqnr7MkKDhKnlZN7VX7AiD7fFRFGkn/ZpzOsxZX7a7X XgurWaZ9rLCF1l4H1lacsKHFL55vBOoxC/SmsUsUizgKvdgSR9W2+MrJIO2g9QubuMbJNx 9pZCEFY3/0NoVABcKH01Hl7Xr2ECGgRy+JwuBfWlQgaiSd+h4N/HUmNRYwoqXA== ARC-Authentication-Results: i=1; aspmx1.migadu.com; dkim=pass header.d=posteo.net header.s=2017 header.b=p+Bi5R2O; spf=pass (aspmx1.migadu.com: domain of "emacs-orgmode-bounces+larch=yhetil.org@gnu.org" designates 209.51.188.17 as permitted sender) smtp.mailfrom="emacs-orgmode-bounces+larch=yhetil.org@gnu.org"; dmarc=pass (policy=none) header.from=posteo.net ARC-Seal: i=1; s=key1; d=yhetil.org; t=1708530103; a=rsa-sha256; cv=none; b=Rfzystz90AwbwCcr5Ssfki7VYiGuJA644jUSrp15XNgT339Hvlk8f8DQYYgPt52HuBXGGP I8ipPou2sT4hxWhRmEZyP+0lRwVRFQYX9X0LATGmSppHDWAswQsX5sODllsqklFiDWQd4/ +0kk6eGeXkjS4f/AlXygcN7m5pcDe1U6rflzg1th3EdeWFVEl/g9D6soI66fF5sVl9jY/N k0SydKYjVvrfvXwhQ8w1yvO7p6AIs4l+NC4CwDJK5QJG4rQPAaE8qsLFoUt65el/jtbz7X 70XgOhSIvVObqH/pS0I3509dyyFcV5SOv2c0/9TTeb6p9rtzAIiCOqZZAxcS8g== Received: from lists.gnu.org (lists.gnu.org [209.51.188.17]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by aspmx1.migadu.com (Postfix) with ESMTPS id BF9AC7C4FB for ; Wed, 21 Feb 2024 16:41:43 +0100 (CET) Received: from localhost ([::1] helo=lists1p.gnu.org) by lists.gnu.org with esmtp (Exim 4.90_1) (envelope-from ) id 1rcob4-0002ms-F8; Wed, 21 Feb 2024 10:33:24 -0500 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 1rcoXZ-00040t-9U for emacs-orgmode@gnu.org; Wed, 21 Feb 2024 10:29:46 -0500 Received: from mout02.posteo.de ([185.67.36.66]) by eggs.gnu.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.90_1) (envelope-from ) id 1rckHr-0000P5-Nv for emacs-orgmode@gnu.org; Wed, 21 Feb 2024 05:57:17 -0500 Received: from submission (posteo.de [185.67.36.169]) by mout02.posteo.de (Postfix) with ESMTPS id 657FF240105 for ; Wed, 21 Feb 2024 11:57:13 +0100 (CET) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=posteo.net; s=2017; t=1708513033; bh=O6v0pOOAowaBZaKu1ybxIPu2fYC3ehDGxhP3Hu0nkXU=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version:Content-Type: Content-Transfer-Encoding:From; b=p+Bi5R2ONi5V5IyravvxpsurSj249AVwqIxuNd9QFKMZmQ19hsNcoOEuu2TqyEv0x oeZ1yGxSpbUAoOFZ7SsOKADQ7hRVYqTVBNYQcwQKLIiHECSUnaRDLmyYC7FHhSFz9O LMCfniQo4VlC6vwGIS3qx2Yv8cehYQH0v1YPG925ivvpmazTA52GQfiZM+BtA4PHb7 A0wcTXm9rZtxtl7nRdLOZKDEmYLoRcnE90qiVjN/tqJ8Jww5888kDiolOir6aCEqnT EvdzU+oWnE+i7aoqi0NCbIa/5lg+LlQMYXl3lmeCGiNyl/YFPt5haj8XDYz/Xdonr1 IlJ1R5gynresg== Received: from customer (localhost [127.0.0.1]) by submission (posteo.de) with ESMTPSA id 4TftWr50Zpz6tyb; Wed, 21 Feb 2024 11:57:12 +0100 (CET) From: =?utf-8?Q?Juan_Manuel_Mac=C3=ADas?= To: Ihor Radchenko Cc: orgmode Subject: Re: [proof of concept] inline language blocks In-Reply-To: <8734tmmcnv.fsf@localhost> (Ihor Radchenko's message of "Wed, 21 Feb 2024 08:42:12 +0000") References: <87msrudgcn.fsf@posteo.net> <8734tmmcnv.fsf@localhost> Date: Wed, 21 Feb 2024 10:57:09 +0000 Message-ID: <87edd6ytiy.fsf@posteo.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Received-SPF: pass client-ip=185.67.36.66; envelope-from=maciaschain@posteo.net; helo=mout02.posteo.de 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, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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: emacs-orgmode@gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+larch=yhetil.org@gnu.org Sender: emacs-orgmode-bounces+larch=yhetil.org@gnu.org X-Migadu-Flow: FLOW_IN X-Migadu-Country: US X-Migadu-Scanner: mx10.migadu.com X-Migadu-Spam-Score: -8.12 X-Spam-Score: -8.12 X-Migadu-Queue-Id: BF9AC7C4FB X-TUID: sRtvF9LcNlLA Ihor Radchenko writes: > Juan Manuel Mac=C3=ADas writes: > >> I'm dedicating a local branch to developing this proof of concept and >> testing it in my workflow, so far with good results. The basic idea is >> to provide Org with multilingual features and various methods for >> selecting languages. >> >> The inline-language-block is intended for small segments of text in a >> language other than the main language. They can span several lines but >> not more than a paragraph. They can be used for in-line textual quotes, >> glosses, etc. They are constructions equivalent to, for example, LaTeX >> \foreignlanguage{french}{text} or HTML text. >> >> I have thought of a syntax that is as least intrusive as possible, so as >> not to make reading uncomfortable. I have tried the following: >> >> :fr{some text in French} :it{some text in Italian} :la{some text in Lati= n} >> >> You can also use a literal term instead of a language code: >> >> :klingon!{some text in Klingon} >> >> The blocks can be nested: >> >> :klingon!{Some text in Klingon with :it{some text in Italian}} >> >> And they may include other elements: >> >> :el{Some text in Greek with a {{{macro}}} and a [[link]]} > > This is a good idea, although it would be better to make this new markup > element within the framework of more general inline special block we > discussed in the past: https://list.orgmode.org/orgmode/87a6b8pbhg.fsf@po= steo.net/ Fun fact: the local branch is called inline-special-block, because I originally had that idea in mind when I created it. Then, halfway through, I doubted whether it wouldn't be better to have a specific inline language selector, whose use would be as direct as an emphasis mark. So in the branch there is also a "proto"-inline-special-block with similar syntax: &foo{}. I opted for the -language-block version because, as I said, its use is very 'direct' and covers a common need to segment multilingual text within the paragraph. I think at the time we also discussed whether or not it would be a good idea to provide the inline special blocks with options and attributes, like their older brothers. And how to do it. My biggest concern here is the (let's say) latexification of the paragraph. I mean, one of the great things about Org versus heavier markup like LaTeX is that when org wants to be verbose it uses dedicated lines, but usually keeps the paragraphs clean and readable. I think that any element inside the paragraph should tend to be as "transparent" as simple emphasis marks. I remember that there was also discussion about puting the options outside the paragraph, using some type of identifier. It doesn't seem like a bad idea to me, but I think it adds an extra complication for the user. It would be very tedious for me to write like this (even more tedious than writing in LaTeX). Best regards, --=20 Juan Manuel Mac=C3=ADas=20