xmlgraphics-fop-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jeroen de Zwart" <face...@dds.nl>
Subject Re: Code submission: TrueType font support Build with Xalan2?
Date Wed, 31 Jan 2001 09:21:42 GMT
Just wanted to let you know you did a wonderfull job,

For the moment I build fop with xalan1 and(!) xalan2, altough I think
there's absolutely a need to make
fop work with only one version. Well that discussion is already a hot issue.

Oh, I think with the documentation it's best to mension that you will have
to run Fop with the -cuserconfig flag because if you don'nt you will see a
nice bunch of dots. Took some stupid time for me. :)

Jeroen de Zwart


----- Original Message -----
From: "Tore Engvig" <tengvig@infostream.no>
To: <fop-dev@xml.apache.org>
Sent: Tuesday, January 30, 2001 8:02 PM
Subject: RE: Code submission: TrueType font support Build with Xalan2?


>
> Agreed, org.apache.fop.tools.xslt.XSLTransform.transform() is a better
> approach.
>
> If you really need to test TrueType support now, you can remove most of
> that method, it isn't used anyway (the top lines are: if (true) return
> doc;)
>
> This is actually a code bloat that occured while cut'ing and paste'ing
> from the original PFMReader. If you just want to check out TrueType fonts
> you should remove the PFMReader.java file from the source since the same
> line is present there - but there it's actually used.
>
> Removal of code bloat is of course on the todo list :)
> I guess that the postProcessXML method will be removed from the PFMReader
> too as a part of doing a better encoding support.
>
>
> Tore
>
>
> On Tue, 30 Jan 2001, Kelly Campbell wrote:
>
> > This code could use org.apache.fop.tools.xslt.XSLTransform.transform()
> > instead and then it would use either Xalan1 or Xalan2, whichever is
> > available.
> >
> > -Kelly
> >
> > -----Original Message-----
> > From: Jeroen de Zwart [mailto:facecom@dds.nl]
> > Sent: Tuesday, January 30, 2001 5:07 AM
> > To: fop-dev@xml.apache.org
> > Subject: Re: Code submission: TrueType font support Build with Xalan2?
> >
> >
> > I'm very excited about this font submission but i can't build fop with
it
> > because
> > the class org.apache.xalan.xslt.XSLTInputSource is not in xalan2.
> > anybody who knows how to build it with xalan2?
> >
> > messages from ant:
> > ...
> > JAXP1.1 transforms is present. Installing TRaX support
> >   [copydir] Copying 2 files to D:\java\xml-fop\build\src
> >
> > prepare-src:
> >   [copydir] Copying 407 files to D:\java\xml-fop\build\src
> >
> > compile:
> > Compiling the sources
> >     [javac] Compiling 601 source files to D:\java\xml-fop\build\classes
> >     [javac]
> > D:\java\xml-fop\build\src\org\apache\fop\fonts\apps\TTFReader.java:458:
> > Class org.apache.xalan.xslt.XSLTInputSource not found.
> >     [javac]             org.apache.xalan.xslt.XSLTInputSource xmlSource
=
> >     [javac]                                  ^
> > ....
> >
> >
> > Jeroen de Zwart
> >
> >
> > ----- Original Message -----
> > From: "Tore Engvig" <tengvig@infostream.no>
> > To: <fop-dev@xml.apache.org>
> > Sent: Tuesday, January 30, 2001 12:29 AM
> > Subject: Code submission: TrueType font support
> >
> >
> > >
> > >
> > > Attached is a .tar.gz file containing code, a changes file describing
> > > added files and changes to existing files, and an example document
> > > describing how to create font metrics and embed truetype and type 1
> > > fonts.
> > >
> > > The submitted code is support for using TrueType fonts, and embedding
> > > of TrueType and Type1 fonts, and support for kerning.
> > >
> > > To embed fonts you have to enter the fontnames to embed in the
> > > userconfig.xml file. You also have to use the userconfig.xml file to
> > > enable kerning.
> > >
> > > Fontsupport is still using the old approach of compiling in the
> > > fontclass. In the future it would've been nicer to create metric.xml
> > > files and enable them trough the userconfig.xml file. It would've also
> > > been nice to know wich fonts that are used in a document and only
> > > embed those fonts (or add metric information for used fonts only) - an
> > > even nicer approach would've been to known which glyphs use the
> > > different fonts and only embed subsets.
> > >
> > > This code works for most latin fonts, but as the example shows, it has
> > > some weaknesses. It assumes too much about the encoding and doesn't
> > > reencode fonts. That's on the todo list. Also on the todo list are:
> > > reading metrics from .afm files and support for more fonttypes (eg CID
> > > Keyed fonts).
> > >
> > > Note: Acrobat3 doesn't like embedded fonts. You'll have to use
> > > Acrobat4.
> > >
> > >
> > >
> > >
> >
> >
>
> --------------------------------------------------------------------------
--
> > ----
> >
> >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> > > For additional commands, email: fop-dev-help@xml.apache.org
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> > For additional commands, email: fop-dev-help@xml.apache.org
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> > For additional commands, email: fop-dev-help@xml.apache.org
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
> For additional commands, email: fop-dev-help@xml.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: fop-dev-unsubscribe@xml.apache.org
For additional commands, email: fop-dev-help@xml.apache.org


Mime
View raw message