Re: [ft] Regression in rendering quality with subpixel antialiasing

2006-09-21 Thread Bernd Schubert 
Hello David,

On Thursday 21 September 2006 07:02, David Turner wrote:
> > Psst, if Steve reads this it really might happen. Then, after the update
> > to Etch about 40 group members will complain about blurry fonts and in
> > end I have to regularily recompile another package... (though probably I
> > won't be in this group anymore that time).
>
> Most other distributions have *not* enabled the bytecode interpreter, and I
> don't see many people screaming about it. For the difficult ones, simply
> explain them that it has been disabled exactly for the same reason why MP3
> playback oe DVD decoding are not available by default and need tweaks.

Um, I have to admit that I simple added the marillat archive into our 
sources.list, so there's everything available. Anyway, if Christian Marillat 
wouldn't do his really great work, I wouldn't care much about the multimedia 
stuff on our institut systems, its just not required for our work. However, 
we are looking all the day on the screen and are programming, writing 
articles, etc., so good fonts are really neccessary.

Anyway, I will discuss this with Steve, maybe we can create two libfreetype6 
packages - one in the main archive without bytecode and one in non-free with 
bytecode..

>
> > [...]
> > However, I already wrote in my first mail, that full subpixel hinting
> > doesn't
> > entirely help e.g. with OpenOffice. I have uploaded two new shots.
> >
> > http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/freetype-snapshot
> >s/3-old_full_sub.png
> > http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/freetype-snapshot
> >s/3-new_full_sub.png
> >
> > I think you can see that 3-old_full_sub.png looks better than
> > 3-new_full_sub.png. Do you have an idea whats going on?
>
> Obviously, the "old" one is using bytecode interpretation, while the "new"
> one is the result of auto-hinting. I don't know much about OpenOffice
> though

Ah, for me this is absolutely not so abvious, I only see two different font 
graphs and one is a bit more blurry than the other ;)

May I ask you for some basic help with libXft, libfreetype and libfontconfig? 
So far I don't even know about there relations to each other. I guess a 
program does a function call to libxft and libxft does a function call to 
libfreetype to finally render the font, doesn't it? But who of them is 
calling libfontconfig, libxft or libfreetype?
Hmm, a 'ldd soffice.bin' shows me that it is not linked to libXft. So either 
my guess to the function call order is wrong or OpenOffice really calls 
freetype functions without libXft.
Is there a typical function call to libfreetype? I would just like to compare 
what openoffice does differently.

Thanks,
Bernd


-- 
Bernd Schubert
PCI / Theoretische Chemie
Universität Heidelberg
INF 229
69120 Heidelberg



___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] Use of FTC_Manager_LookupFace

2006-09-21 Thread David Turner 
Helo Steve,

On Wed, 20 Sep 2006 12:36:52 -0700, "Steve Hales" <[EMAIL PROTECTED]> said:
> In my prototype I've just called FT_New_Face() pointing to the same file,
> but I've then done a FT_Set_Char_Size() operation on it, then FT_Load is
> done on the resulting object.
>

If you only use FTC_Manager_LookupFace (i.e. not FTC_Manager_LookupSize),
and if you always use FT_Set_Char_Size on a FT_Face returned by the cache
manager, your program will be correct.

However, I'd recommend using FTC_Manager_LookupSize instead, since this
will avoid you calling FT_Set_Char_Size which can be relatively slow in
certain cases (e.g. with the bytecode interpreter enabled)
 
> If I use FTC_Manager_LookupSize() and I use the size->face object, is
> this different for each size requested?
>
yes, since the cache should hold no more than a single FT_Face object for
a given FTC_FaceID value. However keep in mind that these objects might be
purged from the cache on your next call to a cache function.

Hope this helps,

> Great font engine, BTW.
> 
> Steve
> --
> aim : heyigor
> 
> 
> 
> 
> ___
> Freetype mailing list
> Freetype@nongnu.org
> http://lists.nongnu.org/mailman/listinfo/freetype
- David Turner
- The FreeType Project  (www.freetype.org)



___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] Regression in rendering quality with subpixel antialiasing

2006-09-21 Thread David Turner 
> Psst, if Steve reads this it really might happen. Then, after the update
> to Etch about 40 group members will complain about blurry fonts and in end I 
> have to regularily recompile another package... (though probably I won't
> be in this group anymore that time).
> 
Most other distributions have *not* enabled the bytecode interpreter, and I 
don't
see many people screaming about it. For the difficult ones, simply explain them
that it has been disabled exactly for the same reason why MP3 playback oe DVD
decoding are not available by default and need tweaks.

> [...]
> However, I already wrote in my first mail, that full subpixel hinting
> doesn't 
> entirely help e.g. with OpenOffice. I have uploaded two new shots.
> 
> http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/freetype-snapshots/3-old_full_sub.png
> http://www.pci.uni-heidelberg.de/tc/usr/bernd/downloads/freetype-snapshots/3-new_full_sub.png
> 
> I think you can see that 3-old_full_sub.png looks better than 
> 3-new_full_sub.png. Do you have an idea whats going on?
>
Obviously, the "old" one is using bytecode interpretation, while the "new" one 
is
the result of auto-hinting. I don't know much about OpenOffice though

Regards,
 
- David Turner
- The FreeType Project  (www.freetype.org)



___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

[ft] How to compile universal freetype on MacOS X 10.4?

2006-09-21 Thread Russell E. Owen 
I'm trying to build a universal (ppc and i386) libfreetype 2.1.12 (or 
any reasonably recent version) on my PPC Mac (10.4.7 with XCode 2.4). I 
can built something, but it's always PPC-only.

I started from Apple Tech Note 2137:

but read elsewhere that their suggestion to set LDFLAGS is wrong and 
will cause the build to fail.

