|
|
added two sample fonts for the sample doc where you can test it. |
|
2006-01-12 00:03
|
|
|
2006-01-12 00:04
|
|
|
2006-01-12 00:04
|
|
|
|
Seeing the font names in doc, i would say this doc has been saved with a build based on freetype 2.1.9 which has a bug on win32. Win32 builds use now freetype 2.1.10 which corrects font loading. Please test again with docs fully created and saved with the 11-01 build |
|
|
tested here and its fixed |
|
|
its still there. look at the screenshot |
|
2006-03-07 23:08
|
Fonts.png (19,403 bytes) |
|
|
do not know what you have done, 'cause the font name you get look as if you do not use the freetype dll provided with my snapshot |
|
|
Otherwise the font names returned for these fonts with the *correct* dll match the expected behavior. |
|
|
i am of course using you dll as i have no other. what i do: unpack the snapshot, run scribus. |
|
|
The screenshot you uploaded show that the snapshot you used use freetype 2.1.9 whereas i use freetype 2.1.10. Have tested last snapshot here, works as expected. |
|
|
could i have the wrong freetype version on linux. let me test. win is definitely your dll |
|
|
echo "=media-lib/freetype-2.1.10" >> /etc/portage/package.keywords emerge -u freetype |
- Anonymous
