The ttf-tahoma-replacement pacakges and ttf-symbol-replacement pacakges
are now part of the wine1.2 package in Karmic
** Changed in: wine (Ubuntu)
Status: In Progress => Fix Released
--
Wine should install (some) fonts system wide in a separate package
https://bugs.launchpad.net/bugs/2477
I've started work on this. I believe the best way is to create a
separate "ttf-tahoma-replacement" package containing tahoma.ttf and
tahomabd.ttf. Just in case a user manually installs the real tahoma,
I'm going to rename them tahoma-replacement.ttf and tahomabd-
replacement.ttf, and then give th
Thank you for posting this bug. Meny people prefere aliased fonts and
for then choosing the Wine Tahoma would be the best choice (now they
have to install msttfcore fonts and even with them they do not have good
rendering).
Also msttfcore fonts have no free license and as such not allowed for
dist
The license is ok. See:
http://www.gnome.org/fonts/#Final_Bitstream_Vera_Fonts
Basically, we're fine as long as the name doesn't contain Bitstream
Vera.
Is DejaVu Sans what is substituted now when a website asks to render text with
tahoma and it's unavailable?
--
Wine should install (some) f
Two things could be wrong with that font
1. WineTahoma is a Bitstream Vera Sans derivative, it must have the same
license.
See the copyright notice in the ttf file:
Copyright (c) 2004 Larry Snyder, Based on Bitstream Vera Sans Copyright (c)
2003 by Bitstream, Inc. Font renamed in accordance with
