[prev in list] [next in list] [prev in thread] [next in thread] 

List:       icu
Subject:    RE: Layout engine headers
From:       Eric Mader <mader () jtcsv ! com>
Date:       2001-09-27 0:13:06
[Download RAW message or body]

At 02:37 PM 9/26/2001, Carl W. Brown wrote:
>Eric,
>
>When I build ICU an Windows with "allinone" I do not get layout built.  I
>have to build layout separately.  Is there an installation verification test
>for layout?

Layout was added as a dependency of "all" post 1.8.1, sorry about that...

Making a verification test for layout that we can distribute is a bit of a 
problem. Layout reads font tables to do what it does, so any test we ship 
would need to include the fonts. So far, we haven't found any interesting 
fonts which we can legally distribute with the test. (Most "interesting" 
fonts have Open Type tables; there aren't many free OT fonts around as far 
as I know)

If you want, I can send you the test program and tell you what fonts it 
needs, but I can't give you the fonts.


>Carl

Eric

> > -----Original Message-----
> > From: Eric Mader [mailto:mader@jtcsv.com]
> > Sent: Wednesday, September 26, 2001 1:32 PM
> > To: Carl W. Brown; Icu
> > Subject: Re: Layout engine headers
> >
> >
> > At 12:24 PM 9/26/2001, Carl W. Brown wrote:
> > >In reviewing ICU for a piece on developing for ICU I noticed
> > that the layout
> > >headers are different from the rest of ICU.
> > >
> > >The loengine.h includes:
> > >
> > >#include "unicode/utypes.h"
> > >#include "unicode/unicode.h"
> > >#include "unicode/unistr.h"
> > >
> > >#include "layout/LETypes.h"
> > >#include "layout/LayoutEngine.h"
> > >
> > >This does not work if you are using a "icu/include" path in your
> > make file.
> > >This also seems to violate the basic ICU development strategy of not
> > >including any root directory include because they are private.
> >
> > When layout gets installed, "icu/include/layout" gets created and the
> > layout interfaces are copied there, so using "icu/include" in your path
> > should work just fine. Here's how it looks on my Windows 2000 system:
> >
> > C:\>ls dev\icu\include
> > layout   unicode
> >
> > C:\>ls dev\icu\include\layout
> > LEFontInstance.h  LEScripts.h       LETypes.h
> > LEGlyphFilter.h   LESwaps.h         LayoutEngine.h
> >
> > C:\>
> >
> > When you build on Windows using VC++, layout should build automatically;
> > when you build on UNIX you have to use "--enable-layout=yes" argument to
> > runConfigureICU.
> >
> > >What are the proper guidelines for layout includes?
> > >
> > >I would have expected that loengine.h, LETypes.h &
> > LayoutEngine.h should be
> > >in the icu/include/unicode directory.
> >
> > Layout was originally developed separately from ICU, using
> > different coding
> > conventions. To save a lot of trouble (and to avoid a great disruption to
> > the other builds which use the layout code :-) we decided not to
> > change the
> > coding conventions, and to put the layout headers in a separate include
> > directory to underscore this difference.
> >
> >
> > >Carl
> >
> > Eric Mader
> > IBM GCoC, Cupertino
> > 10275 N. De Anza Blvd.
> > Cupertino, CA 95014
> >


[prev in list] [next in list] [prev in thread] [next in thread]