Hello,
Yasushi SHOJI ya...@atmark-techno.com writes:
Right. It is doable, but for Japanese I don't think anyone wants to
do it, or at least not a ordinal usage, IMO.
OK.
Ok, I've checked what I can. It seems working at least for me. Let's
patch up the `org-export-dictionary' to see it
Hello,
Yasushi SHOJI yasushi.sh...@atmark-techno.com writes:
And here is a patch for the rest of Japanese translation strings.
Applied. Thank you.
Regards,
--
Nicolas Goaziou
Hi,
At Mon, 23 Dec 2013 10:09:44 +0100,
Nicolas Goaziou wrote:
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,
Hi,
At Thu, 02 Jan 2014 17:15:17 +0900,
Yasushi SHOJI wrote:
At Mon, 23 Dec 2013 10:09:44 +0100,
Nicolas Goaziou wrote:
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
Hello,
Yasushi SHOJI ya...@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
Hello,
Yasushi SHOJI ya...@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
Hi Nicolas,
At Sun, 22 Dec 2013 09:20:57 +0100,
Nicolas Goaziou wrote:
Yasushi SHOJI ya...@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
Hello,
Yasushi SHOJI ya...@atmark-techno.com 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
HI,
At Sat, 21 Dec 2013 10:05:35 +0100,
Nicolas Goaziou wrote:
Yasushi SHOJI ya...@atmark-techno.com 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
Hi,
At Wed, 30 Oct 2013 11:15:36 +0100,
Nicolas Goaziou wrote:
t...@tsdye.com (Thomas S. Dye) writes:
Patch includes table continuation strings for several languages.
Translations all from the internet. Caveat emptor.
Applied. Thank you.
+ (ja :utf-8 前ページから続く)
[...]
+
Hi Tom,
t...@tsdye.com writes:
Patch includes table continuation strings for several languages.
Translations all from the internet. Caveat emptor.
The German strings are fine.
Best regards
--
Michael Strey
http://www.strey.biz
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
Patch includes table continuation strings for several languages.
Translations all from the internet. Caveat emptor.
Applied. Thank you.
+ (ja :utf-8 前ページから続く)
[...]
+ (ja :utf-8 次ページに続く)
These will not be very helpful, though, as
Nicolas Goaziou n.goaz...@gmail.com writes:
Hello,
t...@tsdye.com (Thomas S. Dye) writes:
Patch includes table continuation strings for several languages.
Translations all from the internet. Caveat emptor.
Applied. Thank you.
+ (ja :utf-8 前ページから続く)
[...]
+ (ja :utf-8
Aloha all,
Patch includes table continuation strings for several languages.
Translations all from the internet. Caveat emptor.
All the best,
Tom
From 0c551e51f5eff759957a415d7d29a830b43631d2 Mon Sep 17 00:00:00 2001
From: Thomas Dye t...@tsdye.com
Date: Tue, 29 Oct 2013 14:39:48 -1000
Subject:
14 matches
Mail list logo
