From: Ihor Radchenko <firstname.lastname@example.org>
To: "Juan Manuel Macías" <email@example.com>
Cc: orgmode <firstname.lastname@example.org>
Subject: Re: [patch] ox-html.el: add html attribute (verse numbers) to verse blocks
Date: Tue, 31 May 2022 13:06:03 +0800 [thread overview]
Message-ID: <874k161ebo.fsf@localhost> (raw)
Juan Manuel Macías <email@example.com> writes:
> Ihor Radchenko writes:
>> Sounds reasonable. However, a more consistent way to handle line numbers
>> would be using switches, like what we do in EXAMPLE blocks. See
>> org-element-example-block-parser and 12.6 Literal Examples section of
>> the manual.
> (I didn't remember that I had sent this patch...).
> I'll take a look at the function you mention, when I have some time. In
> any case, keep in mind that there are some conventions in verse
> numbering: the white lines (separation between stanzas) are never
> numbered and there is a sequence: 5 (first verse alwais remains
> unnumbered) ... 10 ... 15 ..., which can be chosen using the :lines
> attribute. :lines t defaults to a sequence of 5 verses. I chose this
> syntax to follow the syntax of verse numbering with output to LaTeX
> (another patch of mine that is already included in Org. In that case,
> the 'verse' LaTeX package is used).
The default switches syntax was originally designed for code block and
it generally supports continuous numbering across several subsequent
code blocks or starting the numbering from certain line. Will such
features be useful for verses?
Do you know if customizing :lines 5 to something other than 5 is often
needed? Maybe it can be an export option?
next prev parent reply other threads:[~2022-05-31 5:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 14:27 [patch] ox-html.el: add html attribute (verse numbers) to verse blocks Juan Manuel Macías
2022-05-30 5:10 ` Ihor Radchenko
2022-05-30 15:36 ` Juan Manuel Macías
2022-05-31 5:06 ` Ihor Radchenko [this message]
2022-05-31 11:00 ` Juan Manuel Macías
2022-07-04 11:44 ` Ihor Radchenko
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 \
* 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).