From: Nicolas Goaziou <n.goaziou@gmail.com>
To: Yasushi SHOJI <yashi@atmark-techno.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] Table continuation strings
Date: Sun, 22 Dec 2013 09:20:57 +0100 [thread overview]
Message-ID: <878uvdjnyu.fsf@gmail.com> (raw)
In-Reply-To: <87iouhc1bi.wl@dns1.atmark-techno.com> (Yasushi SHOJI's message of "Sun, 22 Dec 2013 06:59:45 +0900")
Hello,
Yasushi SHOJI <yashi@atmark-techno.com> writes:
> Ah, OK. Those coding keys are for the back-ends to select proper
> strings, not for the string encoding.
This is also related to string encoding. You will get garbage if you
insert a string containing characters outside the encoding you use to
save the file, won't you?
> Then, is there any restriction with HTML back-ends? Why does it need
> numeric character reference instead of just plain characters, if the
> coding system is not a concern?
See above. You may want to save your html file in a different encoding
than UTF-8. IIUC, numeric character reference are more generic.
> Correct me if I'm wrong. My understainding is as follows: All
> translation strings is in `emacs-internal' coding system, since it is
> defined in .el. A org file ready to be exported has a coding system
> specific to the buffer, ie. utf-8, iso-latin-1, euc-jp, etc.
Correct.
> Org export back-ends get a strings for the back-ends from the
> translation table when appropriate. At that time Emacs converts the
> strings encoding system to match the buffer encoding system (or does
> Emacs convert all encoding when it writes to file?).
The latter. The output in concatenated into a single string, which is
then inserted in the target buffer (and saved to a file, if needed).
> Back-ends uses `org-export-coding-system' if set, otherwise use the
> current buffer coding system.
Some back-ends also use their own variable (e.g.
`org-html-coding-system').
> If my understanding is ok, all entries of Japanese translation should
> have :default instead of :utf-8.
:default instead of :utf-8 means Org will use these translations also
for LaTeX, HTML and ASCII export. If you think that is correct, then we
can switch to :default, indeed.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2013-12-22 8:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-30 0:44 [PATCH] Table continuation strings Thomas S. Dye
2013-10-30 8:28 ` Michael Strey
2013-10-30 10:15 ` Nicolas Goaziou
2013-10-30 15:59 ` Thomas S. Dye
2013-12-21 3:15 ` Yasushi SHOJI
2013-12-21 9:05 ` Nicolas Goaziou
2013-12-21 21:59 ` Yasushi SHOJI
2013-12-22 8:20 ` Nicolas Goaziou [this message]
2013-12-22 16:13 ` Yasushi SHOJI
2013-12-23 9:09 ` Nicolas Goaziou
2014-01-02 8:15 ` Yasushi SHOJI
2014-01-02 8:29 ` Yasushi SHOJI
2014-01-03 8:59 ` Nicolas Goaziou
2014-01-03 8:59 ` Nicolas Goaziou
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=878uvdjnyu.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=yashi@atmark-techno.com \
/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).