From mboxrd@z Thu Jan 1 00:00:00 1970 From: Yasushi SHOJI Subject: Re: [PATCH] Table continuation strings Date: Sun, 22 Dec 2013 06:59:45 +0900 Message-ID: <87iouhc1bi.wl@dns1.atmark-techno.com> References: <87ppqn9i9j.fsf@gmail.com> <87lhzec2sh.wl@dns1.atmark-techno.com> <87k3eyk200.fsf@gmail.com> Mime-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:38608) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuUeP-0008Q9-8i for emacs-orgmode@gnu.org; Sat, 21 Dec 2013 17:04:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1VuUaY-0006di-Di for emacs-orgmode@gnu.org; Sat, 21 Dec 2013 17:00:08 -0500 Received: from plane.gmane.org ([80.91.229.3]:60906) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1VuUaY-0006a9-7R for emacs-orgmode@gnu.org; Sat, 21 Dec 2013 17:00:02 -0500 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1VuUaV-00050V-S5 for emacs-orgmode@gnu.org; Sat, 21 Dec 2013 22:59:59 +0100 Received: from p654782.hkidff01.ap.so-net.ne.jp ([121.101.71.130]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Dec 2013 22:59:59 +0100 Received: from yashi by p654782.hkidff01.ap.so-net.ne.jp with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 21 Dec 2013 22:59:59 +0100 In-Reply-To: <87k3eyk200.fsf@gmail.com> 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: emacs-orgmode@gnu.org HI, At Sat, 21 Dec 2013 10:05:35 +0100, Nicolas Goaziou wrote: > > Yasushi SHOJI writes: > > > The thing I don't understand is the reason all Japanese entries have > > `:utf-8'. Would you kindly enlighten me the relationship among the > > followings: > > > > - transtion coding key (ie :utf-8, :default, :html) > > - your current buffer coding system > > - `buffer-file-coding-system' and friends > > Coding keys are related to export back-ends. Therefore :latex entry will > be used for `latex' export, :html for `html' export, `:utf-8' for both > text (utf-8) and odt export, and so on. > > As its name suggests, :default key is used as a fallback value when no > appropriate property is found. It makes up for a handy shortcut when > some strings are identical. Ah, OK. Those coding keys are for the back-ends to select proper strings, not for the string encoding. 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? > Coding system is a different thing. When `org-export-coding-system' is > non-nil, it will be used as the coding system for output (note that some > export back-ends override this behaviour). Otherwise, output will have > the same encoding as the source buffer. 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. 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?). Back-ends uses `org-export-coding-system' if set, otherwise use the current buffer coding system. If my understanding is ok, all entries of Japanese translation should have :default instead of :utf-8. Thanks, -- yashi