Re: Thai issue for 2.0 timeframe

Jean-Marc Desperrier wrote:
> [email protected] wrote:
>> I've talked with Axel Hecht and he think the appropriate group should
>> be .general, not .18n.
>>
>> [...] Current workaround is
>> Thai Community Edition [2] which patched by using extra library such as
>> ICU [4][5].
>>
>> [...] Some Thai people may hear
>> about Firefox coolness and directly to grab official build and discover
>> there can't handle line-breaking.
>>
>> The sustain solution for this problem is waiting for infrastructure
>> change by using Cairo for rendering. This change will coming in Firefox
>> 3.0, so we will miss this in 2.0 timeframe.
> 
> This is not that guaranteed to change in Cairo/FF 3. It depends on what 
> ROC implements and he said in the comment of his blog :
> http://weblogs.mozillazine.org/roc/archives/2006/02/post_1.html
> 
> "It might make sense to eventually get line-breaking information from 
> UPA. However, ultimate control has to stay with nsTextFrame so we can do 
> hyphenation, CSS 'whitespace', and other effects. Given that, the 
> simplest thing to do for now, while we get everything else working, is 
> to keep on getting line-break information the way we currently do."
> 
> I think it's worth insisting that FF 3 needs UPA level line-breaking.

I think that it's worth to keep in mind that we need hooks to support 
thai-enabling extensions, if the general world wouldn't want to suffer 
from a recognizable perf hit here.

But yes, I have the recollection that roc didn't promise to fix thai 
with his stuff.

>> I propose some idea for this problem
>> - In long term, delay official Thai localization build (in [1]) until
>> we solve line-breaking problem in trunk
>> - In short term, use unofficial or Community Edition builds instead but
>> point to these build clearly on any related Mozilla webpages. Now we
>> have central Firefox Thai site [6] that links to all available builds
>> but I think host this page on Mozilla web site is better.
>>
>> Can this possible for Mozilla process?
> 
> I really think that what makes sense is to have the official Thai 
> release include the patch you have now in the Community Edition, even if 
> they are not in trunk.
> I hope you have success in convincing MoFo that something needs to be 
> done in that line.

I personally don't think that we should make official patched builds. 
That said, I haven't heard back from my own inquiry on priorities for 
thai in relation to firefox milestones, so I'm still in the open.
I do think though that we may want to discuss a way of adding this 
community edition to the all.html page.
But that is just my opinion, not a mozilla.com product placement thing.

Axel