On 2014-03-18 15:46, Rasmus wrote:
Rick Frankel writes:
On 2014-03-17 23:36, Rasmus wrote:
When you refer above to "utf-8 entities", do you mean the named html
entities (e.g., <) or the actual utf-8 encoded characters?
The latter. Do M-x describe-char on such an character. Emacs will
tell yo
Rick Frankel writes:
> On 2014-03-17 23:36, Rasmus wrote:
> When you refer above to "utf-8 entities", do you mean the named html
> entities (e.g., <) or the actual utf-8 encoded characters?
The latter. Do M-x describe-char on such an character. Emacs will
tell you the code points. My conjectu
On 2014-03-17 23:36, Rasmus wrote:
Rick Frankel writes:
On Mon, Mar 17, 2014 at 11:19:27PM +0100, Rasmus wrote:
Hi Rick,
Rick Frankel writes:
> On Mon, Mar 17, 2014 at 03:17:10AM +0100, Bastien wrote:
>> Hello,
>>
>> Nicolas Goaziou writes:
>>
>> > So if the change is only stylistic, I see
On Mon, Mar 17, 2014 at 11:19:27PM +0100, Rasmus wrote:
> Hi Rick,
>
> Rick Frankel writes:
>
> > On Mon, Mar 17, 2014 at 03:17:10AM +0100, Bastien wrote:
> >> Hello,
> >>
> >> Nicolas Goaziou writes:
> >>
> >> > So if the change is only stylistic, I see no reason to break
> >> > compatibility
Hi Rick,
Rick Frankel writes:
> On Mon, Mar 17, 2014 at 03:17:10AM +0100, Bastien wrote:
>> Hello,
>>
>> Nicolas Goaziou 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 us
On Mon, Mar 17, 2014 at 03:17:10AM +0100, Bastien wrote:
> Hello,
>
> Nicolas Goaziou 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 wh
Hello,
Nicolas Goaziou 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-stri
Nicolas Goaziou writes:
>> Second, for some reason ox-html replaces a couple of entities by
>> itself—rather than letting org-entities do it—but uses hex references
>> (or whatever), rather than a "nice" HTML character entity. The second
>> patch fixes this. (I naively assume that there is not
Hello,
Rasmus writes:
> Here's a couple of minor changes for ox-html.
Thank you.
> First, I dropped the references to HTML5 hgroup since apparently W3
> did the same¹.
Applied.
> Second, for some reason ox-html replaces a couple of entities by
> itself—rather than letting org-entities do it
