Bug#917291: marked as done (libharfbuzz0b: wrong glyph for chinese word 小 (U+5C0F))
Your message dated Sat, 14 May 2022 10:19:07 +0200
with message-id <Yn9l+0id5k6gf7oq@ramacher.at>
and subject line Re: Bug#917291: libass9 issue
has caused the Debian Bug report #917291,
regarding libharfbuzz0b: wrong glyph for chinese word 小 (U+5C0F)
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)
--
917291: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=917291
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: Debian Bug Tracking System <submit@bugs.debian.org>
- Subject: libharfbuzz0b: wrong glyph for chinese word 小 (U+5C0F)
- From: Tommy Wu <tommy@teatime.com.tw>
- Date: Tue, 25 Dec 2018 22:57:15 +0800
- Message-id: <154574983509.1216584.18097695557496310045.reportbug@mail.teatime.com.tw>
Package: libharfbuzz0b
Version: 2.3.0-1
Severity: normal
Dear Maintainer,
U+5C0F (小) is not render correctly after version 2.0.0.
It work fine for version under 1.9.0.
-- System Information:
Debian Release: buster/sid
APT prefers testing
APT policy: (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386, armhf
Kernel: Linux 4.18.0-3-amd64 (SMP w/8 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=zh_TW.UTF-8 (charmap=UTF-8), LANGUAGE=en_US:en (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Init: systemd (via /run/systemd/system)
Versions of packages libharfbuzz0b depends on:
ii libc6 2.28-2
ii libfreetype6 2.9.1-3
ii libglib2.0-0 2.58.1-2
ii libgraphite2-3 1.3.12-1
libharfbuzz0b recommends no packages.
libharfbuzz0b suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
- To: tommy@teatime.com.tw, 917291-done@bugs.debian.org
- Subject: Re: Bug#917291: libass9 issue
- From: Sebastian Ramacher <sramacher@debian.org>
- Date: Sat, 14 May 2022 10:19:07 +0200
- Message-id: <Yn9l+0id5k6gf7oq@ramacher.at>
- In-reply-to: <20181226064049.B60E.6ADF6260@teatime.com.tw>
- References: <154574983509.1216584.18097695557496310045.reportbug@mail.teatime.com.tw> <20181226064049.B60E.6ADF6260@teatime.com.tw>
Version: 1:0.16.0-1
On 2018-12-26 06:40:50 +0800, Tommy Wu wrote:
>
> I think this is not bug in harfbuzz 2.x, it should be the libass9 issue, the API change after harfbuzz 2.0.0, it's not compatible with libass 0.14 now.
> recompile libass9 with --disable-harfbuzz option will solve this issue.
Since 0.14.0 a bunch of glpyh rendering fixes landed in libass. If the
issue still exists in 0.16.0, please reopen the bug report.
Cheers
--
Sebastian Ramacher
--- End Message ---
Reply to: