From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: orgmode <emacs-orgmode@gnu.org>
Subject: [proof of concept] inline language blocks
Date: Tue, 20 Feb 2024 20:35:04 +0000 [thread overview]
Message-ID: <87msrudgcn.fsf@posteo.net> (raw)
Hi,
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 <span lang=fr>text</span>.
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 Latin}
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]]}
To this end, I have defined the following element:
#+begin_src emacs-lisp
(defun org-element-inline-language-block-parser ()
"Parse inline language block at point.
When at an inline language block, return a new syntax node of
`inline-language-block' type containing `:begin', `:end',
`:type', `:contents-begin', `:contents-end' and `:post-blank' as
properties. Otherwise, return nil.
Assume point is at the beginning of the block."
(save-excursion
(when (looking-at ":\\([A-Za-z!]+\\){")
(goto-char (match-end 0))
(let* ((begin (match-beginning 0))
(contents-begin (match-end 0))
(type (org-element--get-cached-string
(match-string-no-properties 1)))
(contents-end
(progn
(goto-char (- contents-begin 1))
(org-element--parse-paired-brackets ?\{)
(- (point) 1)))
(post-blank (skip-chars-forward " \t"))
(end (point)))
(when contents-end
(org-element-create
'inline-language-block
(list :type type
:contents-begin contents-begin
:contents-end contents-end
:begin begin
:end end
:post-blank post-blank)))))))
(defun org-element-inline-language-block-interpreter (inline-language-block contents)
"Interpret INLINE LANGUAGE BLOCK object as Org syntax."
(format ":%s{%s}"
(org-element-property :type inline-language-block)
contents))
#+end_src
And, for now, this function for ox-latex:
#+begin_src emacs-lisp
(defun org-latex-inline-language-block (inline-language-block contents info)
"Transcode an INLINE LANGUAGE BLOCK element from Org to LaTeX.
CONTENTS holds the contents of the block. INFO is a plist
holding contextual information."
(let ((type (org-element-property :type inline-language-block)))
(if (string-match-p "!" type)
(format "\\foreignlanguage{%s}{%s}"
(replace-regexp-in-string "!" "" type)
contents)
(let* ((plist (cdr
(assoc type org-latex-language-alist)))
(language (plist-get plist :babel))
(language-ini-only (plist-get plist :babel-ini-only))
(language-ini-alt (plist-get plist :babel-ini-alt))
(lang (or language language-ini-only language-ini-alt)))
(format "\\foreignlanguage{%s}{%s}" lang contents)))))
#+end_src
Opinions, suggestions, feedback, ideas?
Best regards,
Juan Manuel
--
Juan Manuel Macías -- Composición tipográfica, tratamiento de datos, diseño editorial y ortotipografía
next reply other threads:[~2024-02-20 20:36 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-20 20:35 Juan Manuel Macías [this message]
2024-02-21 8:42 ` [proof of concept] inline language blocks Ihor Radchenko
2024-02-21 10:57 ` Juan Manuel Macías
2024-02-21 12:00 ` Ihor Radchenko
2024-02-21 12:53 ` Juan Manuel Macías
2024-02-21 13:10 ` Ihor Radchenko
2024-02-21 14:13 ` Juan Manuel Macías
2024-02-21 20:32 ` [proof of concept] inline-special-block (was: [proof of concept] inline language blocks) Juan Manuel Macías
2024-02-21 23:29 ` [proof of concept] inline-special-block Juan Manuel Macías
2024-02-22 22:03 ` Juan Manuel Macías
2024-02-21 22:11 ` [proof of concept] inline language blocks Samuel Wales
2024-02-21 22:28 ` Juan Manuel Macías
2024-02-21 22:55 ` Samuel Wales
2024-02-21 23:02 ` Juan Manuel Macías
2024-02-28 10:29 ` Max Nikulin
2024-02-28 13:15 ` Juan Manuel Macías
2024-02-28 17:21 ` Max Nikulin
2024-02-28 23:42 ` Juan Manuel Macías
2024-02-29 7:05 ` Max Nikulin
2024-02-29 10:41 ` Juan Manuel Macías
2024-02-29 12:05 ` Max Nikulin
2024-02-29 12:50 ` Juan Manuel Macías
2024-02-21 23:33 ` Suhail Singh
2024-03-31 14:56 ` Daniel Clemente
2024-03-31 15:20 ` Ihor Radchenko
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87msrudgcn.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).