pool/fontconfig
SHA256
4
0
Fork 1
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

- DejaVu Sans, Droid Sans: added information why use BCI instead of

Browse Source 
autohinter

OBS-URL: https://build.opensuse.org/package/show/M17N/fontconfig?expand=0&rev=71
This commit is contained in:
Petr Gajdos 2012-05-28 14:58:31 +00:00 committed by Git OBS Bridge
parent 928ed08671
commit ddf79a1445
2 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
fontconfig.changes
View File

@ -9,7 +9,8 @@ Mon May 28 13:28:21 UTC 2012 - pgajdos@suse.com
------------------------------------------------------------------- -------------------------------------------------------------------
Mon May 28 11:53:08 UTC 2012 - pgajdos@suse.com Mon May 28 11:53:08 UTC 2012 - pgajdos@suse.com
- DejaVu Sans: added information why use BCI instead of autohinter - DejaVu Sans, Droid Sans: added information why use BCI instead of
autohinter
------------------------------------------------------------------- -------------------------------------------------------------------
Mon May 28 11:10:10 UTC 2012 - pgajdos@suse.com Mon May 28 11:10:10 UTC 2012 - pgajdos@suse.com

3
suse-hinting.conf
View File

@ -88,7 +88,8 @@
For example, for DejaVu Sans: when autohinter used, For example, for DejaVu Sans: when autohinter used,
there is unnatural big space between 'a' and 'z', there is unnatural big space between 'a' and 'z',
'd' and 'o' or 'o' and 'g' in string "lazy dog" 'd' and 'o' or 'o' and 'g' in string "lazy dog"
for smaller sizes. That doesn't show with BCI. for smaller sizes. That doesn't show with BCI.
Similarly for Droid Sans.
Because of this problem, better don't switch on Because of this problem, better don't switch on
the autohinter for the autohinter for