So I've been trying this (which does work for building a universal 
libpng, but not, alas, libfreetype):

$ CFLAGS="-O -g -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 
-arch ppc" \
   ./configure --disable-dependency-tracking
$ make

I'm not savvy about this stuff, but naively the compile steps appeared 
OK (the CFLAGS options were present).

$ make
./builds/unix/libtool --mode=compile gcc -pedantic -ansi  
-I/Users/rowen/Desktop/freetype-2.2.1/objs -I./builds/unix 
-I/Users/rowen/Desktop/freetype-2.2.1/include -c -Wall -O -g -isysroot 
/Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc 
-DFT_CONFIG_OPTION_SYSTEM_ZLIB -DFT_CONFIG_CONFIG_H="" 
-DFT2_BUILD_LIBRARY -DFT_CONFIG_MODULES_H=""  -o 
/Users/rowen/Desktop/freetype-2.2.1/objs/ftsystem.lo 
builds/unix/ftsystem.c
 gcc -pedantic -ansi -I/Users/rowen/Desktop/freetype-2.2.1/objs 
-I./builds/unix -I/Users/rowen/Desktop/freetype-2.2.1/include -c -Wall 
-O -g -isysroot /Developer/SDKs/MacOSX10.4u.sdk -arch i386 -arch ppc 
-DFT_CONFIG_OPTION_SYSTEM_ZLIB "-DFT_CONFIG_CONFIG_H=" 
-DFT2_BUILD_LIBRARY "-DFT_CONFIG_MODULES_H=" 
builds/unix/ftsystem.c  -fno-common -DPIC -o 
/Users/rowen/Desktop/freetype-2.2.1/objs/.libs/ftsystem.o

but the result is clearly ppc-only (no data for i386 is listed):
$ otool -hv -arch all objs/.libs/libfreetype.dylib 
objs/.libs/libfreetype.dylib:
Mach header
  magic cputype cpusubtype   filetype ncmds sizeofcmds  flags
   MH_MAGIC PPCALL  DYLIB 8   1180 DYLDLINK 
SUBSECTIONS_VIA_SYMBOLS
$

Any hints?

-- Russell



___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] How to compile universal freetype on MacOS X 10.4?

2006-09-21 Thread Tor Andersson 

I'm trying to build a universal (ppc and i386) libfreetype 2.1.12 (or
any reasonably recent version) on my PPC Mac (10.4.7 with XCode 2.4). I
can built something, but it's always PPC-only.


I believe that you need to compile twice, once with each -arch flag, to
separate files. Then you merge together the two resulting (i386 and ppc)
dylib files with "lipo".

At least that's how Xcode does it. I do not believe that gcc can compile to both
architectures in the same command, which it looks like you're trying to do.

Tor


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] How to compile universal freetype on MacOS X 10.4?

2006-09-21 Thread Tor Andersson 

On 9/22/06, Russell E Owen <[EMAIL PROTECTED]> wrote:

At 12:01 AM +0200 2006-09-22, Tor Andersson wrote:
>>I'm trying to build a universal (ppc and i386) libfreetype 2.1.12 (or
>>any reasonably recent version) on my PPC Mac (10.4.7 with XCode 2.4). I
>>can built something, but it's always PPC-only.
>
>I believe that you need to compile twice, once with each -arch flag, to
>separate files. Then you merge together the two resulting (i386 and ppc)
>dylib files with "lipo".
>
>At least that's how Xcode does it. I do not believe that gcc can
>compile to both
>architectures in the same command, which it looks like you're trying to do.

I suppose that may be necessary for freetype. I hope not, because I
don't have easy access to an Intel Mac.

However, if you are making a blanket assertion that having gcc build
for both i386 and ppc at the same time doesn't work...that's wrong.
The tech note I reference shows how to do it, and it works just fine
for libpng.


That's what I meant, so I guess I am wrong.

I've built universal apps on ppc macs, but I've always
used Xcode (which compiles the architectures separately)
and/or lipo to stitch the architectures together into a fat binary.


Also, I know somebody who built a universal libfreetype on his Intel
Mac. He claims to have used a similar incantation (and doing it all
at once, not building separately and combining) but he doesn't
remember the exact details.



___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] How to compile universal freetype on MacOS X 10.4?

2006-09-21 Thread Leonard Rosenthol 

I believe that you need to compile twice, once with each -arch flag, to
separate files. Then you merge together the two resulting (i386 and ppc)
dylib files with "lipo".


That is correct - that is indeed what you need to do.


Leonard

--
---
Leonard Rosenthol
Chief Technical Officer  
PDF Sages, Inc.  215-938-7080 (voice)
 215-689-3863 (fax)


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype

Re: [ft] How to compile universal freetype on MacOS X 10.4?

2006-09-21 Thread mpsuzuki 
Hi,

On Fri, 22 Sep 2006 00:50:03 +0200
"Tor Andersson" <[EMAIL PROTECTED]> wrote:
>On 9/22/06, Russell E Owen <[EMAIL PROTECTED]> wrote:
>> At 12:01 AM +0200 2006-09-22, Tor Andersson wrote:
>> >>I'm trying to build a universal (ppc and i386) libfreetype 2.1.12 (or
>> >>any reasonably recent version) on my PPC Mac (10.4.7 with XCode 2.4). I
>> >>can built something, but it's always PPC-only.

Sorry for your inconvenience, I have 2 points to note.

freetype-2.2.1 has bug in configure script about classic MacOS font support,
and its QuickDraw support does not working in i386 Mac.
freetype-2.1.x or latest CVS version (both bugs are fixed) is recommended.

Regards,
mpsuzuki


___
Freetype mailing list
Freetype@nongnu.org
http://lists.nongnu.org/mailman/listinfo/freetype