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-1ubuntu
On Wed, Oct 3, 2012 at 8:38 PM, Jan Groenewald 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
tem
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.
On Wed, Oct 3, 2012 at 4:38 PM, Jan Groenewald wrote:
>
> On 3 October 2012 10:34, Theppitak Karoonboonyanan
> wrote:
>
>> 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 tex
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 Ubunt
>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 suppos
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/te
nsitive
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, t
** 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
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.ne
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 lig
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:
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 rep
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 fon
Does this twist for 89-ttf-thai-tlwg-synthetic.conf help for your case?
th
MS Sans Serif
Microsoft Sans Serif
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/294
- 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'
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.cg
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 notificati
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 hig
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, i
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
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
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
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 becaus
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 Ubunt
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-
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 notifica
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 ste
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
> [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
> [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 no
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 u
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 mailin
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
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
If dropping pango-libthai in favor of upstream version is to be taken,
just make pango Build-Depend on libthai-dev, and its configure script
will try to detect it.
--
pango-libthai ships nothing
https://launchpad.net/bugs/99655
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://li
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/
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 relea
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 b
40 matches
Mail list logo
