From: "Juan Manuel Macías" <maciaschain@posteo.net>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: Bastien <bzg@gnu.org>, orgmode <emacs-orgmode@gnu.org>,
TEC <tecosaur@gmail.com>
Subject: Re: [PATCH] A proposal to add LaTeX attributes to verse blocks
Date: Sun, 02 May 2021 11:09:44 +0000 [thread overview]
Message-ID: <87tunlpf2f.fsf@posteo.net> (raw)
In-Reply-To: <87tunlxws3.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Sun, 02 May 2021 11:19:56 +0100")
Hi Eric and all,
Thank you for your comments.
Eric S Fraga writes:
> What is being proposed looks reasonable to me. I don't use =verse= very
> often but have used it now and again and I can particular see the need
> for numbering and centring, in particular.
Indeed, optical centering is the correct typographic representation for
poetry and poetry quotes. There would only be a couple exceptions: a)
Certain types of avant-garde poetry (whose representation on paper is
usually freer) and b) those poems whose verses spill over the margins
and span several lines (in such case, the attribute :versewidth would
have to take the value \textwidth, and then the verse package takes care
of adjusting the overflowing part of the verses).
Here I have uploaded two very illustrative examples of optical
centering, two pages from a Tolkien book (/The Monsters and the Critics
and Other Essays/) and another page from a book that I recently
typesetted (here also includes verse numbering):
https://imgur.com/a/cGi4CpD
> Is the verse package loaded automatically already? I did not see any
> change in the patch to that aspect and when I export a simple test, the
> package is not loaded.
For now, you need to load the verse package or add it to
org-latex-packages-alist...
Best regards,
Juan Manuel
next prev parent reply other threads:[~2021-05-02 11:11 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 17:23 [PATCH] A proposal to add LaTeX attributes to verse blocks Juan Manuel Macías
2021-01-03 10:25 ` TEC
2021-01-03 13:07 ` Juan Manuel Macías
2021-01-03 13:08 ` TEC
2021-01-07 18:52 ` Juan Manuel Macías
2021-05-01 10:58 ` Bastien
2021-05-01 11:46 ` Juan Manuel Macías
2021-05-02 10:24 ` Eric S Fraga
[not found] ` <87tunlxws3.fsf@ucl.ac.uk>
2021-05-02 11:09 ` Juan Manuel Macías [this message]
2021-05-02 11:31 ` Timothy
2021-05-03 23:22 ` Tim Cross
2021-05-08 7:31 ` Juan Manuel Macías
2021-05-15 13:46 ` Bastien
2021-05-01 10:58 ` Timothy
-- strict thread matches above, loose matches on Subject: below --
2020-12-17 17:11 [patch] " Juan Manuel Macías
2021-01-03 10:22 ` TEC
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=87tunlpf2f.fsf@posteo.net \
--to=maciaschain@posteo.net \
--cc=bzg@gnu.org \
--cc=e.fraga@ucl.ac.uk \
--cc=emacs-orgmode@gnu.org \
--cc=tecosaur@gmail.com \
/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).