#40 Typography: Too much default LEADING

open
nobody
5
2014-06-11
2013-03-05
nomnex
No

1.1.0 version on Linux Fedora

the default LEADING of the font is too important. It render the font unusable with any text document.

I write technical manuals and reports using LibreOffice Writer. I have to set a fix spacing value to have an acceptable line spacing in my body text. It make impossible to insert inline images (e.g. icons in PNG format).

Please, please, compare the default leading--in any application--of the following fonts: MS Times New Roman, MS Arial, Liberation Serif, Liberation Sans, Adobe Minion, etc. Those fonts have a small default LEADING. Custom paragraph styles can allow more spacing when necessary.

I guess the default LEADING of the STIX font is caused by the support of LATIN + some other languages,and math characters, but it breaks the outstanding quality of this font in text only documents (reports, letters, thesis, etc).

It is easy to set a custom text paragraph style with an increased leading value,when the need arises.

In addition, I would like to use the font in some other applications. They do not allow a line spacing setting, e.g. web browser, text editor, desktop wiki.

I do not know much about fonts but I have noticed that most of the open source which support several languages have too much leading. They looks unprofessional in text document, and they uses too much paper.

It really like this font and its license. I hope you can do something about the leading. Thank you.

Discussion

  • This is even getting worse with the STIX Word fonts. There is a WIP patch in Gecko to prefer OS/2 sTypo* metrics to hhea ascent/descent when the USE_TYPO_METRICS flag is set or when Open Type MATH font is available. This works with STIX Word (has a MATH table) but not with STIX General (no MATH table) so I suspect the USE_TYPO_METRICS flag is not set.

    See https://bugzilla.mozilla.org/show_bug.cgi?id=947650
    http://www.microsoft.com/typography/otspec/os2.htm

     
  • stipub
    stipub
    2014-06-11

    This issue is targeted to be fixed in version 2.0.0 which is currently under development.