From: Rick Frankel <rick@rickster.com>
To: Rasmus <rasmus@gmx.us>
Cc: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: Re: [patch][ox-html] Stylistic changes
Date: Tue, 18 Mar 2014 09:49:32 -0400 [thread overview]
Message-ID: <0d5c03b1f1e36a4250cbd11d467d3efe@mail.rickster.com> (raw)
In-Reply-To: <874n2w2n62.fsf@gmx.us>
On 2014-03-17 23:36, Rasmus wrote:
> Rick Frankel <rick@rickster.com> writes:
>
> On Mon, Mar 17, 2014 at 11:19:27PM +0100, Rasmus wrote:
> Hi Rick,
>
>
> Rick Frankel <rick@rickster.com> writes:
>
> > On Mon, Mar 17, 2014 at 03:17:10AM +0100, Bastien wrote:
> >> Hello,
> >>
> >> Nicolas Goaziou <n.goaziou@gmail.com> writes:
> >>
> >> > So if the change is only stylistic, I see no reason to break
> >> > compatibility with "ox-freemind.el".
> >
> >> I would favor a solution where the HTML backend uses what's
> >> readable (— and friends) and where the Freemind backend
> >> deals with this.
> >>
> >> Maybe `org-html-special-string-regexps' could be a variable
> >> and Freemind could temporarily set it up to what it needs?
> >
> > The use of numeric vs. named entities is not just stylistic.
> > XHMTL[45] only support the 5 basic named entities interally:
> >
> > - & - the ampersand &
> > - " - the double quote "
> > - ' single quote '
> > - < - less-than <
> > - > - greater-than >
> >
> > So including any others will generate non-conforming output.
> > Since the change is cosmetic, I don't see the purpose in adding a lot
> > of conditional code to the exporter to output different entities for
> > html[45] vs xhtml[45].
>
> AFAIK, we have a lot more entities in org-entities with &PRETTY-NAME;.
> When I've entities I've used a pretty name over a numeric value when I
> found one. What's you'r opinion on that? Should we go for readable
> or aim towards replacing them with these numeric values?
>
> We should use only those named entities (above) which are valid in
> xhtml(5). So, yes, we should change to using numeric entites for any
> other than the above.
>
> Since Emacs knows both the codepoints and the hex for utf8 entities it
> may be fairly simple to change the HTML representations, though I
> don't like it. . .
When you refer above to "utf-8 entities", do you mean the named html
entities (e.g., <) or the actual utf-8 encoded characters?
I believe the named entities are encoding independent, while including
encoded characters in html output is fine -- although making sure the
page is served with the correct character encoding is another issue
entirely.
As to using a more extensive set of named entities, as i said above,
the problem is that the xhtml flavors don't support them, and I don't
see any advantage in making the exporter handle character encoding
differently based on ouput doctype.
As Nicolas would point out, you can always use a filter to map all the
entities in the output.
rick
next prev parent reply other threads:[~2014-03-18 13:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-16 0:33 [patch][ox-html] Stylistic changes Rasmus
2014-03-16 9:59 ` Nicolas Goaziou
2014-03-16 13:06 ` Rasmus
2014-03-17 2:17 ` Bastien
2014-03-17 17:01 ` Rick Frankel
2014-03-17 22:19 ` Rasmus
2014-03-18 0:35 ` Rick Frankel
[not found] ` <874n2w2n62.fsf@gmx.us>
2014-03-18 13:49 ` Rick Frankel [this message]
2014-03-18 19:46 ` Rasmus
2014-03-19 14:00 ` Rick Frankel
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=0d5c03b1f1e36a4250cbd11d467d3efe@mail.rickster.com \
--to=rick@rickster.com \
--cc=emacs-orgmode@gnu.org \
--cc=rasmus@gmx.us \
/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).