From: Robert Horn <rjhorn@alum.mit.edu>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Always use utf-8 for HTML export (No support for other coding systems)
Date: Sun, 03 Mar 2013 18:51:30 -0500 [thread overview]
Message-ID: <m3sj4c2gal.fsf@quad.robs.office> (raw)
In-Reply-To: <8738wcban3.fsf@Rainer.invalid>
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 it's not
> unduly complicating things, I'd suggest to avoid prescribing the UTF-8
> encoding for any and all exports.
>
Chinese law mandates use of GB-18030, not UTF-8. The two are losslessly
and unambiguously convertable, but their bit encodings are different.
They are accustomed to dealing with UTF-8 from other parts of the world,
but might prefer to generate local pages in compliance with the law.
R Horn
rjhorn@alum.mit.edu
next prev parent reply other threads:[~2013-03-03 23:51 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-02 18:05 Support Freemind/Freeplane export Jambunathan K
2013-03-02 21:36 ` Nicolas Goaziou
2013-03-02 22:29 ` Bastien
2013-03-02 22:49 ` Bastien
2013-03-03 8:12 ` Achim Gratz
2013-03-03 8:39 ` Bastien
2013-03-03 8:52 ` Nicolas Goaziou
2013-03-03 15:03 ` Jambunathan K
2013-03-03 16:25 ` Jambunathan K
2013-03-03 21:00 ` Nicolas Goaziou
2013-03-03 17:32 ` Bastien
2013-03-03 17:47 ` Always use utf-8 for HTML export (No support for other coding systems) Jambunathan K
2013-03-03 18:28 ` Achim Gratz
2013-03-03 18:43 ` Nagarjuna G
2013-03-03 19:39 ` Achim Gratz
2013-03-03 23:51 ` Robert Horn [this message]
2013-03-04 4:14 ` Jambunathan K
2013-03-04 7:21 ` Bastien
2013-03-04 8:04 ` Robert Klein
2013-03-04 19:01 ` Bastien
2013-03-03 17:44 ` Support Freemind/Freeplane export Jambunathan K
2013-03-03 18:20 ` Bastien
2013-03-04 1:33 ` François Pinard
2013-03-10 15:52 ` Scott Randby
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=m3sj4c2gal.fsf@quad.robs.office \
--to=rjhorn@alum.mit.edu \
--cc=Stromeko@nexgo.de \
--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).