From: Timothy <firstname.lastname@example.org>
To: Jens Lechtenboerger <email@example.com>
Cc: Kyle Meyer <firstname.lastname@example.org>, org-mode-email <email@example.com>
Subject: Re: [PATCH] tweaks to ox-html style
Date: Sat, 13 Feb 2021 02:22:31 +0800 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
Jens Lechtenboerger <email@example.com> writes:
> On 2021-02-12, Jens Lechtenboerger wrote:
>> I do not know why the CDATA lines exist. I don’t see a reason to
>> keep them (patch 0001), but that might be a lack of understanding on
>> my part.
> OK, that is probably for XHTML, where < and & are only allowed
> inside CDATA sections.
> Timothy, did you try to validate XHTML output?
If you look at the commit message for 001, you can see the following:
> remove CDATA strings, as they are now
> considered obsolete --- see
Does that page clear things up for you?
I did a bit more googling and found
which mentions CDATA:
> The CDATA code is then seen as text by the HTML parser (and can thus
> interfere with the scripting or styling language!), while the XML
> parser sees the content as text without markup semantics.
In other words, CDATA allows you to keep XML comparability, but now
breaks strict HTML comparability. IMO the latter is much more important
for an org-html export.
next prev parent reply other threads:[~2021-02-12 18:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-20 10:46 [PATCH] TEC
2021-01-20 11:00 ` [PATCH] tweaks to ox-html style TEC
2021-02-12 6:16 ` Kyle Meyer
2021-02-12 16:57 ` Jens Lechtenboerger
2021-02-12 17:08 ` Jens Lechtenboerger
2021-02-12 18:22 ` Timothy [this message]
2021-02-13 14:43 ` Jens Lechtenboerger
2021-02-12 18:16 ` Timothy
2021-02-12 21:46 ` Tim Cross
2021-02-13 9:28 ` Eric S Fraga
2021-02-13 13:32 ` Christian Moe
2021-02-14 4:36 ` Timothy
2021-04-28 3:38 ` [PATCH] Bastien
2021-04-28 3:53 ` [PATCH] Timothy
2021-04-28 6:36 ` [PATCH] Bastien
2021-04-28 6:33 ` [PATCH] Bastien
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).