Hello Erik, I'm not sure but I may have had the exact same issue and Glenn Adams provided me with a simple solution that worked. See:
http://mail-archives.apache.org/mod_mbox/xmlgraphics-fop-users/201606.mbox/browser Best regards, -- *NeoDoc* *Maxime Bégnis* [email protected] Tél: +33 (0)4.42.52.24.20 789 Rue de La Gare 13770 Venelles France http://www.neodoc.fr/ Le 06/04/2017 à 16:57, Erik Ogan a écrit : > I am having some issues with ligation in Arabic & Devanagari scripts > in my embedded FOP application. I have not disabled Complex Script > Features, and have explicitly turned them on just to be sure: > > … > FopFactoryBuilder builder = new FopConfParser(cfgStream, > baseURI).getFopFactoryBuilder(); > builder.setComplexScriptFeatures(true); > … > > I’ve searched the archives for tips, but most of the discussion of > ligatures is around removing/disabling them. > > This discussion was the only one I found that seemed like it offered a > solution: > http://marc.info/?l=fop-user&m=142547685119005&w=2 > > But alas, adding script attributes to my fo:block elements (as you’ll > see in the file below) seems to have had no effect. > > I’m using NoTo Sans as my font, which does have ligature information. > > Here is an example (intermediate) FO file: > https://s3-us-west-2.amazonaws.com/erik-fop-questions/with-scripts.fo > (I have also tried downcasing & upcasing the script attributes) > > Here is my configuration file: > https://s3-us-west-2.amazonaws.com/erik-fop-questions/config.xml > > And here is a resulting PDF: > https://s3-us-west-2.amazonaws.com/erik-fop-questions/current.pdf > > The most _infuriating_ part of this is that before this project was > put on hold 1.5 years ago I apparently had it working in early > experiments (before I’d even corrected the alignment of Arabic & > Hebrew): > > https://s3-us-west-2.amazonaws.com/erik-fop-questions/2015-08-09-example.pdf > > I am using the same code, with the same configuration and font files, > yet it is producing a different result. I’ve been tearing my hair out > for weeks trying to figure out what is different. > > I also have a dim memory of having had this issue in earlier > experiments, and discovering a simple solution. But I have NO idea > what that solution was, nor how it would be external to the code & > configuration I am currently running. > > … I JUST had a flashbulb memory that perhaps the solution then was > upgrading from Java 1.6 to 1.7. I’m running all of this on 1.8 right > now. > > Any help or suggestions folks have would be GREATLY appreciated. Thanks! > > -e >
