[Pkg-fonts-devel] RFC: how to name alternative font package?

["Arne Götje (高盛華)"]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi list,

I'm in the process of preparing a new release of my
ttf-arphic-{ukai|uming} packages.
I want to change the fonts from multiple ttf files with only a few
glyphs different to one TTC (Truetype Collection) file which produce
multiple "virtual" fonts. This will save a lot of disk space...

Now, I found a problem. TTC fonts only work on Pango and QT4 (>= 4.3.0)
applications. So, for GTK2 apps in sid, this is not a problem, but KDE3
will not be able to use the fonts and neither is OO.o 2.2.1

KDE4 will be able to use them... and KDE4 should be released in late
October according to their website.

Also, for CJK TeX users, I will probably need to provide a seperate
package with PS fonts inside.

Now, I'm thinking of releasing multiple versions of the same fonts:
 1. the old way with having multiple ttf files which only differ in some
glyphs but use a lot of disk space.
 This will be the ttf-arphic-{ukai|uming} fonts.
 2. the new way with a single TTC file for GTK2 and QT4 apps
 Question: how to name the packages?
 3. a postscript version for CJK TeX users
 Question: how to name the packages?

Should TTC fonts still be named ttf-$foundry-$font ? or rather
ttc-$foundry-$font ?
How about Postscript fonts for TeX?

Any suggestions?

Cheers
Arne
- --
Arne Götje (高盛華) <arne at linux.org.tw>
PGP/GnuPG key: 1024D/685D1E8C
Fingerprint: 2056 F6B7 DEA8 B478 311F  1C34 6E9F D06E 685D 1E8C
Key available at wwwkeys.pgp.net.   Encrypted e-mail preferred.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFGhMbybp/QbmhdHowRAg1tAJwOx8B8sHBTqn6hYVp/GapotdZojQCg6438
JHKPY6rSjMCVuWQkeAGDvQM=
=J0ww
-----END PGP SIGNATURE-----