On 12/10/09 11:15, Raúl Núñez de Arenas Coronado wrote:
>
> Saluton Dominique :)
>
> Dominique Pellé<[email protected]> skribis:
>> Bram Moolenaar wrote:
>>> There currently is no tutor.eo file. Well, we could make a tutor.eo
>>> in latin-3. Latin-1 does not work, thus people using latin-1
>>> encoding will see tutor.eo with a few wrong characters. Not sure if
>>> this is better than not having a tutor.eo file.
> [...]
>> So to sum up, 3 possibilities:
>>
>> 1/ only utf-8 Esperanto files (as currently)
>> 2/ utf-8 + latin3
>> 3/ utf-8 + latin1 after transliterating ĉ -> cx, ĝ -> gx, etc.
>
> My personal opinion would be 1/, because I think that monobyte encodings
> should be actively deprecated, but:
>
> a) Vim actively supports monobyte encodings
> b) Using 2/ is "free", since Vim itself can convert the current
> tutor.eo.utf-8 to latin-3 without any effort.
>
> So, I think that using 2/ is not a bad idea, thinking of the people with
> monobyte encodings that already use latin-3 for Esperanto.
>
> 3/ is, IMHO, the worst option: I hate the "x notation" and moreover it
> breaks some alignments as you said. Latin-3 (or any other monobyte
> encoding for that matter) is bad enough...
>
For case 3/, this "X-code", even though widely used on computers and
allowing reversibility except in non-Esperantized proper names (since
the Esperanto alphabet does not include the letter X) is in competition
with the "H-code", which is part of the "official" grammar of Esperanto,
where it is said that "printers and typists who don't possess the glyphs
for the accented letters of Esperanto may use ch, gh, hh, jh, sh and u
instead of ĉ, ĝ, ĥ, ĵ, ŝ and ŭ respectively". This official
transliteration system, however, suffers from ambiguities in the cases
where c+h, g+h, h+h, j+h or s+h come together in the middle of a word
(e.g., a compound word), and it does not distinguish between ŭ
(consonant [w]) and u (vowel [u]).
I think solution 2/ is the right one for locales which do not use UTF-8
and, let's not forget it, for Vim binaries built with -multi_byte. The
latter case would of course require a pre-built tutor.eo.iso-8859-3
since a Vim with -multi_byte (and -iconv) can of course not convert from
UTF-8.
Best regards,
Tony.
--
Atlee is a very modest man. And with reason.
-- Winston Churchill
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
