Debian Bug report logs - #714641
ttf-wqy-microhei: Incorrect advanceWidths in hmtx for composite glyphs.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: bungeman <bungeman@chromium.org>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: ttf-wqy-microhei: Incorrect adnvanceWidths in hmtx for composite glyphs.

Date: Mon, 01 Jul 2013 10:22:43 -0400

[Message part 1 (text/plain, inline)]

Package: ttf-wqy-microhei
Version: 0.2.0-beta-1ubuntu1
Severity: important

The issue appears when using ttf-wqy-microhei in Chromium (and possibly other
programs). See https://code.google.com/p/chromium/issues/detail?id=233851 for
the original report against Chromium.

The issue itself is that the version of ttf-wqy-microhei in the repository was
created with an old version of FontForge which created incorrect advanceWidths
in the htmx tables of this font. As a result many Korean glyphs have tiny
advance withs (1/8 of what they should be) and so stack on top of each other
when linear metrics are requested and used.

On the Chromium bug report there is attatched (see Comment #12) a patched
version of this font which is identical to the one currently in the repository,
but with these advance widths fixed (and the checksums updated). I will also
attach this patched version to this report.

It would be best to contact the original author (who should still have the
original component fonts, SFD sources, and build scripts which do not appear to
be available) to re-build this font with a newer version of FontForge. If this
cannot be done, using the patched version would at least alleviate a number of
issues for Korean users as it appears this is the inital default Korean font.



-- System Information:
Debian Release: wheezy/sid
  APT prefers ubuntu-precise-base
  APT policy: (600, 'ubuntu-precise-base')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.5-gg1236 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

ttf-wqy-microhei depends on no packages.

Versions of packages ttf-wqy-microhei recommends:
ii  fontconfig  2.8.0-3ubuntu9.1

ttf-wqy-microhei suggests no packages.

-- no debconf information

[wqy-microhei.ttc (application/octet-stream, attachment)]

Message #18 received at 714641@bugs.debian.org (full text, mbox, reply):

From: Anthony Fok <foka@debian.org>

To: Qianqian Fang <fangq@nmr.mgh.harvard.edu>, Qianqian Fang <fangqq@gmail.com>

Cc: 714641@bugs.debian.org

Subject: Fwd: Bug#714641: ttf-wqy-microhei: Incorrect advanceWidths in hmtx for composite glyphs.

Date: Mon, 9 Dec 2013 16:20:10 +0800

Dear Qianqian,

Congratulations to you and your family for the arrival of your new
baby boy Andy!
I just saw the news on your home page minutes ago, and saw the photos
on your Facebook page.  He is very handsome!  Congratulations!

I had tried to reach you earlier via Google Chat, but I guess you must
be very busy with the baby boy.  Anyhow, just so that you, the
upstream author of "WenQuanYi Micro Hei", are informed of the latest
bug report and fix regarding advanceWidths in the font, I am
forwarding the excellent bug report by Google and Chromium developer
Ben Wagner (Bungeman):

    ttf-wqy-microhei: Incorrect advanceWidths in hmtx for composite glyphs.
    http://bugs.debian.org/714641

Bungeman has diagnosed the problem, found the root cause, and provided
a patched font for the interim.  I used FontTools/TTX and cmp to
verify Bungeman's patched font file, and indeed, his patched version
is excellent, minimal yet comprehensive, and very clean indeed, much
better than what I would have been able to do.  So I will gladly use
font file that Bungeman provided to upload a new package.  I have
already discussed Zhengpeng Hou (Freeflying), who kindly gave me the
go-ahead to do whatever to update the package.

That is to say, please don't bother making a new upstream version just
to fix this bug.  I know you must be super busy right now both with
work and with looking after the baby.  My wife gave birth about a
little more than a year ago, and both of us went through many
sleepless nights especially in the first few months.  :-)

Cheers,
Anthony

======================= Forwarded Message =======================
From: bungeman <bungeman@chromium.org>
To: Debian Bug Tracking System <submit@bugs.debian.org>
Subject: ttf-wqy-microhei: Incorrect advanceWidths in hmtx for composite glyphs.
Date: Mon, 01 Jul 2013 10:22:43 -0400

