Vincent Hennebert wrote:
> >>>Integrating FOrayFont in the pre-release would be great...
> >>
> >>Quite unrealistic as it stands now, sorry.
> >
> > That is your (FOP's) decision, but it makes no sense to me. You are
> > willing to go backwards in almost any other area, but are
> unwilling to
Vincent Hennebert wrote:
> > I am not sure what you mean "getPDF/PSSubset".
>
> If I'm correct it is only possible to embed the whole font
> file in a pdf output, by using getPDFFontFileStream.
> Currently aXSL doesn't seem to provide a means to embed only a subset.
OK. I understand. Yes, subs
Victor Mote a écrit :
Jeremias Maerki wrote:
output format. Maybe the Font interface should simply have a
method to return a very generic interface for more detailed
and font- and output-system-specific access to the font.
Consumers of this interface can then cast it to a special
interface/c
Victor Mote a écrit :
I am not sure what you mean "getPDF/PSSubset".
If I'm correct it is only possible to embed the whole font file in a pdf output,
by using getPDFFontFileStream. Currently aXSL doesn't seem to provide a means to
embed only a subset.
Point me to the FOP code that does th
Jeremias Maerki wrote:
> I have recently implemented Type 1 embedding for those fonts
> which have the PFB file specified. Before that all Type 1
> fonts were only referenced, their encoding redefined to
> WinAnsi and assigned a font key which is used inside the pages.
OK. That should make it
Jeremias Maerki wrote:
> And what about PCL? And SVG? And AFP? IMO, output format
> specific code should not appear in the main interfaces for
> font access. Every target platform will have their little
> specialities: special font formats, font conversions may be
> necessary (Type 1 to SVG fo
On 13.09.2005 21:47:01 Victor Mote wrote:
> > 1. Currently the Fop PSRenderer embeds all of the configured
> > fonts in the PS
> > file, even those that will never be used. It does this by
> > parsing itself the
> > font files;
>
> Hmmm. I think something has changed here since I last looked
On 13.09.2005 20:57:31 Vincent Hennebert wrote:
> >>Let's look at it from another side. If someone writes some
> >>kind of FO editor or a configuration tool for FOray/FOP a
> >>method that reports all available fonts will certainly be useful. :-)
> >
> > OK. That makes sense. To avoid wasteful
Vincent Hennebert wrote:
> > OK. That makes sense. To avoid wasteful parsing, it will
> mean that at
> > least
> > 3 new classes need to be exposed through interfaces
> (RegisteredFont,
> > RegisteredFontFamily, and RegisteredFontDesc), which may be a good
> > thing anyway.
>
> Yes, I think
Let's look at it from another side. If someone writes some
kind of FO editor or a configuration tool for FOray/FOP a
method that reports all available fonts will certainly be useful. :-)
OK. That makes sense. To avoid wasteful parsing, it will mean that at least
3 new classes need to be exposed
Jeremias Maerki wrote:
> Looks like you can't even be 100% sure that the base 14 fonts
> are available.
Right.
> Let's look at it from another side. If someone writes some
> kind of FO editor or a configuration tool for FOray/FOP a
> method that reports all available fonts will certainly be u
On 13.09.2005 15:47:12 Victor Mote wrote:
> Jeremias Maerki wrote:
>
> > > BTW, are these fonts well defined in the postscript standard? Or do
> > > they only exist in PDF?
> >
> > PDF was derived from PostScript, so yes, they are well-defined.
>
> There is a group of so-called Base-35 fonts f
Jeremias Maerki wrote:
> > BTW, are these fonts well defined in the postscript standard? Or do
> > they only exist in PDF?
>
> PDF was derived from PostScript, so yes, they are well-defined.
There is a group of so-called Base-35 fonts for PostScript that is a
superset of the Base-14 fonts. I wa
On 13.09.2005 00:53:56 Vincent Hennebert wrote:
> Well, so there is no simple solution :-(
>
> I could probably add a method like getConfiguredFonts in the font server to
> put
> in the postscript file all of the fonts defined in the config file. But that
> really sounds dirty to me.
>
> A te
Well, so there is no simple solution :-(
I could probably add a method like getConfiguredFonts in the font server to put
in the postscript file all of the fonts defined in the config file. But that
really sounds dirty to me.
A temporary solution (before implementing a two-pass approach) would
I know exactly what you mean. The only way around this is to do a
two-pass approach when writing PostScript, meaning that you keep track
of resources (like fonts) while writing the pages and later you put
together the complete PostScript document by including the needed
resources in the right place
16 matches
Mail list logo
