Marco Cimarosti <[EMAIL PROTECTED]> writes: > UTF-Morse - "Bringing Unicode in the telegraph age!" ... > U+0041 ..-- .- LATIN CAPITAL LETTER A [2] > U+0042 ..-- -... LATIN CAPITAL LETTER B [2] > U+0043 ..-- -.-. LATIN CAPITAL LETTER C [2] > U+0044 ..-- -.. LATIN CAPITAL LETTER D [2] > U+0045 ..-- . LATIN CAPITAL LETTER E [2] > U+0046 ..-- ..-. LATIN CAPITAL LETTER F [2] > U+0047 ..-- --. LATIN CAPITAL LETTER G [2]
Interestingly, there is a Japanese morse language that conflicts with these allocation: http://www5b.biglobe.ne.jp/~a1c/CW_J.htm (SJIS encoded) Perhaps it would be useful to have a morse language selection indicator in UTF-Morse a'la the succesful ISO-2022-JP. The problem could also be defered to higher level frameworks, such as the flexible MIME framework: Content-Type: text/plain; charset=utf-morse+japanese This seems like a serious problem that could delay deployment of UTF-Morse.
