You are viewing a plain text version of this content. The canonical link for it is here.
Posted to fop-users@xmlgraphics.apache.org by Ingo Maas <in...@ebp.de> on 2009/02/06 17:01:39 UTC
[Postscript] German umlauts are not shown for Postscript output of Trunk
Hi,
Recently, I upgraded to current Trunk. I noticed that German umlauts are not
shown for Postscript output anymore. Using release 0.95, German umlauts look
fine.
I have made a diff of both output documents, and there are some subtle
differences, see attached files. Both documents do contain the octal
entities for the umlauts.
I'm using font metrics definitions for Type 1 fonts for Postscript renderer
in configuration file 'fop.xconf'.
Can someone have a look at it to confirm that something is broken in
Postscript renderer output in Trunk, please?
Regards, Ingo
--
Ernst Basler + Partner GmbH
Ingo Maas
Tuchmacherstra�e 47
DE-14482 Potsdam
+49 331 74 75 9 0 (Zentrale)
+49 331 74 75 9 78 (Direkt)
+49 331 74 75 9 90 (Fax)
Gesch�ftsf�hrer: Dr. Ludger Paus
Amtsgericht Potsdam - HRB 6362 P
USt-Id Nr. 152768391
<ma...@ebp.de> mailto:Ingo.Maas@ebp.de
<http://www.ebp.de/> http://www.ebp.de
Re: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Looks like a bug. The font reencoding to WinAnsiEncoding does not seem
to happen if the font is not embedded. I'll look into it on Monday.
Thanks for reporting this.
On 06.02.2009 17:01:39 Ingo Maas wrote:
> Hi,
>
> Recently, I upgraded to current Trunk. I noticed that German umlauts are not
> shown for Postscript output anymore. Using release 0.95, German umlauts look
> fine.
> I have made a diff of both output documents, and there are some subtle
> differences, see attached files. Both documents do contain the octal
> entities for the umlauts.
> I'm using font metrics definitions for Type 1 fonts for Postscript renderer
> in configuration file 'fop.xconf'.
>
> Can someone have a look at it to confirm that something is broken in
> Postscript renderer output in Trunk, please?
>
> Regards, Ingo
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: AW: AW: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Thanks. So, I fixed the wrong thing this morning (although it wasn't a
bad idea to change what I changed). Based on your information I believe
I've now fixed the right thing:
http://svn.apache.org/viewvc?rev=742620&view=rev
Anyway, I would like to recommend to you to stop using XML font metrics
file and instead rely on the AFM accompanying a PFB file. To make FOP
reference the font instead of to embed it, you can use this:
http://xmlgraphics.apache.org/fop/trunk/fonts.html#embedding
(only available in FOP Trunk)
It's recommended because this gets you access to all the glyphs in a
Type 1 font and not just the ones in "WinAnsiEncoding". And also a bit
because PFMs are often unreliable.
On 09.02.2009 15:29:44 Ingo Maas wrote:
> Yes, Arial (used in Word template) is configured to be mapped to
> NimbusSanL-Regu. I have both PFM and PFB in a Type 1 fonts folder. There is
> no AFM though.
>
> Here is the section from fop.xconf:
> <renderer mime="application/postscript">
> <fonts>
> <font metrics-url="psfonts/n019003l.xml" kerning="yes">
> <font-triplet name="Helvetica" style="normal"
> weight="normal"/>
> <font-triplet name="Arial" style="normal"
> weight="normal"/>
> </font>
> <font metrics-url="psfonts/n019004l.xml" kerning="yes">
> <font-triplet name="Helvetica" style="normal"
> weight="bold"/>
> <font-triplet name="Arial" style="normal"
> weight="bold"/>
> </font>
> <font metrics-url="psfonts/n019023l.xml" kerning="yes">
> <font-triplet name="Helvetica" style="oblique"
> weight="normal"/>
> <font-triplet name="Arial" style="oblique"
> weight="normal"/>
> </font>
> <font metrics-url="psfonts/n019024l.xml" kerning="yes">
> <font-triplet name="Helvetica" style="oblique"
> weight="bold"/>
> <font-triplet name="Arial" style="oblique"
> weight="bold"/>
> </font>
> </fonts>
> </renderer>
>
> > -----Ursprüngliche Nachricht-----
> > Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> > Gesendet: Montag, 9. Februar 2009 15:13
> > An: fop-users@xmlgraphics.apache.org
> > Betreff: Re: AW: [Postscript] German umlauts are not shown
> > for Postscript output of Trunk
> >
> > I've never seen Arial as a Type 1 font, yet, so I assume
> > you're trying to use a TrueType font with PostScript output.
> > That is currently not supported (not even 0.95). Your earlier
> > PostScript files used "Times-Roman" (Base 14) and
> > "NimbusSanL-Regu". Maybe you did something strange in your
> > font configuration. Have you, by chance, configured "Arial"
> > to be mapped to "NimbusSanL-Regu"? That would explain it. If
> > yes, is the AFM file in the same directory where you placed
> > the PFB file for the font? Or just the PFM?
> >
> > On 09.02.2009 14:36:11 Ingo Maas wrote:
> > > Hi Jeremias,
> > >
> > > I enabled the suggested PS renderer option and checked both
> > FOP trunk
> > > versions with and without your latest changes. The umlaut
> > problem is
> > > fixed only halfway. My document uses two fonts, 'Times New Roman'
> > > (resolved as 'any' font) and 'Arial' (refered to using metrics
> > > declarations in fop.xconf). For 'Times New Roman' turning on the
> > > optimization option has fixed the problem in both versions. For
> > > 'Arial' the problem still remains in Trunk.
> > > I'll recover back to FOP 0.95 for now.
> > >
> > > Regards, Ingo
> > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> > > > Gesendet: Montag, 9. Februar 2009 10:25
> > > > An: fop-users@xmlgraphics.apache.org
> > > > Betreff: Re: [Postscript] German umlauts are not shown for
> > > > Postscript output of Trunk
> > > >
> > > > Fixed in FOP Trunk:
> > http://svn.apache.org/viewvc?rev=742346&view=rev
> > > > Should now also work without resource optimization,
> > though turning
> > > > on resource optimization is recommended if you want smaller
> > > > PostScript files containing only what you really need.
> > > >
> > > > On 09.02.2009 09:44:02 Jeremias Maerki wrote:
> > > > > I think I know now what the problem is. You're using PS
> > > > output with no
> > > > > "resource optimization" [1] (the default). In that mode,
> > > > the fonts are
> > > > > set up before we know what characters are used. I seem to have
> > > > > forgotten to test the PS output in that mode after my
> > > > changes to make
> > > > > all available glyphs in a Type 1 font usable in PostScript. The
> > > > > short-term work-around is to enable "resource optimization":
> > > > > <optimize-resources>true</optimize-resources> in the
> > configuration.
> > > > >
> > > > > I'll see to it that this gets fixed.
> > > > >
> > > > > [1]
> > > > >
> > http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configurati
> > > > > on
> > > > >
> > > > > On 06.02.2009 17:01:39 Ingo Maas wrote:
> > > > > > Hi,
> > > > > >
> > > > > > Recently, I upgraded to current Trunk. I noticed that
> > > > German umlauts
> > > > > > are not shown for Postscript output anymore. Using
> > release 0.95,
> > > > > > German umlauts look fine.
> > > > > > I have made a diff of both output documents, and
> > there are some
> > > > > > subtle differences, see attached files. Both documents do
> > > > > > contain the octal entities for the umlauts.
> > > > > > I'm using font metrics definitions for Type 1 fonts for
> > > > Postscript
> > > > > > renderer in configuration file 'fop.xconf'.
> > > > > >
> > > > > > Can someone have a look at it to confirm that something
> > > > is broken in
> > > > > > Postscript renderer output in Trunk, please?
> > > > > >
> > > > > > Regards, Ingo
> > > >
> > > >
> > > > Jeremias Maerki
> > > >
> >
> >
> >
> > Jeremias Maerki
> >
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Not want Space between inlines
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I'm not sure I'm hitting the right spot here, but you could try to use
linefeed-treatment="ignore" (default is "treat-as-space"). Your
stylesheet may be responsible for adding whitespace or more probably
line feeds which would explain the unwanted spaces. Without seeing your
FO file it's difficult to guess.
See also:
http://www.w3.org/TR/xsl11/#linefeed-treatment
On 09.02.2009 17:41:09 Michonska Sylvie wrote:
> Hello,
>
> I use FOP to transform XML files to PDF files.
>
> I use a style sheet to transform my XML to FO :
> For an paragraph, i build a fo:block with some inlines,
> each inline contents differents attributs (different font, different color or/and ..)
>
> With FOP 0.94, in my PDF, the inlines are separate by a space (between each inline).
> I don't want this space.
> Before, with FOP 0.20.5, the same fo:block and some fo:inline don't product these spaces.
>
> I think that i must use un attribut but i don't find it.
>
> Thank you for your help.
> Sylvie.
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
RE: Not want Space between inlines
Posted by Michonska Sylvie <sm...@sopragroup.com>.
Hello,
This problem (space between inline) come CRLF (linebreak) between the
inline tags in the file .fo
If i suppress the linebreak, i don't have the space between the text.
If i transform by fop (0.94) directly the xml file in pdf file,
i don't have this problem.
I have this problem only, during the debug test, if i transform the xml
file
in fo file, and then the fo file in pdf file.
Sorry for my first message,
if i transform in FOP 0.20.5 the xml file in fo file, then, fo file in
pdf file,
i have the same problem.
My main need is to transform a xml file to pdf file.
If the xml file don't content CRLF (linebreak) between tags,
the pdf file is good.
For the moment, it's OK.
Thank you.
Sylvie.
-----Message d'origine-----
De : Andreas Delmelle [mailto:andreas.delmelle@telenet.be]
Envoye : lundi 9 fevrier 2009 18:41
A : fop-users@xmlgraphics.apache.org
Objet : Re: Not want Space between inlines
On 09 Feb 2009, at 17:41, Michonska Sylvie wrote:
Hi
> I use a style sheet to transform my XML to FO :
> For an paragraph, i build a fo:block with some inlines,
> each inline contents differents attributs (different font, different
> color or/and ..)
A small hint:
If you can, try to use fo:wrapper instead of fo:inline. That's much
less of a drain on resources. This is only possible if you do NOT need
non-inheritable properties (like border or padding, for example) or
special alignment-adjust.
For inheritable properties like font-* and color, fo:wrappers work
just as well, but they are much more light-weight than fo:inlines.
[Note to self: should REALLY add this remark to the performance hints
on the site. Can have a significant impact in larger documents.]
> With FOP 0.94, in my PDF, the inlines are separate by a space
> (between each inline).
> I don't want this space.
> Before, with FOP 0.20.5, the same fo:block and some fo:inline don't
> product these spaces.
As Jeremias already noted: very difficult to judge without looking at
the FO file, but it is very likely that the undesirable white-space is
actually a result of the built-in template rule for text() being
triggered somewhere (so actually comes from the source XML).
Overriding that built-in template rule in your stylesheet, like so:
<xsl:template match="text()">
<xsl:value-of select="normalize-space(.)" />
</xsl:template>
Could mean that you don't even need special FO attributes, as it will
already filter out this unwanted white-space at the XSLT stage, so FOP
doesn't even see it.
HTH!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: Not want Space between inlines
Posted by Andreas Delmelle <an...@telenet.be>.
On 09 Feb 2009, at 17:41, Michonska Sylvie wrote:
Hi
> I use a style sheet to transform my XML to FO :
> For an paragraph, i build a fo:block with some inlines,
> each inline contents differents attributs (different font, different
> color or/and ..)
A small hint:
If you can, try to use fo:wrapper instead of fo:inline. That's much
less of a drain on resources. This is only possible if you do NOT need
non-inheritable properties (like border or padding, for example) or
special alignment-adjust.
For inheritable properties like font-* and color, fo:wrappers work
just as well, but they are much more light-weight than fo:inlines.
[Note to self: should REALLY add this remark to the performance hints
on the site. Can have a significant impact in larger documents.]
> With FOP 0.94, in my PDF, the inlines are separate by a space
> (between each inline).
> I don't want this space.
> Before, with FOP 0.20.5, the same fo:block and some fo:inline don't
> product these spaces.
As Jeremias already noted: very difficult to judge without looking at
the FO file, but it is very likely that the undesirable white-space is
actually a result of the built-in template rule for text() being
triggered somewhere (so actually comes from the source XML).
Overriding that built-in template rule in your stylesheet, like so:
<xsl:template match="text()">
<xsl:value-of select="normalize-space(.)" />
</xsl:template>
Could mean that you don't even need special FO attributes, as it will
already filter out this unwanted white-space at the XSLT stage, so FOP
doesn't even see it.
HTH!
Andreas
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Not want Space between inlines
Posted by Michonska Sylvie <sm...@sopragroup.com>.
Hello,
I use FOP to transform XML files to PDF files.
I use a style sheet to transform my XML to FO :
For an paragraph, i build a fo:block with some inlines,
each inline contents differents attributs (different font, different color or/and ..)
With FOP 0.94, in my PDF, the inlines are separate by a space (between each inline).
I don't want this space.
Before, with FOP 0.20.5, the same fo:block and some fo:inline don't product these spaces.
I think that i must use un attribut but i don't find it.
Thank you for your help.
Sylvie.
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
AW: AW: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Ingo Maas <in...@ebp.de>.
Yes, Arial (used in Word template) is configured to be mapped to
NimbusSanL-Regu. I have both PFM and PFB in a Type 1 fonts folder. There is
no AFM though.
Here is the section from fop.xconf:
<renderer mime="application/postscript">
<fonts>
<font metrics-url="psfonts/n019003l.xml" kerning="yes">
<font-triplet name="Helvetica" style="normal"
weight="normal"/>
<font-triplet name="Arial" style="normal"
weight="normal"/>
</font>
<font metrics-url="psfonts/n019004l.xml" kerning="yes">
<font-triplet name="Helvetica" style="normal"
weight="bold"/>
<font-triplet name="Arial" style="normal"
weight="bold"/>
</font>
<font metrics-url="psfonts/n019023l.xml" kerning="yes">
<font-triplet name="Helvetica" style="oblique"
weight="normal"/>
<font-triplet name="Arial" style="oblique"
weight="normal"/>
</font>
<font metrics-url="psfonts/n019024l.xml" kerning="yes">
<font-triplet name="Helvetica" style="oblique"
weight="bold"/>
<font-triplet name="Arial" style="oblique"
weight="bold"/>
</font>
</fonts>
</renderer>
> -----Ursprüngliche Nachricht-----
> Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> Gesendet: Montag, 9. Februar 2009 15:13
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: AW: [Postscript] German umlauts are not shown
> for Postscript output of Trunk
>
> I've never seen Arial as a Type 1 font, yet, so I assume
> you're trying to use a TrueType font with PostScript output.
> That is currently not supported (not even 0.95). Your earlier
> PostScript files used "Times-Roman" (Base 14) and
> "NimbusSanL-Regu". Maybe you did something strange in your
> font configuration. Have you, by chance, configured "Arial"
> to be mapped to "NimbusSanL-Regu"? That would explain it. If
> yes, is the AFM file in the same directory where you placed
> the PFB file for the font? Or just the PFM?
>
> On 09.02.2009 14:36:11 Ingo Maas wrote:
> > Hi Jeremias,
> >
> > I enabled the suggested PS renderer option and checked both
> FOP trunk
> > versions with and without your latest changes. The umlaut
> problem is
> > fixed only halfway. My document uses two fonts, 'Times New Roman'
> > (resolved as 'any' font) and 'Arial' (refered to using metrics
> > declarations in fop.xconf). For 'Times New Roman' turning on the
> > optimization option has fixed the problem in both versions. For
> > 'Arial' the problem still remains in Trunk.
> > I'll recover back to FOP 0.95 for now.
> >
> > Regards, Ingo
> >
> > > -----Ursprüngliche Nachricht-----
> > > Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> > > Gesendet: Montag, 9. Februar 2009 10:25
> > > An: fop-users@xmlgraphics.apache.org
> > > Betreff: Re: [Postscript] German umlauts are not shown for
> > > Postscript output of Trunk
> > >
> > > Fixed in FOP Trunk:
> http://svn.apache.org/viewvc?rev=742346&view=rev
> > > Should now also work without resource optimization,
> though turning
> > > on resource optimization is recommended if you want smaller
> > > PostScript files containing only what you really need.
> > >
> > > On 09.02.2009 09:44:02 Jeremias Maerki wrote:
> > > > I think I know now what the problem is. You're using PS
> > > output with no
> > > > "resource optimization" [1] (the default). In that mode,
> > > the fonts are
> > > > set up before we know what characters are used. I seem to have
> > > > forgotten to test the PS output in that mode after my
> > > changes to make
> > > > all available glyphs in a Type 1 font usable in PostScript. The
> > > > short-term work-around is to enable "resource optimization":
> > > > <optimize-resources>true</optimize-resources> in the
> configuration.
> > > >
> > > > I'll see to it that this gets fixed.
> > > >
> > > > [1]
> > > >
> http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configurati
> > > > on
> > > >
> > > > On 06.02.2009 17:01:39 Ingo Maas wrote:
> > > > > Hi,
> > > > >
> > > > > Recently, I upgraded to current Trunk. I noticed that
> > > German umlauts
> > > > > are not shown for Postscript output anymore. Using
> release 0.95,
> > > > > German umlauts look fine.
> > > > > I have made a diff of both output documents, and
> there are some
> > > > > subtle differences, see attached files. Both documents do
> > > > > contain the octal entities for the umlauts.
> > > > > I'm using font metrics definitions for Type 1 fonts for
> > > Postscript
> > > > > renderer in configuration file 'fop.xconf'.
> > > > >
> > > > > Can someone have a look at it to confirm that something
> > > is broken in
> > > > > Postscript renderer output in Trunk, please?
> > > > >
> > > > > Regards, Ingo
> > >
> > >
> > > Jeremias Maerki
> > >
>
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: AW: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I've never seen Arial as a Type 1 font, yet, so I assume you're trying
to use a TrueType font with PostScript output. That is currently not
supported (not even 0.95). Your earlier PostScript files used
"Times-Roman" (Base 14) and "NimbusSanL-Regu". Maybe you did something
strange in your font configuration. Have you, by chance, configured
"Arial" to be mapped to "NimbusSanL-Regu"? That would explain it. If yes,
is the AFM file in the same directory where you placed the PFB file for
the font? Or just the PFM?
On 09.02.2009 14:36:11 Ingo Maas wrote:
> Hi Jeremias,
>
> I enabled the suggested PS renderer option and checked both FOP trunk
> versions with and without your latest changes. The umlaut problem is fixed
> only halfway. My document uses two fonts, 'Times New Roman' (resolved as
> 'any' font) and 'Arial' (refered to using metrics declarations in
> fop.xconf). For 'Times New Roman' turning on the optimization option has
> fixed the problem in both versions. For 'Arial' the problem still remains in
> Trunk.
> I'll recover back to FOP 0.95 for now.
>
> Regards, Ingo
>
> > -----Ursprüngliche Nachricht-----
> > Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> > Gesendet: Montag, 9. Februar 2009 10:25
> > An: fop-users@xmlgraphics.apache.org
> > Betreff: Re: [Postscript] German umlauts are not shown for
> > Postscript output of Trunk
> >
> > Fixed in FOP Trunk: http://svn.apache.org/viewvc?rev=742346&view=rev
> > Should now also work without resource optimization, though
> > turning on resource optimization is recommended if you want
> > smaller PostScript files containing only what you really need.
> >
> > On 09.02.2009 09:44:02 Jeremias Maerki wrote:
> > > I think I know now what the problem is. You're using PS
> > output with no
> > > "resource optimization" [1] (the default). In that mode,
> > the fonts are
> > > set up before we know what characters are used. I seem to have
> > > forgotten to test the PS output in that mode after my
> > changes to make
> > > all available glyphs in a Type 1 font usable in PostScript. The
> > > short-term work-around is to enable "resource optimization":
> > > <optimize-resources>true</optimize-resources> in the configuration.
> > >
> > > I'll see to it that this gets fixed.
> > >
> > > [1]
> > > http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configuration
> > >
> > > On 06.02.2009 17:01:39 Ingo Maas wrote:
> > > > Hi,
> > > >
> > > > Recently, I upgraded to current Trunk. I noticed that
> > German umlauts
> > > > are not shown for Postscript output anymore. Using release 0.95,
> > > > German umlauts look fine.
> > > > I have made a diff of both output documents, and there are some
> > > > subtle differences, see attached files. Both documents do contain
> > > > the octal entities for the umlauts.
> > > > I'm using font metrics definitions for Type 1 fonts for
> > Postscript
> > > > renderer in configuration file 'fop.xconf'.
> > > >
> > > > Can someone have a look at it to confirm that something
> > is broken in
> > > > Postscript renderer output in Trunk, please?
> > > >
> > > > Regards, Ingo
> >
> >
> > Jeremias Maerki
> >
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
AW: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Ingo Maas <in...@ebp.de>.
Hi Jeremias,
I enabled the suggested PS renderer option and checked both FOP trunk
versions with and without your latest changes. The umlaut problem is fixed
only halfway. My document uses two fonts, 'Times New Roman' (resolved as
'any' font) and 'Arial' (refered to using metrics declarations in
fop.xconf). For 'Times New Roman' turning on the optimization option has
fixed the problem in both versions. For 'Arial' the problem still remains in
Trunk.
I'll recover back to FOP 0.95 for now.
Regards, Ingo
> -----Ursprüngliche Nachricht-----
> Von: Jeremias Maerki [mailto:dev@jeremias-maerki.ch]
> Gesendet: Montag, 9. Februar 2009 10:25
> An: fop-users@xmlgraphics.apache.org
> Betreff: Re: [Postscript] German umlauts are not shown for
> Postscript output of Trunk
>
> Fixed in FOP Trunk: http://svn.apache.org/viewvc?rev=742346&view=rev
> Should now also work without resource optimization, though
> turning on resource optimization is recommended if you want
> smaller PostScript files containing only what you really need.
>
> On 09.02.2009 09:44:02 Jeremias Maerki wrote:
> > I think I know now what the problem is. You're using PS
> output with no
> > "resource optimization" [1] (the default). In that mode,
> the fonts are
> > set up before we know what characters are used. I seem to have
> > forgotten to test the PS output in that mode after my
> changes to make
> > all available glyphs in a Type 1 font usable in PostScript. The
> > short-term work-around is to enable "resource optimization":
> > <optimize-resources>true</optimize-resources> in the configuration.
> >
> > I'll see to it that this gets fixed.
> >
> > [1]
> > http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configuration
> >
> > On 06.02.2009 17:01:39 Ingo Maas wrote:
> > > Hi,
> > >
> > > Recently, I upgraded to current Trunk. I noticed that
> German umlauts
> > > are not shown for Postscript output anymore. Using release 0.95,
> > > German umlauts look fine.
> > > I have made a diff of both output documents, and there are some
> > > subtle differences, see attached files. Both documents do contain
> > > the octal entities for the umlauts.
> > > I'm using font metrics definitions for Type 1 fonts for
> Postscript
> > > renderer in configuration file 'fop.xconf'.
> > >
> > > Can someone have a look at it to confirm that something
> is broken in
> > > Postscript renderer output in Trunk, please?
> > >
> > > Regards, Ingo
>
>
> Jeremias Maerki
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
Fixed in FOP Trunk: http://svn.apache.org/viewvc?rev=742346&view=rev
Should now also work without resource optimization, though turning on
resource optimization is recommended if you want smaller PostScript
files containing only what you really need.
On 09.02.2009 09:44:02 Jeremias Maerki wrote:
> I think I know now what the problem is. You're using PS output with no
> "resource optimization" [1] (the default). In that mode, the fonts are
> set up before we know what characters are used. I seem to have forgotten
> to test the PS output in that mode after my changes to make all
> available glyphs in a Type 1 font usable in PostScript. The short-term
> work-around is to enable "resource optimization":
> <optimize-resources>true</optimize-resources> in the configuration.
>
> I'll see to it that this gets fixed.
>
> [1] http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configuration
>
> On 06.02.2009 17:01:39 Ingo Maas wrote:
> > Hi,
> >
> > Recently, I upgraded to current Trunk. I noticed that German umlauts are not
> > shown for Postscript output anymore. Using release 0.95, German umlauts look
> > fine.
> > I have made a diff of both output documents, and there are some subtle
> > differences, see attached files. Both documents do contain the octal
> > entities for the umlauts.
> > I'm using font metrics definitions for Type 1 fonts for Postscript renderer
> > in configuration file 'fop.xconf'.
> >
> > Can someone have a look at it to confirm that something is broken in
> > Postscript renderer output in Trunk, please?
> >
> > Regards, Ingo
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org
Re: [Postscript] German umlauts are not shown for Postscript output of Trunk
Posted by Jeremias Maerki <de...@jeremias-maerki.ch>.
I think I know now what the problem is. You're using PS output with no
"resource optimization" [1] (the default). In that mode, the fonts are
set up before we know what characters are used. I seem to have forgotten
to test the PS output in that mode after my changes to make all
available glyphs in a Type 1 font usable in PostScript. The short-term
work-around is to enable "resource optimization":
<optimize-resources>true</optimize-resources> in the configuration.
I'll see to it that this gets fixed.
[1] http://xmlgraphics.apache.org/fop/trunk/output.html#ps-configuration
On 06.02.2009 17:01:39 Ingo Maas wrote:
> Hi,
>
> Recently, I upgraded to current Trunk. I noticed that German umlauts are not
> shown for Postscript output anymore. Using release 0.95, German umlauts look
> fine.
> I have made a diff of both output documents, and there are some subtle
> differences, see attached files. Both documents do contain the octal
> entities for the umlauts.
> I'm using font metrics definitions for Type 1 fonts for Postscript renderer
> in configuration file 'fop.xconf'.
>
> Can someone have a look at it to confirm that something is broken in
> Postscript renderer output in Trunk, please?
>
> Regards, Ingo
Jeremias Maerki
---------------------------------------------------------------------
To unsubscribe, e-mail: fop-users-unsubscribe@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-help@xmlgraphics.apache.org