emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Christian Moe <mail@christianmoe.com>
Cc: orgmode <emacs-orgmode@gnu.org>
Subject: Re: org-critical-edition (a package for philologists and classicists)
Date: Tue, 15 Jun 2021 12:44:53 +0000	[thread overview]
Message-ID: <87eed3qou2.fsf@posteo.net> (raw)
In-Reply-To: <87bl883k4r.fsf@christianmoe.com> (Christian Moe's message of "Mon, 14 Jun 2021 10:50:28 +0200")

Hi Christian, thank you very much for your comments.

Christian Moe writes:

> Very neat!
> Curious about a design choice: If I understand correctly,
> org-critical-edition puts the hidden notes in the description and the
> visible annotated text in the target of an org link. This is the reverse
> of the out-of-the-box link appearance (description visible, target
> hidden if description present). Why take the extra trouble to do it this
> way?

Indeed, the decision to reverse the order of the link appearance may
seem somewhat shocking :-) I did it like this to keep a syntactic
structure similar to the reledmac command \edtext, when the user (the
reledmac user) views the links full displayed. In LaTeX/reledmac the
structure is:

...some text... \edtext{annotated passage}{critical notes} ...some text...

The annotated passage is part of the text and is also the "lemma" in the
critical note.

In org-critical-edition I define a new link type called `edtext', using
`org-link-set-parameters', and the identifying string (`edtext:') must be
placed in the target part.

Best regards,

Juan Manuel 

      reply	other threads:[~2021-06-15 12:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-07 13:09 org-critical-edition (a package for philologists and classicists) Juan Manuel Macías
2021-06-14  8:50 ` Christian Moe
2021-06-15 12:44   ` Juan Manuel Macías [this message]

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:

  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=87eed3qou2.fsf@posteo.net \
    --to=maciaschain@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@christianmoe.com \


* 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


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).