[Bug 1077343] Re: !pdfTeX error: pdflatex (file ../latex/lthuni.enc): cannot open encoding file f or reading
The bug should belong to latex-fonts-thai-tlwg. And I don't think putting absolute path in the map file is neccessary. 'kpathsea' can do the file search for you, given that the target file is properly installed in one of its search paths. I guess latex-fonts-thai-tlwg in 12.04 is 1:0.4.17-1ubuntu1, right? Let's check if the Ubuntu-specific patch has done the job correctly. (I am the Debian maintainer, not Ubuntu. That's all I can comment.) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1077343 Title: !pdfTeX error: pdflatex (file ../latex/lthuni.enc): cannot open encoding file f or reading To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1077343/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
From comment #7 postinst called with unknown argument 'triggered' Wait.. The last sympthom was still the same. It's not about trigger change, then. This problem is caused by tex-common generated postinst. (See http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648697 for more info.) It's supposed to be fixed since tex-common 3.4. It's weird that this still persists. Let's reassign this bug to tex-common, though. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
Ah, I see. tex-common in Precise is still 2.10. How can we get newer one? The latest version is 3.13. And thailatex requires tex-common (= 3.4). How did the build pass in the first place? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
On Wed, Oct 3, 2012 at 4:38 PM, Jan Groenewald j...@aims.ac.za wrote: On 3 October 2012 10:34, Theppitak Karoonboonyanan t...@linux.thai.netwrote: The latest version is 3.13. And thailatex requires tex-common (= 3.4). How did the build pass in the first place? I am testing texlive-backports on precise, though other users experience this problem on an upgrade to quantal as well. And tex-common version in the backports is? (Sorry, I have no idea about versions in Ubuntu.) The point is that thailatex should be built against tex-common (= 3.4) to get rid of the postinst error. For quantal, I've checked the 0.5.0-2 binary deb [1], and the buggy code has been removed from postinst. So, the bug should be gone. [1] ftp://ftp.ubuntu.com/ubuntu/pool/universe/t/thailatex/thailatex_0.5.0-2_all.deb Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
On Wed, Oct 3, 2012 at 7:01 PM, Jan Groenewald j...@aims.ac.za wrote: If I install that thailatex deb manually wiht dpkg, then tex-common manages to finish configuring. You mean the deb from quantal? That's because it's built with tex-common in quantal, not because tex-common in older system works it out. Will this fix make it into the texlive-backports PPA for precise? Please make sure tex-common is also upgraded in the backports. Otherwise, when one rebuilds the package from source, it would fail to upgrade again. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
On Wed, Oct 3, 2012 at 8:38 PM, Jan Groenewald j...@aims.ac.za wrote: This says tex-common 3.13 : https://launchpad.net/~texlive-backports/+archive/ppa OK. That's more than sufficient. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1027661] Re: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10
Just seen this via Debian QA page. So, it seemed the initial problem was caused by an old tex-common, as fixed here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648697 Then, the last trigger problem after the rebuild should be caused by the new texlive files being moved from /usr/share/texmf-texlive to /usr/share/texlive/texlive-dist, and thailatex trigger watch was not updated accordingly. It's weird that I cannot reproduce this with Debian squeeze-wheezy upgrade, though. So, I can't be sure if my guess is correct. If I'm correct, this patch should fix it. Could you try it out? If it works, I'll upload the fix to Debian and let's request for a sync to Ubuntu. diff --git a/debian/triggers b/debian/triggers index 32e4f57..78d80cd 100644 --- a/debian/triggers +++ b/debian/triggers @@ -1 +1 @@ -interest /usr/share/texmf-texlive/tex/generic/babel/babel.sty +interest /usr/share/texlive/texmf-dist/tex/generic/babel/babel.sty ** Bug watch added: Debian Bug tracker #648697 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=648697 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1027661 Title: thailatex and texlive-latex-base errors when upgrading from 12.04 - 12.10 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thailatex/+bug/1027661/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 704250] Re: missing dependency on correct input system
On Thu, Jul 28, 2011 at 9:24 PM, Paisa Seeluangsawat 704...@bugs.launchpad.net wrote: Installing either ibus-table-thai or ibus-m17n seems to solve the problem. I don't know which one is preferred. Last time I tried ibus on Fedora, I was not happy with either of these. ibus-table-thai dumbly maps keys to characters, without any sequence validation, while ibus-m17n relies on preedit mode, which is totally not belong for Thai. Fortunately, surrounding text support has been added to ibus for some time. [1] This enables development of context-sensitive validating input method, just like what gtk-im-libthai currently does. Problem is I can't find a time slot to do it yet. [1] https://bugzilla.redhat.com/show_bug.cgi?id=435880 Meanwhile, ibus-table-thai should be fine. Or if the surrounding text API has been deployed by ibus-m17n, that would be nice. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ ** Bug watch added: Red Hat Bugzilla #435880 https://bugzilla.redhat.com/show_bug.cgi?id=435880 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/704250 Title: missing dependency on correct input system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/language-support-input-th/+bug/704250/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294545] Re: Problem with showing some Lao Unicode char
** Also affects: pango via https://bugzilla.gnome.org/show_bug.cgi?id=616495 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/294545 Title: Problem with showing some Lao Unicode char -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680464] Re: Purisa fonts have junk entry in liga table
The new upstream version fixing this bug has been released and uploaded to Debian sid. Please import thaifonts-scalable 1:0.4.15-1 from Debian to close this bug. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680464 Title: Purisa fonts have junk entry in liga table -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 680464] Re: Purisa fonts have junk entry in liga table
Thanks for the report. I've committed the fix upstream. It will be available in next upstream version. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/680464 Title: Purisa fonts have junk entry in liga table -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539008] Re: Microsoft Sans Serif maps to Thai font even on european setups
So, please sync thaifonts-scalable 0.4.14-1 from sid/squeeze which has been marked as addressing this bug. (Sorry, I noticed LP had already recognized this, so, I thought the sync would be done next. But that didn't happen.) -- Microsoft Sans Serif maps to Thai font even on european setups https://bugs.launchpad.net/bugs/539008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539008] Re: Microsoft Sans Serif maps to Thai font even on european setups
Sorry that I can't verify this myself. My system is still mono-free. So, I'll just take your reports. Loma doesn't provide accented Latin characters. So, it's up to applications how they handle the missing glyphs. Web browsers and OO.o take the glyphs from other fonts, while, according to your report, Winforms/Mono apps don't. That may explains. OK, as the workaround is valid, I'll apply it upstream. Hope to release it before Maverick is frozen. -- Microsoft Sans Serif maps to Thai font even on european setups https://bugs.launchpad.net/bugs/539008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539008] Re: Microsoft Sans Serif maps to Thai font even on european setups
Does this twist for 89-ttf-thai-tlwg-synthetic.conf help for your case? match target=pattern test name=lang compare=contains stringth/string /test test qual=any name=family compare=eq stringMS Sans Serif/string stringMicrosoft Sans Serif/string /test edit name=family mode=append binding=same stringLoma/string /edit /match -- Microsoft Sans Serif maps to Thai font even on european setups https://bugs.launchpad.net/bugs/539008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 539008] Re: Microsoft Sans Serif maps to Thai font even on european setups
OK. Thanks. So, I'll consider applying this to upstream source. I've tested it with HTML with 'lang' tag. It works, but I'm not sure if it's the case in general. German web sites without 'lang=de' tag may still suffer from this issue, despite the twist. -- Microsoft Sans Serif maps to Thai font even on european setups https://bugs.launchpad.net/bugs/539008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 294545] Re: Problem with showing some Lao Unicode char
This is apparently pango's bug. Please follow up upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=616495 ** Bug watch added: GNOME Bug Tracker #616495 https://bugzilla.gnome.org/show_bug.cgi?id=616495 -- Problem with showing some Lao Unicode char https://bugs.launchpad.net/bugs/294545 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 509919] Re: Hundreds of packages depend on libthai and libthai-data
- The vulnerability has been fixed in 0.1.12-1ubuntu0.2 [1] So, you might have already updated it before reporting this bug. [1] https://launchpad.net/ubuntu/+source/libthai/0.1.12-1ubuntu0.2 - The vulnerability was later proved to be ineffective in libthai [2]. Instead, it's pango/glib that's vulnerable. So, if you want to get rid of all packages with security flaw, just remove pango instead. :P [2] https://bugzilla.redhat.com/show_bug.cgi?id=554416 - Regarding the dependency, nothing can be done in libthai to change this. It's pango that pulls it in, according to upstream decision. Before the merge, it used to be shipped as a separate third-party plug- in. Well, if you ask for the re-split, one can ask for other language engines to be split, too. So, this should be reassigned to pango, for its maintainers to decide. ** Bug watch added: Red Hat Bugzilla #554416 https://bugzilla.redhat.com/show_bug.cgi?id=554416 -- Hundreds of packages depend on libthai and libthai-data https://bugs.launchpad.net/bugs/509919 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 407680] Re: failed to start SCIM on Thai language session.
This is not scim-thai problem. It's the problem with libx11 Thai locale management, which has been fixed since libx11 1.1.99.1. http://bugs.freedesktop.org/show_bug.cgi?id=15719 And another problem with SCIM events has also been solved in libx11 1.2.2. http://bugs.freedesktop.org/show_bug.cgi?id=16475 (Sorry, I don't know which Ubuntu release ships which libx11 version.) See more detailed discussion here: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520509 So, does this bug still exist in Ubuntu 9.04? ** Bug watch added: freedesktop.org Bugzilla #15719 https://bugs.freedesktop.org/show_bug.cgi?id=15719 ** Bug watch added: freedesktop.org Bugzilla #16475 https://bugs.freedesktop.org/show_bug.cgi?id=16475 ** Bug watch added: Debian Bug tracker #520509 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=520509 -- failed to start SCIM on Thai language session. https://bugs.launchpad.net/bugs/407680 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434054] Re: Waree font too high compared to Tahoma
Then, why not making it installed by default? Without both ttf-tahoma-replacement and the fallback rule, What font is chosen for Tahoma? (It's still Waree for my system, Debian sid). -- Waree font too high compared to Tahoma https://bugs.launchpad.net/bugs/434054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434054] Re: Waree font too high compared to Tahoma
The fallback is to serve browsing Thai web pages that explicitly use Tahoma, as Waree is the closest match we have. However, I didn't aware of the existence of ttf-tahoma-replacement package, as I uploaded this package at Debian, where ttf-tahoma- replacement is not available. Feel free to patch it as you think suitable for Ubuntu. I can apply that to Debian once ttf-tahoma-replacement is available there. BTW, there is a newer package version (1:0.4.13-1) of thaifonts-scalable in Debian unstable which ships 2 LP bug fixes from upstream (LP #387872, #313427). It should be nice to have it in Ubuntu as well, if it's still allowed for Karmic. Otherwise, just patching the current version should be fine. -- Waree font too high compared to Tahoma https://bugs.launchpad.net/bugs/434054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434054] Re: Waree font too high compared to Tahoma
For the record, anyway, ttf-tahoma-replacement provides only limited set of glyphs. It won't serve Thai people. Removing the rule will result in fontconfig implicit fallback for missing glyphs when rendering Thai pages, which can end up with any font, depending on what is installed. Fortunately, it's Waree for my system. But for others, I don't know. But it's not that serious. Waree itself is not the exact replacement anyway. So, I'm OK with the fallback removal. But please keep other synthesizing rules in the file intact. They are still useful for Thai people. -- Waree font too high compared to Tahoma https://bugs.launchpad.net/bugs/434054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 434054] Re: Waree font too high compared to Tahoma
Wait. On a second thought, I don't think the removal is necessary. Users can get Tahoma replacement from ttf-tahoma-replacement by installing it. And Waree won't be effective, except for missing glyphs. Only on Tahoma missing is Waree fallen back to. What's wrong with that? -- Waree font too high compared to Tahoma https://bugs.launchpad.net/bugs/434054 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387872] Re: 90-ttf-thai-tlwg-synthetic.conf is not valid against fonts.dtd schema
This bug has been fixed upstream in 0.4.13: http://linux.thai.net/node/178 Please sync the new package from Debian to close this bug. Thanks. -- 90-ttf-thai-tlwg-synthetic.conf is not valid against fonts.dtd schema https://bugs.launchpad.net/bugs/387872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 313427] Re: [jaunty] some font cannot show characters with diacritics
This is caused by the wrong spline direction, which makes synthetic glyph emboldening becomes shrinking instead. You can notice this by using an extremely large point size, like 72pt. The diacritics are still there, at very very small size. This has been addressed upstream in version 0.4.13: http://linux.thai.net/node/178 (But the real faces for Purisa have also been added to gain some adjustment possibility, anyway.) Please sync the new package from Debian unstable to close this bug. Thanks. -- [jaunty] some font cannot show characters with diacritics https://bugs.launchpad.net/bugs/313427 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 387872] Re: 90-ttf-thai-tlwg-synthetic.conf is not valid against fonts.dtd schema
Note for verification, the config file has been renamed from 90-ttf- thai-tlwg-synthetic.conf to 89-ttf-thai-tlwg-synthetic.conf, i.e. with prefix 90 decreased to 89). -- 90-ttf-thai-tlwg-synthetic.conf is not valid against fonts.dtd schema https://bugs.launchpad.net/bugs/387872 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
[EMAIL PROTECTED]:~$ echo $XMODIFIERS [EMAIL PROTECTED]:~$ ... but If I switch session to thai everything work fine. ??? Ah.. So, I've been attacking a different problem than yours. All my patches were for Thai locale, not English. Using English locale for Thai environments needs some cautions, as it's for English, not for Thai. English locale doesn't set any IM option through im-switch. So, all apps just use the default null values. For GTK+, the default input method is Simple, which is mainly for English and for European accents composition. (I don't know if it's reasonable to try to add Thai support to it, but we can try it later.) Your available choices are scim-thai and gtk-im-libthai. You can install either on your system, up to your preference, and then configure im-switch to choose it. To se what options are available for you: $ im-switch -l ... === The available input method configuration files are: default default-xim none scim scim-bridge scim-immodule scim_xim th-gtk-im-libthai th-xim === In case you prefer gtk-im-libthai: $ im-switch -a th-gtk-im-libthai Or if you prefer scim: $ im-switch -a scim-immodule This needs a new login to take effect. Note that with gtk-im-libthai, you won't benefit from any input sequence check for non-GTK+ apps. Those apps will use XIM, which doesn't check anything on en_US locale. Only GTK+ apps benefit from it. If you want to also use Thai XIM upon en_US locale, you will need to set LC_CTYPE environment to th_TH.UTF-8. For example, in your ~/.bashrc: export LC_CTYPE=th_TH.UTF-8 And finally, note that all GTK+ text entry widgets have an Input Method context menu, which allows you to choose a different input method on the fly. All described above are for setting the default one for your session. -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 273856] Re: Thai language input not work correctly
On Sat, Oct 4, 2008 at 4:02 PM, Theppitak Karoonboonyanan [EMAIL PROTECTED] wrote: English locale doesn't set any IM option through im-switch. So, all apps just use the default null values. For GTK+, the default input method is Simple, which is mainly for English and for European accents composition. (I don't know if it's reasonable to try to add Thai support to it, but we can try it later.) This may be reasonable. The problem seems to be introduced in GTK+ 2.14, as GTK+ 2.12 on Debian sid doesn't have this problem. And after checking the source, I find an extra step in the key event filtering, where European dead key sequences are always assumed, which is not the case for Thai. I'll try to verify if it's the real culprit. Regards, -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Re: [Bug 273856] Re: Thai language input not work correctly
On Sat, Oct 4, 2008 at 5:23 PM, Theppitak Karoonboonyanan [EMAIL PROTECTED] wrote: This may be reasonable. The problem seems to be introduced in GTK+ 2.14, as GTK+ 2.12 on Debian sid doesn't have this problem. And after checking the source, I find an extra step in the key event filtering, where European dead key sequences are always assumed, which is not the case for Thai. I'll try to verify if it's the real culprit. And it is. GtkIMContextSimple in GTK+ 2.14 has rearranged its compose table based on Unicode normalization, and with this, inserted a new step to check composition algorithmically. And this extra step assumes all Unicode non-spacing marks as dead keys, including Thai combining characters. And it tries to reorder the marks with the base character, something common in European input method. But this creates invalid Thai strings, which are thus rejected. I've come up with a patch against GTK+ to redefine the dead keys, so that only non-spacing marks for relevant scripts are counted. This allows Thai text input (in a very primitive way) on English locale again. -- Theppitak Karoonboonyanan http://linux.thai.net/~thep/ ** Attachment added: 092_im_simple_deadkey.patch http://launchpadlibrarian.net/18217714/092_im_simple_deadkey.patch -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
Reopen the bug, as it's not over yet. And reassign it to gtk+2.0. ** Changed in: gtk+2.0 (Ubuntu Intrepid) Sourcepackagename: libx11 = gtk+2.0 Status: Fix Released = Confirmed -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
GNOME #555000 filed: http://bugzilla.gnome.org/show_bug.cgi?id=555000 -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
For those of you who are interested in testing the patch, I've created the patched debs here: http://linux.thai.net/~thep/ubuntu/source/gtk+2.0/ -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
pango-libthai has been obsolete for a long time, after being integrated upstream. Please file another bug against language-support-extra-th to remove the dependency. Regarding the input, please make sure you have upgraded libx11-6 and libx11-data to at least 2:1.1.5-1ubuntu1. If you have already upgraded and the problem still exists, please also describe what application you were using, as well as the selected input method. Thanks. -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
[EMAIL PROTECTED]:/home/isra# aptitude show libx11-data Package: libx11-data State: installed Automatically installed: no Version: 2:1.1.5-1ubuntu1 So, I suppose the same is true for libx11-6, right? And could you try echo $XMODIFIERS command in a terminal? -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
Assigned to libx11. ** Changed in: libx11 (Ubuntu) Sourcepackagename: scim = libx11 -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 273856] Re: Thai language input not work correctly
Arne, The problem with SCIM is that it only works on non-Thai locales. You may try it again under th_TH.UTF-8 locale to see the problem people reported here. In fact, I have proposed a patch against libx11 in Freedesktop #16475 [1] to fix this. Just waiting for it to be checked-in. Unfortunately, it doesn't seem to happen before Intrepid release. [1] https://bugs.freedesktop.org/show_bug.cgi?id=16475 Thai XIM also has some pending bugs with UTF-8 locale: it rejects all combining characters, as my previous work in Xlib assumed too much about the multi-byte strings. (Only TIS-620 locale was available at that time.) And another patch has been proposed in Freedesktop #12759 [2] for this. [2] https://bugs.freedesktop.org/show_bug.cgi?id=12759 And finally, a minor bug in Thai XIM: it stops filtering input sequences when NumLock/CapsLock is on, as reported, with proposed patch, in Freedesktop #12517 [3]. [3] https://bugs.freedesktop.org/show_bug.cgi?id=12517 All the three patches are against libx11. So, you can safely assign this bug to it, IMO. All the patches are tested in my custom debs. [4] And I would appreciate if they get into Intrepid in time, and if Ubuntu help polish and push them upstream. [4] ftp://ftp.debianclub.org/debclub/pool/main/libx/libx11/libx11_1.1.5-2thep1.dsc -- Thai language input not work correctly https://bugs.launchpad.net/bugs/273856 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 194759] [NEW] Autohint can now be turned on for Thai
Public bug reported: Binary package hint: openoffice.org In Bug #35305, turning off autohinting was proposed because Thai fonts in Ubuntu were not suitable for hinting at that time. However, with thaifonts-scalable in hardy, it can now be turned on, and the quality is now acceptable. That is, the following code can be removed from /usr/lib/openoffice/program/soffice: # turn off autohinting for thai (Ubuntu #35305). case $LANG in th*) SAL_AUTOHINTING_PRIORITY=0 export SAL_AUTOHINTING_PRIORITY esac Besides, if possible, syncing thaifonts-scalable 0.4.9-1 from Debian would bring some new fonts to Thai users, too. ** Affects: openoffice.org (Ubuntu) Importance: Low Assignee: Chris Cheney (ccheney) Status: In Progress -- Autohint can now be turned on for Thai https://bugs.launchpad.net/bugs/194759 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99655] pango-libthai ships nothing
Public bug reported: Binary package hint: pango-libthai pango 0.1.6-3 in feisty ships nothing but document files in /usr/share/doc. It must be from my build rule with hard-coded module version specific to debian, and different from ubuntu. This certainly needs an urgent fix before feisty release. I'll prepare the fix soon. ** Affects: pango-libthai (Ubuntu) Importance: Undecided Status: Unconfirmed -- pango-libthai ships nothing https://launchpad.net/bugs/99655 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 99655] Re: pango-libthai ships nothing
I have put the updated package at: http://linux.thai.net/~thep/ubuntu/source/pango-libthai/ Please check and update it. Thanks. -- pango-libthai ships nothing https://launchpad.net/bugs/99655 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 43393] Re: Doesn't show thai language correctly
I haven't seen a screenshot demonstrating the symptom. But I guess it's the same problem as I heard in local communities, which is caused by too high rank of TlwgMono font in fontconfig matching. That makes Thai text to always be displayed with Monospace font by default. If so, it could be fixed by syncing thaifonts-scalable 0.4.5-2 from Debian Etch. In that package, I have provided fontconfig info so that correct Thai fonts are selected. -- Doesn't show thai language correctly https://launchpad.net/bugs/43393 -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
