emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

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: Mon, 23 Dec 2013 10:09:44 +0100	[thread overview]
Message-ID: <87k3ewhr1j.fsf@gmail.com> (raw)
In-Reply-To: <878uvcamoh.wl@dns1.atmark-techno.com> (Yasushi SHOJI's message of "Mon, 23 Dec 2013 01:13:34 +0900")

Hello,

Yasushi SHOJI <yashi@atmark-techno.com> writes:

> That means that whenever your-choice-of-coding-system can handle the
> "characters" for the translation string, meaning that the coding
> system has code points for all of the characters of the translation
> string and Emacs can convert between them, it is free to use any
> character for the output, right?
>
> If one wants to use French, she sets the current buffer coding system
> to any coding system which can handle French and set the language
> option as "fr".  In that case, her/his org buffer should already have
> French characters in it, there is no need for translation string to be
> strictly ASCII only when you export with plain / ascii, no?

There's a limitation: if you use Latin1 characters (e.g. when you write
in French), you cannot export to text/ascii anymore.

So, if, for some reason, you really need to export to ascii only, but
still need to write in french, you have to be careful not to use any of
these Latin1 characters, in particular in translated strings. Similarly,
Japanese :ascii entries could be written using romanji.

I don't know to what extent it is useful, though.

> I'm checking exporters I use, including plain text and html, but it
> doesn't seems to go wrong. But I really needs some help for other
> back-ends. I'll post a patch for testing if anyone's interested in.

Good idea.

You can also set entries to :default and provide a different :latex
value, if required.


Regards,

-- 
Nicolas Goaziou

next prev parent reply	other threads:[~2013-12-23  9:09 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
2013-12-22 16:13           ` Yasushi SHOJI
2013-12-23  9:09             ` Nicolas Goaziou [this message]
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=87k3ewhr1j.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

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).