I'm sorry, for the screenshot i changed the settings, to create the bad.jpg. When i tried to revert all the font related changes i could still remember, i found it reverted to an acceptable:<br><br>- full hinting (i guess)
<br>- anti aliasing on<br>- auto hinter off<br><br>The problem must have been fixed since 2.3.0. Sorry for not checking if the problem persisted in the latest version. I am however certain that the BCI was enabled at the time, since i could manually change the settings.
<br><br>I do have one small question, why is the autohinter so ugly? (Is this on purpose?)<br><br>Maarten.<br><br><div><span class="gmail_quote">On 5/17/07, <b class="gmail_sendername">Werner LEMBERG</b> <<a href="mailto:wl@gnu.org">
wl@gnu.org</a>> wrote:</span><blockquote class="gmail_quote" style="margin-top: 0; margin-right: 0; margin-bottom: 0; margin-left: 0; margin-left: 0.80ex; border-left-color: #cccccc; border-left-width: 1px; border-left-style: solid; padding-left: 1ex">
> Here are some screenshots, were the bad.jpg is a good approximation<br>> of the original situation.<br><br>Please try ftview and/or ftdiff on this particular font.<br><br>> > > Am i again asking the wrong mailinglist?
<br>> ><br>> > Yes, your question really belongs to freetype list.<br><br>Not necessarily.<br><br>> > I don't know why Werner sent you this way. Probably because he<br>> > saw the XML snippets in your mail and automatically thought you
<br>> > have a fontconfig question.<br><br>:-) Indeed. I need a way to reproduce a problem in a generic way, and<br>even the before/after snapshot doesn't really help, except that the<br>`good' one looks like having bytecode hinting enabled and the `bad'
<br>one disabled.<br><br><br> Werner<br></blockquote></div><br>