From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: org-html-use-unicode-chars breaks source code blocks
Date: Fri, 07 Aug 2015 11:56:31 +0200 [thread overview]
Message-ID: <87zj23h168.fsf@gmx.us> (raw)
In-Reply-To: 87zj26gart.fsf@nicolasgoaziou.fr
Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
> Hello,
>
> Rasmus <rasmus@gmx.us> writes:
>
>> Vladimir Alexiev <vladimir.alexiev@ontotext.com> writes:
>>
>>> I've set org-html-use-unicode-chars since I want ox-html to leave IRIs as IRIs.
>>> But this has another undesired effect: it breaks <URL> references in code,
>>> since it doesn't escape the brackets.
>>
>> I think this should only apply to entities. Any reason to do it on the
>> whole output? Nicolas?
>
> It was introduced in e8742b78e0a982a7fca0bf25b4f3551be58660ef. I'm not
> sure about the intent of this variable but I tend to think it is about
> beautification of the output. As a consequence, it isn't meant to apply
> to Org entities specifically.
>
> However, as you noticed, it is not subtle enough to apply
> `mm-url-decode-entities' on the full output. It needs to be applied
> piece-wise wherever that makes sense. `org-html-entity' is one case.
> Maybe `org-html-plain-text' for another one.
OK. I added it to plain-text as well. What is an example of a plain-text
that would need beautification?
Should we apply it to snippets as well? In the spirit of "beautification"
it would make sense, but it could also seem like a bad choice.
Rasmus
--
Slowly unravels in a ball of yarn and the devil collects it
next prev parent reply other threads:[~2015-08-07 9:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-04 13:40 org-html-use-unicode-chars breaks source code blocks Vladimir Alexiev
2015-08-04 17:35 ` Rasmus
2015-08-04 18:37 ` Nicolas Goaziou
2015-08-07 9:56 ` Rasmus [this message]
2015-08-07 10:37 ` Nicolas Goaziou
2015-08-07 10:57 ` Rasmus
2015-08-08 21:09 ` Andreas Leha
2015-08-09 19:32 ` Sebastien Vauban
2015-08-16 13:48 ` Bastien Guerry
2015-08-16 18:47 ` Brady Trainor
2015-08-17 8:01 ` Nicolas Goaziou
2015-08-17 8:41 ` Brady Trainor
2015-08-17 16:44 ` Rasmus
2015-08-16 14:03 ` Bastien Guerry
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=87zj23h168.fsf@gmx.us \
--to=rasmus@gmx.us \
--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).