Re: Requesting your GitHub User Identifier - For Jira Migration

[Glenn Adams]

Hi Jocelin,

Please send me your Jira user ID and a valid (preferred) email address. You
can reply privately to me if you wish.

Regards,
Glenn

On Wed, May 10, 2023 at 3:18 AM Jocelin HEINEN (ext)
 wrote:

> Hi,
>
> I have created a Jira issue.
> My GitHub username: *JoHein*
>
> Thank you
>
> ------
> *De :* Glenn Adams 
> *Envoyé :* dimanche 7 mai 2023 06:19
> *À :* FOP Users ; FOP Developers <
> fop-...@xmlgraphics.apache.org>; Batik Developers <
> batik-...@xmlgraphics.apache.org>; XML Graphics Project <
> gene...@xmlgraphics.apache.org>
> *Objet :* Requesting your GitHub User Identifier - For Jira Migration
>
> Caution: External email. Do not open attachments or click links, unless
> this email comes from a known sender and you know the content is safe.
>
> Hi All,
>
> If you haven't yet heard, we are migrating the XMLGraphics project's issue
> tracking from Jira to GitHub.
>
> For the purpose of performing the migration from Jira to GitHub Issues, I
> would like to have your GitHub User Identifier if you have previously
> interacted with the XMLGraphics Jira Projects in any way, e.g., creating a
> Jira Issue, commenting on a Jira Issue, adding an attachment to a Jira
> Issue, etc.
>
> Your Identifier will be used to add you as an assignee or refer to you via
> a *mention* in GitHub issues that are created from the migration process.
>
> Please send your Identifier in response to this email at your earliest
> convenience. For your reference, my GitHub User Identifier is skynavga.
> If you don't have a GitHub Identifier, then you can create a GitHub account
> to create one. Or, if you don't wish to create a GitHub account, you can
> let me know that as well, in which case the migration process will not link
> migrated issues to you.
>
> Also, if you wish to avoid responding publicly, please send your response
> directly to me at .
>
> Kind regards,
> Glenn
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont
> établis à l’intention exclusive des destinataires désignés. Il contient des
> informations confidentielles et pouvant être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
> ce message non conforme à sa destination, toute diffusion ou toute
> publication, totale ou partielle, est interdite, sauf autorisation expresse
> de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message
> lors de son acheminement, Atos (et ses filiales) décline(nt) toute
> responsabilité au titre de son contenu. Bien que ce message ait fait
> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut
> garantir l’absence totale de logiciels malveillants dans son contenu et ne
> pourrait être tenu pour responsable des dommages engendrés par la
> transmission de l’un d’eux.
>
> This message and any attachments (the "message") are intended solely for
> the addressee(s). It contains confidential information, that may be
> privileged. If you receive this message in error, please notify the sender
> immediately and delete the message. Any use of the message in violation of
> its purpose, any dissemination or disclosure, either wholly or partially is
> strictly prohibited, unless it has been explicitly authorized by the
> sender. As its integrity cannot be secured on the internet, Atos and its
> subsidiaries decline any liability for the content of this message.
> Although the sender endeavors to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and will
> not be liable for any damages resulting from any virus transmitted.
>

Requesting your GitHub User Identifier - For Jira Migration

[Glenn Adams]

Hi All,

If you haven't yet heard, we are migrating the XMLGraphics project's issue
tracking from Jira to GitHub.

For the purpose of performing the migration from Jira to GitHub Issues, I
would like to have your GitHub User Identifier if you have previously
interacted with the XMLGraphics Jira Projects in any way, e.g., creating a
Jira Issue, commenting on a Jira Issue, adding an attachment to a Jira
Issue, etc.

Your Identifier will be used to add you as an assignee or refer to you via
a *mention* in GitHub issues that are created from the migration process.

Please send your Identifier in response to this email at your earliest
convenience. For your reference, my GitHub User Identifier is skynavga. If
you don't have a GitHub Identifier, then you can create a GitHub account to
create one. Or, if you don't wish to create a GitHub account, you can let
me know that as well, in which case the migration process will not link
migrated issues to you.

Also, if you wish to avoid responding publicly, please send your response
directly to me at .

Kind regards,
Glenn

Re: AFP with custom font TTF generates space-letter-space

[Glenn Adams]

Pas de problème Jocelin. Juste une suggestion amicale.

G.

On Thu, Apr 27, 2023 at 9:27 AM Jocelin HEINEN (ext)
 wrote:

> Yes sorry about that still don't have a Jira account but will do when I
> have and can create the issue
> --
> *De :* Glenn Adams 
> *Envoyé :* jeudi 27 avril 2023 16:22
> *À :* fop-users@xmlgraphics.apache.org 
> *Objet :* Re: AFP with custom font TTF generates space-letter-space
>
> Caution: External email. Do not open attachments or click links, unless
> this email comes from a known sender and you know the content is safe.
>
> Also, please put any example XML into an attachment rather than inlined in
> the problem description or a comment.
>
> Thanks.
>
> On Thu, Apr 27, 2023 at 5:12 AM Simon Steiner 
> wrote:
>
> Hi,
>
>
>
> You may need to open a bug in jira for us to check this.
>
>
>
> Thanks
>
>
>
> *From:* Jocelin HEINEN (ext) 
> *Sent:* 27 April 2023 11:03
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: AFP with custom font TTF generates space-letter-space
>
>
>
> Hi,
>
> Thank you for the quick answer.
> Unfortunately I did try a while ago that attribute and I did retry after
> your answer but still the same. (result below with position-by-char).
> I have also tried several others TTF but ended up with the exact same
> result.
>
>
>
>  A r i a l  a r i a l N  a r i a l N B
>
> ESC
>
> AMB 223
>
> AMI 236
>
> SCFL 1
>
> SVI 11
> --
>
> *De :* Simon Steiner 
> *Envoyé :* jeudi 27 avril 2023 11:50
> *À :* fop-users@xmlgraphics.apache.org 
> *Objet :* RE: AFP with custom font TTF generates space-letter-space
>
>
>
> *Caution:* External email. Do not open attachments or click links, unless
> this email comes from a known sender and you know the content is safe.
>
>
>
> Hi,
>
>
>
> What about using:
>
>
>
>  position-by-char="false">
>
>
>
> Thanks
>
>
>
> *From:* Jocelin HEINEN (ext) 
> *Sent:* 27 April 2023 10:40
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* AFP with custom font TTF generates space-letter-space
>
>
>
> Hi,
>
> I am producing an AFP file with Apache FOP 2.8 and java 17.
> In my fo.xconf file am using a custom font with the TTF format and I have
> using also a xsl file. (you can find them below)
>
> Altough then file renders properly when viewed with a tool like "Papyrus
> AFP viewer",
>
> I have noticed that the content has issues when analyzed using AFPexplorer.
>
> In the example below you see that the words are not generated words by
> words but space-letter-space which is causing problems during printing.
>
>
> *AFPexplorer*
>
> MDR:  1= A r i a l  2= a r i a l N  3= a r i a l N
>
>
>
> PTX tag:
>  A  r  i  a  l  a  r  i  a  l  N  a  r  i  a  l  N  B
>
> ESC
>
> AMB 223
>
> AMI 236
>
> SCFL 1
>
> SVI 11
>
> I do not understand what is missing to produce an AFP file with the
> correct structure.
>
> Any help is welcome 
>
> Thank you for your time.
>
> Jo
>
>
> *fo.xconf*
>
> 
>
> 
>
> 
> .
> 
> ./
>
> true
> 
>
>
> 
> 
>
> 240
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>
> 
>
> *XSL file*
>
> 
>
> http://www.w3.org/1999/XSL/Transform;>
> 
> 
> solid 0.1mm black
> 
> 
> http://www.w3.org/1999/XSL/Format;>
> 
>  page-width="21cm" margin-top="1cm"
> margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
> 
> 
> 
> 
> 
> 
> 
> Arial
> arialN
> arialNB
> 
>
> 
> 
> 
> 
>
>
>
>
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont
> établis à l’intention exclusive des destinataires désignés. Il contient des
> informations confidentielles et pouvant être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
> ce message non conforme à sa destination, toute diffusion ou toute
> publication, totale ou partielle, est interdite, sauf autorisation expresse
> de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message
> lors de son acheminement, Atos (et ses filiales) décline(nt) toute
> responsabilité au titre de son contenu. Bien que ce message ait fait
> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut
> garantir l’abs

Re: AFP with custom font TTF generates space-letter-space

[Glenn Adams]

Also, please put any example XML into an attachment rather than inlined in
the problem description or a comment.

Thanks.

On Thu, Apr 27, 2023 at 5:12 AM Simon Steiner 
wrote:

> Hi,
>
>
>
> You may need to open a bug in jira for us to check this.
>
>
>
> Thanks
>
>
>
> *From:* Jocelin HEINEN (ext) 
> *Sent:* 27 April 2023 11:03
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: AFP with custom font TTF generates space-letter-space
>
>
>
> Hi,
>
> Thank you for the quick answer.
> Unfortunately I did try a while ago that attribute and I did retry after
> your answer but still the same. (result below with position-by-char).
> I have also tried several others TTF but ended up with the exact same
> result.
>
>
>
>  A r i a l  a r i a l N  a r i a l N B
>
> ESC
>
> AMB 223
>
> AMI 236
>
> SCFL 1
>
> SVI 11
> --
>
> *De :* Simon Steiner 
> *Envoyé :* jeudi 27 avril 2023 11:50
> *À :* fop-users@xmlgraphics.apache.org 
> *Objet :* RE: AFP with custom font TTF generates space-letter-space
>
>
>
> *Caution:* External email. Do not open attachments or click links, unless
> this email comes from a known sender and you know the content is safe.
>
>
>
> Hi,
>
>
>
> What about using:
>
>
>
>  position-by-char="false">
>
>
>
> Thanks
>
>
>
> *From:* Jocelin HEINEN (ext) 
> *Sent:* 27 April 2023 10:40
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* AFP with custom font TTF generates space-letter-space
>
>
>
> Hi,
>
> I am producing an AFP file with Apache FOP 2.8 and java 17.
> In my fo.xconf file am using a custom font with the TTF format and I have
> using also a xsl file. (you can find them below)
>
> Altough then file renders properly when viewed with a tool like "Papyrus
> AFP viewer",
>
> I have noticed that the content has issues when analyzed using AFPexplorer.
>
> In the example below you see that the words are not generated words by
> words but space-letter-space which is causing problems during printing.
>
>
> *AFPexplorer*
>
> MDR:  1= A r i a l  2= a r i a l N  3= a r i a l N
>
>
>
> PTX tag:
>  A  r  i  a  l  a  r  i  a  l  N  a  r  i  a  l  N  B
>
> ESC
>
> AMB 223
>
> AMI 236
>
> SCFL 1
>
> SVI 11
>
> I do not understand what is missing to produce an AFP file with the
> correct structure.
>
> Any help is welcome 
>
> Thank you for your time.
>
> Jo
>
>
> *fo.xconf*
>
> 
>
> 
>
> 
> .
> 
> ./
>
> true
> 
>
>
> 
> 
>
> 240
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
> 
>
> 
>
> 
>
> *XSL file*
>
> 
>
> http://www.w3.org/1999/XSL/Transform;>
> 
> 
> solid 0.1mm black
> 
> 
> http://www.w3.org/1999/XSL/Format;>
> 
>  page-width="21cm" margin-top="1cm"
> margin-bottom="2cm" margin-left="2.5cm" margin-right="2.5cm">
> 
> 
> 
> 
> 
> 
> 
> Arial
> arialN
> arialNB
> 
>
> 
> 
> 
> 
>
>
>
>
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont
> établis à l’intention exclusive des destinataires désignés. Il contient des
> informations confidentielles et pouvant être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
> ce message non conforme à sa destination, toute diffusion ou toute
> publication, totale ou partielle, est interdite, sauf autorisation expresse
> de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message
> lors de son acheminement, Atos (et ses filiales) décline(nt) toute
> responsabilité au titre de son contenu. Bien que ce message ait fait
> l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut
> garantir l’absence totale de logiciels malveillants dans son contenu et ne
> pourrait être tenu pour responsable des dommages engendrés par la
> transmission de l’un d’eux.
>
> This message and any attachments (the "message") are intended solely for
> the addressee(s). It contains confidential information, that may be
> privileged. If you receive this message in error, please notify the sender
> immediately and delete the message. Any use of the message in violation of
> its purpose, any dissemination or disclosure, either wholly or partially is
> strictly prohibited, unless it has been explicitly authorized by the
> sender. As its integrity cannot be secured on the internet, Atos and its
> subsidiaries decline any liability for the content of this message.
> Although the sender endeavors to maintain a computer virus-free network,
> the sender does not warrant that this transmission is virus-free and will
> not be liable for any damages resulting from any virus transmitted.
>
> Ce message et toutes les pièces jointes (ci-après le "message") sont
> établis à l’intention exclusive des destinataires désignés. Il contient des
> informations confidentielles et pouvant être protégé par le secret
> professionnel. Si vous recevez ce message par erreur, merci d'en avertir
> immédiatement l'expéditeur et de détruire le message. Toute utilisation de
> ce message non conforme à sa 

Re: does FOP support characters defined in a cmap_format_12 font table?

[Glenn Adams]

On Thu, Nov 30, 2017 at 2:35 AM, Ron Van den Branden <
ron.vandenbran...@kantl.be> wrote:

> Thanks for pointing this out. From that issue thread, I gather this won't
> be resolved in the near future.
>
> Perhaps it's worth, then, pointing this out in the documentation (
> https://xmlgraphics.apache.org/fop/2.2/fonts.html) so users won't get
> false expectations when trying to find suitable fonts for characters that
> eventually are unsupported by FOP?
>
That's a reasonable request.


