Re: [m17n-list] hi-itrans fix

[bd satish]

Hi,

> Of course, the idea is that imaginary/ alomst never typed glyphs can be 
> longer. Just like code length in information theory, which among other places 
> can be observed -to some extant- in the morse code.

I pondered over this and I agree with it. Optimize the mappings for
frequently-used cases, even though there may be conflicting mappings.
For those ambiguous mappings, there are alternate ways of entering
them (though involving more keystrokes), as Vishvas enumertated in a
previous message. I think this is a good compromise, so let's not
split into "-optitrans", but merge them into existing files.

As for the other changes in the patch, I'll review them when I have time.

--Satish


On 17 March 2013 23:55, विश्वासो वासुकेयः (Vishvas Vasuki)
<address@hidden> wrote:
>
> On Sun, Mar 17, 2013 at 2:17 PM, विश्वासो वासुकेयः (Vishvas Vasuki)
> <address@hidden> wrote:
>>
>>
>>>
>>> Having said the above, I'd probably wait for the other maintainers' or
>>> users' opinion on the matter.
>>
>> Sure - If you insist that you need to retain that old mapping, you may
>> also want to to fork and submit another mapping, rather than denying other
>> users an intuitive and convenient upgrade.
>
>
> @kenichi - Or you could rename (both icon files and the mapping) hi-itrans,
> kn-itrans and sa-itrans to *-optitrans if satish insists. Your call.
>
>
>
> --
> --
> Vishvas /विश्वासः
>