From: <tomas@tuxteam.de>
To: emacs-orgmode@gnu.org
Subject: Re: section continuation
Date: Thu, 29 Dec 2022 11:28:09 +0100 [thread overview]
Message-ID: <Y61ruS7tauKCKEdS@tuxteam.de> (raw)
In-Reply-To: <def17bac-653f-53f8-d057-6589f11cdbc3@gmx.at>
[-- Attachment #1: Type: text/plain, Size: 1978 bytes --]
On Thu, Dec 29, 2022 at 10:21:55AM +0100, Heinz Tuechler wrote:
[...]
> Agreed. I think that "allow certain nodes to only have one text element
> at the very beginning" is an arbitrary choice.
There are many arbitrary choices when designing a data structure to
represent text.
> Inconvenient, but logically cleaner would be to allow for text either
> only in leaves,
You'd regret that quickly: what do you do for inline markup (e.g.
bold, italics)? You'd have to introduce a special markup for
"normal" text. Good-bye "lightweight markup" :)
> or in any place of the nodes.
This is XML's "mixed content". Note that specific XMLs can and
do limit that, via DTDs or other validation restrictions (aka
schema). If you're doing text using some suitable XML schema,
you most probably won't be able to put a whole paragraph whithin
a section title. Or a table. If you want a whole italics stretch
straddling a paragraph boundary, you'll have to close it before
the paragraph's end and re-open it next paragraph or something
(although they might, logically or philosophically, belong
together).
Human language is too exciting to fit into a tree structure.
> The latter appears more natural to me, as it would allow for connecting
> words between sub sections and closing remarks at the end of a section.
> Usually, one would circumvent the problem by inserting a connecting text
> at the end of subsections, although this would offend the hierarchy.
> best regards, Heinz
You'll always end up offending some hierarchy some of the time.
In some places you can be sent to jail for that ;-)
No, seriously: Document models sometimes get stretched to data
description languages (I always cringe when people talk about
a JSON or YAML "document") and vice-versa. This is a strength,
but also a weakness.
And don't forget, OASIS's OpenDocument format also doesn't seem
to support "going back". Perhaps for a reason.
Cheers
--
t
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
next prev parent reply other threads:[~2022-12-29 10:28 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-27 13:08 section continuation (was: Is the cascading logic of outlines a feature, or a design bug?) abq
2022-12-27 13:57 ` tomas
2022-12-28 2:22 ` Samuel Wales
2022-12-27 14:15 ` section continuation abq
2022-12-27 15:36 ` tomas
2022-12-27 20:22 ` abq
2022-12-28 5:17 ` Ihor Radchenko
2022-12-28 8:58 ` tomas
2022-12-29 6:01 ` Tim Cross
2022-12-29 8:57 ` tomas
2022-12-29 9:21 ` Heinz Tuechler
2022-12-29 10:09 ` Jean Louis
2022-12-29 10:42 ` Ihor Radchenko
2022-12-29 14:00 ` Jean Louis
2022-12-31 12:16 ` Ihor Radchenko
2022-12-31 12:26 ` tomas
2023-01-01 21:29 ` Tom Gillespie
2022-12-29 10:28 ` tomas [this message]
2022-12-31 12:03 ` Greg Minshall
2022-12-29 10:06 ` Jean Louis
2022-12-29 12:47 ` Max Nikulin
2022-12-28 17:37 ` Timothy
2022-12-28 19:34 ` tomas
2022-12-29 10:21 ` Ihor Radchenko
2022-12-29 10:30 ` tomas
2023-01-01 21:19 ` Marcin Borkowski
2022-12-28 20:01 ` Heinz Tuechler
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=Y61ruS7tauKCKEdS@tuxteam.de \
--to=tomas@tuxteam.de \
--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).