[Pkg-fonts-devel] Bug#762296: "Droid Sans Fallback" refers to three different files

Gunnar Hjalmarsson gunnarhj at ubuntu.com
Sun Sep 21 09:39:45 UTC 2014

On 2014-09-21 09:52, Christian PERRIER wrote:
> As of now, we have:
> bubulle at sesostris:~/src/debian/pkg-fonts/git/fonts-android(master) $ more debian/fonts-droid.install
> Droid*.ttf      usr/share/fonts/truetype/droid
> ...
> So basically : "let's install all fonts whose name starts with "Droid"
> ". How can we technically do "All fonts whose name starts with 'Droid'
> but two of them"
> Unless we, of course, list them all one by one....

They were listed previously.


> Maybe something like this
> override_dh_install:
> 	dh_install
> 	rm <path>/DroidSansFallback.ttf || true
> 	rm <path>/DroidSansFallbackLegacy.ttf || true

Would work too.

On 2014-09-21 10:28, Jonas Smedegaard wrote:
> How about this instead:
> Droid*.ttf      usr/share/fonts-droid/truetype

That would put away all of them. Did you really mean that?

> ...and then register DroidSansFull.ttf with alternatives system, 
> symlinking it into usr/share/fonts/truetype/droid/DroidSans.ttf

That's over my head, but it would be fine with me if it works.

However, I can't help suspecting that there is no real need to include
DroidSansFallback.ttf and DroidSansFallbackLegacy.ttf.

* Got the impression from https://bugs.debian.org/737105 that
  DroidSansFallbackFull.ttf is sufficient for Ghostscript too.

* Is the reporter of https://bugs.debian.org/714436 of the opinion that
  DroidSansFallback.ttf displays Korean characters better than
  fonts-nanum, or was he just not aware of the possibility to install
  the latter to fix his issue?

If I'm right, I suppose it would be preferable to not unnecessarily
complicate the package.

Gunnar Hjalmarsson

More information about the Pkg-fonts-devel mailing list