FYI, I just posted a reply including three screenshots, but it got routed
to the moderation queue for veing slightly over the 40 KB limit...
On Sat, Dec 6, 2014 at 12:51 PM, Marc Sabatella
wrote:
> If one ttf is worth a thousand words, what are three PNG's worth? :-) I
> think these will clarif
Mint 17 is Ubuntu 14.04.
Its PPA are trusty labelled
--
View this message in context:
http://dev-list.musescore.org/Kerning-tp7579040p7579057.html
Sent from the MuseScore Developer mailing list archive at Nabble.com.
-
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 u
I am using Ubutnu 14.04, and 31 the July 2012 version of FontForge.
As for other applications, no, I had not tried that. Good idea. With your
version of the fonts placed in "~/.fonts", they do show up in LibreOffice,
and they look like they do on your system: "rj" kerns, "Te" does not, "VA"
does
Well, it seems to me we are stuck: the results Marc gets by generating fonts
with "OpenType" OFF are the results I get by generating fonts with
"OpenType" ON, practically down to the pixel.
There is still the possibility it depends on the Qt lib version (mine 5.2.1
and his 5.4), but it would great
(continued)
If I built from the latest sources with OpenType *off*, I get the results I
apparently am "meant" to get:
This is somewhere between the completely unkerned look of Miwarre's
versions and the fully kerned look of my previous versions. Here, the "rj"
kerns as expected (at least for F
Trying again as the attachments in my previous reply exceeded the size
limit:
If one ttf is worth a thousand words, what are three PNG's worth? :-) I
think these will clarify *what* I am seeing, but doesn't completely answer
*why* I see it or *what to do* about it.
Here is how Miwarre's FreeSeri
Hmm, actually looking at your picture, I won't swear there was *no* kerning of
the VA. Might have been that much. But there is definitely noticeably more if
I turn off OpenType. Did you try that - either yourself or using the fonts I
built? I'm away from my computer but will try to post imag
There might not be an individual pair for "Te", but apparently it's covered by
one of the "kern class" tables or whatever it is called. Because it most
definitely *does* kern in both FreeSerif and FreeSans, but *only* if I uncehck
the OpenType option. This is true for both Ubuntu 14.04 with Qt
Marc Sabatella wrote
> No dice. Neither of those fonts kern correctly for me on any of my three
> systems. Again, both Linux systems are running Qt 5.4; there, neither
> font kerns at all. My Windows machine has Qt 5.3. On that machine, your
> FreeSerif will kern the "rj" but not the "Te" or th
No dice. Neither of those fonts kern correctly for me on any of my three
systems. Again, both Linux systems are running Qt 5.4; there, neither font
kerns at all. My Windows machine has Qt 5.3. On that machine, your
FreeSerif will kern the "rj" but not the "Te" or the "VA". Your FreeSans
will
OK, one .ttf is worth a thousand words... ;)
you (as well as everybody else) can download my attempts so far from:
http://vistamaremusica.com/extras/FreeSans.ttf
and
http://vistamaremusica.com/extras/FreeSerif.ttf
Both kerns correctly in my MuseScore and contain all the original data. I
didn't
Thank again. As you can see, I don't really know this stuff. For the
record, I did not use "old style kern" at all. I always had apple and old
style kern off. I had tested the apple option and it seemed to have no
effect with respect to kerning back in August. The only relevant option
appeared
Ok, let's use the big guns...
I run ttx on the current MuseScore FreeXxxx.ttf fonts and on your Mac and
non-Mac variants (downloaded from your github PR). Leaving aside for the
moment being the bold variants, these are the results.
*1) Common tables*: All fonts contains the following tables (whic
Thanks for the investigation! That's good information about the reason for
the lack of kerning in FreeSans. Also good advice about the string to test
with. You are of course correct that VA is an easy case to test. But
FWIW, I found that this pair will *not* kern for me if I build
FreeSerif.ttf
I start by limiting my observations to Linux, where I can analyse things more
thoroughly. My system: Linux Mint 17 64bit, with self compiled sources with
Qt Creator 3.1.2 and Qt lib 5.2.1. MuseScore built-in .ttf fonts are used as
they come in the current master.
I had the additional problem that
A small detail: I discovered that the 'standard' FreeSans.ttf coming with my
distro has a different structure than FreeSerif: if open with FontForge, it
lacks kerning data for Latin (as 'our' FreeSans does); possibly they are in
the old-style 'kern' table rather than in the GPOS table / 'kern' sub-
Some additional information and corrections:
I have downloaded the latest sources for FreeSerif (normal and bold) and
FreeSans and done some more testing.
I have realized that another difference between my two Linux systems is
that the Qt 5.3 system had FreeSerif & FreeSans already installed
syst
I am noticing inconsistencies in kerning between systems in the text fonts we
provide (FreeSerif, FreeSans, MuseJazz in particular), and want to start a
discussion here rather than IRC where it will disappear into the ether like
it did in the days leading up to Beta 1 when I last looked at this.
B
19 matches
Mail list logo