> Kind regards,
>
> Ron
>
> On 29/11/2017 18:41, Glenn Adams wrote:
>
> Characters outside the BMP are not yet supported by FOP. See [1].
>
> [1] https://issues.apache.org/jira/browse/FOP-1969
>
> On Wed, Nov 29, 2017 at 7:29 AM, Ron Van den Branden <
> ron.vandenbran...@kantl.be> wrote:
>
>> Perhaps I should make clear that this is a general pattern: for all
>> characters that are exclusively defined in a font's "cmap_format_12"
>> subtable (and that don't also occur in a "cmap_format_4" subtable), FOP
>> reports these as non available.
>>
>> Is this a limitation or bug in FOP, or my misundertanding of how to use
>> such characters?
>>
>> Best,
>>
>> Ron
>>
>>
>> -
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>>
>>
>
>

Re: does FOP support characters defined in a cmap_format_12 font table?

[Glenn Adams]

Characters outside the BMP are not yet supported by FOP. See [1].

[1] https://issues.apache.org/jira/browse/FOP-1969

On Wed, Nov 29, 2017 at 7:29 AM, Ron Van den Branden <
ron.vandenbran...@kantl.be> wrote:

> Perhaps I should make clear that this is a general pattern: for all
> characters that are exclusively defined in a font's "cmap_format_12"
> subtable (and that don't also occur in a "cmap_format_4" subtable), FOP
> reports these as non available.
>
> Is this a limitation or bug in FOP, or my misundertanding of how to use
> such characters?
>
> Best,
>
> Ron
>
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: Defining XML Entities in FOP 2.2

[Glenn Adams]

Since the XSLT front end functionality in FOP serves merely as a
convenience function for the user, you may choose to use alternative tools
not integrated into FOP as your front end. I suggest you do this in order
to transform from your input data set into XSL-FO input files which you can
feed directly to FOP without making use of the the XSLT front end found in
FOP that does not support XML Entities.

Regards,
Glenn

On Tue, May 16, 2017 at 5:54 AM, Jens Hofschröer  wrote:

> Hi
>
> Since FOP 2.2 it is no longer allowed to use a DOCTYPE declaration[1]. An
> issue originally only disallowing the loading of external DTDs.
>
> We are using FOP to transform a Docbook document separated in several
> files. Each of these files uses a local "settings.dtd" with common XML
> Entities used across the whole document. This is no longer possible with
> FOP 2.2. Even a simple DOCTYPE declaration without any file reference is
> disallowed now.
>
> The following error occurs if you have any DOCTYPE in your document(s):
> > javax.xml.transform.TransformerException: DOCTYPE is disallowed when
> the feature "http://apache.org/xml/features/disallow-doctype-decl; set to
> true.
>
> For Docbook these XML Entities are a common and documented[2] way to use
> "constants" across your document. So please allow the use of internal
> DOCTYPE and/or the use of local DTDs.
>
> Greetings
> Jens Hofschröer
>
>
> [1] https://issues.apache.org/jira/browse/FOP-2668
> [2] http://www.sagehill.net/docbookxsl/Db5Entities.html
>
> --
> http://blog.nigjo.de/netbeans/
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: any plans of an FOP 2.2 release any time soon

[Glenn Adams]

On Tue, Nov 29, 2016 at 10:55 PM, Vishnu K <vishnu...@gmail.com> wrote:

>  I second Mark.. I am specifically interested in memory leak fix
> https://issues.apache.org/jira/browse/FOP-2525,  but our guidelines
> doesn't allow me to patch the fix myself..
>
> Also is there a formal test bucket that anyone can run against a specific
> 2.2.0 snapshot to see how stable the snapshot is ?
>

The CI system that builds FOP [1] (whenever a build is triggered) runs the
FOP test suite, reporting an regression that occurs. Actually, any test
failure results in a build failure. At present, there are 2,841 tests
enabled.

[1] https://builds.apache.org/job/xmlgraphics-fop/


>
>
> vishnu.
>
> On Tue, Nov 29, 2016 at 9:34 PM, Pascal Sancho <psancho@gmail.com>
> wrote:
>
>> Hi,
>>
>> FOP active team is quite little, so having a release plan will not
>> help. As FOP is open source, volunteers are welcome to help.
>>
>> 2016-11-29 11:11 GMT+01:00 Mark Gibson <mark.gib...@staff.bluematrix.com
>> >:
>> > For some of us, it’s not appropriate to take the development branch.
>> > However, we are really keen to get the next release version of FOP so
>> we can
>> > use the fix for the PDF image plug-in.
>> >
>> >
>> >
>> > I appreciate the nature of these mainly volunteer led apache projects.
>> > However, I would like to encourage you to prioritise slightly more
>> regular
>> > releases …. Delivering little and often.
>> >
>> >
>> >
>> > Thanks
>> >
>> > Mark
>> >
>> >
>> >
>> > From: Glenn Adams [mailto:gl...@skynav.com]
>> > Sent: 25 November 2016 20:47
>> > To: FOP Users <fop-users@xmlgraphics.apache.org>
>> > Cc: Vishnu K <vishnu...@gmail.com>
>> > Subject: Re: any plans of an FOP 2.2 release any time soon
>> >
>> >
>> >
>> > We do not have a schedule yet for a 2.2 release.
>> >
>> >
>> >
>> > On Fri, Nov 25, 2016 at 11:07 AM, Vishnu K <vishnu...@gmail.com> wrote:
>> >
>> > Hi , I am new to FOP mailing list.. I would like to ask will there be
>> an FOP
>> > 2.2 release sooner ?
>> >
>> > regards
>> >
>> > vishnu.
>> >
>> >
>>
>>
>>
>> --
>> pascal
>>
>> -
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>>
>>
>

Re: Latest 2.2.0-SNAPSHOT broken fop-2.2.0-20161020.085836-42

[Glenn Adams]

No 2.2 release date plan yet, but let me ask the the PMC to review where we
are to determine if a release is appropriate.

On Fri, Oct 21, 2016 at 1:58 AM, Mark Gibson <
mark.gib...@staff.bluematrix.com> wrote:

> Are there any plans to release 2.2 in the near term?  Or is the focus
> mainly on bug nuking and feature implementation at the moment?
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com]
> *Sent:* 21 October 2016 02:08
> *To:* Jon Wu <j...@wuservices.com>
> *Cc:* FOP Users <fop-users@xmlgraphics.apache.org>; FOP Developers <
> fop-...@xmlgraphics.apache.org>
> *Subject:* Re: Latest 2.2.0-SNAPSHOT broken fop-2.2.0-20161020.085836-42
>
>
>
> You could always download the source tree from trunk and build the maven
> artifacts locally.
>
>
>
> On Thu, Oct 20, 2016 at 6:31 PM, Jon Wu <j...@wuservices.com> wrote:
>
> Thanks for the quick fix Glenn!
>
>
>
> Do you know if there's an easy way for me to use some FOP 2.2 without
> depending on the latest SNAPSHOT until the final is released?
>
>
>
> Wasn't sure if there was an easy solution to using a newer than official
> version and staying on the same build without having my own Maven server,
> but I'm pretty new to SBT/Ivy/Maven. The current version works for what
> I've needed it for, but pointing to SNAPSHOT causes long daily dependency
> resolutions and it could break any time of course.
>
>
>
> On Thu, Oct 20, 2016 at 3:01 PM Glenn Adams <gl...@skynav.com> wrote:
>
> Stand by. I will commit a fix to this configuration bug in a few moments.
>
>
>
> On Thu, Oct 20, 2016 at 2:38 PM, Jon Wu <j...@wuservices.com> wrote:
>
> Can SNAPSHOT be republished?
>
>
>
> I've been using 2.2.0-SNAPSHOT for compatibility with the latest PDFBox,
> but my build broke this morning because I think the last published snapshot
> is bad.
>
>
>
> Should https://repository.apache.org/content/repositories/snapshots/org/
> apache/xmlgraphics/fop/2.2.0-SNAPSHOT/fop-2.2.0-20161020.085836-42.pom,
> have 2.2.0-SNAPSHOT instead of
> ${fop.version} like the other POM files?
>
>
>
> I get this error in SBT
>
> [warn] io problem while parsing ivy file: https://repository.apache.org/
> content/repositories/snapshots/org/apache/xmlgraphics/fop/2.2.0-
> SNAPSHOT/fop-2.2.0-20161020.085836-42.pom: Impossible to load parent for
> file:/Users/jon/.ivy2/cache/org.apache.xmlgraphics/fop/
> ivy-2.2.0-SNAPSHOT.xml.original. Parent=org.apache.xmlgraphics#
> fop-parent;${fop.version}
>
>
>
> - RELATED QUESTION -
>
> It's brittle for my build to depend on the latest SNAPSHOT working,
> however there are so many transitive dependencies of the latest FOP. Is
> there an easy way for me to keep referring to the same SNAPSHOT build + all
> its dependencies?
>
>
>
>
>

Re: Latest 2.2.0-SNAPSHOT broken fop-2.2.0-20161020.085836-42

[Glenn Adams]

You could always download the source tree from trunk and build the maven
artifacts locally.

On Thu, Oct 20, 2016 at 6:31 PM, Jon Wu <j...@wuservices.com> wrote:

> Thanks for the quick fix Glenn!
>
> Do you know if there's an easy way for me to use some FOP 2.2 without
> depending on the latest SNAPSHOT until the final is released?
>
> Wasn't sure if there was an easy solution to using a newer than official
> version and staying on the same build without having my own Maven server,
> but I'm pretty new to SBT/Ivy/Maven. The current version works for what
> I've needed it for, but pointing to SNAPSHOT causes long daily dependency
> resolutions and it could break any time of course.
>
> On Thu, Oct 20, 2016 at 3:01 PM Glenn Adams <gl...@skynav.com> wrote:
>
>> Stand by. I will commit a fix to this configuration bug in a few moments.
>>
>> On Thu, Oct 20, 2016 at 2:38 PM, Jon Wu <j...@wuservices.com> wrote:
>>
>> Can SNAPSHOT be republished?
>>
>> I've been using 2.2.0-SNAPSHOT for compatibility with the latest PDFBox,
>> but my build broke this morning because I think the last published snapshot
>> is bad.
>>
>> Should https://repository.apache.org/content/repositories/snapshots/org/
>> apache/xmlgraphics/fop/2.2.0-SNAPSHOT/fop-2.2.0-20161020.085836-42.pom,
>> have 2.2.0-SNAPSHOT instead of
>> ${fop.version} like the other POM files?
>>
>> I get this error in SBT
>> [warn] io problem while parsing ivy file: https://repository.apache.org/
>> content/repositories/snapshots/org/apache/xmlgraphics/fop/2.2.0-
>> SNAPSHOT/fop-2.2.0-20161020.085836-42.pom: Impossible to load parent for
>> file:/Users/jon/.ivy2/cache/org.apache.xmlgraphics/fop/
>> ivy-2.2.0-SNAPSHOT.xml.original. Parent=org.apache.xmlgraphics#
>> fop-parent;${fop.version}
>>
>> - RELATED QUESTION -
>> It's brittle for my build to depend on the latest SNAPSHOT working,
>> however there are so many transitive dependencies of the latest FOP. Is
>> there an easy way for me to keep referring to the same SNAPSHOT build + all
>> its dependencies?
>>
>>
>>

Re: Latest 2.2.0-SNAPSHOT broken fop-2.2.0-20161020.085836-42

[Glenn Adams]

Stand by. I will commit a fix to this configuration bug in a few moments.

On Thu, Oct 20, 2016 at 2:38 PM, Jon Wu  wrote:

> Can SNAPSHOT be republished?
>
> I've been using 2.2.0-SNAPSHOT for compatibility with the latest PDFBox,
> but my build broke this morning because I think the last published snapshot
> is bad.
>
> Should https://repository.apache.org/content/repositories/snapshots/org/
> apache/xmlgraphics/fop/2.2.0-SNAPSHOT/fop-2.2.0-20161020.085836-42.pom,
> have 2.2.0-SNAPSHOT instead of
> ${fop.version} like the other POM files?
>
> I get this error in SBT
> [warn] io problem while parsing ivy file: https://repository.apache.org/
> content/repositories/snapshots/org/apache/xmlgraphics/fop/2.2.0-
> SNAPSHOT/fop-2.2.0-20161020.085836-42.pom: Impossible to load parent for
> file:/Users/jon/.ivy2/cache/org.apache.xmlgraphics/fop/
> ivy-2.2.0-SNAPSHOT.xml.original. Parent=org.apache.xmlgraphics#
> fop-parent;${fop.version}
>
> - RELATED QUESTION -
> It's brittle for my build to depend on the latest SNAPSHOT working,
> however there are so many transitive dependencies of the latest FOP. Is
> there an easy way for me to keep referring to the same SNAPSHOT build + all
> its dependencies?
>

Re: FOP and Avalon

[Glenn Adams]

There has been no discussion that I'm aware of. You are welcome to submit a
patch making the necessary changes.

On Thu, Aug 11, 2016 at 1:36 PM, jdebinder  wrote:

> The last question on this topic was back in 2007.  I also see a couple of
> more recent posts about the Maven link to Avalon 4.3.1.  I have to repeat
> the question about removing the dependency on Avalon.  As now even the
> Excalibur project has also been retired as of 2010.  I work on a product
> for
> IBM and due to security risks we are required to remove all frameworks that
> are no longer supported.  Since FOP depends on Avalon we will also have to
> remove our dependency on FOP and try to find something to replace it.
>
> Is there any more thought to removing the dependency on the Avalon
> framework?
>
>
>
> --
> View this message in context: http://apache-fop.1065347.n5.
> nabble.com/FOP-and-Avalon-tp44302.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: Spurious warning about missing fonts

[Glenn Adams]

They aren't spurious. You need to find where you are using these fonts
(directly or indirectly). It seems you are using bold versions of Symbol
and ZapfDingbats.

On Thu, Jul 28, 2016 at 7:11 AM, Stefan Radermacher 
wrote:

> Hello,
>
> FOP is generating a lot of warning about not finding some of the base-14
> fonts, even though I'm not actually using those. When processing my
> files, I'm practically inundated with these messages:
>
>
> Font "Symbol,normal,700" not found. Substituting with "Symbol,normal,400".
> Font "ZapfDingbats,normal,700" not found. Substituting with
> "ZapfDingbats,normal,400".
>
> I did some research and found this old archived discussion from the
> fop-dev list:
>
>
> http://apache-fop.1065347.n5.nabble.com/ZapfDingbats-and-Symbol-not-found-whereas-they-are-not-needed-td31330.html
>
> and also an entry in FOP's jira tracker:
>
> https://issues.apache.org/jira/browse/FOP-1667
>
> Both seem to indicate that this is the issue I am encountering. However
> this problem is practially ancient, is there any chance that this might
> get fixed?
>
> Kind regards
> Stefan
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: isolated high surrogate

[Glenn Adams]

nothing to do with being an FOP developer; keep in mind that the actual
input to FOP is XSL-FO, and not XNL + stylesheet; this latter functionality
is a convenience layer that IMO should never have been added to FOP, for
the simple reason that we keep fielding problem reports related to template
processing that are outside the scope of FOP; best to discuss template
problems with XSLT related MLs

On Thu, Jul 14, 2016 at 3:09 PM, Marc Kaufman <marck...@adobe.com> wrote:

> Worthwhile for someone to do, probably. Outside of my current needs. I’m
> not interested in being a FOP developer.
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com]
> *Sent:* Thursday, July 14, 2016 1:48 PM
>
> *To:* FOP Users <fop-users@xmlgraphics.apache.org>
> *Subject:* Re: isolated high surrogate
>
>
>
> I'd suggest you test FOP by using an XSL-FO input file directly rather
> than an XSL template. Template processing is not part of FOP functionality
> in the first place.
>
>
>
> On Thu, Jul 14, 2016 at 2:37 PM, Marc Kaufman <marck...@adobe.com> wrote:
>
> More specifically, if I replace “ “ with u/200B (zero width space) in the
> string that contains surrogate characters, FOP parsing fails even if I just
> use xsl:value-of. I’m not going to pursue that at this time. Maybe when FOP
> handles non-BMP characters it should be revisited.
>
>
>
> Marc
>
>
>
> *From:* Marc Kaufman [mailto:marck...@adobe.com]
> *Sent:* Thursday, July 14, 2016 12:34 PM
>
>
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: isolated high surrogate
>
>
>
> I’ve isolated the problem to a template definition that is trying to
> replace apace characters with non-breaking spaces. Evidently it clobbers
> some surrogate pairs. FWIW: here’s the offending line(s):
>
>
>
>   *<**xsl:template **name*=*"zero_width_space_1"**>*
>
> *<**xsl:param **name*=*"data"**/>*
>
> *<**xsl:param **name*=*"counter" **select*=*"0"**/>*
>
> *<**xsl:choose**>*
>
>   *<**xsl:when **test*=*"$counter  string-length($data)+1"**>*
>
> *<**xsl:value-of **select*=
> *'concat(substring($data,$counter,1),"")'**/>*
>
> *<**xsl:call-template **name*=*"zero_width_space_2"**>*
>
>   *<**xsl:with-param **name*=*"data" **select*=*"$data"**/>*
>
>   *<**xsl:with-param **name*=*"counter" **select*=*"$counter+1"*
> */>*
>
> **
>
>   **
>
>   *<**xsl:otherwise**>*
>
>   **
>
> **
>
>   **
>
>
>
>   *<**xsl:template **name*=*"zero_width_space_2"**>*
>
> *<**xsl:param **name*=*"data"**/>*
>
> *<**xsl:param **name*=*"counter"**/>*
>
> *<**xsl:value-of **select*=
> *'concat(substring($data,$counter,1),"")'**/>*
>
> *<**xsl:call-template **name*=*"zero_width_space_1"**>*
>
>   *<**xsl:with-param **name*=*"data" **select*=*"$data"**/>*
>
>   *<**xsl:with-param **name*=*"counter" **select*=*"$counter+1"**/>*
>
> **
>
>   **
>
>
>
> So, not an FOP problem.
>
>
>
> Marc
>
>
>
> *From:* Marc Kaufman [mailto:marck...@adobe.com <marck...@adobe.com>]
> *Sent:* Thursday, July 14, 2016 12:22 PM
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: isolated high surrogate
>
>
>
> I tried that. Doesn’t work. I understand that non-BMP is not supported,
> and I’m prepared to live with two .notdef characters in the result, but I’m
> not sure why I’m getting the fatal error from the parser.
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com <gl...@skynav.com>]
> *Sent:* Thursday, July 14, 2016 12:01 PM
> *To:* FOP Users <fop-users@xmlgraphics.apache.org>
> *Subject:* Re: isolated high surrogate
>
>
>
> Non-BMP characters are not presently supported by FOP, see [1]. When they
> are supported, you would best encode them in a file using a single (not
> two) numeric character entities, e.g., , etc.
>
>
>
> [1] https://issues.apache.org/jira/browse/FOP-1969
>
>
>
> On Thu, Jul 14, 2016 at 12:51 PM, Marc Kaufman <marck...@adobe.com> wrote:
>
> I’m stumped by this error:
>
> org.xml.sax.SAXParseException; lineNumber: 92; columnNumber: 51;
> java.lang.IllegalArgumentException: isolated high surrogate
>
>
>
> I have text with surrogate pairs throughout the file, but this only occurs
> in this context:
>
>  font-family="Kozuka Gothic PR6N" font-size="18pt" color="black">
>
>   *<**xsl:call-template **name*=*"zero_width_space_1"**>*
>
> *<**xsl:with-param **name*=*"data" **select*=*"@documentName"**/>*
>
>   **
>
> 
>
>
>
> I’ve checked the input stream, and all the surrogates are correctly
> paired. I’ve tried escaping the surrogate pairs (e.g. “
<

Re: isolated high surrogate

[Glenn Adams]

I'd suggest you test FOP by using an XSL-FO input file directly rather than
an XSL template. Template processing is not part of FOP functionality in
the first place.

On Thu, Jul 14, 2016 at 2:37 PM, Marc Kaufman <marck...@adobe.com> wrote:

> More specifically, if I replace “ “ with u/200B (zero width space) in the
> string that contains surrogate characters, FOP parsing fails even if I just
> use xsl:value-of. I’m not going to pursue that at this time. Maybe when FOP
> handles non-BMP characters it should be revisited.
>
>
>
> Marc
>
>
>
> *From:* Marc Kaufman [mailto:marck...@adobe.com]
> *Sent:* Thursday, July 14, 2016 12:34 PM
>
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: isolated high surrogate
>
>
>
> I’ve isolated the problem to a template definition that is trying to
> replace apace characters with non-breaking spaces. Evidently it clobbers
> some surrogate pairs. FWIW: here’s the offending line(s):
>
>
>
>   *<**xsl:template **name*=*"zero_width_space_1"**>*
>
> *<**xsl:param **name*=*"data"**/>*
>
> *<**xsl:param **name*=*"counter" **select*=*"0"**/>*
>
> *<**xsl:choose**>*
>
>   *<**xsl:when **test*=*"$counter  string-length($data)+1"**>*
>
> *<**xsl:value-of **select*=
> *'concat(substring($data,$counter,1),"")'**/>*
>
> *<**xsl:call-template **name*=*"zero_width_space_2"**>*
>
>   *<**xsl:with-param **name*=*"data" **select*=*"$data"**/>*
>
>   *<**xsl:with-param **name*=*"counter" **select*=*"$counter+1"*
> */>*
>
> **
>
>   **
>
>   *<**xsl:otherwise**>*
>
>   **
>
> **
>
>   **
>
>
>
>   *<**xsl:template **name*=*"zero_width_space_2"**>*
>
> *<**xsl:param **name*=*"data"**/>*
>
> *<**xsl:param **name*=*"counter"**/>*
>
> *<**xsl:value-of **select*=
> *'concat(substring($data,$counter,1),"")'**/>*
>
> *<**xsl:call-template **name*=*"zero_width_space_1"**>*
>
>   *<**xsl:with-param **name*=*"data" **select*=*"$data"**/>*
>
>   *<**xsl:with-param **name*=*"counter" **select*=*"$counter+1"**/>*
>
> **
>
>   **
>
>
>
> So, not an FOP problem.
>
>
>
> Marc
>
>
>
> *From:* Marc Kaufman [mailto:marck...@adobe.com <marck...@adobe.com>]
> *Sent:* Thursday, July 14, 2016 12:22 PM
> *To:* fop-users@xmlgraphics.apache.org
> *Subject:* RE: isolated high surrogate
>
>
>
> I tried that. Doesn’t work. I understand that non-BMP is not supported,
> and I’m prepared to live with two .notdef characters in the result, but I’m
> not sure why I’m getting the fatal error from the parser.
>
>
>
> *From:* Glenn Adams [mailto:gl...@skynav.com <gl...@skynav.com>]
> *Sent:* Thursday, July 14, 2016 12:01 PM
> *To:* FOP Users <fop-users@xmlgraphics.apache.org>
> *Subject:* Re: isolated high surrogate
>
>
>
> Non-BMP characters are not presently supported by FOP, see [1]. When they
> are supported, you would best encode them in a file using a single (not
> two) numeric character entities, e.g., , etc.
>
>
>
> [1] https://issues.apache.org/jira/browse/FOP-1969
>
>
>
> On Thu, Jul 14, 2016 at 12:51 PM, Marc Kaufman <marck...@adobe.com> wrote:
>
> I’m stumped by this error:
>
> org.xml.sax.SAXParseException; lineNumber: 92; columnNumber: 51;
> java.lang.IllegalArgumentException: isolated high surrogate
>
>
>
> I have text with surrogate pairs throughout the file, but this only occurs
> in this context:
>
>  font-family="Kozuka Gothic PR6N" font-size="18pt" color="black">
>
>   *<**xsl:call-template **name*=*"zero_width_space_1"**>*
>
> *<**xsl:with-param **name*=*"data" **select*=*"@documentName"**/>*
>
>   **
>
> 
>
>
>
> I’ve checked the input stream, and all the surrogates are correctly
> paired. I’ve tried escaping the surrogate pairs (e.g. “
<

Re: isolated high surrogate

[Glenn Adams]

Non-BMP characters are not presently supported by FOP, see [1]. When they
are supported, you would best encode them in a file using a single (not
two) numeric character entities, e.g., , etc.

[1] https://issues.apache.org/jira/browse/FOP-1969

On Thu, Jul 14, 2016 at 12:51 PM, Marc Kaufman  wrote:

> I’m stumped by this error:
>
> org.xml.sax.SAXParseException; lineNumber: 92; columnNumber: 51;
> java.lang.IllegalArgumentException: isolated high surrogate
>
>
>
> I have text with surrogate pairs throughout the file, but this only occurs
> in this context:
>
>  font-family="Kozuka Gothic PR6N" font-size="18pt" color="black">
>
>   *<**xsl:call-template **name*=*"zero_width_space_1"**>*
>
> *<**xsl:with-param **name*=*"data" **select*=*"@documentName"**/>*
>
>   **
>
> 
>
>
>
> I’ve checked the input stream, and all the surrogates are correctly
> paired. I’ve tried escaping the surrogate pairs (e.g. “

Re: NoSuchMethod - CFFCIDFont.getProperty

[Glenn Adams]

You should check to make sure your VM is loading fontbox-2.0.0.jar from the
fop/lib directory.

On Tue, Jul 12, 2016 at 2:04 PM, Marc Kaufman  wrote:

> I’m trying to use an Adobe CFF font (KozGoPr6N-Regular.otf). During the
> font loading I get to:
>
> OTFFile.readName() line 34: Object familyName =
> fileFont.getProperty(“FamilyName”);
>
> But fileFont is a org.apache.fontbox.cff.CFFCIDFont, and there is no such
> method “getProperty”.
>
>
>
> Stack:
>
> OTFFile.readName() line: 134
>
> OTFFile(OpenFont).readFont(FontFileReader, String, String) line: 740
>
> OFFontLoader.read(String) line: 109
>
> OFFontLoader.read() line: 93
>
> OFFontLoader(FontLoader).getFont() line: 124
>
> FontLoader.loadFont(FontUris, String, boolean, EmbeddingMode,
> EncodingMode, boolean, boolean, InternalResourceResolver) line: 108
>
>
>

Re: Arabic text and letter join

[Glenn Adams]

Please post a very short XSL-FO file containing a minimal example
demonstrating the problem.

On Thu, Jun 16, 2016 at 8:23 AM, Maxime Bégnis  wrote:

> Hello,
>
> I'm using FOP 2.1 to generate PDF documents in Arabic. It seems that the
> letters that should be joined are not. Attached is a sample result PDF.
>
> I paste here an example for the title of the document hoping it will be
> correctly displayed for the readers of this mail.
>
> ‫تكاليف‬ ‫سبتمبر‬
>
> I tried different fonts (Arial and Traditional Arabic) without success.
> Note that the text direction is handled properly.
>
> I would appreciate any advice on this.
>
> BR,
>
> --
> --
> *NeoDoc*
> *Maxime Bégnis*
> max...@neodoc.fr
> Tél: +33 (0)4.42.52.24.20
> 789 Rue de La Gare
> 13770 Venelles
> France
> http://www.neodoc.fr/
>

Re: When is the next release scheduled for

[Glenn Adams]

On Tue, May 24, 2016 at 9:45 AM, Mark Gibson <
mark.gib...@staff.bluematrix.com> wrote:

> Hi,
>
> There's a fix on trunk (https://issues.apache.org/jira/browse/FOP-2562)
> that we'd be very keen to see included in an official release ( we don't
> have the risk appetite for running production against a dev version of FOP
> ).
>
> What is the schedule for the next release version?
>

Generally speaking, we do not publish a schedule for upcoming releases. At
this point, we do not have a proposed schedule.


>
> Thanks
> Mark
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: FOP alignment problem between two font type

[Glenn Adams]

On Tue, Mar 8, 2016 at 10:00 PM, gkaplan <gkap...@kaplansoftware.com> wrote:

> I tried to use Arial Unicode MS but FOP complains that it is not found.
> I’m assuming it is not one of the built-in fonts.
>
> 1.   Do I need to configure FOP to use a custom font and then include
> it somewhere?
>
yes, see [1][2]

[1] https://xmlgraphics.apache.org/fop/2.1/configuration.html
[2] https://xmlgraphics.apache.org/fop/2.1/fonts.html

> 2.   If I do use a custom font, will it have to reside on everyone
> else’s machine, or will it reside inside the PDF so that it renders
> properly everywhere else?
>
by default, the used subset will be be embedded in the PDF, so it does not
have to be present (externally) when rendering the PDF

>
>
> Thanks
>
>
>
> *From:* Glenn Adams-2 [via Apache FOP] [mailto:ml-node+[hidden email]
> <http:///user/SendEmail.jtp?type=node=43653=0>]
> *Sent:* Tuesday, March 08, 2016 11:45 PM
> *To:* Gerry Kaplan <[hidden email]
> <http:///user/SendEmail.jtp?type=node=43653=1>>
> *Subject:* Re: FOP alignment problem between two font type
>
>
>
>
>
>
>
> On Tue, Mar 8, 2016 at 6:53 PM, Puja <[hidden email]
> <http:///user/SendEmail.jtp?type=node=43652=0>> wrote:
>
> I faced such issue with sigma character, I couldn't find worthwhile
> solution. Ended up using image of sigma character.
>
> On Mar 8, 2016 19:40, "gkaplan [via Apache FOP]" <[hidden email]
> <http://user/SendEmail.jtp?type=node=43651=0>> wrote:
>
> I am using XSL to create the FOP markup, so it is not possible for me to
> easily wrap special characters in their own inline block. I am using the
> greater-than-or-equals ≥ symbol which is only available in the Symbol font.
> The rest of the document is in sans-serif.
>
> What's odd is that any numbers subsequent to the ≥ symbol are also in the
> Symbol font.
>
> My markup includes an attribute-set as follows:
>
> 
>  select="$fontSize"/>
> sans-serif,
> Symbol
> 
>
> But when the PDF is generated, the baseline (or some other attribute) of
> the ≥ symbol is much lower.
>
> Arial Unicode MS
>
> Noto Sans
>
> etc.
>
>
>
> Is there really no way to fix this? I've tried tinkering with setting
> baselines, etc. but nothing fixes this. Also, as the previous solution
> mentions, I don't know of any fonts that include this symbol as well as the
> full alphabet.
>
> Thanks in advance for any help.
> --
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
>
> http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322p43650.html
>
> To unsubscribe from FOP alignment problem between two font type, click
> here.
> NAML
> <http://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
>
> --
>
> View this message in context: Re: FOP alignment problem between two font
> type
> <http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322p43651.html>
> Sent from the FOP - Users mailing list archive
> <http://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.html> at Nabble.com.
>
>
>
>
> --
>
> *If you reply to this email, your message will be added to the discussion
> below:*
>
>
> http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322p43652.html
>
> To unsubscribe from FOP alignment problem between two font type, click
> here.
> NAML
> <http://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
> --
> View this message in context: RE: FOP alignment problem between two font
> type
> <http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322p43653.html>
>
> Sent from the FOP - Users mailing list archive
> <http://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.html> at Nabble.com.
>

Re: FOP alignment problem between two font type

[Glenn Adams]

On Tue, Mar 8, 2016 at 6:53 PM, Puja  wrote:

> I faced such issue with sigma character, I couldn't find worthwhile
> solution. Ended up using image of sigma character.
> On Mar 8, 2016 19:40, "gkaplan [via Apache FOP]" <[hidden email]
> > wrote:
>
>> I am using XSL to create the FOP markup, so it is not possible for me to
>> easily wrap special characters in their own inline block. I am using the
>> greater-than-or-equals ≥ symbol which is only available in the Symbol font.
>> The rest of the document is in sans-serif.
>>
>> What's odd is that any numbers subsequent to the ≥ symbol are also in the
>> Symbol font.
>>
>> My markup includes an attribute-set as follows:
>>
>> 
>> > select="$fontSize"/>
>> sans-serif,
>> Symbol
>> 
>>
>> But when the PDF is generated, the baseline (or some other attribute) of
>> the ≥ symbol is much lower.
>
> Arial Unicode MS
Noto Sans
etc.

>
>>
>> Is there really no way to fix this? I've tried tinkering with setting
>> baselines, etc. but nothing fixes this. Also, as the previous solution
>> mentions, I don't know of any fonts that include this symbol as well as the
>> full alphabet.
>>
>> Thanks in advance for any help.
>>
>> --
>> If you reply to this email, your message will be added to the discussion
>> below:
>>
>> http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322p43650.html
>> To unsubscribe from FOP alignment problem between two font type, click
>> here.
>> NAML
>> 
>>
>
> --
> View this message in context: Re: FOP alignment problem between two font
> type
> 
> Sent from the FOP - Users mailing list archive
>  at Nabble.com.
>

Re: upgrading to FOP 2.1

[Glenn Adams]

If you don't use non-latin scripts, such as Arabic, CJK, etc., and don't
care about ligatures, you can turn off complex script processing. See [1].
There may also be other performance affecting factors.

[1] https://xmlgraphics.apache.org/fop/2.1/complexscripts.html

On Tue, Feb 23, 2016 at 3:12 AM, Amerise Marianna <
marianna.amer...@cerved.com> wrote:

> Hi,
>
>
>
> We want to move our application from FOP 0.20.5 to FOP 2.1.
>
> After upgrading, i noticed that the running times have increased compared
> to version 0.20.5.
>
> Is there something to put in the fop.xconf file?
>
> Have you suggestions for improving performance?
>
>
>
>
>
> Thanks in advance,
>
> Marianna
>
>
>

Re: CJK supplementary characters support issue

[Glenn Adams]

This is a known issue, see [1].

[1] https://issues.apache.org/jira/browse/FOP-1969

On Mon, Feb 22, 2016 at 7:19 AM, Chauhan Shubham <
chauhan.shubha...@gmail.com> wrote:

> Hello!
>
> I am currently facing issue with the CJK supplementary characters support.
> While processing the xml having Non-BMP code points (Code points outside
> the
> Unicode Base Multilingual Plane (BMP), i.e., characters whose scalar value
> is greater than 65535 (decimal)) are converted to parts of the surrogate
> pairs while formatting before being processed. Attaching the .fo file.
>
> Today, the majority of Unicode's characters are outside the BMP. This
> involves many alphabets and other character sets. Here are links to two of
> these non-BMP planes:
> http://www.unicode.org/roadmaps/smp/ and
> http://www.unicode.org/roadmaps/sip/ and more are to come because dozens
> of
> alphabets are not part of Unicode, yet.
>
> At present, FOP does not correctly seem to handle this. Hence, request if
> someone can help me with this?
>
> Thanks!
>
> Shubham Chauhan chinese.fo
> 
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/CJK-supplementary-characters-support-issue-tp43547.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: fo:character and zero width space

[Glenn Adams]

On Fri, Feb 12, 2016 at 3:17 AM, Carlos Villegas <c...@uniscope.jp> wrote:

> This is the result of my tests so far:
>
> treat-as-word-space doesn't have any effect. Looking at the compliance
> page, it's listed as not supported!
>

Perhaps adding support for treat-as-word-space would be a sufficient fix
for this problem. Feel free to post a patch.


>
> By wrapping the thai text in a fo:inline, using a regular space as word
> separator and setting word-spacing property, I get some results but I
> haven't been able to get zero width on the spaces for non-justified text.
> According to the spec, word-spacing is used to adjust the word spacing "in
> addition to normal spacing", so I tried something like the following:
>
> Thai
> text with normal spaces as word separators
>
> When justifying I do get some lines where the word spacing is zero, but
> when justifying left, there's always some interword spacing. I tried
> several values, but can't get it to zero.
> One complication I have is how to know the "normal" word space so I can
> adjust it to zero.
>
> Anyway to get word-spacing optimum and minimum to zero?
>

>
> Carlos
>
> On 2/12/16 15:11, Glenn Adams wrote:
>
>
>
> On Thu, Feb 11, 2016 at 9:23 PM, Carlos Villegas < <c...@uniscope.jp>
> c...@uniscope.jp> wrote:
>
>> I'm trying to use FOP 2.0 to render Thai language. FOP doesn't really
>> support Thai script
>
>
> FOP does support Thai, at least glyph composition, though there appears to
> be a few open issues (FOP-2092
> <https://issues.apache.org/jira/browse/FOP-2092>, FOP-2355
> <https://issues.apache.org/jira/browse/FOP-2355>). It is also true that
> FOP is not presently performing line breaking in phrase internal positions (
> FOP-2066 <https://issues.apache.org/jira/browse/FOP-2266>), which
> proposes a solution to employ ICU and use dictionary based LB.
>
>
>> , so I'm using an external program (libthai) to do glyph composition and
>> word breaking.
>> Thai doesn't use spaces to separate words, so I was just inserting zero
>> width spaces to separate words. This works fine.
>> However, for justified text, these zero width spaces don't stretch, so
>> nothing happens, I get no justified text.
>> So, I tried to use fo:character with character set to zero width space,
>> and setting the letter-spacing.maximum to allow some stretching.
>>
>
> Zero width space (U+200B) is not treated as a word separator space by
> default. Have you tried something like:
>
> 
>
> If that doesn't work, then keep in mind that letter spacing has no meaning
> when applied to a single character, but applies to a sequence of
> characters. Accordingly, I would try something like:
>
>  letter-spacing.maximum="0.1em">
>
> or
>
>  letter-spacing.maximum="0.1em"> treat-as-word-space='true'>
>
> If neither approach works, it may require some time with a visual
> debugger, e.g., Eclipse, to step through the code and find out where things
> go wrong.
>
>
>
>> But now FOP doesn't seem to treat the zero width space as such this way,
>> it doesn't break anymore at all!
>>
>> Note that Thai does make use of regular spaces to separate sentences and
>> for other purposes but there's no guarantee that you have spaces in a given
>> paragraph or in case of long sentences.
>>
>> Is there a way to insert a breakable space with minimum and optimum to
>> zero width and some small value for maximum?
>>
>> Carlos
>>
>>
>> -
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: <fop-users-h...@xmlgraphics.apache.org>
>> fop-users-h...@xmlgraphics.apache.org
>>
>>
>
>

Re: fo:character and zero width space

[Glenn Adams]

On Fri, Feb 12, 2016 at 12:08 AM, Carlos Villegas <c...@uniscope.jp> wrote:

> Thanks, I'll try your suggestions.
>
> The open issues in Thai glyph composition are major, basically the output
> is simply not acceptable.
>

Understood.


> Correct positioning of vowels, diacritics and tonemarks is not a esthetic
> thing only, sometimes when they are in the wrong position they print on top
> of each other or on top of the wrong base character.   So I wouldn't say
> FOP supports Thai!
>

Actually, I read and speak Thai, so I would agree. It will be useful to
resolve these last bugs on the Thai script support so folks can start using
FOP for Thai content.


>
> I have Java code that I can donate that does glyph substitution for Thai,
> but this is based on the fact that Thai fonts also encode alternate glyphs
> into the Unicode user range.
>

This approach is not acceptable in FOP due to the reliance upon
non-standard coding and font dependent usage. FOP will only use of
GSUB/GPOS font tables, so we need to make this work properly for Thai.


> There are basically two encodings: Microsoft's and Mac's, and my code
> works with Microsoft's fonts. However, I think, the right way to do this is
> to read the font's own substitution tables, this information must be there
> inside the fonts, and use that. But if the font doesn't really have that
> information, my code could be use as a fallback if you at least know that
> it is a Microsoft encoded font.
>
> Carlos
>
>
> On 2/12/16 15:11, Glenn Adams wrote:
>
>
>
> On Thu, Feb 11, 2016 at 9:23 PM, Carlos Villegas < <c...@uniscope.jp>
> c...@uniscope.jp> wrote:
>
>> I'm trying to use FOP 2.0 to render Thai language. FOP doesn't really
>> support Thai script
>
>
> FOP does support Thai, at least glyph composition, though there appears to
> be a few open issues (FOP-2092
> <https://issues.apache.org/jira/browse/FOP-2092>, FOP-2355
> <https://issues.apache.org/jira/browse/FOP-2355>). It is also true that
> FOP is not presently performing line breaking in phrase internal positions (
> FOP-2066 <https://issues.apache.org/jira/browse/FOP-2266>), which
> proposes a solution to employ ICU and use dictionary based LB.
>
>
>> , so I'm using an external program (libthai) to do glyph composition and
>> word breaking.
>> Thai doesn't use spaces to separate words, so I was just inserting zero
>> width spaces to separate words. This works fine.
>> However, for justified text, these zero width spaces don't stretch, so
>> nothing happens, I get no justified text.
>> So, I tried to use fo:character with character set to zero width space,
>> and setting the letter-spacing.maximum to allow some stretching.
>>
>
> Zero width space (U+200B) is not treated as a word separator space by
> default. Have you tried something like:
>
> 
>
> If that doesn't work, then keep in mind that letter spacing has no meaning
> when applied to a single character, but applies to a sequence of
> characters. Accordingly, I would try something like:
>
>  letter-spacing.maximum="0.1em">
>
> or
>
>  letter-spacing.maximum="0.1em"> treat-as-word-space='true'>
>
> If neither approach works, it may require some time with a visual
> debugger, e.g., Eclipse, to step through the code and find out where things
> go wrong.
>
>
>
>> But now FOP doesn't seem to treat the zero width space as such this way,
>> it doesn't break anymore at all!
>>
>> Note that Thai does make use of regular spaces to separate sentences and
>> for other purposes but there's no guarantee that you have spaces in a given
>> paragraph or in case of long sentences.
>>
>> Is there a way to insert a breakable space with minimum and optimum to
>> zero width and some small value for maximum?
>>
>> Carlos
>>
>>
>> -
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: <fop-users-h...@xmlgraphics.apache.org>
>> fop-users-h...@xmlgraphics.apache.org
>>
>>
>
>

Re: fo:character and zero width space

[Glenn Adams]

On Thu, Feb 11, 2016 at 9:23 PM, Carlos Villegas  wrote:

> I'm trying to use FOP 2.0 to render Thai language. FOP doesn't really
> support Thai script


FOP does support Thai, at least glyph composition, though there appears to
be a few open issues (FOP-2092
, FOP-2355
). It is also true that FOP
is not presently performing line breaking in phrase internal positions (
FOP-2066 ), which proposes
a solution to employ ICU and use dictionary based LB.


> , so I'm using an external program (libthai) to do glyph composition and
> word breaking.
> Thai doesn't use spaces to separate words, so I was just inserting zero
> width spaces to separate words. This works fine.
> However, for justified text, these zero width spaces don't stretch, so
> nothing happens, I get no justified text.
> So, I tried to use fo:character with character set to zero width space,
> and setting the letter-spacing.maximum to allow some stretching.
>

Zero width space (U+200B) is not treated as a word separator space by
default. Have you tried something like:



If that doesn't work, then keep in mind that letter spacing has no meaning
when applied to a single character, but applies to a sequence of
characters. Accordingly, I would try something like:



or



If neither approach works, it may require some time with a visual debugger,
e.g., Eclipse, to step through the code and find out where things go wrong.



> But now FOP doesn't seem to treat the zero width space as such this way,
> it doesn't break anymore at all!
>
> Note that Thai does make use of regular spaces to separate sentences and
> for other purposes but there's no guarantee that you have spaces in a given
> paragraph or in case of long sentences.
>
> Is there a way to insert a breakable space with minimum and optimum to
> zero width and some small value for maximum?
>
> Carlos
>
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: changing the look of the PDF output by FOP

[Glenn Adams]

The first thing you need to understand is that the input to FOP is XSL-FO
[1]. Although FOP provides a built-in utility mechanism to convert
arbitrary XML to XSL-FO by means of an XSLT transformation as a
pre-processing step, this mechanism is convenience function only, and
unrelated to FOP functionality in general.

So, you should think of FOP as a transformation pipeline that converts
XSL-FO into some rendered form, like PDF. If we add the convenience
function above to the description, you get:

XML + XSLT -> XSL-FO -> {Rendered Format, e.g., PDF}

To understand what the rendered output is, you need to understand XSL-FO
enough to control the pre-processing stage (XML + XSLT -> XSL-FO). The real
functionality of FOP is all in the second part of the pipeline: XSL-FO ->
Rendered Format.

[1] https://www.w3.org/TR/xsl/




On Sun, Jan 31, 2016 at 9:23 PM, Peter Michaux 
wrote:

> Hi,
>
> I'm new to FOP and feeling a little disoriented about the correct way to
> change the look of the PDF that is output by FOP.
>
> My source is an AsciiDoc text file and I have no trouble converting that
> to a Docbook XML file.
>
> $ asciidoc --backend=docbook45 book.txt
>
> I can then use the fop command line tool to convert to a PDF file.
>
> $ fop-2.1/fop -xml book.xml \
>   -xsl docbook-xsl-ns-1.79.1/fo/docbook.xsl \
>   -pdf book.pdf
>
> The default look of the produced book.pdf is nice but I'd like to adjust
> font families, font sizes, margins, etc.
>
> I did discover one way to customize the fonts by creating a fop.xconf file
> with the following content
>
> 
> 
> 
> 
>  embed-url="fonts/MyriadPro-Cond.otf" embedding-mode="subset">
>  style="normal" weight="normal"/>
> 
>  embed-url="fonts/MinionPro-Regular.otf" embedding-mode="subset">
>  weight="normal"/>
> 
>  embedding-mode="subset">
>  weight="normal"/>
> 
> 
> 
> 
> 
>
> and then using the following command
>
> $ fop-2.1/fop -c fop.xconf\
>   -xml book.xml   \
>   -xsl docbook-xsl-ns-1.79.1/fo/docbook.xsl   \
>   -param body.font.family Minion-Regular  \
>   -param title.font.family Myriad-Condensed   \
>   -param monospace.font.family Andale-Mono\
>   -pdf book.pdf
>
> Even though the above font setting technique was something I learned from
> a blog on the Web, at this point, I'm already unsure if I'm going in the
> right to doing this kind of customization properly or not. I imagine there
> is a better way to than passing a growing number of parameters to the fop
> command line tool.
>
> Then I tried to see if I could have an affect on margins and the footer
> font.
>
> $ fop-2.1/fop -c fop.xconf\
>   -xml book.xml   \
>   -xsl docbook-xsl-ns-1.79.1/fo/docbook.xsl   \
>   -param body.font.family Minion-Regular  \
>   -param title.font.family Myriad-Condensed   \
>   -param page.margin.top 0\
>   -param footer.content.font-family Helvetica \
>   -param monospace.font.family Andale-Mono\
>   -pdf book.pdf
>
> The page.margin.top param did work. A small success!
>
> The footer.content.font-family param did not work. I also tried
> footer.content.properties.font-family, footer.content.font.family, and
> footer.content.properties.font.family without finding the right solution.
>
> What's the right way to configure things so fop is outputting the PDF I
> dream of sharing with folks?
>
> Thanks!
>
> Peter
>
>

Re: Any news about the FOP 2.1 release timeline?

[Glenn Adams]

Note that the team is discussing a possible bugfix release before the maven
transition work is complete. I will send an update on this subject if that
should transpire.

On Mon, Jan 4, 2016 at 10:54 AM, Glenn Adams <gl...@skynav.com> wrote:

> No fixed release schedule has been set. One gating factor is a transition
> to maven build process which I expect to be put in place before a new
> release, but this will depend also on doing the same transition for batik
> and xmlgraphics-commons.
>
> On Mon, Jan 4, 2016 at 7:20 AM, Radu Coravu <radu_cor...@sync.ro> wrote:
>
>> Hi everybody,
>>
>> Do you know when the next Apache FOP (2.1?) will be released?
>> I'm interested in having some NPEs which were introduced in 2.0 fixed:
>>
>> https://issues.apache.org/jira/browse/FOP-2461
>>
>> Regards,
>> Radu
>>
>> Radu Coravu
>>   XML Editor, Schema Editor and XSLT Editor/Debugger
>> http://www.oxygenxml.com
>>
>> -
>> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
>> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>>
>>
>

Re: Any news about the FOP 2.1 release timeline?

[Glenn Adams]

No fixed release schedule has been set. One gating factor is a transition
to maven build process which I expect to be put in place before a new
release, but this will depend also on doing the same transition for batik
and xmlgraphics-commons.

On Mon, Jan 4, 2016 at 7:20 AM, Radu Coravu  wrote:

> Hi everybody,
>
> Do you know when the next Apache FOP (2.1?) will be released?
> I'm interested in having some NPEs which were introduced in 2.0 fixed:
>
> https://issues.apache.org/jira/browse/FOP-2461
>
> Regards,
> Radu
>
> Radu Coravu
>   XML Editor, Schema Editor and XSLT Editor/Debugger
> http://www.oxygenxml.com
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: FOP Special characters rendering

[Glenn Adams]

You need to use a font that has a glyph for each character. None of the
"base 14" fonts do so.

Also, FYI, please provide example input in terms of FO content, not XSL
input.

On Mon, Dec 14, 2015 at 9:14 PM, FOPUser  wrote:

> We are currently using FOP 1.0 for PDF generation. One of the requirements
> for our application is to support  special characters. The special
> characters are part of the content that the application receives from a
> third party. So, we don’t know where special characters occurs in the
> content. The requirement is the render the  special characters in the PDF .
> While, testing the special characters we found all, the special characters
> from the Symbol fonts are rendered as ‘#’ in the PDF.   From the logs it is
> clear  non availability of the glyps are the reason for special characters
> rendered as #.  The symbol fonts are part of the  14 base fonts and doesn’t
> need any additional configuration. Appreciate any help that will help us
> move forward on this.
> I am using the example from the
> https://xmlgraphics.apache.org/fop/quickstartguide.html and below are
> examples and output from PDF generation.
>
> name.xml:
> Ohm unicode - ""Omega decimal code- ""
>
> name2fo.xsl:
>
> 
>xmlns:xsl="http://www.w3.org/1999/XSL/Transform;
>   xmlns:fo="http://www.w3.org/1999/XSL/Format;>
>   
>   
> 
>   
>page-height="29.7cm" page-width="21.0cm" margin="2cm">
>   
> 
>   
>   
> 
>   
>  
>   
> 
>   
> 
>   
> 
>
> Output:
> C:\fop -xml name.xml -xsl name2fo.xsl -pdf name.pdf
>
> Dec 14, 2015 9:49:55 PM org.apache.fop.events.LoggingEventListener
> processEvent
> WARNING: Glyph "?" (0x2126, Ohm) not available in font "Helvetica".
> Dec 14, 2015 9:49:55 PM org.apache.fop.events.LoggingEventListener
> processEvent
> WARNING: Glyph "?" (0x3a9, Omegagreek) not available in font "Helvetica".
> Dec 14, 2015 9:49:55 PM org.apache.fop.events.LoggingEventListener
> processEvent
> INFO: Rendered page #1.
> name.pdf 
> name.pdf 
>
>
>
> --
> View this message in context:
> http://apache-fop.1065347.n5.nabble.com/FOP-Special-characters-rendering-tp43155.html
> Sent from the FOP - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
> For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
>
>

Re: NPE while generating multi language pdf with FOP 1.1

[Glenn Adams]

No. But you are welcome to patch and build a local copy yourself.

On Thu, Jul 23, 2015 at 1:39 PM, jeya venkatesh M m.jeyavenkat...@gmail.com
 wrote:

 Hello,

 We are migrating from FOP 1.0 to 1.1. I get NPE while generating a multi
 language PDF. It usually worked in 1.0.

 I verified that this is associated with issue FOP 2415 is fixed as part
 2.0. As of now, we are not in position to upgrade to 2.0. Is there any
 option to get it fixed in patch?

 Below is the stack trace.

 Regards,
 Venkatesh

 -
 Jul 22, 2015 3:15:17 PM org.apache.fop.hyphenation.Hyphenator
 getHyphenationTree
 SEVERE: Couldn't find hyphenation pattern for lang=en.
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Microsoft JhengHei,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Microsoft JhengHei,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Microsoft JhengHei,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Gulim,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Gulim,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character:
 Gulim,normal,400
 Jul 22, 2015 3:15:18 PM org.apache.fop.fo.properties.CommonHyphenation
 getHyphChar
 WARNING: Substituted specified hyphenation character (0x2d) with 0x20
 because the font doesn't have the specified hyphenation character: Shonar
 Bangla,normal,400
 Exception running transformationjava.lang.NullPointerException
 at
 org.apache.fop.complexscripts.scripts.IndicScriptProcessor$Syllabizer.makeSyllabizer(IndicScriptProcessor.java:430)
 at
 org.apache.fop.complexscripts.scripts.IndicScriptProcessor$Syllabizer.getSyllabizer(IndicScriptProcessor.java:417)
 at
 org.apache.fop.complexscripts.scripts.IndicScriptProcessor.syllabize(IndicScriptProcessor.java:226)

 at
 org.apache.fop.complexscripts.scripts.IndicScriptProcessor.substitute(IndicScriptProcessor.java:186)
 at
 org.apache.fop.complexscripts.scripts.ScriptProcessor.substitute(ScriptProcessor.java:96)
 at
 org.apache.fop.complexscripts.fonts.GlyphSubstitutionTable.substitute(GlyphSubstitutionTable.java:102)
 at
 org.apache.fop.fonts.MultiByteFont.performSubstitution(MultiByteFont.java:412)
 at org.apache.fop.fonts.LazyFont.performSubstitution(LazyFont.java:414)
 at org.apache.fop.fonts.Font.performSubstitution(Font.java:410)
 at
 org.apache.fop.layoutmgr.inline.TextLayoutManager.processWordMapping(TextLayoutManager.java:1006)
 at
 org.apache.fop.layoutmgr.inline.TextLayoutManager.processWord(TextLayoutManager.java:1177)
 at
 org.apache.fop.layoutmgr.inline.TextLayoutManager.getNextKnuthElements(TextLayoutManager.java:910)
 at
 org.apache.fop.layoutmgr.inline.InlineLayoutManager.getNextKnuthElements(InlineLayoutManager.java:329)
 at
 org.apache.fop.layoutmgr.inline.LineLayoutManager.collectInlineKnuthElements(LineLayoutManager.java:689)
 at
 org.apache.fop.layoutmgr.inline.LineLayoutManager.getNextKnuthElements(LineLayoutManager.java:622)
 at
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextChildElements(BlockLayoutManager.java:141)
 at
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextKnuthElements(BlockStackingLayoutManager.java:288)
 at
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:113)
 at
 org.apache.fop.layoutmgr.BlockLayoutManager.getNextKnuthElements(BlockLayoutManager.java:105)
 at
 org.apache.fop.layoutmgr.BlockStackingLayoutManager.getNextChildElements(BlockStackingLayoutManager.java:497)
 at
 org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:256)
 at
 org.apache.fop.layoutmgr.BlockContainerLayoutManager.getNextKnuthElements(BlockContainerLayoutManager.java:186)
 at
 org.apache.fop.layoutmgr.table.TableCellLayoutManager.getNextKnuthElements(TableCellLayoutManager.java:153)
 at
 

Re: FOP2.0 taking more time format complex script documents

[Glenn Adams]

Yes, you are right. It also uses more memory. These are unavoidable side
effects of the ability to process complex scripts and font features.

If you don't need any complex script features, then you can disable that
processing as described in the documentation [1].

[1]
http://xmlgraphics.apache.org/fop/2.0/complexscripts.html#Disabling-complex-scripts

On Tue, Jun 23, 2015 at 6:48 AM, sripathi sripathi.rao...@gmail.com wrote:

 Hi All,

  Initially,we are used FOP0.20.5 in my application,now we migrated to
 FOP2.0.But FOP2.0 is taking more time to format complex
 script(Chinese,Japanese..etc) documents comparing to FOP0.20.5.

 Could you please help me on this issue..


 Thanks,
 Sripathi



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP2-0-taking-more-time-format-complex-script-documents-tp42461.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Missing glyph error, but font contains glyph

[Glenn Adams]

If you are using the built-in Times font, then it does not include a glyph
for that character.

On Tue, Jun 23, 2015 at 9:09 AM, mulos daniel.strackb...@mbi.de wrote:

  Hi,



 output format is PDF. Font type is TTF.



 If I embedd another font (cambria), the character is found correctly. But
 why? Times contains this character. The config file (times.xml) contains
 it, too.



 Thanks,



 Daniel







 *Von:* Robert Meyer-5 [via Apache FOP] [mailto:ml-node+[hidden email]
 http:///user/SendEmail.jtp?type=nodenode=42465i=0]
 *Gesendet:* Dienstag, 23. Juni 2015 17:00
 *An:* Daniel Strackbein
 *Betreff:* RE: Missing glyph error, but font contains glyph



 Hi,

 Could you provide extra details such as the output format (PDF,
 Postscript, AFP) and the font type you're using (Type1, TTF, OpenType)?

 Thanks,

 Robert

  Date: Tue, 23 Jun 2015 07:34:36 -0700


  From: [hidden email]
 http:///user/SendEmail.jtp?type=nodenode=42464i=0
  To: [hidden email] http:///user/SendEmail.jtp?type=nodenode=42464i=1
  Subject: Missing glyph error, but font contains glyph
 
  Hi, I get the following error:
 
  Jun 23, 2015 4:28:46 PM org.apache.fop.events.LoggingEventListener
  processEvent
  WARNING: Glyph ? (0x1e7, gcaron) not available in font TimesNewRoman.
  java version 1.7.0_17
  Java(TM) SE Runtime Environment (build 1.7.0_17-b02)
  Java HotSpot(TM) 64-Bit Server VM (build 23.7-b01, mixed mode)
 
  This character exists in the times new roman font. Why does this message
  appear?
 
 
 
  --
  View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Missing-glyph-error-but-font-contains-glyph-tp42463.html
  Sent from the FOP - Users mailing list archive at Nabble.com.
 
  -
  To unsubscribe, e-mail: [hidden email]
 http:///user/SendEmail.jtp?type=nodenode=42464i=2
  For additional commands, e-mail: [hidden email]
 http:///user/SendEmail.jtp?type=nodenode=42464i=3
 


  --

 *If you reply to this email, your message will be added to the discussion
 below:*


 http://apache-fop.1065347.n5.nabble.com/Missing-glyph-error-but-font-contains-glyph-tp42463p42464.html

 To unsubscribe from Missing glyph error, but font contains glyph, click
 here.
 NAML
 http://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml

 --
 View this message in context: AW: Missing glyph error, but font contains
 glyph
 http://apache-fop.1065347.n5.nabble.com/Missing-glyph-error-but-font-contains-glyph-tp42463p42465.html

 Sent from the FOP - Users mailing list archive
 http://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.html at Nabble.com.

Re: FOP 1.1 - Japanese 4-byte characters are rendering as '?' in pdf

[Glenn Adams]

Firstly, I suggest you avoid using the term 4-byte Japanese characters,
since that has no meaning except in the context of some encoding, like
UTF-8, UTF-16, UTF-32, etc. In Java, all String objects are encoded in
UTF-16 as 16-bit code units. So BMP characters use one 16-bit code unit,
and non-BMP characters use two 16-bit code units, i.e., an upper and lower
surrogate.

Hiragana characters are encoded in the BMP in the range U+3040 to U+309F
[1], Katakana in U+30A0 to U+30FF [2], and CJK Ideographs starting at
U+4E00.

[1] http://www.unicode.org/charts/PDF/U3040.pdf
[2] http://www.unicode.org/charts/PDF/U30A0.pdf
[3] http://www.unicode.org/charts/PDF/U4E00.pdf

For external FO files, or XML files you will translate to FO via XSLT, you
should use the UTF-8 encoding of Unicode, and ensure that you provide a
correct XML declaration at the beginning of your file:

?xml version=1.0 encoding=utf-8?

I also suggest that you ensure the presence of the UTF-8 encoding of the
BOM [4] at the beginning of the file: 0xEF 0xBB 0xBF.

[4] http://en.wikipedia.org/wiki/Byte_order_mark

On Wed, May 20, 2015 at 3:20 AM, mrunal28 loha...@gmail.com wrote:

 Hi Glenn,

 I am trying to understand if Katakana japanese language is a BMP unicode as
 per below link:
 http://www.sttmedia.com/unicode-basiclingualplane
 http://www.sttmedia.com/unicode-basiclingualplane

 If I assume that Katakana is a 4-byte japanese language. As per your reply
 if Katakana is BMP encoded and FOP supports it, then using FOP 1.1, my code
 should render 4-byte japanese characters correctly in pdf.

 I am attaching my code which I am using to convert japanese text into pdf.
 Please find attached files. fop_allfonts.xconf
 http://apache-fop.1065347.n5.nabble.com/file/n42155/fop_allfonts.xconf
 ExampleXML2PDF.java
 http://apache-fop.1065347.n5.nabble.com/file/n42155/ExampleXML2PDF.java

 Please if you have suggestion on shared files.

 So Questions are:
 1. Is Kanataka is BMP encoded? I assume it is.
 2. Am I missing something in code to convert japanese 4-byte into pdf?



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-1-1-Japanese-4-byte-characters-are-rendering-as-in-pdf-tp42117p42155.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP 1.1 - Japanese 4-byte characters are rendering as '?' in pdf

[Glenn Adams]

Not sure what you mean by four byte characters unless you are referring
to non-BMP Unicode code points, i.e., those that require two 16-bit UTF-16
surrogates. FOP does not yet support non-BMP encoded characters.

On Mon, May 18, 2015 at 6:01 AM, mrunal28 loha...@gmail.com wrote:

 Hi,

 I am using FOP 1.1 and trying to convert xml to pdf. My XML file contains
 japanese 4-byte characters(/カサタナハ) whose font is japanese katakana.

 But my generated PDF contains '?' instead of original japanese characters.

 I have font file for example katakana.ttf and made corresponding entry in
 FOP config file as below:

 fop
   renderers
   renderer mime=application/pdf
  fonts

font-triplet name=katakana style=normal
 weight=normal/

   /fonts
   /renderer
   /renderers
 /fop

 Can anyone please tell me if FOP 1.1 supports japanese 4-byte characters
 and
 if so what extra configuration is required?

 I look out for same but none of FOP documentation clearly mentions that.



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-1-1-Japanese-4-byte-characters-are-rendering-as-in-pdf-tp42117.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Arabic letters not formed properly after adding Zero Width Space (#x200B;)

[Glenn Adams]

well, you will have to find a different solution for Arabic, as any
whitespace character between two nominally joining Arabic letters
effectively prevents their joining

On Wed, Apr 22, 2015 at 5:09 AM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hello Glenn,

 If we remove the ZWSP , the contents are overflowing to the next cell.
 Actually we introducted ZWSP for solving that issue.

 P.S. We were not allowed to use fop hypenation due to licensing issue and
 that's why we took the XSLT solution.

 Regards
 Kumar.T



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Arabic-letters-not-formed-properly-after-adding-Zero-Width-Space-x200B-tp41977p41995.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Arabic letters not formed properly after adding Zero Width Space (#x200B;)

[Glenn Adams]

You cannot insert spaces between Arabic characters and expect them to join.
Remove the ZWSP characters you are inserting into the Arabic.

On Tue, Apr 21, 2015 at 12:22 PM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hi Glen,

 I have attached the minified xsl-fo xml. There is only one table-row and
 all
 the arabic characters in that row have issues . (One clue for searching the
 problemtic arabic characters. Please search for the word
 C​H​O​P​R​A​A​A​A​A​A​,​ ​A​D​I​T​Y​A in the xml and arabic characters
 that comes in the subsequent cells are the problematic ones)

 xslfo_minified.xml
 http://apache-fop.1065347.n5.nabble.com/file/n41986/xslfo_minified.xml

 Thanks a lot for the help
 Kumar.T



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Arabic-letters-not-formed-properly-after-adding-Zero-Width-Space-x200B-tp41977p41986.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Arabic letters not formed properly after adding Zero Width Space (#x200B;)

[Glenn Adams]

I don't want to see the XSLT or the input XML to XLST. I need to see the
XSL-FO data (the output from performing XSLT).

The input to FOP is an XSL-FO file. Anything else is noise.

On Tue, Apr 21, 2015 at 7:45 AM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hi Glenn,

 I am attaching the input xml

 NewFile.xml
 http://apache-fop.1065347.n5.nabble.com/file/n41980/NewFile.xml



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Arabic-letters-not-formed-properly-after-adding-Zero-Width-Space-x200B-tp41977p41980.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Arabic letters not formed properly after adding Zero Width Space (#x200B;)

[Glenn Adams]

my apologies; now you can take the next step of simplifying the XSL-FO file
to the minimum content that demonstrates your problem; we call this a
maximally minimal test file

On Tue, Apr 21, 2015 at 10:08 AM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hi Glenn,

 I have already attached that in the first post. I am re-attaching it.

 xslfo.xml http://apache-fop.1065347.n5.nabble.com/file/n41984/xslfo.xml

 Regards
 Kumar.T



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Arabic-letters-not-formed-properly-after-adding-Zero-Width-Space-x200B-tp41977p41984.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Arabic letters not formed properly after adding Zero Width Space (#x200B;)

[Glenn Adams]

I need to see the FO input data, not XSLT.

On Mon, Apr 20, 2015 at 9:37 AM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hi All,
 I am trying to generate a PDF report using Apache FOP in Arabic Language .
 The report generation is working fine but I have used the following snippet
 of xslt for wrapping the data within the cell.

 xsl:template name=intersperse-with-zero-spaces
 xsl:param name=str/
 xsl:variable name=spacechars
 #x9;#xA;
 #x2000;#x2001;#x2002;#x2003;#x2004;#x2005;
 #x2006;#x2007;#x2008;#x2009;#x200A;#x200B;
 /xsl:variable

 xsl:if test=string-length($str) gt; 0
 xsl:variable name=c1 select=substring($str, 1,
 1)/
 xsl:variable name=c2 select=substring($str, 2,
 1)/

 xsl:value-of select=$c1/
 xsl:if test=$c2 != '' and
 not(contains($spacechars, $c1) or
 contains($spacechars, $c2))
 xsl:text#x200B;/xsl:text
 /xsl:if

 xsl:call-template
 name=intersperse-with-zero-spaces
 xsl:with-param name=str
 select=substring($str, 2)/
 /xsl:call-template
 /xsl:if
 /xsl:template

 After calling this template for all the data , the Arabic characters are
 not
 forming properly and looks mis-formed. For examples , Please check the 5th
 column from right to left and Arabic character is not proper.  I am
 attaching the sample PDF and fo.xml for your reference. Could you please
 help me sort this issue out.

 Regards
 Kumar.T

 xslfo.xml http://apache-fop.1065347.n5.nabble.com/file/n41977/xslfo.xml

 TargetSearch_20042015_Bhavana_both.pdf
 
 http://apache-fop.1065347.n5.nabble.com/file/n41977/TargetSearch_20042015_Bhavana_both.pdf
 




 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Arabic-letters-not-formed-properly-after-adding-Zero-Width-Space-x200B-tp41977.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FW: FOP 1.1 and RTF

[Glenn Adams]

basically, relatively little effort has been spent on RTF support; we
always welcome patches submitted by interested parties

On Tue, Mar 24, 2015 at 4:56 AM, Simon Steiner simonsteiner1...@gmail.com
wrote:

 Sending to mailing list

 -Original Message-
 From: Michele Zamparelli [mailto:mzamp...@eso.org]
 Sent: 24 March 2015 10:08
 To: sstei...@apache.org; lmpmberna...@gmail.com; gad...@apache.org
 Subject: FOP 1.1 and RTF

 Hallo,

 we have been using Apache FOP to generate PDF from DocBook since 2012 for
 a  project at http://sourceforge.net/projects/mbse4md/
 Now we are being asked if we can produce RTF files, and using Apache FOP
 support would appear to be the most natural thing to do.

 I noticed though that the official FOP-1.1 seems to have an issue with
 that (or so says https://issues.apache.org/jira/browse/FOP-2182), and
 furthermore (even when using daily builds version of FOP), it seems that
 something is wrong with page counting and maybe with internal references (I
 am not an expert of these things, I just dumbly look at the produced output
 and compare it with the PDF one).

 Apologies if you are not the right addressees, but I wanted to ask if any
 plans are there to fix these things.
 I am not knowledgeable of free software development paradigms, but would
 this be something which could be supported by a monetary contribution?

 thanks,

 Michele


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Virama at the end of word

[Glenn Adams]

it's on my (long) list

On Fri, Mar 13, 2015 at 1:20 PM, Claudius Teodorescu 
claudius.teodore...@gmail.com wrote:

 Hi, Glenn,


 Any news on this issue?


 Thanks,
 Claudius



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Virama-at-the-end-of-word-tp41811p41845.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Virama at the end of word

[Glenn Adams]

well, at least the behavior is consistent ;) to proceed, please file an
issue [1] against FOP and include the input FO file (and your output PDF)
file, as well as a copy of the fop.xconf file you use and an indication of
the version of FOP you are using

[1] https://issues.apache.org/jira/secure/CreateIssue!default.jspa

On Wed, Mar 4, 2015 at 6:55 AM, Claudius Teodorescu 
claudius.teodore...@gmail.com wrote:

 Hi,

 We do have the following issue with some fonts (see PDF at [1]): the virama
 at the end of an word (before a whitespace) is not rendered, neither is the
 vertical line of the corresponding consonant. (See examples for fonts
 Aparajita, Akshar Unicode, Chandas, Kokila, , etc.)

 Any ideas?


 Thanks,
 Claudius

 [1]
 https://github.com/claudius108/sarit/raw/master/tests/resources/fonts.pdf



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Virama-at-the-end-of-word-tp41811.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Chinese font?

[Glenn Adams]

Try FOP 1.1 or current trunk build.

On Fri, Feb 13, 2015 at 8:21 AM, Maxime Bégnis max...@neodoc.biz wrote:

  Hi,

 I'm trying to produce a PDF containing Chinese text using FOP 1.0. I tried
 many TTF fonts but there is always some characters appearing as a #.

 Does anyone recommend a specific Chinese TTF font to be used with FOP?

 Many thanks,

 --
 --
  *NeoDoc*
 *Maxime Bégnis*
  max...@neodoc.biz
  Tél: +33 (0)4.42.52.24.20
  5, rue de la Touloubre
  13770 Venelles
  France
  http://www.neodoc.fr/

Re: fo:page-number spacing problems in Arabic

[Glenn Adams]

No released version yet. It is available in trunk.

On Wed, Jan 21, 2015 at 5:06 AM, kthangavel kumar.thanga...@gmail.com
wrote:

 Hello All,

 I am facing a similar issue in my project. I would love to know if this is
 fixed. If yes , what is the version in which it is available?

 I am currently using apache fop 1.1

 Thanks
 Kumar T



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/fo-page-number-spacing-problems-in-Arabic-tp37417p41631.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: DITA-OT/FOP and Devanagari Scripts

[Glenn Adams]

There is already a open issue for Mangal problems:
https://issues.apache.org/jira/browse/FOP-2437.

You should try a different font to see if the problem remains or not, e.g.,
Aparajita, Kokila, Utsaah.

On Mon, Jan 12, 2015 at 3:02 AM, Janaki Ramamurthy janaki...@gmail.com
wrote:

 Good Afternoon,

 1. We are using FOP 1.1 that is built-in in Oxygen
 2. Mangal is the font we are using for Hindi
 3. I am customizing the PDF plug-in in DITA-OT. I am not sure what files I
 could give you as sample.

 Jayanti

 On 12 January 2015 at 15:02, Pascal Sancho psancho@gmail.com wrote:

 Hi,
 Theorically, FOP should support Devanagari scripts.
 you should provide further information:
  - FOP version
  - used fonts (for Devanagari scripts)
  - short FO example demonstrating the issue,
  - etc.

 That said, and IIUC, you are probably facing to the existing issue about
 Devanagari diacritics (see issue [1]).
 Can you confirm that point? if yes, you should want to add further
 info/comment there.

 [1] https://issues.apache.org/jira/browse/FOP-2437


 2015-01-12 8:09 GMT+01:00 Janaki Ramamurthy janaki...@gmail.com:

 Good Afternoon,

 I am customizing the PDF plug-in and have got it working for the most
 part. However, the customer wants us to include some Hindi content
 (Devanagari script) and I notice that it is not rendered properly when I
 use Apache FOP. (As to details of not rendered properly, I can only
 explain in lay man terms that the matras, half-matras and jod-akshars
 are displayed incorrectly. Attached is the image of the original and
 rendered content.)


 https://lh5.googleusercontent.com/-KURl0tsIbLM/VK-fSDxNQuI/AAU/FnXD51BcCE4/s1600/Test_1.png


 However, when I used a trial version of Antenna House FOP Processor,
 the Hindi text was rendered correctly.

 I was reading the documentation for both OT and FOP. Am I correct in
 understanding that I cannot render DITA content in Devanagari script using
 the FOP combination?

 I am using Oxygen as the XML Editor.

 Any help will be appreciated.

 Regards,
 Janaki

 --
 You received this message because you are subscribed to the Google
 Groups DITA-OT Users group.
 To unsubscribe from this group and stop receiving emails from it, send
 an email to dita-ot-users+unsubscr...@googlegroups.com.
 For more options, visit https://groups.google.com/d/optout.




 --
 Eliot Kimber





 --
 pascal

Re: Devanagari Diacritics

[Glenn Adams]

I think there's a bug lurking, as I've seen this too. Please file a JIRA
issue and provide minimal input FO file that demonstrates problem as well
as PDF output and your configuration file.

On Wed, Dec 17, 2014 at 6:32 PM, Raymond Budd ray.b...@gmail.com wrote:

 Hi,

 I have a question about Devanagari. Please excuse my limited background
 with the script.

 It appears that diacritics are occasionally shifted left or right when
 rendered using Mangal font. See an example FO file below. The diacritic in
 the first line is written, but partially covered. In the last line, the
 Chandrabindu is written after the letter. Oddly, I've seen other examples
 where these are displayed correctly.

 Is there something missing in the block definition?

 Thanks in advance for any help,
 Ray

 ?xml version=1.0 encoding=UTF-8?
 fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; font-family=Arial
   fo:layout-master-set
 fo:simple-page-master margin-top=36pt margin-bottom=36pt
 margin-left=54pt margin-right=54pt page-width=8.5in
 page-height=11in master-name=normal
   fo:region-body margin-bottom=36pt margin-top=36pt /
 /fo:simple-page-master
   /fo:layout-master-set
   fo:page-sequence id=DocumentBody master-reference=normal
 fo:flow flow-name=xsl-region-body
 fo:block line-height=150% color=black text-align=start
 font-family=Mangal font-size=24pt
 नहीं
 आएँ।
 /fo:block
 /fo:flow
   /fo:page-sequence
 /fo:root

Re: need generic xsl design for dynamic pdf files

[Glenn Adams]

On Sun, Nov 23, 2014 at 9:52 AM, Raj Singh rajoca2...@gmail.com wrote:

 Dear team,
  I am new to java,xml and fop,plz guide me in my urgent requirement,
 below r d points for requirements
  1. I've to print pdf files using socket in java.
  2. I've to write such method which will contain three parameters
 as input those would be
 filename with path,ip address and port.
  3. Based on those inputs i've to read the file(s) from app server
 path, have to print the
 pdf file with as per the file content which can be anything.
  4. Some body suggested me to use xsl-fop, but in my case the file
 name will be dynamic
 ,is there any method to desgin the generic xsl for any type of
 file plz guide me


No. Look for XSLT tutorials. This is NOT the Mail List for discussing XSLT
[1]. FOP only provides an XSLT pre-processor function as a convenience for
users that don't want to invoke XSLT separately.  The real substance of FOP
is the processing of XSL-FO content [2] produced by the XSLT preprocessor
(or input directly to FOP). Feel free to ask about XSL-FO specifics here
though. See also FOP documentation [3].

[1] http://www.w3.org/TR/xslt
[2] http://www.w3.org/TR/2006/REC-xsl11-20061205/
[3] http://xmlgraphics.apache.org/fop/




 you can reach at rajoca2...@gmail.com
 Thanks in advance
 Raj Singh

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP alignment problem between two font type

[Glenn Adams]

use a single font that has glyphs for both characters

On Mon, Oct 20, 2014 at 5:11 AM, Puja pujaag...@gmail.com wrote:

 
 http://apache-fop.1065347.n5.nabble.com/file/n41322/FOP_AlignmentProblem.png
 
 Hi,

 I am using FOP 1.0 version for converting reports in PDF. Problem I am
 facing is alignment between two font type. I am using
 Font-Family=Halvetica,Symbol

 My xml requirement is to display greek omega sign as a unit for
 impedance.As
 per my understanding as omega is not present in Halvetica, font used to
 diplay omega is Symbol but alignment for both font type does not match. I
 tried display-align, text-align, vertical-align but it doesn't work. Below
 is section from my fo file, please suggest how to correct the alignment. I
 have attached current alignment screen shot as well.

 fo:table-cell number-columns-spanned=2 text-align=right
fo:block
  fo:inline
   fo:inline747/fo:inline
 /fo:inline
 fo:inline space-start=5pxΩ/fo:inline
/fo:block
 /fo:table-cell





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-alignment-problem-between-two-font-type-tp41322.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Encoding problem with one specific letter and postscript

[Glenn Adams]

Why aren't generating PDF directly from FOP?

On Sun, Oct 12, 2014 at 1:16 PM, Lembit Gerz lembit.g...@nortal.com wrote:

  Hello,



 I am using FOP 1.1 to generate postscript files with embedded fonts. Later
 I’m using ps2pdf to convert the postscript files to pdfs. The text includes
 Lithuanian letters.

 However, after coverting them to pdf, two specific letters are displayed
 as squares, all the ohter Lituhuanian letters are displayed correctly. The
 problematic letters are the upper- and lowercase letters ė and Ė (e with
 dot, 0116 and 0117 in unicode). I can copy all the letters from the pdf
 (including the two problematic ones – when copying the square and pasting
 it somewhere, it displays the letter correctly).

 I am using the standard Arial font from Windows fonts (arial.ttf).

 This is my fop-config.xml:

 configuration

 renderers

 renderer mime=application/postscript

auto-rotate-landscapetrue/auto-rotate-landscape

fonts

font embed-url=./arial.ttf encoding-mode=single-byte

font-triplet name=Arial style=normal
 weight=normal/

/font

/fonts

 /renderer

 /renderers

 /configuration



 When leaving out the encoding-mode=“single-byte“, the letters display
 correctly, but when copying from the pdf, I get gibberish.

 When generating straight to pdf with FOP, everything is displayed
 correctly and copying is also possible.

 I have tried other ps-pdf converters and they give the same result.

 Using a metric file did not help.



 The problem can be reproduced with the xml and xslt in the fop quick start
 guide (https://xmlgraphics.apache.org/fop/quickstartguide.html) with
 these modifications:

 Set the name in name.xml to ABC14pąęčėųūĘĖŲČĄ.

 Add the attribute font-familiy=“Arial“ to the fo:block in name2fo.xsl.

 Use the above fop-config file and include the standard Arial font in FOP’s
 directory.

 Run ’fop -xml name.xml -xsl name2fo.xsl -ps name.ps -c fop-config.xml’



 Can anyone suggest, what could be the issue or how should I go about
 debugging this?

 Thank You.





 Lembit

Re: Encoding problem with one specific letter and postscript

[Glenn Adams]

If you do try the same data using FOP generating PDF directly, then does
the problem occur?

On Sun, Oct 12, 2014 at 1:42 PM, Lembit Gerz lembit.g...@nortal.com wrote:

  To add watermarks or other transformations to the document.

 The current  setup is the following: generate postscript - apply an awk
 skript to the ps, that for example adds a watermark - convert the ps to
 pdf.

 I know it might be a hacky solution, but unfortunately changing this setup
 is currently out of the question.



 *From:* Glenn Adams [mailto:gl...@skynav.com]
 *Sent:* 12. oktoober 2014. a. 22:31
 *To:* FOP Users
 *Subject:* Re: Encoding problem with one specific letter and postscript



 Why aren't generating PDF directly from FOP?



 On Sun, Oct 12, 2014 at 1:16 PM, Lembit Gerz lembit.g...@nortal.com
 wrote:

 Hello,



 I am using FOP 1.1 to generate postscript files with embedded fonts. Later
 I’m using ps2pdf to convert the postscript files to pdfs. The text includes
 Lithuanian letters.

 However, after coverting them to pdf, two specific letters are displayed
 as squares, all the ohter Lituhuanian letters are displayed correctly. The
 problematic letters are the upper- and lowercase letters ė and Ė (e with
 dot, 0116 and 0117 in unicode). I can copy all the letters from the pdf
 (including the two problematic ones – when copying the square and pasting
 it somewhere, it displays the letter correctly).

 I am using the standard Arial font from Windows fonts (arial.ttf).

 This is my fop-config.xml:

 configuration

 renderers

 renderer mime=application/postscript

auto-rotate-landscapetrue/auto-rotate-landscape

fonts

font embed-url=./arial.ttf encoding-mode=single-byte

font-triplet name=Arial style=normal
 weight=normal/

/font

/fonts

 /renderer

 /renderers

 /configuration



 When leaving out the encoding-mode=“single-byte“, the letters display
 correctly, but when copying from the pdf, I get gibberish.

 When generating straight to pdf with FOP, everything is displayed
 correctly and copying is also possible.

 I have tried other ps-pdf converters and they give the same result.

 Using a metric file did not help.



 The problem can be reproduced with the xml and xslt in the fop quick start
 guide (https://xmlgraphics.apache.org/fop/quickstartguide.html) with
 these modifications:

 Set the name in name.xml to ABC14pąęčėųūĘĖŲČĄ.

 Add the attribute font-familiy=“Arial“ to the fo:block in name2fo.xsl.

 Use the above fop-config file and include the standard Arial font in FOP’s
 directory.

 Run ’fop -xml name.xml -xsl name2fo.xsl -ps name.ps -c fop-config.xml’



 Can anyone suggest, what could be the issue or how should I go about
 debugging this?

 Thank You.





 Lembit

Re: Encoding problem with one specific letter and postscript

[Glenn Adams]

You should provide the following:

   - maximally minimal input FO file (XML/XSLT input files are irrelevant)
   - the output PS file you obtain (when producing PS directly)
   - the output PDF file you obtain (when producing PDF directly)


On Sun, Oct 12, 2014 at 2:09 PM, Lembit Gerz lembit.g...@nortal.com wrote:

  No, if I generate the PDF directly using the same data and font file,
 then all the letters are displayed correctly and copying from the PDF is
 also possible.





 *From:* Glenn Adams [mailto:gl...@skynav.com]
 *Sent:* 12. oktoober 2014. a. 23:03

 *To:* FOP Users
 *Subject:* Re: Encoding problem with one specific letter and postscript



 If you do try the same data using FOP generating PDF directly, then does
 the problem occur?



 On Sun, Oct 12, 2014 at 1:42 PM, Lembit Gerz lembit.g...@nortal.com
 wrote:

 To add watermarks or other transformations to the document.

 The current  setup is the following: generate postscript - apply an awk
 skript to the ps, that for example adds a watermark - convert the ps to
 pdf.

 I know it might be a hacky solution, but unfortunately changing this setup
 is currently out of the question.



 *From:* Glenn Adams [mailto:gl...@skynav.com]
 *Sent:* 12. oktoober 2014. a. 22:31
 *To:* FOP Users
 *Subject:* Re: Encoding problem with one specific letter and postscript



 Why aren't generating PDF directly from FOP?



 On Sun, Oct 12, 2014 at 1:16 PM, Lembit Gerz lembit.g...@nortal.com
 wrote:

 Hello,



 I am using FOP 1.1 to generate postscript files with embedded fonts. Later
 I’m using ps2pdf to convert the postscript files to pdfs. The text includes
 Lithuanian letters.

 However, after coverting them to pdf, two specific letters are displayed
 as squares, all the ohter Lituhuanian letters are displayed correctly. The
 problematic letters are the upper- and lowercase letters ė and Ė (e with
 dot, 0116 and 0117 in unicode). I can copy all the letters from the pdf
 (including the two problematic ones – when copying the square and pasting
 it somewhere, it displays the letter correctly).

 I am using the standard Arial font from Windows fonts (arial.ttf).

 This is my fop-config.xml:

 configuration

 renderers

 renderer mime=application/postscript

auto-rotate-landscapetrue/auto-rotate-landscape

fonts

font embed-url=./arial.ttf encoding-mode=single-byte

font-triplet name=Arial style=normal
 weight=normal/

/font

/fonts

 /renderer

 /renderers

 /configuration



 When leaving out the encoding-mode=“single-byte“, the letters display
 correctly, but when copying from the pdf, I get gibberish.

 When generating straight to pdf with FOP, everything is displayed
 correctly and copying is also possible.

 I have tried other ps-pdf converters and they give the same result.

 Using a metric file did not help.



 The problem can be reproduced with the xml and xslt in the fop quick start
 guide (https://xmlgraphics.apache.org/fop/quickstartguide.html) with
 these modifications:

 Set the name in name.xml to ABC14pąęčėųūĘĖŲČĄ.

 Add the attribute font-familiy=“Arial“ to the fo:block in name2fo.xsl.

 Use the above fop-config file and include the standard Arial font in FOP’s
 directory.

 Run ’fop -xml name.xml -xsl name2fo.xsl -ps name.ps -c fop-config.xml’



 Can anyone suggest, what could be the issue or how should I go about
 debugging this?

 Thank You.





 Lembit

Re: Loading fonts problem

[Glenn Adams]

On Tue, Sep 23, 2014 at 4:01 AM, MartinKl klapec.mar...@hotmail.com wrote:

 Hello,
 thank you for reaction.

 I just wanted to explained why is not so easy to make automatic test.  I´ve
 decided to upgrade to fop 1.1 but I strugle the same problem.


 http://apache-fop.1065347.n5.nabble.com/Upgrading-fop-0-95-to-fop-1-1-because-of-PDF-A-1b-td41090.html#a41160
 
 http://apache-fop.1065347.n5.nabble.com/Upgrading-fop-0-95-to-fop-1-1-because-of-PDF-A-1b-td41090.html#a41160
 

 There is also an example.

 It is solved now but I had to apply two patches on stable 1.1 version to
 make it work.  Now we embed full fonts to the pdfs but the size of them
 increased dramatically so I would prefer to solve it.


A lot of work has occurred in trunk since 1.1 to reduce font embed sizes.
You really should try the current trunk build.



 Great Regards
 Martin



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Loading-fonts-problem-tp41009p41241.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Loading fonts problem

[Glenn Adams]

As I believe has been mentioned before, any part of the process of
translating from arbitrary XML into XSL-FO proper is effectively out of
scope for this ML and group unless it is a real bug in the convenience
mechanism provided by FOP to invoke XSLT for you.

If there is a problem parsing or formatting XSL-FO input, then you need to
focus on creating the smallest possible example of XSL-FO document that
demonstrates the problem.

Everything else that happens up to providing XSL-FO input should be viewed
as secondary as far as FOP is concerned.

Cheers,
Glenn

On Mon, Sep 22, 2014 at 12:18 PM, MartinKl klapec.mar...@hotmail.com
wrote:

 Hello,
 I havent meantion one important thing about how we produce document. We do
 it in two ways. The first we use xsl-fo and xml with data. The second one
 is
 that we have a special markup language which produce xls transformation.
 The markup language is even simplier than hmtl and serves good for simple
 documents mostly with static content. Lots of people in the bank can use it
 but they also make mistakes in it.


 And that the problem causing retesting a big group of real templates. With
 automatic test I can cover most of the mistakes but not those user made
 ones.

 Another problem is the upgrade doesnt bring much new for us from bussines
 side so it is hard to get a budget because bussines managers do not see any
 added value.

 I hope I explained it well :) Who work for bank probably smile now because
 he knows what I am talking about :)





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Loading-fonts-problem-tp41009p41239.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP cant find preloader classes

[Glenn Adams]

On Sun, Aug 17, 2014 at 7:33 PM, pfuller pful...@callista.com.au wrote:

 We have upgraded to FOP 1.1 and when trying to process an image we are
 getting the following error:

 SEVERE: Image not available. URI:
 http://x.com:8281/contentServlet?id=70375422672598045316. Reason
 : org.apache.xmlgraphics.image.loader.ImageException: The file format is
 not
 supported. No ImagePreloader found for
 http://x.com:8281/contentServlet?id=70375422672598045316 (No context info
 available)
 org.apache.xmlgraphics.image.loader.ImageException: The file format is not
 supported. No ImagePreloader found for
 http://x.com:8281/contentServlet?id=70375422672598045316
 at

 org.apache.xmlgraphics.image.loader.ImageManager.preloadImage(ImageManager.java:180)
 at

 org.apache.xmlgraphics.image.loader.cache.ImageCache.needImageInfo(ImageCache.java:128)
 at

 org.apache.xmlgraphics.image.loader.ImageManager.getImageInfo(ImageManager.java:122)
 at org.apache.fop.fo.flow.ExternalGraphic.bind(ExternalGraphic.java:81)


 We have installed Apache FOP into an Oracle database schema and it is
 called
 via a plsql package. The fop jar and all its dependent jar libraries are in
 the same database schema(effectively same classpath). This is were the
 error
 occurs. If we run it locally in Jdeveloper, using the same jars delivered
 in
 FOP1.1 then it works correctly.

 The images served by the servlet are JPG and BMP images. We have confirmed
 that the images can be accessed successfully on the box running the
 process.

 We tried the following solution suggested by the below post of changing the
 META-INF/services files:


 http://apache-fop.1065347.n5.nabble.com/FOP-1-0-images-fail-to-render-td7348.html

 This solution actually worked, however we are tentative to go with this
 solution since we are failing to understand why the process works locally,
 but not deployed via the database. We also assume that the FOP1.1 is
 working
 as released, and what we have done seems to be hacking dependencies.

 Is anyone able to explain why the
 META-INF/Services/org.apache.xmlgraphics.image.loader.spi.ImagePreloader
 file contains only the following:

 org.apache.fop.image.loader.batik.PreloaderWMF
 org.apache.fop.image.loader.batik.PreloaderSVG

 when the solution that is working for us contains:

 g.apache.xmlgraphics.image.loader.impl.PreloaderTIFF
 org.apache.xmlgraphics.image.loader.impl.PreloaderGIF
 org.apache.xmlgraphics.image.loader.impl.PreloaderJPEG
 org.apache.xmlgraphics.image.loader.impl.PreloaderBMP
 org.apache.xmlgraphics.image.loader.impl.PreloaderEMF
 org.apache.xmlgraphics.image.loader.impl.PreloaderEPS
 org.apache.xmlgraphics.image.loader.impl.imageio.PreloaderImageIO


There are two distinct
META-INF/Services/org.apache.xmlgraphics.image.loader.spi.ImagePreloader
files, one in xmlgraphics-commons...jar and one in fop...jar. Normally the
SPI layer (i.e., Avalon Framework) loads these separately and merges the
results in order to find all available preloaders. However, this could be
failing for some reason, and loading only one but not both. HTH.




 Thanks,

 Peter





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-cant-find-preloader-classes-tp41075.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Regarding PDF generation for arabic locale.

[Glenn Adams]

You continue to fail to provide sufficient information to determine your
problem. Please supply the folllowing:

   - your input FO file
   - the output PDF file produced when formatting the above
   - your FOP config file
   - any relevant console output



On Tue, Jul 15, 2014 at 6:59 AM, ramakanth reddy ramakanth.kon...@gmail.com
 wrote:

 Hi Fop Dev Team,

 I am unable to generate PDF file using apache fop-1.1 for past 1 month .

 I have also submitted my issue in JIRA but still I am unable to resolve .

 Please provide some sample examples for arabic characterset PDF creation.

 I search in internet but still I didn't get any useful link.


 --
 ThanksRegards,
 Ramakanth,
 +91-8884035968.

Re: Is it possible to merger pdf's using xsl-fo alone?

[Glenn Adams]

No.


On Thu, Jul 3, 2014 at 6:34 AM, Vijaya Raghavan.R 
vijayaraghava...@solartis.net wrote:

 Is it possible to merge pdf's using xsl-fo alone...?

 Hi,

 Now we are using Itext for merging pdf's.
 Is there any solution to merge pdf's without using itext..

 Note: Is it possible to merge pdf's in xsl fo ? If yes, guide me.

 Thanks in advance





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Is-it-possible-to-merger-pdf-s-using-xsl-fo-alone-tp40856.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: xsl fo 1.1 pdf duplex printing

[Glenn Adams]

I recently added experimental support for PDF 1.5 Optional Content Groups
(OCGs), aka Layers. It is rather rudimentary and not yet documented (except
in the PDF spec), but you can find a couple of examples at [1][2].

The main hook for this is the use of an fox:layer property on a block class
FO element type, which points at a previously declared pdf:layer element.

[1]
https://github.com/apache/fop/blob/trunk/test/layoutengine/standard-testcases/pdf-dictionary-extension_2.xml
[2]
https://github.com/apache/fop/blob/trunk/test/layoutengine/standard-testcases/pdf-dictionary-extension_3.xml


On Tue, Jun 17, 2014 at 9:23 AM, Vijaya Raghavan.R 
vijayaraghava...@solartis.net wrote:

 Hi,

 Need some clarifications in xsl fo 1.1 version.

 - Is it possible set duplex (back to back ) printing setup in xsl
 design?
 - Need to show notes in pdf, but need to hide it while printing the
 pdf ( using xsl )
 - how to include book marks for external pdf's


 If anyone having ideas, please help.

 Thanks in Advance





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/xsl-fo-1-1-pdf-duplex-printing-tp40800.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Devanagari support

[Glenn Adams]

You do not need to specify the script property, unless the automatic
algorithm doesn't select the desired script. This latter would only be the
case if you are using an older font that supports only the pre-2005
OpenType Devanagari rendering rules ('deva'). The current automatic
algorithm maps to 'dev2', which matches the current OpenType font spec.


On Thu, May 29, 2014 at 3:55 AM, Raymond Budd ray.b...@gmail.com wrote:

  Hi,

 I have a question about Devanagari support. Please excuse my limited
 background with the script.

 The site shows that join controls are not supported:
 https://xmlgraphics.apache.org/fop/trunk/complexscripts.html, and I want
 to make sure the behavior I see is as expected. A basic example of this is
 with: में

 On command line PDF generation with the example FO file below, this
 generates two separate characters instead of the single character above (I
 can provide the config, FO, and generated PDF files if it helps). I get the
 same result when running with script set to 'dev2' or 'deva'.

 If this is currently not supported, does anyone have an idea of when this
 support would be available, if there's a workaround, or suggestion for
 improving the results?

 Also, I'm not sure I understand the distinction between the standard and
 extended script codes. Is there a pointer to somewhere I can find out more
 about the difference?

 Thanks in advance for any help,
 Ray

 
 sample FO file:
 

 ?xml version=1.0 encoding=UTF-8?
 fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format; font-family=Arial
   fo:layout-master-set
 fo:simple-page-master margin-top=36pt margin-bottom=36pt
 margin-left=54pt margin-right=54pt page-width=8.5in
 page-height=11in master-name=normal
   fo:region-body margin-bottom=36pt margin-top=36pt /
 /fo:simple-page-master
   /fo:layout-master-set
   fo:page-sequence id=DocumentBody master-reference=normal
 fo:flow flow-name=xsl-region-body
 fo:block line-height=125% color=black text-align=start
 script=deva font-family=ArialUnicodeMS font-size=14pt
   में
 /fo:block
 /fo:flow
   /fo:page-sequence
 /fo:root

Re: Greek Characters in Postscript Output

[Glenn Adams]

Don't bother supplying XSL/XML input files. Preprocess them into an XSL-FO
file and then send it (and test with it), otherwise the XSL/XML files are
just noise.

Also, make sure you are using Unicode code points for the greek characters,
e.g., #x0370; through #x03ff;. Also, don't bother with FOP 1.0, use FOP
1.1 or the current trunk builds.


On Mon, May 19, 2014 at 8:05 PM, Normen n.ruh...@alphasoft.biz wrote:

 an even simpler example with the same (negative) result when using Arial
 and
 Verdana TTFs:

 projectteam.xml
 http://apache-fop.1065347.n5.nabble.com/file/n40639/projectteam.xml
 projectteam2fo.xsl
 http://apache-fop.1065347.n5.nabble.com/file/n40639/projectteam2fo.xsl
 Java_Printing.pdf
 http://apache-fop.1065347.n5.nabble.com/file/n40639/Java_Printing.pdf




 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Greek-Characters-in-Postscript-Output-tp40610p40639.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: PDF rendering (and SVG-in-PDF rendering) of Arabic fonts not working correctly with ligatures for many fonts

[Glenn Adams]

Arabic is not presently supported in SVG when using FOP. For direct FOP use
(not SVG), then if you are using any version of FOP prior to FOP 1.1,
Arabic is not supported. If you are using 1.1 or current dev build, then
you are doing something wrong.

You need to provide more details.


On Wed, May 14, 2014 at 11:08 AM, Robert Gurol robert.gu...@signavio.comwrote:

 Hi all,

 for rendering PDF containing both Arabic text and SVG containing arabic
 text, I recently experimented with different fonts.

 Except for the Tahoma font (which I'd rather not use for its license
 restrictions), Arabic text is rendered without ligatures, i.e. the letters
 of words are displayed as if they were written alone, while Arabic demands
 they be rendered differently inside of words and at the beginning and end
 of words, so they apper connected like hand-written text.

 That even though most fonts I tried seem to work perfectly well with PNG
 transcoding (when registered with the GraphicsEnvironment beforehand),
 generating Arabic text as expected.

  The fonts I tried so far are Lateef, Scheherazade and (Wikipedia-used)
 Amiri.
 Amiri (Regular) contains almost all characters of the unicode character
 sets Arabic, Arabic Supplement, Arabic Presentation Forms A and Arabic
 Presentation Forms B.

 As far as I know, ArabicTextHandler tries to replace adjacent letters with
 the respective connected forms and annotates the characters (not: code
 points, alas) with the respective in-word-position information for the
 letter, and it is called in both PNG transcoding and SVG-in-PDF transcoding.
 However, PNG looks much better in all cases, the ligatures seem to work
 only there.

 Is this a known issue?

 If not, I will gladly provide more information and test resources.

 Regards,

 Robert

Re: Drastic Performance Improvement by dropping xerces and xalan

[Glenn Adams]

Personally, I support removing all XSLT functions from FOP, but I'm afraid
that would cause many users to find it less useful. I think it was a
serious architectural error to combine those functions in the first place,
but that horse left the gate long ago.


On Tue, May 13, 2014 at 4:18 AM, Peter p.kullm...@arenae.ch wrote:

 We had some performance problems with fop and began to investigate. For a
 specific example document of about 400 pages fop took about 55 seconds on a
 server at a client. The same process was much faster in our own setting
 (taking about 11 seconds). What we found out is the following:

 - fop from the distribution (either 1.1 release or 1.2 snapshot) takes 55
 seconds
 - fop from the suse package takes only 11 seconds

 The two configurations differ in the jars: The suse config does not include
 xercesImpl, xalan and serializer

 We are running
 java version 1.7.0_40
 OpenJDK Runtime Environment (IcedTea 2.4.1) (suse-8.18.1-x86_64)
 OpenJDK 64-Bit Server VM (build 24.0-b50, mixed mode)

 So, removing these three libraries drastically improved performance for us.

 Can someone explain why this is so? Can I safely drop these jars?

 Best regards
 Peter




 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Drastic-Performance-Improvement-by-dropping-xerces-and-xalan-tp40586.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Warning messages on using FOP

[Glenn Adams]

This is not an FOP problem, it is an XLST/Docbook problem. Before you run
FOP, use xsltproc or equivalent to verify the correctness of your XSLT
usage.


On Mon, May 12, 2014 at 6:18 AM, anmol gupta anmolgupta11...@gmail.comwrote:

 Hi,

 I am getting the following warning messages.



 No template for /book/chapter/section/section/section/note/para (or any
 of its leaves) exists in the context named title in the en localization.

 No template for /book/chapter/section/section/para (or any of its
 leaves) exists in the context named title in the en localization.

 No template for /book/chapter/section/section/orderedlist/listitem/para
 (or any of its leaves) exists in the context named title in the en
 localization.

 No template for /book/chapter/section/section/orderedlist/listitem/para
 (or any of its leaves) exists in the context named title in the en
 localization.

 No template for /book/chapter/section/section/orderedlist/listitem/para
 (or any of its leaves) exists in the context named title in the en
 localization.

 No template for
 /book/chapter/section/section/orderedlist/listitem/note/para (or any of
 its leaves) exists in the context named title in the en localization.

 ..

 WARNING: Destination: Unresolved ID reference id2846293 found.

 May 12, 2014 12:01:54 PM org.apache.fop.events.LoggingEventListener
 processEvent

 WARNING: Destination: Unresolved ID reference id3105986 found.

 May 12, 2014 12:01:54 PM org.apache.fop.events.LoggingEventListener
 processEvent

 WARNING: Destination: Unresolved ID reference id3105990 found.

 May 12, 2014 12:01:54 PM org.apache.fop.events.LoggingEventListener
 processEvent

 WARNING: Destination: Unresolved ID reference id3106003 found.

 May 12, 2014 12:01:54 PM org.apache.fop.events.LoggingEventListener
 processEvent

 WARNING: Destination: Unresolved ID reference id3106027 found.


 I am using FOP for generating PDFs using docbook and xsltproc to convert
 .xml to .fo. Is this some error in the xml or FOP messages as i could see
 the generated PDF. If not, is there a way to stop these warning from
 getting printed.


 Also, I get messages regarding Rendering page. How  can i stop these
 messages from getting printed.


 Regards,

 Anmol

Re: why the xml and xsl files have to be in the bin folder of tomcat when I generate a application web for that the application works?

[Glenn Adams]

Since you reported a problem, how about reporting your fix?


On Mon, Apr 7, 2014 at 4:11 PM, edi4988 edi4...@gmail.com wrote:

 Thank you for the replies, I solved the problem.


 2014-04-03 16:32 GMT-06:00 Luis Bernardo [via Apache FOP] [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=40454i=0
 :


 As explained in http://xmlgraphics.apache.org/fop/trunk/servlets.html,
 if you use the sample servlet then you should access it as in

-



 http://localhost:8080/fop/fop?xml=/home/path/to/xmlfile.xmlxsl=/home/path/to/xslfile.xsl

 Are you doing that? Can you provide the URL you use?


 On 4/3/14, 10:13 PM, edi4988 wrote:

  I have my xslt and xml files in my Tomcat Server, but when I try to use
 this files  by example in the path  http://localhost:8080/XML/SIICG.xml the 
 application doesn't work. But if I have the files by example in
 c:/xml/SIICG.xml the application works fine.

  Do you know any idea what am i doing wrong?

  I use the example on this page :

 http://svn.apache.org/viewvc/xmlgraphics/fop/tags/fop-1_1/src/java/org/apache/fop/servlet/FopServlet.java?view=log

  Thanx


 2014-04-03 12:00 GMT-06:00 rsargent [via Apache FOP] [hidden 
 email]http://user/SendEmail.jtp?type=nodenode=40425i=0
 :

  Move them to the app root?

  On 04/03/2014 11:57 AM, edi4988 wrote:

 Do you know what can I do if my files have this path 
 http://localhost:8080/XML/SIICG.xml
  ?

 Thanx



 --
 View this message in context: 
 http://apache-fop.1065347.n5.nabble.com/why-the-xml-and-xsl-files-have-to-be-in-the-bin-folder-of-tomcat-when-I-generate-a-application-web-f-tp40348p40422.html




 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: [hidden email] 
 http://user/SendEmail.jtp?type=nodenode=40423i=0
 For additional commands, e-mail: [hidden email] 
 http://user/SendEmail.jtp?type=nodenode=40423i=1




 --
  If you reply to this email, your message will be added to the
 discussion below:

 http://apache-fop.1065347.n5.nabble.com/why-the-xml-and-xsl-files-have-to-be-in-the-bin-folder-of-tomcat-when-I-generate-a-application-web-f-tp40348p40423.html
   To unsubscribe from why the xml and xsl files have to be in the bin
 folder of tomcat when I generate a application web for that the application
 works?, click here.
 NAMLhttp://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml



 --
 View this message in context: Re: why the xml and xsl files have to be
 in the bin folder of tomcat when I generate a application web for that the
 application 
 works?http://apache-fop.1065347.n5.nabble.com/why-the-xml-and-xsl-files-have-to-be-in-the-bin-folder-of-tomcat-when-I-generate-a-application-web-f-tp40348p40425.html

 Sent from the FOP - Users mailing list 
 archivehttp://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.htmlat 
 Nabble.com.




 --
  If you reply to this email, your message will be added to the
 discussion below:

 http://apache-fop.1065347.n5.nabble.com/why-the-xml-and-xsl-files-have-to-be-in-the-bin-folder-of-tomcat-when-I-generate-a-application-web-f-tp40348p40427.html
  To unsubscribe from why the xml and xsl files have to be in the bin
 folder of tomcat when I generate a application web for that the application
 works?, click here.
 NAMLhttp://apache-fop.1065347.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewerid=instant_html%21nabble%3Aemail.namlbase=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespacebreadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml



 --
 View this message in context: Re: why the xml and xsl files have to be in
 the bin folder of tomcat when I generate a application web for that the
 application 
 works?http://apache-fop.1065347.n5.nabble.com/why-the-xml-and-xsl-files-have-to-be-in-the-bin-folder-of-tomcat-when-I-generate-a-application-web-f-tp40348p40454.html
 Sent from the FOP - Users mailing list 
 archivehttp://apache-fop.1065347.n5.nabble.com/FOP-Users-f3.htmlat 
 Nabble.com.

Re: Nested Bulleted Lists Problem

[Glenn Adams]

the folks on this ML may be awesome, but keep in mind that the content of
your thread has little to do with FOP and mostly to do with XSLT; although
FOP provides a convenience function for ingesting XML along with an XSLT
stylesheet, that isn't the primary function of FOP, which is formatting
XSL-FO content;

in the future, it would be better to pursue XSLT questions on MLs that
focus on XSLT functionality



On Sat, Apr 5, 2014 at 1:09 PM, a3leggeddog s...@3ldinc.com wrote:

 First of all, let me just say that this mailing list is awesome!  I can't
 thank you all enough for all of your help - I really appreciate it.

 Yes, sadly I'm going from HTML and, worse, I'm going from HTML that I can't
 control.  In fact, this particular issue is the result of HTML produced by
 an HTML control: ckEditor.

 I have a lot to go on here, and I'm continuing to mess with the XSLT.  If I
 can get it to work, I'll reposted here so, hopefully, someone else can
 benefit.  I will also reach out to ckSource because I don't believe what
 they're producing is valid HTML either.

 Best,
 Seth



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Nested-Bulleted-Lists-Problem-tp40436p40448.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: right align arabic in table-cell

[Glenn Adams]

On Wed, Mar 19, 2014 at 10:22 PM, Jason Harrop jhar...@gmail.com wrote:

 Bummer.  I guess I could nest a table in the table-cell.  Any reason
 that wouldn't work?


Why aren't you putting writing-mode on the original table? i.e., why use an
inner table?



 On Thu, Mar 20, 2014 at 2:33 PM, Glenn Adams gl...@skynav.com wrote:
 
 
  On Wed, Mar 19, 2014 at 5:44 PM, Jason Harrop jhar...@gmail.com wrote:
 
  Hi Glenn
 
  Thanks very much for that.
 
  So the following should right align in the table cell?
 
  table-cell  xmlns=http://www.w3.org/1999/XSL/Format;
 
block-container writing-mode=rl-tb
  block
inlineالمدينة/inline
  /block
/block-container
  table-cell
 
  But  that didn't work in FOP 1.1 nor with
 
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/fop-20140319.jar
 
 
  No. I guess I wasn't plain enough. You need to put writing mode on table
 to
  affect the table cells. What you've done above doesn't change the
 start/end
  edges of the cell, just the start/end edges of the content in the cell.
 The
  cell still maps start to left and end to right. Note that you have to
 make
  the choice on the table as a whole.
 
 
 
 
  (Refer May 2011 thread Complex Script, BIDI text supported?)
 
  cheers .. Jason
 
 
 
  On Wed, Mar 19, 2014 at 6:18 PM, Glenn Adams gl...@skynav.com wrote:
   Per XSL-FO 1.1 [1]:
  
   Property writing-mode applies to: fo:page-sequence,
   fo:simple-page-master,
   fo:region-body, fo:region-before, fo:region-after, fo:region-start,
   fo:region-end, fo:block-container, fo:inline-container, and fo:table.
  
   As you can, none of these is fo:block. You need to specify it on
   fo:table or
   something higher up the tree. Note that specifying a RTL WM on
 fo:table
   causes columns to be numbered from right to left, i.e., the first
 column
   will be right-most.
  
   [1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#prapply
  
  
  
  
   On Wed, Mar 19, 2014 at 12:12 AM, Jason Harrop jhar...@gmail.com
   wrote:
  
   Hi, What's the correct way to write align a block of arabic in an
   individual table-cell?
  
   I found that with writing-mode=rl-tb, it was also necessary to add
   text-align=end
  
  fo:table-cell 
 fo:block  text-align=end writing-mode=rl-tb
 inline font-family=Arialالمدينة/inline
 /fo:block
   /fo:table-cell
  
   thanks .. Jason
  
   -
   To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
   For additional commands, e-mail:
 fop-users-h...@xmlgraphics.apache.org
  
  
 
  -
  To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
  For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
 
 

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: right align arabic in table-cell

[Glenn Adams]

On Thu, Mar 20, 2014 at 2:03 PM, Jason Harrop jhar...@gmail.com wrote:

 Its a  Word document I'm converting to FO, and in it, bidi is a
 paragraph level property:

  http://webapp.docx4java.org/OnlineDemo/ecma376/WordML/bidi_1.html

 The table in question contains some cells with English content (left
 aligned), and others with Arabic content (in Word, these ones are
 right aligned by the bidi property).


I'm not familiar with WordML, but basically, you need to decide whether the
table is a LTR or RTL table, which will determine (ignoring vertical modes):

   - whether columns proceed from LTR or RTL
   - the mapping of WM relative properties *-start and *-end to absolute
   directions -*left and *-right.
   - the default paragraph bidi level for content in the scope of the table
   (that doesn't have an overriding WM, e.g., that might be specified in a
   descendant block-container);

If you want to mix LTR and RTL content in the same table, you will need to
specify appropriate overrides to produce the desired result:

   - enclose the content of a block in a table-cell with bidi-override
   - specify text-align=right on RTL blocks in a LTR table cell

For example, in a LTR table containing RTL cell content:

table writing-mode=ltr
...
table-cell text-align=right
blockbidi-override unicode-bidi=embed direction=rtlRTL content in a
LTR table cell/bidi-override/block
/table-cell
...
/table

Note that text-align doesn't actually apply to table-cell, but rather,
applies to block. However, we can write the text-align property on
table-cell since it is inherited by its children. This might be useful if
the cell contains multiple blocks and you don't want to specify text-align
on them individually.



 On Fri, Mar 21, 2014 at 1:26 AM, Glenn Adams gl...@skynav.com wrote:
 
 
 
  On Wed, Mar 19, 2014 at 10:22 PM, Jason Harrop jhar...@gmail.com
 wrote:
 
  Bummer.  I guess I could nest a table in the table-cell.  Any reason
  that wouldn't work?
 
 
  Why aren't you putting writing-mode on the original table? i.e., why use
 an
  inner table?
 
 
 
  On Thu, Mar 20, 2014 at 2:33 PM, Glenn Adams gl...@skynav.com wrote:
  
  
   On Wed, Mar 19, 2014 at 5:44 PM, Jason Harrop jhar...@gmail.com
 wrote:
  
   Hi Glenn
  
   Thanks very much for that.
  
   So the following should right align in the table cell?
  
   table-cell  xmlns=http://www.w3.org/1999/XSL/Format;
  
 block-container writing-mode=rl-tb
   block
 inlineالمدينة/inline
   /block
 /block-container
   table-cell
  
   But  that didn't work in FOP 1.1 nor with
  
  
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/fop-20140319.jar
  
  
   No. I guess I wasn't plain enough. You need to put writing mode on
 table
   to
   affect the table cells. What you've done above doesn't change the
   start/end
   edges of the cell, just the start/end edges of the content in the
 cell.
   The
   cell still maps start to left and end to right. Note that you have to
   make
   the choice on the table as a whole.
  
  
  
  
   (Refer May 2011 thread Complex Script, BIDI text supported?)
  
   cheers .. Jason
  
  
  
   On Wed, Mar 19, 2014 at 6:18 PM, Glenn Adams gl...@skynav.com
 wrote:
Per XSL-FO 1.1 [1]:
   
Property writing-mode applies to: fo:page-sequence,
fo:simple-page-master,
fo:region-body, fo:region-before, fo:region-after, fo:region-start,
fo:region-end, fo:block-container, fo:inline-container, and
fo:table.
   
As you can, none of these is fo:block. You need to specify it on
fo:table or
something higher up the tree. Note that specifying a RTL WM on
fo:table
causes columns to be numbered from right to left, i.e., the first
column
will be right-most.
   
[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#prapply
   
   
   
   
On Wed, Mar 19, 2014 at 12:12 AM, Jason Harrop jhar...@gmail.com
wrote:
   
Hi, What's the correct way to write align a block of arabic in an
individual table-cell?
   
I found that with writing-mode=rl-tb, it was also necessary to
 add
text-align=end
   
   fo:table-cell 
  fo:block  text-align=end writing-mode=rl-tb
  inline font-family=Arialالمدينة/inline
  /fo:block
/fo:table-cell
   
thanks .. Jason
   
   
   
 -
To unsubscribe, e-mail:
 fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail:
fop-users-h...@xmlgraphics.apache.org
   
   
  
   -
   To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
   For additional commands, e-mail:
 fop-users-h...@xmlgraphics.apache.org
  
  
 
  -
  To unsubscribe

Re: right align arabic in table-cell

[Glenn Adams]

Per XSL-FO 1.1 [1]:

Property writing-mode applies to: fo:page-sequence, fo:simple-page-master,
fo:region-body, fo:region-before, fo:region-after, fo:region-start,
fo:region-end, fo:block-container, fo:inline-container, and fo:table.

As you can, none of these is fo:block. You need to specify it on fo:table
or something higher up the tree. Note that specifying a RTL WM on fo:table
causes columns to be numbered from right to left, i.e., the first column
will be right-most.

[1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#prapply




On Wed, Mar 19, 2014 at 12:12 AM, Jason Harrop jhar...@gmail.com wrote:

 Hi, What's the correct way to write align a block of arabic in an
 individual table-cell?

 I found that with writing-mode=rl-tb, it was also necessary to add
 text-align=end

fo:table-cell 
   fo:block  text-align=end writing-mode=rl-tb
   inline font-family=Arialالمدينة/inline
   /fo:block
 /fo:table-cell

 thanks .. Jason

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Table of Content

[Glenn Adams]

This is a task for XSLT or a pre-processor used in conjunction with FOP.
You need to process your incoming data to generate a ToC using FOP
primitives, and then FOP will do the formatting. XSLT gives you one way to
do that processing, but there are others. Best to think of FOP as simply a
converter from XSL-FO to PDF (or PS, AFP, etc), and nothing more. For the
sake of convenience, FOP allows you to provide input via an input XML file
and an XSLT file, where the XSLT file specifies a transformation from your
input XML file into XSL-FO primitives. But that's all it does. It is up to
you to determine that transformation.

Good Luck,
Glenn


On Mon, Mar 17, 2014 at 12:52 AM, Anastasia anasta...@pdf3d.com wrote:

 Good Day!

 We are interested in using the FOP Apache application. But we require the
 function of making Table of Contents and Index in the document. Could you
 please tell us, is there a way to create a table of contents and index in
 your program? As the only way to implement it, that we see, is to create a
 simple table. Thank you for your answer!

 --
 Best regards, Anastasya.


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Table of Content

[Glenn Adams]

On Wed, Mar 19, 2014 at 2:28 AM, Michael Wechner
michael.wech...@wyona.comwrote:

 I think this is rather an XSL-FO question

 http://en.wikipedia.org/wiki/XSL_Formatting_Objects


Not really. See my prior.




 HTH

 Michael

 Am 17.03.14 07:52, schrieb Anastasia:
  Good Day!
 
  We are interested in using the FOP Apache application. But we require
  the function of making Table of Contents and Index in the document.
  Could you please tell us, is there a way to create a table of contents
  and index in your program? As the only way to implement it, that we
  see, is to create a simple table. Thank you for your answer!

Re: right align arabic in table-cell

[Glenn Adams]

On Wed, Mar 19, 2014 at 5:44 PM, Jason Harrop jhar...@gmail.com wrote:

 Hi Glenn

 Thanks very much for that.

 So the following should right align in the table cell?

 table-cell  xmlns=http://www.w3.org/1999/XSL/Format;

   block-container writing-mode=rl-tb
 block
   inlineالمدينة/inline
 /block
   /block-container
 table-cell

 But  that didn't work in FOP 1.1 nor with
 http://ci.apache.org/projects/xmlgraphics/fop/snapshots/fop-20140319.jar


No. I guess I wasn't plain enough. You need to put writing mode on table to
affect the table cells. What you've done above doesn't change the start/end
edges of the cell, just the start/end edges of the content in the cell. The
cell still maps start to left and end to right. Note that you have to make
the choice on the table as a whole.




 (Refer May 2011 thread Complex Script, BIDI text supported?)

 cheers .. Jason



 On Wed, Mar 19, 2014 at 6:18 PM, Glenn Adams gl...@skynav.com wrote:
  Per XSL-FO 1.1 [1]:
 
  Property writing-mode applies to: fo:page-sequence,
 fo:simple-page-master,
  fo:region-body, fo:region-before, fo:region-after, fo:region-start,
  fo:region-end, fo:block-container, fo:inline-container, and fo:table.
 
  As you can, none of these is fo:block. You need to specify it on
 fo:table or
  something higher up the tree. Note that specifying a RTL WM on fo:table
  causes columns to be numbered from right to left, i.e., the first column
  will be right-most.
 
  [1] http://www.w3.org/TR/2006/REC-xsl11-20061205/#prapply
 
 
 
 
  On Wed, Mar 19, 2014 at 12:12 AM, Jason Harrop jhar...@gmail.com
 wrote:
 
  Hi, What's the correct way to write align a block of arabic in an
  individual table-cell?
 
  I found that with writing-mode=rl-tb, it was also necessary to add
  text-align=end
 
 fo:table-cell 
fo:block  text-align=end writing-mode=rl-tb
inline font-family=Arialالمدينة/inline
/fo:block
  /fo:table-cell
 
  thanks .. Jason
 
  -
  To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
  For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org
 
 

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Maven dependencies for fop 1.1

[Glenn Adams]

We don't retroactively change release images. As Chris stated in his
previous email the avalon dependency will be fixed in the next release.


On Thu, Dec 26, 2013 at 9:52 AM, Carlos cper...@gmail.com wrote:

 Hi,

 Was this change commited? I'm using this dependecy:

 dependency
 groupIdorg.apache.xmlgraphics/groupId
 artifactIdfop/artifactId
 version1.1/version
 /dependency

 But still find the same problem:

 The following artifacts could not be resolved:
 org.apache.avalon.framework:avalon-framework-api:jar:4.2.0,
 org.apache.avalon.framework:avalon-framework-impl:jar:4.2.0: Could not find
 artifact org.apache.avalon.framework:avalon-framework-api:jar:4.2.0 in
 central (http://repo.maven.apache.org/maven2) -

 Thanks in advance!!!



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Maven-dependencies-for-fop-1-1-tp37437p39829.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP - features I miss

[Glenn Adams]

On Tue, Dec 10, 2013 at 5:41 AM, Jan Tosovsky j.tosov...@email.cz wrote:

 2. support for ligatures for non-english environments
 https://issues.apache.org/jira/browse/FOP-2093


Ligatures do work in non-english environments. The bug you cite is a corner
case. If you have a specific (minimal) example that isn't working, then
create a new JIRA issue for it please.

Regards,
Glenn

Re: Informal FOP Users/Developers/Sponsors Meeting

[Glenn Adams]

Thanks for asking. There were insufficient responders to justify a meeting.
Many of the users/developers are in Europe. Perhaps something can be
organized in the not-too-distant future that could bring together FOP Devs
and Users.

Regards,
Glenn


On Fri, Nov 22, 2013 at 3:46 AM, Jan Tosovsky j.tosov...@email.cz wrote:

 On 2013-10-18 Glenn Adams wrote:
 
  I will be visiting Basis Technology [1] in Cambridge, Massachusetts
  during the week of Oct 28 through Nov 1, who has sponsored my work on
  FOP, especially the Complex Script support. Basis has agreed to host an
  informal meeting of parties interested in FOP, including users,
  developers, or sponsors or potential sponsors.
 
  I would like to determine if there is an interest in having people
  attend a half to full day meeting during that week, which would be
  organized along an unconference style. Some of the topics that I would
  like to talk about include:
 
  * future work on complex script support, e.g., fixing bidi issues,
  adding additional script support;
  * PDF extensions, such as support for inter- and intra-page
  transitions and layers (optional content groups)
  * how to increase interest and use of FOP
  * how to increase levels of sponsorship on the core work of
  maintaining and enhancing FOP

 Is there any outcome from this discussion?

 Are there any plans to improve both the code base and engaging
 developers/sponsors?

 Thanks, Jan


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Transforming Incompatible Stylesheets over to FOP Apache

[Glenn Adams]

I believe you are referring to the XSLT stylesheets used with the
convenience function of FOP to support XML to XSL-FO transformation as a
pre-processing step.

Formally, this step is incidental to the functionality of FOP, whose only
real task it transform XSL-FO documents into an output format.

Since your concern is solely related to this pre-processing step, there
isn't much documentation or other support with FOP for this task.

Indeed, it is my opinion that this preprocessing step functionality should
be removed from FOP entirely, forcing users to solely rely on external
tools to create XSL-FO input for FOP.




On Wed, Oct 30, 2013 at 2:48 PM, matrix ivan.teno...@lmco.com wrote:

 Fellow Forum Members,
 I'm using Arbortext Publisher which utilizes FOP Apache coded stylesheets
 to
 output a PDF compliant to the S1000D standard. However, I need to have my
 PDF publication conform to an Army military standard known as MIL-SPEC
 3031A. These 3031A stylesheets are available for free download at the link
 below:


 https://www.logsa.army.mil/pub/s1000d/FO-3031-A00-USARMY-PARA_001-00_EN-US.zip

 My problem is a compatability related problem. The 3031A stylesheets the
 Army provides are not coded to the FOP Apache standard and therefore
 incompatible with Arbortext Publisher. In short, I'm not able to output my
 publication out of Arbortext Publisher as a 3031A compliant PDF.

 Since I'm new to FOP Apache, I'm hoping anybody out there can outline a
 strategy on what I need to do to convert the Army provided 3031A
 stylesheets
 over to FOP Apache stylesheets?

 Is there a transformation engine that accomplishes this task?

 Also, are there any online training videos that show how to modify FOP
 Apache stylesheet code? My thinking is maybe I could tweak the code so that
 my PDF outputs as something that looks close to a 3031A compliant
 publication.

 Any info will be greatly appreciated.




 .



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Transforming-Incompatible-Stylesheets-over-to-FOP-Apache-tp39504.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Informal FOP Users/Developers/Sponsors Meeting

[Glenn Adams]

Just a train ride away. :)


On Sun, Oct 20, 2013 at 9:58 AM, Bonekrusher djs...@yahoo.com wrote:

 Too bad this is in Mass, and not NY. I would have loved to attend. Good
 Luck!



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Informal-FOP-Users-Developers-Sponsors-Meeting-tp39403p39417.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Informal FOP Users/Developers/Sponsors Meeting

[Glenn Adams]

Dear FOP Users and Developers,

I will be visiting Basis Technology [1] in Cambridge, Massachusetts during
the week of Oct 28 through Nov 1, who has sponsored my work on FOP,
especially the Complex Script support. Basis has agreed to host an informal
meeting of parties interested in FOP, including users, developers, or
sponsors or potential sponsors.

I would like to determine if there is an interest in having people attend a
half to full day meeting during that week, which would be organized along
an *unconference* style. Some of the topics that I would like to talk about
include:

   - future work on complex script support, e.g., fixing bidi issues,
   adding additional script support;
   - PDF extensions, such as support for inter- and intra-page transitions
   and layers (optional content groups)
   - how to increase interest and use of FOP
   - how to increase levels of sponsorship on the core work of maintaining
   and enhancing FOP

Please let me know if you are interested in attending, which day of that
week would be best for you, and any additional topics you would like to
explore.

I realize this is rather short notice, but let's see if there is sufficient
interest.

Regards,
Glenn

[1] http://www.basistech.com/

Re: negative text-indent and arabic (rtl) text

[Glenn Adams]

On Wed, Oct 16, 2013 at 4:41 AM, jsolutions j...@jsolutions.co.uk wrote:

 http://apache-fop.1065347.n5.nabble.com/file/n39383/out.pdf


Thanks for this input. Please file a bug against FOP at [1], and be sure to
attach your test input and output pdf.

https://issues.apache.org/jira/browse/FOP#selectedTab=com.atlassian.jira.plugin.system.project%3Asummary-panel

Re: negative text-indent and arabic (rtl) text

[Glenn Adams]

Feel free to submit a patch for the bug you will file, including a new test
case to add to the standard junit layout tests.


On Wed, Oct 16, 2013 at 10:45 AM, jsolutions j...@jsolutions.co.uk wrote:

 Thanks Glenn,

 I shall file a bug. For what it's worth, I believe it is due to the
 text-indent being added as a KnuthInlineBox rather than implemented by
 increasing the offset / reducing the length of the line for line breaking
 purposes. I believe this is what TeX does via it's \parshape command. I
 think the KnuthInlineBox is causing problems with the line breaking. (I
 shall add that comment to the bug as well).

 I will almost certainly need a fix for this so may well make some changes
 myself in the next week or so unless someone beats me to it :)

 JC



 -
 John Cumming - jSolutions Ltd
 http://www.jsolutions.co.uk
 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/negative-text-indent-and-arabic-rtl-text-tp39383p39388.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Processing selected nodes...

[Glenn Adams]

This question relates to XSLT, not XSL-FO or FOP, so this isn't really the
right ML to post this.


On Sun, Sep 29, 2013 at 12:23 AM, Bernard Giannetti 
thebernmeis...@hotmail.com wrote:

 Hi,

 I'm using FOP, embedded in a desktop application, to create PDFs from a
 single data XML file using an XSLT file.

 Say the data XML file is a list of items, for example:

 items
   item
 apple
   /item
   item
 orange
   /item
   item
 water melon
   /item
 ...
 /items

 I want to be able to tell the XSLT to only process specific items (say
 apple and orange).

 I've created a java.util.ArrayList and passed that to the transformer
 using setParameter( theList, theList ).  In the XSLT, when I
 use xsl:value-of select=$theList /, I'll get in the output  [apple,
 orange].  Fair enough.

 However, what I really want (I think) is to take the array and iterate
 over it, calling a template for each item.  Is this possible?

 From what I've managed to deduce from a lot of searching/reading is that
 it's possible even to pass in a Java object and somehow get XSLT to access
 that Java object.  I'm not sure if that is overkill for what I want to do,
 but I cannot even achieve processing a list of items one by one.


 Thanks in advance,

 Bernard.

Re: Greater than or Equal to symbol Fop 1.0

[Glenn Adams]

change to a font that contains glyphs for the desired characters


On Thu, Sep 12, 2013 at 1:06 PM, Bonekrusher djs...@yahoo.com wrote:

 Hi,

 I want to output the Greater than or Equal (≥) and Less than or equal (≤)
 to
 symbols in Fop 1.0. But the output displays as #.

 I have tried:

 ≥
 ≥
 ≥
 ≥

 Any suggestions to get this to output correctly in 1.0. In works in 1.1,
 but
 my project is in 1.0. Also my xml in encoded UTF-8.





 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/Greater-than-or-Equal-to-symbol-Fop-1-0-tp39197.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Does fop-1.1 block-container respect top attribute?

[Glenn Adams]

P.S. In the future, don't bother sending the XSLT if your question is
related to formatting. Only the XSL-FO content is relevant.

P.S.S. Why do you use nested block containers for the first block?


On Tue, Aug 27, 2013 at 5:24 PM, Rob Sargent rsarg...@xmission.com wrote:

 I cannot seem to push a block down using 'top=n' set to any value n  0
 (and  1 of course)

 I've even added an extra, enclosing (superfluous?) block-container inside
 the table-cell. left and right are working just fine but top not so
 much.

 I thought this was a compliant piece of FOP.  Am I wrong about that or
 just doing something stupid again. (Hey, I've been away awhile).

 Thanks.

 My xsl: this template is called as the table-cell is laid out.

 xsl:template name=scout-image
 xsl:param name=curpage/
 xsl:param name=curpos/
 xsl:param name=imageCount/
 xsl:if test=contains($curpage/@**layout-id, 'scout') and
 count($curpage/image[@pos = $imageCount + $curpos]) = 1
 xsl:variable name=scoutsize
 xsl:choose
 xsl:when test=$imageCount = 3
 xsl:value-of select=number(0.9)/
 /xsl:when
 xsl:when test=$imageCount = 1
 xsl:value-of select=number(1.0)/
 /xsl:when
 xsl:otherwise
 xsl:value-of select=number(1.25)/
 /xsl:otherwise
 /xsl:choose
 /xsl:variable
 fo:block-container
 fo:block-container position=absolute z-index=-1
 height={$scoutsize}in width={$scoutsize}in
 xsl:choose
 xsl:when test=$curpage/@pos mod 2 = 0
 xsl:attribute name=left
 xsl:value-of select=0/
 /xsl:attribute
 /xsl:when
 xsl:otherwise
 xsl:attribute name=right
 xsl:value-of select=0/
 /xsl:attribute
 /xsl:otherwise
 /xsl:choose
 xsl:choose
 xsl:when test=$imageCount = 1
 xsl:attribute name=top
 xsl:value-of select=0.1/
 /xsl:attribute
 /xsl:when
 xsl:otherwise
 xsl:attribute name=top
 xsl:value-of select=0/
 /xsl:attribute
 /xsl:otherwise
 /xsl:choose

 xsl:call-template name=show-image
 xsl:with-param name=img
 select=$curpage/image[@pos= $curpos + $imageCount] /
 xsl:with-param name=width select=$scoutsize /
 xsl:with-param name=height select=$scoutsize /
 xsl:with-param name=addBlack select=false() /
 /xsl:call-template
 /fo:block-container
 /fo:block-container
 /xsl:if
 /xsl:template


 My fop:
  fo:table-cell
fo:block-container
   fo:block-container width=1in height=1in z-index=-1
 position=absolute left=0 top=0.1
   fo:block
 fo:external-graphic border-collapse=separate
 content-height=1in content-width=1in display-align=center
 src=ref_scout_3_0_650043924 /
   /fo:block
   /fo:block-container
/fo:block-container
fo:block-container width=1.2102857142857144in
 top=3.9297774842857143in position=absolute left=0.0in height=0.6in
   fo:block linefeed-treatment=preserve white-space-collapse=false
 font-size=8pt font-family=StoneSerif**Anterior surface of
 patella/fo:block
/fo:block-container
fo:block-container width=1.2102857142857144in
 top=5.698118852857143in position=absolute left=0.0in height=0.6in
fo:block linefeed-treatment=preserve
 white-space-collapse=false font-size=8pt 
 font-family=StoneSerif**Patellar
 tendon/fo:block
/fo:block-container
   fo:block-container width=1.2102857142857144in
 top=2.4832606942857147in position=absolute left=0.0in height=0.6in
  fo:block linefeed-treatment=preserve
 white-space-collapse=false font-size=8pt 
 font-family=StoneSerif**Quadriceps
 tendon/fo:block
   /fo:block-container
  /fo:table-cell

 --**--**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: 
 fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org

Re: Bug in fop: Arabic is diplayed in isolated forms

[Glenn Adams]

I don't see any problem (attached). What version of FOP are you using? What
font type (ttf/otf) and version are you using?


On Mon, Aug 12, 2013 at 11:00 AM, Raphael Finkel raph...@cs.uky.edu wrote:

 When fop renders Arabic, it uses isolated Arabic forms instead of
 converting
 them to the proper presentation forms (initial, medial, final).  In
 contrast,
 xmlroff using the Cairo rendering engine renders these forms correctly.

 Here is a small xml-fo file:

 ?xml version=1.0 encoding=UTF-8?fo:root xmlns:fo=
 http://www.w3.org/1999/XSL/Format;fo:layout-master-setfo:simple-page-master
 page-height=11in page-width=8.5in margin-bottom=1in margin-top=1in
 margin-right=1in margin-left=1.5in
 master-name=SudaPagefo:region-body margin-bottom=0in margin-top=0in
 margin-right=0in margin-left=0in/fo:region-before
 extent=0.0in/fo:region-after extent=0.0in/fo:region-start
 extent=0in/fo:region-end
 extent=0in//fo:simple-page-master/fo:layout-master-setfo:page-sequence
 master-reference=SudaPagefo:static-content
 flow-name=xsl-footnote-separatorfo:blockfo:leader
 rule-thickness=0.5pt rule-style=solid leader-length=20%
 leader-pattern=rule//fo:block/fo:static-content
 fo:flow flow-name=xsl-region-body
 fo:block font-family=FreeSerif margin-top=.2in
 margin-left=.5in
 [1] Some Arabic: مسر now some Hebrew: שמו [2]
 that's all
 /fo:block
 /fo:flow/fo:page-sequence/fo:root

 I attach the PDF that fop creates.  It has poorly rendered Arabic.  It
 also has
 a bidi problem, but that is not the point here.

 Raphael


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

?xml version=1.0 encoding=UTF-8?
fo:root xmlns:fo=http://www.w3.org/1999/XSL/Format;
  fo:layout-master-set
fo:simple-page-master page-height=11in page-width=8.5in margin-bottom=1in margin-top=1in margin-right=1in margin-left=1.5in master-name=SudaPage
  fo:region-body margin-bottom=0in margin-top=0in margin-right=0in margin-left=0in/
  fo:region-before extent=0.0in/
  fo:region-after extent=0.0in/
  fo:region-start extent=0in/
  fo:region-end extent=0in/
/fo:simple-page-master
  /fo:layout-master-set
  fo:page-sequence master-reference=SudaPage
fo:static-content flow-name=xsl-footnote-separator
  fo:block
fo:leader rule-thickness=0.5pt rule-style=solid leader-length=20% leader-pattern=rule/
  /fo:block
/fo:static-content
fo:flow flow-name=xsl-region-body
fo:block font-family=FreeSerif margin-top=.2in margin-left=.5in
[1] Some Arabic: مسر now some Hebrew: שמו [2] that's all
/fo:block
/fo:flow
  /fo:page-sequence
/fo:root


test.pdf
Description: Adobe PDF document

-
To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Memory usage and page numbering...

[Glenn Adams]

On Sat, Aug 10, 2013 at 5:55 PM, Mahesh Rayudu mahesh.ray...@gmail.comwrote:

 I noticed memory leak issue in font complex-scripts features with trunk
 code. Not seen any memory issues with page numbers/totals. I tested my code
 on Mac 10.7 and CentOS 6.4 with visualvm profiler.


Be specific.

Re: Bug in fop: bidi direction bleeds forward

[Glenn Adams]

Please provide the input FO file, not the input XML/XSLT files. FOP's
proper input is the FO file. The XML to FO translation is a preprocessor
convenience function unrelated to FO processing.

You can create the FO file (mini.fo.xml) as follows:

fop -c mini-fo.cfg -xml mini.xml -xsl mini.fo -foout mini.fo.xml


On Tue, Aug 6, 2013 at 8:30 AM, Raphael Finkel raph...@cs.uky.edu wrote:

 Quick summary: RTL inserts in a bi-directional document modify the
 directionality of brackets following those inserts.

 I am using Apache fop-1.1 on Ubuntu 12.04.2 to generate PDF output from
 XML.

 File mini.xml:

 ?xml version='1.0' encoding='UTF-8'?
 data
 notesbr/[1] RTL insert קום br/[2] (parens
 wrong).br/[3] Back to normal because of this RTL insert: בּ
 ./notes
 /data

 File mini.fo:

 ?xml version=1.0 encoding=ISO-8859-1?
 xsl:stylesheet version=1.0
 xmlns:xsl=http://www.w3.org/1999/XSL/Transform;
 xmlns:fo=http://www.w3.org/1999/XSL/Format;
 
 xsl:template match=/
 fo:root
 fo:layout-master-set
 fo:simple-page-master master-name=myPage
 fo:region-body /
 /fo:simple-page-master
 /fo:layout-master-set
 fo:page-sequence master-reference=myPage
 fo:flow flow-name=xsl-region-body
 fo:block font-family=FreeSans
 xsl:apply-templates
 select=data/notes/
 /fo:block
 /fo:flow
 /fo:page-sequence
 /fo:root
 /xsl:template
 xsl:template match=br
 fo:block/fo:block
 /xsl:template
 /xsl:stylesheet

 File mini-fo.cfg:

 fop version=1.0
 renderers
 renderer mime=application/pdf
 fonts
 font
 metrics-url=FreeSans.xml

 embed-url=/usr/share/fonts/truetype/freefont/FreeSans.ttf
 
 font-triplet name=FreeSans
 style=normal weight=normal/
 /font
 /fonts
 /renderer
 /renderers
 /fop

 Invocation of fop-1.1:

 /tmp/fop-1.1/fop -c mini-fo.cfg -xml mini.xml -xsl mini.fomini.pdf

 I attach mini.pdf.  You can also see its contents by looking at what
 pdftotext outputs:

 [1] RTL insert ‫קום‬
 ]2[ )parens wrong(.
 [3] Back to normal because of this RTL insert: ּ‫. ב‬

 (There are some Unicode \u202b (RIGHT-TO-LEFT EMBEDDING) and \u202c (POP
 DIRECTIONAL FORMATTING) characters in that pdftotext output.)

 When I use xmlroff instead of fop, the result is correct:

 [1] RTL insert ‫קום‬
 [2] (parens wrong).
 [3] Back to normal because of this RTL insert: ּ ‫. ב‬

 Raphael


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Multi Language Support in PDF

[Glenn Adams]

If you read the information I posted at [1], you will find that Telugu
script is not yet supported. However, Devanagari script has initial
support, which you can try out.

[1] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html


On Mon, Aug 5, 2013 at 5:06 AM, jaya chandra Reddy jayachan...@ecomzera.com
 wrote:

 Hi Glenn,


   I gone through the Complex Scripts document which your shared with embed
 process. But i didn't get out put to display asian telugu language. Can you
 please find attachment zip file, which contains all files( java source,
 xslt, xconf file with arial ttf support, output) files.   Correct me
 whether i configured all the things correctly or not and also refer or
 share some example to use complex scripts to use correctly.










 On Sun, Aug 4, 2013 at 2:56 AM, Glenn Adams gl...@skynav.com wrote:

 There is preliminary support for some Indic scripts, but it is not fully
 debugged or tested, so I expect there to be bugs. You should read the
 description at [1] carefully If you encounter a specific problem, then
 email me or this list, and provide a minimum FO test input file, the output
 PDF file, your fop.xconf file and any console output.

 [1] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html

 Regards,
 Glenn



 On Sat, Aug 3, 2013 at 2:55 PM, jaya chandra Reddy 
 jayachan...@ecomzera.com wrote:

 Hi,

i am using fop1.1 version to have multi language support in PDF with
 complex scripts. I have been trying with Devanagari Hindi but could not get
 it work. Can any one give reference or example or testcase. Currently i am
 facing problem of glyph for Indian Languages.  I tried with Japanese it
 works fine. for this i configured Arial Unicode font.

 --
 *Thanks,*
 *JayaChandra,*





 --

 *Thanks,
 JayaChandra,*
 *SeniorSoftwareEngineer, ecomzera*


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Multi Language Support in PDF

[Glenn Adams]

There is preliminary support for some Indic scripts, but it is not fully
debugged or tested, so I expect there to be bugs. You should read the
description at [1] carefully If you encounter a specific problem, then
email me or this list, and provide a minimum FO test input file, the output
PDF file, your fop.xconf file and any console output.

[1] http://xmlgraphics.apache.org/fop/1.1/complexscripts.html

Regards,
Glenn



On Sat, Aug 3, 2013 at 2:55 PM, jaya chandra Reddy jayachan...@ecomzera.com
 wrote:

 Hi,

i am using fop1.1 version to have multi language support in PDF with
 complex scripts. I have been trying with Devanagari Hindi but could not get
 it work. Can any one give reference or example or testcase. Currently i am
 facing problem of glyph for Indian Languages.  I tried with Japanese it
 works fine. for this i configured Arial Unicode font.

 --
 *Thanks,*
 *JayaChandra,*

Re: Vietnamese complex-script support?

[Glenn Adams]

No special script processing should be required other than what is already
provided by the DefaultScriptProcessor, which enables 'ccmp', 'liga', and
'locl' features for GSUB and 'kern', 'mark', and 'mkmk' features for GPOS
for the Latin script.

Make sure you are using a font that contains appropriate GPOS tables in
order to get good mark placement.

Have you tried using some font and find it doesn't work as expected with VN
text? If so, then please send a minimal FO input file and the resulting PDF.

G.



On Thu, Aug 1, 2013 at 7:23 AM, Jonathan Levinson 
jonathan.levin...@intersystems.com wrote:

  Hi,

 ** **

 Are there plans to add complex script support for Vietnamese to FOP?

 ** **

 Thanks,

 Jonathan Levinson

 Senior Software Developer

 InterSystems

 ** **

Re: FOP 1.1: Rendering problem with overflowing table cells

[Glenn Adams]

On Mon, Jun 3, 2013 at 11:09 PM, Ulrich Mayring u...@denic.de wrote:

 sure, I agree if work is going on incorporating new features of
 xmlgraphics-commons, then you wouldn't want to update its version every
 week. However, the best practices I learned are to develop against official
 APIs as soon as possible.

 I was under the impression that the work concerning xmlgraphics-commons is
 already months old and that the dependency on the trunk version has perhaps
 been overlooked.


In general, we release FOP and XGC together at the same time (as we did
with FOP 1.1 and XGC 1.5) on 2012-10-20. During the interim, we use (in
FOP) a snapshot of the XGC trunk build, which we park at:

lib/xmlgraphics-commons-svn-trunk.jar

in the FOP source hierarchy.

Updating this snapshot is a manual process, so it is possible that some dev
has forgotten to update this after making an XGC trunk change. If you
notice a difference between this snapshot and the current XGC trunk build,
then let us know at fop-...@xmlgraphics.apache.org, and I'm sure someone
will remedy that problem shortly.

Regards,
Glenn

Re: FOP 1.1: Rendering problem with overflowing table cells

[Glenn Adams]

Ulrich,

It is not uncommon for works under development (as is the case in the
trunk) to depend on the latest version of a dependent JAR (e.g.,
xmlgraphics-commons). That's just the nature of the dev process. The same
applies for the APIs and Docs.

What you are asking for is appropriate for the next release (whatever
number turns out to be applied), but is an ongoing process in the trunk.
That's part of the risk/reward aspect of using an unreleased version. You
have to spend more effort to use it, but you gain from its new features,
fixes, etc.

Regards,
Glenn



On Fri, May 31, 2013 at 1:36 AM, Ulrich Mayring u...@denic.de wrote:

 Oh, and another thing: the new code depends on an unspecified trunk
 version of xmlgraphics-common. That makes it very hard to track bugs, as I
 might have another version than someone else. If no new release of
 xmlgraphics-common is available I would strongly suggest to depend on a
 specific nightly build, so that everyone downloading fop-trunk is on the
 same page with respect to external dependencies.

 Kind regards,

 Ulrich



 Ulrich Mayring wrote:

 Hello Luis,

 the problem with this approach is that not all setter-methods that were
 available in FopFactory are now available in the builder. Also, please
 note
 that the docs haven't been updated, they still suggest to do it the old
 way.

 For example, if you look at
 http://xmlgraphics.apache.org/**fop/trunk/embedding.html#**
 config-internalhttp://xmlgraphics.apache.org/fop/trunk/embedding.html#config-internalyou'll
 find that the first two methods listed there are not available in the
 builder.

 Kind regards,

 Ulrich

 Luis Bernardo wrote:

 See this thread:
 http://mail-archives.apache.**org/mod_mbox/xmlgraphics-fop-**
 users/201302.mbox/%3c512D5B3C.**8060...@gmail.com%3ehttp://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201302.mbox/%3c512d5b3c.8060...@gmail.com%3e



 On Wednesday, May 29, 2013, Ulrich Mayring wrote:

  Ooops, the newest Nightly Build has changed the Interface of FopFactory
 and FontManager. All the setter-methods in those classes are gone. How
 can
 I programmatically configure FOP now? The docs under
 http://xmlgraphics.apache.org/fop/trunk/embedding.html#
 config-internalhttp://xmlgraphics.apache.org/**fop/trunk/embedding.html#**config-internal
 http://**xmlgraphics.apache.org/fop/**trunk/embedding.html#config-**
 internalhttp://xmlgraphics.apache.org/fop/trunk/embedding.html#config-internal
 still
 suggest the old way.

 cheers,

 Ulrich


 Ulrich Mayring wrote:

  Hi Glenn,

 thanks for the pointer, your suspicion was correct. With the latest
 nightly
 build the page is rendered like it was in FOP 0.95, which I believe is
 the
 correct way.

 Thanks a lot,

 Ulrich

 Glenn Adams wrote:

  I would suggest you check the current trunk (you can use a nightly
 build
 if
 you don't want to build yourself). There were some fixes in this are
 since
 1.1.


 On Wed, May 29, 2013 at 6:56 AM, Ulrich Mayring u...@denic.de
 wrote:

   Hi all,


 please find attached an FO file and two PDFs, which were rendered
 from
 it.
 One was rendered by FOP 0.95, while the other was rendered by FOP
 1.1.

 If you compare the PDFs, you'll see that the header Price (EUR) as
 well
 as the value 8,888,888.88 jut out to the right in the FOP 1.1
 rendering,
 while they look fine in the FOP 0.95 output.

 The structure of the fo:table is such that the rightmost column is
 too
 small to fit either of these two items, so they have to overflow the
 table
 cell in some way (cut off is not an option here). In FOP 0.95 the
 items
 flow out to the left, practically into the previous table cell, but
 there
 is enough room to accommodate them. Whereas FOP 1.1 flows the items
 out
 to
 the right of the table cell, which in this case looks ugly.

 My questions are: can I get the old rendering behavior back? Perhaps
 by
 changing something in the FO? And who is actually doing the right
 thing,
 FOP 0.95 or FOP 1.1?

 Note: in FOP 1.1 these were rendered with the Complex Scripts
 feature
 off, so as to minimise variation between FOP 0.95 and 1.1.

 Many thanks in advance for any pointers,

 Ulrich


 --**--**
 -
 To unsubscribe, e-mail: fop-users-unsubscribe@**
 xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-help@xmlgraphics.**
 apache.org fop-users-h...@xmlgraphics.apache.org





 --**
 --**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-help@xmlgraphics.**
 apache.org fop-users-h...@xmlgraphics.apache.org






 --**--**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org

Re: FOP 1.1: Rendering problem with overflowing table cells

[Glenn Adams]

I would suggest you check the current trunk (you can use a nightly build if
you don't want to build yourself). There were some fixes in this are since
1.1.


On Wed, May 29, 2013 at 6:56 AM, Ulrich Mayring u...@denic.de wrote:

 Hi all,

 please find attached an FO file and two PDFs, which were rendered from it.
 One was rendered by FOP 0.95, while the other was rendered by FOP 1.1.

 If you compare the PDFs, you'll see that the header Price (EUR) as well
 as the value 8,888,888.88 jut out to the right in the FOP 1.1 rendering,
 while they look fine in the FOP 0.95 output.

 The structure of the fo:table is such that the rightmost column is too
 small to fit either of these two items, so they have to overflow the table
 cell in some way (cut off is not an option here). In FOP 0.95 the items
 flow out to the left, practically into the previous table cell, but there
 is enough room to accommodate them. Whereas FOP 1.1 flows the items out to
 the right of the table cell, which in this case looks ugly.

 My questions are: can I get the old rendering behavior back? Perhaps by
 changing something in the FO? And who is actually doing the right thing,
 FOP 0.95 or FOP 1.1?

 Note: in FOP 1.1 these were rendered with the Complex Scripts feature
 off, so as to minimise variation between FOP 0.95 and 1.1.

 Many thanks in advance for any pointers,

 Ulrich


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP 1.1: Rendering problem with overflowing table cells

[Glenn Adams]

I've asked some of the team that worked on those changes to respond to you
on this issue.


On Wed, May 29, 2013 at 9:20 AM, Ulrich Mayring u...@denic.de wrote:

 Apparently the setter methods were deleted by merging a
 Temp_URI_Unification branch back into the trunk. Unfortunately I can't
 find this branch in the repository. Also, the supplied examples never
 configure the FopFactory programmatically.

 Ulrich



 Ulrich Mayring wrote:

 Ooops, the newest Nightly Build has changed the Interface of FopFactory
 and
 FontManager. All the setter-methods in those classes are gone. How can I
 programmatically configure FOP now? The docs under
 http://xmlgraphics.apache.org/**fop/trunk/embedding.html#**
 config-internalhttp://xmlgraphics.apache.org/fop/trunk/embedding.html#config-internalstill
 suggest the old way.

 cheers,

 Ulrich


 Ulrich Mayring wrote:

 Hi Glenn,

 thanks for the pointer, your suspicion was correct. With the latest
 nightly
 build the page is rendered like it was in FOP 0.95, which I believe is
 the
 correct way.

 Thanks a lot,

 Ulrich

 Glenn Adams wrote:

 I would suggest you check the current trunk (you can use a nightly
 build if
 you don't want to build yourself). There were some fixes in this are
 since
 1.1.


 On Wed, May 29, 2013 at 6:56 AM, Ulrich Mayring u...@denic.de wrote:

  Hi all,

 please find attached an FO file and two PDFs, which were rendered from
 it.
 One was rendered by FOP 0.95, while the other was rendered by FOP 1.1.

 If you compare the PDFs, you'll see that the header Price (EUR) as
 well
 as the value 8,888,888.88 jut out to the right in the FOP 1.1
 rendering,
 while they look fine in the FOP 0.95 output.

 The structure of the fo:table is such that the rightmost column is too
 small to fit either of these two items, so they have to overflow the
 table
 cell in some way (cut off is not an option here). In FOP 0.95 the items
 flow out to the left, practically into the previous table cell, but
 there
 is enough room to accommodate them. Whereas FOP 1.1 flows the items
 out to
 the right of the table cell, which in this case looks ugly.

 My questions are: can I get the old rendering behavior back? Perhaps by
 changing something in the FO? And who is actually doing the right
 thing,
 FOP 0.95 or FOP 1.1?

 Note: in FOP 1.1 these were rendered with the Complex Scripts feature
 off, so as to minimise variation between FOP 0.95 and 1.1.

 Many thanks in advance for any pointers,

 Ulrich


 --**--**
 -
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-help@xmlgraphics.**
 apache.org fop-users-h...@xmlgraphics.apache.org





 --**--**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: 
 fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org

Re: FOP 1.1: Unwanted Ligatures in Latin Scripts

[Glenn Adams]

What, am I supposed to guess your output? Come on now, how about an input
FO and output PDF file? Jeez.

Further, have you checked that this font actually contains a GSUB table
with a 'liga' feature that enables the mapping you wish?


On Wed, May 29, 2013 at 2:40 PM, honyk j.tosov...@email.cz wrote:

 Dear All,

  The following features are enabled by default for all scripts which do
 not
  otherwise override this feature set:

  GSUB: {ccmp, liga, locl}
  GPOS: {kern, mark, mkmk}


 talking about ligatures I've made a test for Palatino Linotype on fresh
 installed fop 1.1 and no ligature replacement is applied. The font is found
 (auto-detected) and embedded correctly.

 It works fine in ConTeXt:
 http://wiki.contextgarden.net/Palatino_Linotype_under_MKIV

 Tested on my Win 7.

 So I have the opposite problem. Can I switch this feature on somehow?

 Thanks,

 Jan


 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP 1.1: Unwanted Ligatures in Latin Scripts

[Glenn Adams]

The addition of Complex Script support in FOP 1.1 is the cause. The font
actually controls whether ligatures are used or not.

The following features are enabled by default for all scripts which do not
otherwise override this feature set:

GSUB: {ccmp, liga, locl}
GPOS: {kern, mark, mkmk}

See org.apache.fop.complexscripts.scripts.DefaultScriptProcessor.

If you read the description of these features [1], you will find that they
are defined as should be active by default.

[1] http://www.microsoft.com/typography/otspec/featurelist.htm

So, if a font designer includes a 'liga' table in the font, then those
substitutions will apply. As Pascal has pointed out, you can disable CS
entirely, in which case none of the GSUB or GPOS processing is performed.
Another work around would be to use something like:

fo:character character=f/fo:character character=i/

which happens to work at the moment due to a bug that prevents performing
GSUB processing across an element boundary, but that may be fixed at some
point.

A better long term solution is to introduce the CSS3 Font Module's
font-variant-ligatures property [2], or, more generally, the
font-feature-settings property [3] as fox: extension attributes.

[2] http://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop
[3] http://www.w3.org/TR/css3-fonts/#font-feature-settings-prop

Regards,
Glenn



On Tue, May 28, 2013 at 3:01 AM, Ulrich Mayring u...@denic.de wrote:

 Hi all,

 I just upgraded from 0.95 to 1.1 and one of the issues that crept up is
 that suddenly FOP uses ligatures, which it did not use before. Latin words
 containing the letters fi or fl are now rendered using ligatures in the
 PDF, although they are written as two seperate characters in the XML input
 file.

 I can open a bug and/or supply concrete test cases if needed, but I just
 wanted to ask beforehand whether that is a known problem or perhaps a
 configuration option?

 I am using a TrueType font, Pragmatica Condensed. It may well have to do
 with this font, since the standard FOP examples do not seem to have this
 problem.

 Many thanks in advance for any pointers,

 Ulrich


 --**--**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: 
 fop-users-help@xmlgraphics.**apache.orgfop-users-h...@xmlgraphics.apache.org

Re: FOP 1.1: Unwanted Ligatures in Latin Scripts

[Glenn Adams]

On Tue, May 28, 2013 at 9:59 AM, Ulrich Mayring u...@denic.de wrote:

 Thanks a lot guys for the information. I noticed the new feature Complex
 Scripts, but did not look at it more closely, because I thought it would
 not apply to me using plain English :)

 I have turned the feature off for now, which not only got rid of the
 ligatures, it has also fixed the kerning for numbers, such as postal codes,
 dates and account numbers. With the Complex Scripts feature on these
 numbers are basically rendered in a monospaced way, which looks real ugly
 in most places. Not sure which of the features mentioned are responsible
 for that strange kerning (or lack thereof).


Actually, that may be due to another registered bug on my hit list:

https://issues.apache.org/jira/browse/FOP-2213



 I cannot use any of the suggested workarounds, because the text I process
 is in parts dynamically generated and outside of my control. It would of
 course be great if it were possible to enable/disable the various Complex
 Scripts features independent of each other, preferably not just globally,
 but on a per-paragraph level.


This would be possible if we introduce an fox:font-feature-settings
property as defined in [3] cited below, or at least if they add a generic
'none' or 'off' value that disables all features. However, I doubt you
would ever want to disable all font features, but rather would prefer to
control them on a feature by feature basis, as presently defined in [3].
For example, you could specify:

fo:block fox:font-feature-setting='liga' off
Disable common ligature substitutions for 'ff', 'fi', 'fl', 'ffi', 'ffl',
etc.
/fo:block

I think it probably undesirable to turn of CS on a block basis, though that
could probably be implemented as well without undue difficulty.

I've added a couple of New Feature issues on these items:

https://issues.apache.org/jira/browse/FOP-2256
https://issues.apache.org/jira/browse/FOP-2257



 Kind regards,

 Ulrich


 Glenn Adams wrote:

 The addition of Complex Script support in FOP 1.1 is the cause. The font
 actually controls whether ligatures are used or not.

 The following features are enabled by default for all scripts which do not
 otherwise override this feature set:

 GSUB: {ccmp, liga, locl}
 GPOS: {kern, mark, mkmk}

 See org.apache.fop.complexscripts.**scripts.**DefaultScriptProcessor.

 If you read the description of these features [1], you will find that they
 are defined as should be active by default.

 [1] 
 http://www.microsoft.com/**typography/otspec/featurelist.**htmhttp://www.microsoft.com/typography/otspec/featurelist.htm

 So, if a font designer includes a 'liga' table in the font, then those
 substitutions will apply. As Pascal has pointed out, you can disable CS
 entirely, in which case none of the GSUB or GPOS processing is performed.
 Another work around would be to use something like:

 fo:character character=f/fo:character character=i/

 which happens to work at the moment due to a bug that prevents performing
 GSUB processing across an element boundary, but that may be fixed at some
 point.

 A better long term solution is to introduce the CSS3 Font Module's
 font-variant-ligatures property [2], or, more generally, the
 font-feature-settings property [3] as fox: extension attributes.

 [2] 
 http://www.w3.org/TR/css3-**fonts/#font-variant-ligatures-**prophttp://www.w3.org/TR/css3-fonts/#font-variant-ligatures-prop
 [3] 
 http://www.w3.org/TR/css3-**fonts/#font-feature-settings-**prophttp://www.w3.org/TR/css3-fonts/#font-feature-settings-prop

 Regards,
 Glenn



 On Tue, May 28, 2013 at 3:01 AM, Ulrich Mayring u...@denic.de wrote:

  Hi all,

 I just upgraded from 0.95 to 1.1 and one of the issues that crept up is
 that suddenly FOP uses ligatures, which it did not use before. Latin
 words
 containing the letters fi or fl are now rendered using ligatures in
 the
 PDF, although they are written as two seperate characters in the XML
 input
 file.

 I can open a bug and/or supply concrete test cases if needed, but I just
 wanted to ask beforehand whether that is a known problem or perhaps a
 configuration option?

 I am using a TrueType font, Pragmatica Condensed. It may well have to do
 with this font, since the standard FOP examples do not seem to have this
 problem.

 Many thanks in advance for any pointers,

 Ulrich


 --**
 --**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgra**phics.apache.orghttp://xmlgraphics.apache.org
 fop-users-**unsubscribe@xmlgraphics.**apache.orgfop-users-unsubscr...@xmlgraphics.apache.org
 
 For additional commands, e-mail: fop-users-help@xmlgraphics.**a**
 pache.org 
 http://apache.orgfop-users-help@**xmlgraphics.apache.orgfop-users-h...@xmlgraphics.apache.org
 






 --**--**-
 To unsubscribe, e-mail: 
 fop-users-unsubscribe@**xmlgraphics.apache.orgfop-users-unsubscr

Re: Use TTF font subtable (substitution) possible?

[Glenn Adams]

Support for Advanced Typographic Tables (GSUB, GPOS, etc) [1] was added in
1.1 to support complex scripts [2]. You can also use these same complex
script features with non complex scripts, provided the font supports the
desired features [3].

At present, the default features enabled for all scripts are:

GSUB: { 'ccmp', 'liga', 'locl' }
GPOS: { 'kern', 'mark', 'mkmk' }

It sounds like you want to may want to use the 'salt' (Stylistic
Alternatives), but I'm not certain since I don't know what features are in
the font you are trying to use. In any case, although I plumbed the CS code
to permit the higher layers of FO processing to specify something like the
CSS3 font-feature-settings property, I haven't yet taken any action to add
this property as an fox (extension namespace property) in FOP.

As a work around, if the Font happens to expose the glyph you want via a
Unicode PUA entry in the CMAP, then you can access it via that PUA code
point. There is no other way to specify a specific glyph in FOP. You could
also use SVG and convert the glyph into an SVG outline, though that's
probably over kill.

Regards,
Glenn

[1] http://www.microsoft.com/typography/otspec/ttochap1.htm
[2] http://xmlgraphics.apache.org/fop/trunk/complexscripts.html
[3] http://www.microsoft.com/typography/otspec/featuretags.htm
[4] http://www.w3.org/TR/css3-fonts/#font-feature-settings-prop


On Fri, May 10, 2013 at 11:05 AM, Frank Hirsch frank.hir...@mac.com wrote:

 I am currently trying to use a specific glyph from a TTF font in a
 substitution table.

 1. I learned such glyphs in OTF or TTF fonts can be used in layout
 programs such as InDesign by selecting them directly in the glyph selection
 2. Trying to understand and having checked the documentation, this seems
 to have nothing to do with the font substitution described at
 http://xmlgraphics.apache.org/fop/1.1/fonts.html#substitution
 3. Calling the glyph by HEX or Unicode is not possible since it's the same
 address

 So far I was trying to understand the mechanism of subtables (GSUB
 Lookups) at all, which led me to check the content of my font with
 fontforge.
 There I found all the corresponding tables under Element  Font Info 
 Lookups...

 Is it possible at all to use a glyph from a substitution table in Apache
 FOP at all or am I doing something completely wrong?
 I would love to have in FO the same ability as in my layout software using
 tabular digits...

 Thank's for your help ;)

 - I am running on fop-1.0 and fop-1.1 on Mac OS X with Java 1.7.0u21
 - The font has been defined as
 font embed-url=fonts/DuraSans2012-Bold.ttf
  font-triplet name=DuraSans style=normal weight=bold/
 /font
 - Very basic and simple selection of the font in fo...
 fo:block font-family=DuraSans.../fo:block



 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: Eliminating soft hyphens shown in mid line?

[Glenn Adams]

You can start by filing a bug in JIRA, and supplying the following:

(1) input XSL-FO test file, in a maximally minimal form to show the problem
(2) sample output PDF from that input, showing the problem
(3) information about version and configuration
(4) any console output produced

See [1] for creating a bug in JIRA.

[1] https://issues.apache.org/jira/browse/FOP


On Fri, Apr 19, 2013 at 2:58 AM, Mark Craig mark.cr...@gmail.com wrote:

 Hello,

 Recently I started using soft hyphens with FOP to split some painfully
 long Java properties at . In most cases, this has worked very well and been
 a significant improvement.

 There seems to be some cases, however, where soft hyphens show up in mid
 line when followed by punctuation characters like ., ], and .

 I find the excerpt of the attached .fo:

 fo:blockfo:inline
 font-size=0.9em.#xAD;.#xAD;/fo:inline/fo:block
 fo:blockfo:inline font-size=0.9em.#xAD;
 .#xAD;/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;]/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;\/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;a/fo:inline/fo:block
 fo:blockfo:inline
 font-size=0.9em.#xAD;Z/fo:inline/fo:block


 Looks like this in PDF output:

 .-.
 . .
 .
 .-]
 .\
 .-
 .a
 .Z


 I am seeing this behavior with FOP 1.0, FOP 1.1, and FOP 20130418 nightly
 build.

 What should I do to eliminate the soft hyphens showing up in mid line (not
 before a line break)?

 Thank you for your help.
 Regards,
 Mark



 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP memory growing with a lot of page-sequences

[Glenn Adams]

Put each page-sequence in a separate XSL-FO file.


On Thu, Apr 18, 2013 at 5:09 AM, aemitic aemi...@hotmail.it wrote:

 Hi,

 I noticed that FOP (any version) uses a constantly growing amount of memory
 when creating PDFs. Even if using very small page-sequence blocks and no
 forward references.

 Please refer to this stackoverflow question which contains a small java
 program that replicates the issue.

 How can I limit the amount of used memory when transforming to PDF an FO
 file with a huge number of page-sequence blocks? ( 25)

 Thanks for any help



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequences-tp38355.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP memory growing with a lot of page-sequences

[Glenn Adams]

use a separate tool to combine the PDFs


On Thu, Apr 18, 2013 at 8:31 AM, aemitic aemi...@hotmail.it wrote:

 @Glenn Adams-2
 Could you please elaborate more?

 Transforming multiple XSL-FO files with FOP would mean to produce multiple
 XSL-FO files, wouldn't it?
 I need to produce a single PDF.



 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38360.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org

Re: FOP memory growing with a lot of page-sequences

[Glenn Adams]

It depends on what tool you use to combine them. In any case, I don't think
you will find an alternative any time soon. Just a heads up. If you care to
create a patch that solves this problem, then please post it and I'll make
sure it is applied ASAP.


On Thu, Apr 18, 2013 at 9:01 AM, aemitic aemi...@hotmail.it wrote:

 Thanks for the suggestion.

 This /workaround/ (it's not a solution) cannot be applied. Why:
  - internal pdf links would not work
  - pdf bookmarks would not work
  - page numbering would not be correct
  - creating over 15 PDFs and then merging them with an external tool is
 unacceptable from a performance point of view




 --
 View this message in context:
 http://apache-fop.1065347.n5.nabble.com/FOP-memory-growing-with-a-lot-of-page-sequence-blocks-25-tp38355p38362.html
 Sent from the FOP - Users mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: fop-users-unsubscr...@xmlgraphics.apache.org
 For additional commands, e-mail: fop-users-h...@xmlgraphics.apache.org