<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">三浦です。<br>
<br>
Pythonで、日本語のよみをromajiにするライブラリを作っています。<br>
変換は、辞書を使っています。<br>
<a class="moz-txt-link-freetext" href="https://launchpad.net/unihandecode">https://launchpad.net/unihandecode</a><br>
<br>
内部的には、KAKASIというライブラリを参考に実装しています。<br>
<br>
<a class="moz-txt-link-freetext" href="http://blog.kenichimaehashi.com/?article=13048363750">http://blog.kenichimaehashi.com/?article=13048363750</a><br>
<br>
Javaで実装されたKAKASIもあるので、JOSMプラグインにできるかもしれません。<br>
<br>
三浦<br>
<br>
<br>
On 2012年12月03日 11:47, Daniel Kastl wrote:<br>
</div>
<blockquote
cite="mid:CABXBSH-hZNsuzsS4AdFDfV+oTv7kvwhq1WarJ5ha542jM+DBqg@mail.gmail.com"
type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-2022-JP">
<div>Hi Douglas</div>
<div><br>
</div>
Right, it can't be 100% automated.
<div>So when I meant JOSM plugin, I thought that the automatic
conversion will just be a proposal and needs to be corrected
manually afterwards. But at least there would be an interface
and tags didn't need to be added manually. And some conversions
should be possible without problem, for example Kana to Romaji. </div>
<div>I know that Kanji can be ambiguous, but when you type you
actually type the reading already and then convert it to Kanji.
So the plugin had to listen to the key strokes before converting
to Kanji.</div>
<div><br>
</div>
<div>From personal mapping experience I just feel that adding
multiple name tags with more or less identical content is
annoying work. If it would be possible to do everything fully
automated, it could be better processed afterwards. But because
it needs user interaction and verification, it's better to have
easy to use tools to make correct tagging easier.</div>
<div><br>
</div>
<div>Daniel</div>
<div><br>
</div>
<div><br>
<div class="gmail_quote">On Mon, Dec 3, 2012 at 11:31 AM,
Douglas Perkins <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:douglas@dperkins.org" target="_blank">douglas@dperkins.org</a>></span>
wrote:<br>
<blockquote class="gmail_quote">ダグラスです。<br>
<br>
It's very nice to see the internationalization support
progress!<br>
<br>
Automatically creating name:ja_kana, name:ja_rm, and name:en
is probably not going to work. Japanese kanji have
ambiguous readings, so you can't go from them to a phonetic
reading automatically. And you can't go from a phonetic
reading to kanji, because there are many kanji with the same
reading. Also, there are different ways of writing words in
romaji, and currently there is not consenus on what
name:ja_rm should be. We probably cannot decide on just one
romanization style, because different businesses or places
may have their own preferred spelling. Trying to automate
the entry process for these tags (except for name, which can
be an exact copy of name:ja), may well lead to a large
number of errors.<br>
<br>
残念ですが、name:ja だけと知っても、name:ja_kana も name:ja_rm も name:en
が分からない可能性があります。<br>
漢字の読み方がそんなに簡単なことではないですし。<br>
ローマ字のスタイルはいろいろがありますし。<br>
そうすれば、一つ一つ考えないとエラーが多くなるかもしれません。</blockquote>
</div>
</div>
</blockquote>
<br>
</body>
</html>