From: "Juan Manuel Macías" <email@example.com> To: orgmode <firstname.lastname@example.org> Subject: An attempt to prepare critical editions within Org Date: Thu, 20 May 2021 11:45:07 +0000 [thread overview] Message-ID: <email@example.com> (raw) Hi, If there is a philologist among the colisters who is working on critical editions (a type of text with several complex apparatus of footnotes and endnotes, and with numbering and various material at the margin ---an example of critical edition I recently typesetted for a German publisher: https://maciaschain.gitlab.io/lunotipia/images/muestras_cariton1.png), you may find the following interesting. I am working on a package, org-critical-edition, to prepare philological critical editions from the comfort of Org Mode. The natural backend of these documents should be LaTeX with the 'reledmac' package (https://ctan.org/pkg/reledmac), an excellent package mantained by Maïeul Rouquette (https://github.com/maieul/ledmac), that is the most mature option to work in this type of texts within LaTeX. But in the future I may add some support to export data to the TEI-xml standard, widely used in Humanities. The basic idea of my package is that the 'critical notes' are always hidden and only the annotated passages are shown in the text (they are actually Org links, but what is shown is the target, while the description and the target label remains invisible). Each critical note can be edited or created (over a marked region) in a dedicated buffer. Soon I will upload to GitLab a first version of the package (quite immature at the moment: feedback welcome!) but here is a brief screencast: https://lunotipia.juanmanuelmacias.com/images/org-critical-edition.mp4 Best regards, Juan Manuel
next reply other threads:[~2021-05-20 11:45 UTC|newest] Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-05-20 11:45 Juan Manuel Macías [this message] 2021-05-20 12:24 ` Denis Maier
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 \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: An attempt to prepare critical editions within 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
Code repositories for project(s) associated with this 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).