On 03/03/2013 06:47 PM, Jambunathan K wrote:
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
Against.
Character set of a web document is determined by the /outermost/
entity. The outermost entity available is the web
Robert Klein klein...@mpip-mainz.mpg.de writes:
Personally I prefer to use utf-8, too. However, I've had a number of
uncooperative web servers (and operators), where I had to deliver
documents in 8859-1.
Mhh... yes, that's exactly what happened to me on a server.
Thanks for confirming it
Jambunathan K writes:
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
It is becoming more rare these days, but still possible that the
document encoding cannot be UTF-8 for whatever reason. So if it's not
unduly complicating
On Sun, Mar 3, 2013 at 11:58 PM, Achim Gratz strom...@nexgo.de wrote:
Jambunathan K writes:
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
I am not sure if it effects our project. We use org and Emacs for
Nagarjuna G writes:
I am not sure if it effects our project. We use org and Emacs for
post-processing our wiki pages to produce html pages. Currently we are
getting proper exports since we get the output in utf-8. As far as I
know, using utf-8 will support other coding systems as well. Am I
Achim Gratz writes:
Jambunathan K writes:
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
It is becoming more rare these days, but still possible that the
document encoding cannot be UTF-8 for whatever reason. So if
Robert Horn rjh...@alum.mit.edu writes:
Achim Gratz writes:
Jambunathan K writes:
Always use utf-8 for HTML export (No support for other coding systems).
For or against. Please register your views.
It is becoming more rare these days, but still possible that the
document encoding cannot
Jambunathan K kjambunat...@gmail.com writes:
My proposal and patch to always use utf-8 stands annulled then.
Okay. I guess we shall go with the workaround solution for
ox-freemind.el, then. Can you provide a patch for this?
Thanks!
--
Bastien
