It seems that ctl looks for libmozpango-thaix.so in current directory. When I start mozilla in MOZILLA_FIVE_HOME like % ./mozilla it works fine. However, when I start mozilla from other place like % /export/home/mozilla/dist/bin/mozilla When I tried to type Thai characters, I get the following errors and no Thai characters are displayed. Cannot load module ./libmozpango-thaix.so: ld.so.1: /export/home/mozilla/dist/bin/mozilla-bin: fatal: ./libmozpango-thaix.so: open failed: No such file or directory Prabhat, can you take a look?

this will occurs only on Solaris, right? does it for Linux / Windows also ?

Hi Arthit, I've never tried this on Linux and Solaris.

i see, from bugzilla it indicates "SunOS", not "Solaris" -- thx :) does this needed to be added to Bug 65896 (mozilla's thai support) dependencies list?

I've put correct OS name and dependency. Thanks.

hi masaki, This is because of bad typo/hard-coding of path of libmozpango-thaix.so in the pango.modules file. Can you please apply this patch - thanks, Index: pango.modules =================================================================== RCS file: /cvsroot/mozilla/extensions/ctl/src/pangoLite/pango.modules,v retrieving revision 1.1 diff -r1.1 pango.modules 5c5 < ./libmozpango-thaix.so ThaiScriptEngineX PangoEngineShape PangoRenderX 3585-3675:* --- > libmozpango-thaix.so ThaiScriptEngineX PangoEngineShape PangoRenderX 3585-3675:*

Frank, can you r= please? And should I need to get sr= for extensions/ctl now? Sorry for asking many times....

Comment on attachment 87073 [details] [diff] [review] patch for pango.modules r=Roland.Mainz@informatik.med.uni-giessen.de

Comment on attachment 87073 [details] [diff] [review] patch for pango.modules sr=sfraser

checked into trunk. Thank you very much for review and super-review.

QA contact to Arthit.

tested with the patched binary (from sun netscape team), not see any issue. i can see Thai chars displayed. verified.

Comment on attachment 87073 [details] [diff] [review] patch for pango.modules a=chofmann for 1.0.1 add the fixed 1.0.1 keyword afterhecking in to the branch

checked into branch. Thanks for approval.

arthit.suriyawongkul@sun.com - can you verify this bug fix in 1.01 branch? When verified, pls replace fixed1.0.1 keyword with verified1.0.1. Thanks.