Hi Gürkan! Are you still actively maintaining ttf-georgewilliams? It looks like you haven't done anything about the important bug #395487, which is nearly a year old.
If you don't have time to maintain a package, you should file a
Request for Assistance or Intent to Orphan bug against the wnpp
pseudopackage, so that the Quality Assurance team can do their bit.
On Mon, Oct 30, 2006 at 08:57:46AM +0100, Gürkan Sengün wrote:
> I can not reproduce this problem.
Here is a transcript demonstrating the problem:
$ fc-match Monospace
Bitstream-Vera-Sans-Mono.ttf: "Bitstream Vera Sans Mono" "Roman"
$ sudo aptitude install ttf-georgewilliams
[...]
$ fc-match Monospace
Monospace-Medium.ttf: "Monospace" "Medium"
$
I believe this is an undesirable accident caused by ttf-georgewilliams
installing a font called "Monospace" instead of the more usual "Foo
Mono", where Foo is the name of a family such as Vera or Liberation.
> So your other monospace font is not usable anymore? Which one exactly?
> And can you think of a fix/patch?
I believe the appropriate fix is to change the font name from
"Monospace" to something like "GeorgeWilliams Mono". I'm not familiar
with the font subsystem, but I imagine this will involve changing the
metadata inside the file, NOT just the filename.
signature.asc
Description: Digital signature
