Hi Chris, And how exactly would FOP know, which files are your property files and which language to use?
No, I guess the correct setup would be: The xml you pass to fop contains a field with the language. The xsl file (p4epfo.xsl [Maybe .xml works too, but .xsl is the preferred naming convention) has a list of property files. It reads the language field, grabs the correct property file and replaces the text keys. But it would probably be much easier, if you grab the record from the database and replace the text keys before you pass the XML string to FOP. Regards, Georg Datterl ------ Kontakt ------ Georg Datterl Geneon media solutions gmbh Gutenstetter Straße 8a 90449 Nürnberg HRB Nürnberg: 17193 Geschäftsführer: Yong-Harry Steiert Tel.: 0911/36 78 88 - 26 Fax: 0911/36 78 88 - 20 www.geneon.de Weitere Mitglieder der Willmy MediaGroup: IRS Integrated Realization Services GmbH: www.irs-nbg.de Willmy PrintMedia GmbH: www.willmy.de Willmy Consult & Content GmbH: www.willmycc.de -----Ursprüngliche Nachricht----- Von: CRANFORD, CHRIS [mailto:chris.cranf...@setech.com] Gesendet: Donnerstag, 9. September 2010 16:42 An: fop-users@xmlgraphics.apache.org Betreff: RE: FOP and Internationalization Georg - Please excuse my ignorance, but exactly how would I go about doing that? What I had in mind was that a URL would be called that did the following: - Requested the database record from the data store - Converts the POJO into an XML string in memory. - Pass the XML string to FOP The XSLT I had planned would be a static file that was created and then packaged as a resource file in the web app, much like my property file for internationalization. applicationMessages_en.properties <- English Text applicationMessages_fr.properties <- French Text p4epfo.xml <- Apache FOP XSLT Chris > -----Original Message----- > From: Georg Datterl [mailto:georg.datt...@geneon.de] > Sent: Thursday, September 09, 2010 9:29 AM > To: fop-users@xmlgraphics.apache.org > Subject: AW: FOP and Internationalization > > Hi Chris, > > I guess, your transformation has to take care of that. --------------------------------------------------------------------- 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
