Re: [bug-gettext] ISO-8859-8 and bidi (was Re: [Translation-i18n] gnulib, bison-runtime and texinfo charset)

[Vladimir 'φ-coder/phcoder' Serbinenko]

On 27.03.2012 20:11, Eli Zaretskii wrote:
>> The biggest problems are the lack of sane migration path and that it
>> affects long-term storage.
> The migration path is clear: craft a UTF-8 encoded logical-order
> he.po.
It's not that easy. I expect the original code and accompanying
translations to continue to evolve and having one side in logical and
another side in visual order makes updates tricky. This would amount to
a needless fork and increase in continuous supplied effort.
Or do you propose to change he.po for texinfo to UTF-8
>> So what do you think about having bidi
>> in gettext which would kick-in when the output is on a crappy terminal?
> I think this was asked some time ago, and Bruno said he didn't
> consider it a gettext business.  But I may be mistaken; in any case,
> I'll let Bruno speak for himself.
I'd usually agree with this. But the blocker/troubles/increased
collaboration and maintenance cost seem to result in worse situation
that just having a workaround in gettext. Without this it risks postpone
UTF-8 migration for an undetermined while

P.S: any reason for the total lack of Hebrew TP mailing list? Why I
don't doubt your (your email is listed as primary for the whole team)
ability to forward mail to translators, having ML would provide a
convenient public record.


-- 
Regards
Vladimir 'φ-coder/phcoder' Serbinenko

signature.asc
Description: OpenPGP digital signature