From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nicolas Goaziou Subject: Re: [PATCH] Table continuation strings Date: Mon, 23 Dec 2013 10:09:44 +0100 Message-ID: <87k3ewhr1j.fsf@gmail.com> References: <87ppqn9i9j.fsf@gmail.com> <87lhzec2sh.wl@dns1.atmark-techno.com> <87k3eyk200.fsf@gmail.com> <87iouhc1bi.wl@dns1.atmark-techno.com> <878uvdjnyu.fsf@gmail.com> <878uvcamoh.wl@dns1.atmark-techno.com> Mime-Version: 1.0 Content-Type: text/plain Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56283) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv1Vy-0006aR-2u for emacs-orgmode@gnu.org; Mon, 23 Dec 2013 04:09:35 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Vv1Vs-0000jW-Gh for emacs-orgmode@gnu.org; Mon, 23 Dec 2013 04:09:30 -0500 Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:36317) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Vv1Vs-0000j0-6z for emacs-orgmode@gnu.org; Mon, 23 Dec 2013 04:09:24 -0500 Received: by mail-we0-f176.google.com with SMTP id p61so4592534wes.21 for ; Mon, 23 Dec 2013 01:09:23 -0800 (PST) In-Reply-To: <878uvcamoh.wl@dns1.atmark-techno.com> (Yasushi SHOJI's message of "Mon, 23 Dec 2013 01:13:34 +0900") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Yasushi SHOJI Cc: emacs-orgmode@gnu.org Hello, Yasushi SHOJI 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