Bastien <b...@altern.org> writes:

> Achim Gratz <strom...@nexgo.de> writes:
>
>> It also requires that the HTML is output in UTF-8.  I would
>> (reluctantly, I don't really know much about how this would work)
>> suggest that the export should always be done with symbolic entities and
>> a post-export filter should then replace them with whatever the
>> particular backend prefers.  Does that work?
>
> This seems a good idea to me.  Nicolas, do you think so?

Yes. We can add a defconst associating each HTML entity to its utf-8
counterpart, and add a filter to :filter-final-output in freemind
back-end definition (not to `org-export-filter-final-output-functions',
which is user-oriented).

Any taker? Jambunathan?


Regards,

-- 
Nicolas Goaziou

Reply via email to