Package: ttf-wqy-microhei
Version: 0.2.0-beta-1ubuntu1
Severity: important

The issue appears when using ttf-wqy-microhei in Chromium (and possibly other
programs). See https://code.google.com/p/chromium/issues/detail?id=233851 for
the original report against Chromium.

The issue itself is that the version of ttf-wqy-microhei in the repository was
created with an old version of FontForge which created incorrect advanceWidths
in the htmx tables of this font. As a result many Korean glyphs have tiny
advance widths (1/8 of what they should be) and so stack on top of each other
when linear metrics are requested and used.

On the Chromium bug report there is attached (see Comment #12) a patched
version of this font which is identical to the one currently in the repository,
but with these advance widths fixed (and the checksums updated). I will also
attach this patched version to this report.

It would be best to contact the original author (who should still have the
original component fonts, SFD sources, and build scripts which do not appear to
be available) to re-build this font with a newer version of FontForge. If this
cannot be done, using the patched version would at least alleviate a number of
issues for Korean users as it appears this is the initial default Korean font.



-- System Information:
Debian Release: wheezy/sid
  APT prefers ubuntu-precise-base
  APT policy: (600, 'ubuntu-precise-base')
Architecture: amd64 (x86_64)

Kernel: Linux 3.2.5-gg1236 (SMP w/32 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

ttf-wqy-microhei depends on no packages.

Versions of packages ttf-wqy-microhei recommends:
ii  fontconfig  2.8.0-3ubuntu9.1

ttf-wqy-microhei suggests no packages.

-- no debconf information

Message #27 received at 714641@bugs.debian.org (full text, mbox, reply):

From: Anthony Fok <foka@debian.org>

To: 714641@bugs.debian.org

Cc: Qianqian Fang <fangq@nmr.mgh.harvard.edu>

Subject: Bug#714641: ttf-wqy-microhei: Incorrect advanceWidths in hmtx for composite glyphs.

Date: Thu, 12 Dec 2013 09:10:37 +0800

Hello Bungeman,

Many thanks to your excellent and meticulous work in investigating the issue
and providing us with a corrected wqy-microhei.ttc file.

Upstream author Qianqian Fang replied and gave me the go-ahead to package
your patched version.  He had tried to fix it earlier, but the generating script
failed to run for some reason.  He will investigate an upstream update
if he can find the time soon.

The updated font package with your contribution was uploaded to
Debian's incoming queue some minutes ago, but I made other
housekeeping changes too, e.g. renaming the package to
fonts-wqy-microhei as per the Font Packages Naming Policy.  As such,
the package will require a manual check by the Debian FTPmaster Team,
so it will probably be a few more days yet before the updated package
appears in Debian mirrors.

Thanks again!

Cheers,
Anthony

Message #32 received at 714641-close@bugs.debian.org (full text, mbox, reply):

From: Anthony Fok <foka@debian.org>

To: 714641-close@bugs.debian.org

Subject: Bug#714641: fixed in fonts-wqy-microhei 0.2.0-beta-2

Date: Sat, 28 Dec 2013 00:00:05 +0000

Source: fonts-wqy-microhei
Source-Version: 0.2.0-beta-2

We believe that the bug you reported is fixed in the latest version of
fonts-wqy-microhei, which is due to be installed in the Debian FTP archive.

A summary of the changes between this version and the previous one is
attached.

Thank you for reporting the bug, which will now be closed.  If you
have further comments please address them to 714641@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Anthony Fok <foka@debian.org> (supplier of updated fonts-wqy-microhei package)

(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmaster@ftp-master.debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Thu, 12 Dec 2013 08:38:16 +0800
Source: fonts-wqy-microhei
Binary: fonts-wqy-microhei ttf-wqy-microhei
Architecture: source all
Version: 0.2.0-beta-2
Distribution: unstable
Urgency: low
Maintainer: Debian Fonts Task Force <pkg-fonts-devel@lists.alioth.debian.org>
Changed-By: Anthony Fok <foka@debian.org>
Description: 
 fonts-wqy-microhei - Sans-serif style CJK font derived from Droid
 ttf-wqy-microhei - transitional dummy package
Closes: 705180 714641
Changes: 
 fonts-wqy-microhei (0.2.0-beta-2) unstable; urgency=low
 .
   * Fix incorrect advanceWidths in hmtx for composite glyphs, which
     had caused Korean Hangul glyphs to stack on top of each other.
 .
     From the bug report:
 .
         The issue appears when using ttf-wqy-microhei in Chromium
         (and possibly other programs).
         See https://code.google.com/p/chromium/issues/detail?id=233851 for
         the original report against Chromium.
 .
         The issue itself is that the version of ttf-wqy-microhei in the
         repository was created with an old version of FontForge which
         created incorrect advanceWidths in the htmx tables of this font.
         As a result many Korean glyphs have tiny advance withs (1/8 of
         what they should be) and so stack on top of each other when linear
         metrics are requested and used.
 .
     Many thanks to Chromium developer Ben Wagner (Bungeman) for his
     excellent and meticulous work in investigating the issue and in
     creating a patched version of wqy-microhei.ttc to fix the issue.
     (Closes: #714641; LP: #1258520)
 .
     Also thanks to upstream author Qianqian Fang for giving us the go-ahead
     to use Bungeman's version, and will investigate an upstream update
     if he can find the time.
 .
     To facilitate adoption by other distributions, and for record keeping,
     here are the checksums of wqy-microhei.ttc before and after the patch:
 .
     Checksum of original wqy-microhei.ttc with incorrect hmtx advanceWidths:
      - MD5:    966af48e02884546677a2f762f6725b9
      - SHA1:   42467ef798a8f7bd8192a869ac7e05e17132c5c6
      - SHA256: e4bca8df123ce01b104780f576ea1a58b9a5ff1662a91124b6d3180cb6c88212
 .
     Checksum of wqy-microhei.ttc patched by Bungeman:
      - MD5:    a7ff47b49e15875c113ed77c491953ab
      - SHA1:   cd9c1b74f137db79c5fd403002cb1132d30f749b
      - SHA256: 2420e8078af796b19a3f6ef13de527a1a91c1e7171eea115926c614ced1009b3
 .
   * Acknowledge NMU of ttf-wqy-microhei 0.2.0-beta-1.1 by Aron Xu
     and contributed patch from 0.2.0-beta-1ubuntu1 by Steve Langasek
     (Debian Bug#660060)
 .
   * Acknowledge improvements to ttf-wqy-microhei in Ubuntu
     (0.2.0-beta-1.1ubuntu1 to 0.2.0-beta-1.1ubuntu4) by
     Iain Lane, Scott Ritchie and Gunnar Hjalmarsson:
      - New fontconfig file 65-wqy-microhei.conf
      - Mark as Multi-Arch: foreign (Closes: #705180)
 .
     However, in 65-wqy-microhei.conf, I decide to remove <prefer> for serif
     because WenQuanYi Micro Hei is a sans-serif font and there exist other
     real serif CJK fonts in the Debian repository.
 .
   * Learning from Christian Perrier in his update to fonts-wqy-zenhei:
      - Rename source package to "fonts-wqy-microhei" to fit the Font Packages
        Naming Policy.
      - Use dh minimal rules file
      - Update Standards to 3.9.5 (checked)
      - Bump debhelper compatibility to 9
      - Use xz extreme compression for deb packages
      - Use git for packaging: adapt Vcs-* fields
 .
   * Convert to machine-readable debian/copyright version 1.0
   * Change upstream home page to http://wenq.org/
   * Following the example of fonts-wqy-zenhei, set Debian Fonts Task Force
     as the Maintainer.
   * Add myself to the list of Uploaders
   * Last but not least, many thanks to original maintainer Zhengpeng Hou
     for generously allowing me do whatever I like to this package.  :-)
Checksums-Sha1: 
 fe2317f1efc2c7c98acb0b392cedcd2b869d8d3d 2152 fonts-wqy-microhei_0.2.0-beta-2.dsc
 28023041b22b6368bcfae076de68109b81e77976 2418536 fonts-wqy-microhei_0.2.0-beta.orig.tar.gz
 5eb2f339fc22b07642496f68d7c7bc93aeb84511 7601 fonts-wqy-microhei_0.2.0-beta-2.debian.tar.gz
 15b90c5aeba0f652557db86743101d0555d485bc 1605138 fonts-wqy-microhei_0.2.0-beta-2_all.deb
 e7316e6b7ed7914a40e4059652d128edc44e5dbf 5386 ttf-wqy-microhei_0.2.0-beta-2_all.deb
Checksums-Sha256: 
 d3ecc9b2b922f8571d58cbd3ea2bad724539ea4434903fa0e351598649db5317 2152 fonts-wqy-microhei_0.2.0-beta-2.dsc
 2802ac8023aa36a66ea6e7445854e3a078d377ffff42169341bd237871f7213e 2418536 fonts-wqy-microhei_0.2.0-beta.orig.tar.gz
 da2769cfd3750ab65b10e3f34c52eabf877c880a16c3ee8d8d38dba594585da0 7601 fonts-wqy-microhei_0.2.0-beta-2.debian.tar.gz
 507c8d3b5817e70b4076daf8dee9132a4b4f0123a7d6cd0581ca5d584e55eed9 1605138 fonts-wqy-microhei_0.2.0-beta-2_all.deb
 15fe006e558ee5d9a98387ffc763527d4b3dc8d6bf217a8924f5293eea88bf55 5386 ttf-wqy-microhei_0.2.0-beta-2_all.deb
Files: 
 d3aeff4efc9b457aaa404bbf3a427282 2152 fonts optional fonts-wqy-microhei_0.2.0-beta-2.dsc
 a124c5c6606f4f3b733d3477380e9d2f 2418536 fonts optional fonts-wqy-microhei_0.2.0-beta.orig.tar.gz
 bc911f8a0aca96d2ae215bcec27fdcd4 7601 fonts optional fonts-wqy-microhei_0.2.0-beta-2.debian.tar.gz
 922fc2e9b9efeaf50ad464cb1d7e57d0 1605138 fonts optional fonts-wqy-microhei_0.2.0-beta-2_all.deb
 38e532adee285ea80294f8d1a8a1fa9f 5386 oldlibs extra ttf-wqy-microhei_0.2.0-beta-2_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.15 (GNU/Linux)

iQIcBAEBCAAGBQJSqQfhAAoJEOolALQSxZrPlNQP/Az8cORWc6WSR1xzQa+zjaQM
5Hm/j038MT6k4/6Ax8NBR8e35KUvzURit5CDYpKRREJ9rOYvZQHerNusXuJsAOWI
yOT/6UZO1FKxmZPiQzA07LwBAgjDTmkBvb1Rf3Z7WPJoj+x8RPVResrMo5Vdqz4f
+xVoJb7I2OxrJ46oQ+kmHAIMMiaiFlPVKLbrJRZ4WWjSWR4R43pgvTrr2O84laad
yTargFoRwTmllmLu0IDDXhQp0M7YX6nmSTg2lF7RnkZlvgzAC9ZmKVtcehNHQ4vZ
JBQ3T/TQxyDKKWkxLY6zeQAhXinnHjcbhV+JwxzxuU6k0EgpxMigZpk075eI9mwd
c+CShUKT/pLNdhUeNfWNsCpK3IzwzMFX6SG/BCHgwxzEqVSf5wxqO/rAm2OJjmYf
p8BKHoAWHzH8K0M3+n9Q5nA41zTUCO5qjUlfawJABVZFJxm8/AdhrSmoqu1rvTKp
983fw6YCaI+xs+kVHrzn1+I+TrWBPoH363EETaq2uVvPC5cTe5hAEw7kWKnEL+MZ
eKYU0Ic+QaOYGjiZixA0HxyCY9XAsUOzXWy0lJYAARq780JGR4VYFqyfmTdG2WNm
iqivW4xvP6FztiDOJVBGs90DHSfRSlMN529BwgYNXb8CyiJ7Zdct3PFtSXCWAQkW
33GEtwIfs2cwN8K8B87a
=75Z9
-----END PGP SIGNATURE-----

Send a report that this bug log contains spam.