Re: gdi32-related commit between 0.9.57<->0.9.58broken .NET2/Systems.Windows.Forms
--- On Fri, 28/3/08, Lei Zhang <[EMAIL PROTECTED]> wrote: > From: Lei Zhang <[EMAIL PROTECTED]> > Umm, I have friends who are font fanatics that have > thousands of fonts > installed on their system. If they can do that on Windows, > they > certainly should be able to do that on Linux. Are you > suggesting we a) > limit ourselves to only support what ships with Windows, > and ignore > all other fonts out there, or b) create a white list for > every known > font out there? I don't have an answer to that - in a different machine, I have maybe a 100 chinese fonts of various level of obcurity :-). but it is going to be a nightmare for the wine developers to allow random fonts to break some part of it. __ Sent from Yahoo! Mail. A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html
Re: gdi32-related commit between 0.9.57<->0.9.58broken .NET2/Systems.Windows.Forms
On Fri, Mar 28, 2008 at 11:12 AM, Hin-Tak Leung <[EMAIL PROTECTED]> wrote: > I think blacklisting is not a good approach - what one wants is really > "white-listing": > given microsoft only ships a certain number of fonts, wine should provide > emulation/substitutions of *only* those fonts fron known open-source > alternatives, > rather than expose the whole of fontconfig-available fonts to win32 > applications. > And applications should only expect to get those known MS fonts (or > clones/substitutes). Umm, I have friends who are font fanatics that have thousands of fonts installed on their system. If they can do that on Windows, they certainly should be able to do that on Linux. Are you suggesting we a) limit ourselves to only support what ships with Windows, and ignore all other fonts out there, or b) create a white list for every known font out there? > OTOH, ukai (or one of its Arphic derivative sibings) is fairly critical for > most > chinese-reading person :-). > > I am not sure "There is a fixed version of ukai" - from the codeweaver wiki > and freedesktop's web site, I have the latest ukai release via redhat, and > the wiki seems > to suggests a non-debian mod older ukai to replace a debian-modified one. > So my finger-pointing tendency would say that somehow a debian ukai > modification which breaks gdiplus has got into freedesktop uptream... AFAIK, the bad version of the ukai font is 20060928. It shiped with Ubuntu Feisty [1], Gutsy [2], and FC 8 [3]. Possibly with other distros as well, I have not done an exhaustive search. Just don't use that version and you should be fine. [1] http://packages.ubuntu.com/feisty/ttf-arphic-ukai [2] http://packages.ubuntu.com/gutsy/ttf-arphic-ukai [3] http://rpm.pbone.net/index.php3/stat/4/idpl/5312345/com/cjkunifonts-ukai-0.1.20060928-4.fc8.noarch.rpm.html
Re: gdi32-related commit between 0.9.57<->0.9.58broken .NET2/Systems.Windows.Forms
--- On Thu, 27/3/08, Dmitry Timoshkov <[EMAIL PROTECTED]> wrote: > "Vitaliy Margolen" <[EMAIL PROTECTED]> > wrote: > > > Looks like a time to start blacklisting fonts then. If > the font is invalid > > and does not work even on windows yet it is available > in the system - that's > > the only thing Wine can do. Or just contact all > distros to remove it. Or > > request packagers to refuse installing Wine if said > font found in the system. > > Black listing the fonts is not an appropriate > fix/workaround. There is > already a fixed version of ukai.ttf, and a broken one was > causing problems > in a lot of native programs besides Wine. I think blacklisting is not a good approach - what one wants is really "white-listing": given microsoft only ships a certain number of fonts, wine should provide emulation/substitutions of *only* those fonts fron known open-source alternatives, rather than expose the whole of fontconfig-available fonts to win32 applications. And applications should only expect to get those known MS fonts (or clones/substitutes). OTOH, ukai (or one of its Arphic derivative sibings) is fairly critical for most chinese-reading person :-). I am not sure "There is a fixed version of ukai" - from the codeweaver wiki and freedesktop's web site, I have the latest ukai release via redhat, and the wiki seems to suggests a non-debian mod older ukai to replace a debian-modified one. So my finger-pointing tendency would say that somehow a debian ukai modification which breaks gdiplus has got into freedesktop uptream... __ Sent from Yahoo! Mail. A Smarter Inbox http://uk.docs.yahoo.com/nowyoucan.html
Re: gdi32-related commit between 0.9.57<->0.9.58broken .NET2/Systems.Windows.Forms
"Vitaliy Margolen" <[EMAIL PROTECTED]> wrote: > Looks like a time to start blacklisting fonts then. If the font is invalid > and does not work even on windows yet it is available in the system - that's > the only thing Wine can do. Or just contact all distros to remove it. Or > request packagers to refuse installing Wine if said font found in the system. Black listing the fonts is not an appropriate fix/workaround. There is already a fixed version of ukai.ttf, and a broken one was causing problems in a lot of native programs besides Wine. -- Dmitry.
