Marc Sabatella wrote > I am using Ubutnu 14.04, and 31 the July 2012 version of FontForge.
Linux Mint 17 here, which is a derivative of pretty much the same as your OS (I never manage to remember the correspondence between the two lines). I used the same FontForge as you up to 3 days ago, when I upgraded to the latest release (2014-11-27), without noticing any difference in this area. > With your version of the fonts placed in "~/.fonts", they do show up in > LibreOffice [...] This seems to me to indicate that LibreOffice renders the fonts as they are intended to be rendered! > lasconic had pointed me to > https://bugreports.qt-project.org/browse/QTBUG-11387 which sure sounds > like the same thing - and as I have mentioned, I do see the same results > on Windows 7. But that was reported against 4.6.2. Seems odd that it > would have been fixed for 5.2 then broken again for 5.3 & 5.4, but you > never know. That bug is probably related, but it is not precisely the same: according to the report, it affects .OTF fonts with Type1 (PostScript) glyphs, not .TTF (with TT glyphs) which happen to include GPOS tables. It may indicate that font managing code is not that stable in Qt... > Regarding the loss of info - are you saying that turning off OpenType > necessarily means losing data, or are you just observing that the versions > of the TTF files in my PR were missing data? Remember, it turns out those > were built from much older sources. Do we know we'd lose the same data > building with OpenType off from the current sources? By generating TTF fonts with the "OpenType" option turned OFF, FontForge generates fonts without GSUB and GPOS tables (which is correct) and whatever data was in these tables is not exported into the font (with the exception of kerning, for which a TT-specific table exists and is generated by FF). So, all data in GSUB and GPOS are lost (except kerning); this is perhaps less sever for Latin script (the average user can probably survive without the "fi", "ffi", "fl", "ffl" ligatures) but is a limitation anyway (and -- as I said -- a step back to the 80's in font management), and it might be much more problematic for non-Latin scripts (for instance for Indic scripts). Thanks, Maurizio -- View this message in context: http://dev-list.musescore.org/Kerning-tp7579040p7579056.html Sent from the MuseScore Developer mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Mscore-developer mailing list Mscore-developer@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mscore-developer
