I'll pass for 1). I don't think Werner has subscribed here - I posted a
link back to here when I posted the Savannah bug and I copied his
response here, but I don't think he's following this bug. Did you CC
him?
With regard to 2), I think Sam's test based on rendered string
dimensions did show var
This was posted on the FreeType bug:
"Both versions of FreeMono (20090104 and 20100919) are TTFs, the former has
hints, the latter has not. Consequently, FreeType uses the auto-hinter for the
latter.
Both fonts don't have the `isFixedPitch' flag set in the `post' table, and this
is the very pr
** Bug watch added: GNU Savannah Bug Tracker #36593
http://savannah.gnu.org/bugs/?36593
** Also affects: freetype via
http://savannah.gnu.org/bugs/?36593
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is su
I ran the C test against every font on my Ubuntu 11.10 system with
"Mono" or "Courier" in the name like so:
for name in /usr/share/fonts/truetype/*/*Mono*.ttf; do ./fonttest $name
abcdefgh > `basename $name`.testresult; done
for name in /usr/share/fonts/truetype/*/*Courier*.ttf; do ./font
Sorry Steve, I didn't mean to pick on FreeMono. I agree that it's not
even clear if there's *any* bug here, but there's certainly something
surprising.
I also agree that the rendered width is a poor metric, for the reasons
you describe. That's why my investigations have focused on glyph
metrics,
Okay, I think I see what's happening.
Here's a C program that shows the behaviour only using FreeType:
http://pastebin.com/Jm4XjtNR
Example:
$ gcc fonttest.c `freetype-config --cflags --libs` -o fonttest
$ ./fonttest freefont-20090104-FreeMono.ttf abcdefg
a:448
b:448
c:448
d:448
e:448
f:448
g:44
I think this part of the Pygame API is a relatively thin wrapper around
SDL. I am pretty sure that the size parameter to
pygame.font.Font/SysFont is a pixel size, not a point size, to remain
consistent with the rest of that system.
I'm pretty certain that I can remove Pygame from the equation. I'l
I'm afraid I'm not sure. This is all new to me, I'm just investigating
because I follow the pygame mailing list and found it interesting.
I do think it's interesting that the variation appears always to be +/-1
pixel, regardless of the scaling factor. I'll perhaps try some much
larger scales and s
I'm not in front of the Windows machine right now, but I can run the
script on "/usr/share/fonts/truetype/msttcorefonts/Courier_New.ttf" on
Ubuntu here. This is with a new version of libfreetype:
Courier_New.ttf at pixel size 16, advances:
10 for 95 characters:
!"#$%&'()*+,-./0123456789:;<=>?
I've narrowed it down. The change in behaviour was introduced with this
commit in freetype:
http://git.savannah.gnu.org/cgit/freetype/freetype2.git/commit/?id=8c82ec5b17d0cfc9b0876a2d848acc207a62a25a
The description is:
"Always ignore global advance.
This makes FT_LOAD_IGNORE_GLOBAL_ADVANCE_WIDTH
Okay, I built libfreetype from their git repo, installed it to
/usr/local and reran my test:
$ LD_LIBRARY_PATH=/usr/local/lib/ python testcase.py
freefont-20090104-FreeMono.ttf at pixel size 16, advances:
10 for 95 characters:
!"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`a
Sorry, the results pastebin link didn't work. This one should:
http://pastebin.com/6gvWvMHj
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1001033
Title:
Monospaced font is not monospaced
To manage
I ran a few tests to try to narrow this down, but I don't have a Ubuntu
12.04 system yet, so they may be of limited use.
I used this test script:
http://pastebin.com/tgmShFQm
I ran it on Windows with two different versions of libfreetype (while
keeping the same version of PyGame and everything e
I found the workaround in #7 helpful, but it had two problems, one
major, one minor: It doesn't dissociate vim from the terminal, so if you
close the terminal window vim gets abruptly terminated too; also, vim
spits out quite a few GTK warnings on the console, which I'd rather not
see. Here's what
I just got this today including the "BUG: unable to handle kernel paging
request at fff3" message in the log, on Maverick amd64.
I installed the kernel as described in #11 and Chrome seems stable
again.
Is it useful for me to gather any more information about my system?
--
You recei
Is this a deliberate change? I recently installed Karmic, previously
having had Intrepid installed. In Intrepid, when updates became
available an icon appeared in the notification area next to the network
and sound icons. I could click on it and install the updates when I
wanted to. Now I see the b
I got the same here running 64-bit Jaunty on a Core 2 Duo P7350 and an
nVidia card. It has happened about three times since the upgrade to
Jaunty. It even happened when running from the LiveCD, so I don't think
it's a problem with the proprietary nVidia drivers. Firefox does seem to
be the common f
I have the same problem on a Philips "freevents" 15NB8611 laptop from PC
World. (As I understand it Philips don't build these themselves, and it
may really be something else rebranded. It's got a Core 2 Duo P7350, 4GB
of RAM and some sort of NVIDIA graphics card.) Should I create a
separate bug? It
18 matches
Mail list logo
