Hi Chris, thanks for clarification now I understand.
I gave the resulting PostScript file to our printer manufacturer (Ricoh) and they told me that the printers are returning a configuration error: OFFENDING COMMAND: setpagedevice ERRORINFO: Key = /PageSize Value = arraytpe STACK: dicttype We plan to replace an old LaTeX environment with Apache FOP, and the PostScript files generated by LaTeX print without an error on the printers. Do I need the setpagedevice in the PostScript file and if not, is there a way to disable the generation of this command in FOP? Thanks, Frank cbowditch wrote: > > Frank Niedermann wrote: > > Hi Frank, > >> Hi Chris, >> >> yes and I already used those settings within FOP but it didn't work. >> >> Then Jeremias mentioned that those settings don't affect PostScript >> version and I should use the DSC comment %%LanguageLevel: 2 instead. > > What Jeremias said was that the LanguageLevel setting doesn't affect the > DSC comment version in use. It only affects the %%LanguageLevel comment. > >> >> I don't see how to set this commend on the page you mentioned, >> or am I just overseeing the relevant part? > > If you set the Language Level in fop.xconf file then %%LanguageLevel > comment in Postscript will change to reflect that but the DSC comment > version will not change. > > Regards, > > Chris > >> >> Thanks, >> Frank >> >> >> cbowditch wrote: >> >>>Frank Niedermann wrote: >>> >>>Hi Frank, >>> >>> >>>>Hi Jeremias, >>>> >>>>do you have an example on how to set the LanguageLevel within FOP? >>> >>>Adrian already sent you a link that shows you how to specify Language >>>Level of 2 for Postscript generation: >>> >>>http://xmlgraphics.apache.org/fop/0.95/output.html#ps-configuration >>> >>>This setting goes into fop.xconf file and you have to tell FOP to load >>>the file using -c option from command line. >>> >>>Regards, >>> >>>Chris >>> >>> >>>>I found a wiki page [1] about PostScript configuration within FOP but >>>>on the bottom it says this: >>>> >>>>"Some people will only add a DSC comment into the PostScript file >>>>instead of the actual media selection code. This comment will then >>>>be expanded later." >>>> >>>>Thanks, >>>> Frank >>>> >>>>[1] http://wiki.apache.org/xmlgraphics-fop/ExtensionsForPostScript >>>> >>>> >>>>Jeremias Maerki-2 wrote: >>>> >>>> >>>>>Hi Adrian & Frank, >>>>> >>>>>please note that "%!PS-Adobe-3.0" does not refer to the PostScript >>>>>language level but to the version of the DSC specification which is 3.0. >>>>>The language level is given by the following DSC comment: >>>>> >>>>>%%LanguageLevel: 2 >>>>> >>>>>So this is no bug. >>>>> >>>>>On 01.04.2009 11:11:30 Adrian Cumiskey wrote: >>>>> >>>>> >>>>>>Hi Frank, >>>>>> >>>>>>I don't think you are missing anything, I think it may be a bug. Having >>>>>>stepped through the code, "%!PS-Adobe-3.0" is always written as the >>>>>>first line of the header regardless of the language level. Could you >>>>>>please send us a bug report at >>>>>>https://issues.apache.org/bugzilla/enter_bug.cgi?product=Fop and someone >>>>>>will take a look at the problem. I'll try to find some time later this >>>>>>week. >>>>>> >>>>>>Thanks, >>>>>> >>>>>>Adrian. >>>>>> >>>>>>Frank Niedermann wrote: >>>>>> >>>>>> >>>>>>>Hi Adrian, >>>>>>> >>>>>>>thanks for the link. This is my fopConfiguration.xml file: >>>>>>><fop> >>>>>>> <renderers> >>>>>>> <renderer mime="application/postscript"> >>>>>>> <auto-rotate-landscape>true</auto-rotate-landscape> >>>>>>> <language-level>2</language-level> >>>>>>> </renderer> >>>>>>> </renderers> >>>>>>></fop> >>>>>>> >>>>>>>And this is how I load this configuration file: >>>>>>>String fopConfiguration = "fopConfiguration.xml"; >>>>>>>FopFactory fopFactory = FopFactory.newInstance(); >>>>>>>fopFactory.setUserConfig(new File(fopConfiguration)); >>>>>>>FOUserAgent foUserAgent = fopFactory.newFOUserAgent(); >>>>>>> >>>>>>>But it still creates version 3 PS-files (I checked the header). >>>>>>> >>>>>>>Am I missing something else? >>>>>>> >>>>>>>Thanks, >>>>>>> Frank >>>>>>> >>>>>>> >>>>>>>Adrian Cumiskey-2 wrote: >>>>>>> >>>>>>> >>>>>>> >>>>>>>>Hi Frank, >>>>>>>> >>>>>>>>Yes, you can do this with the language-level configuration option (see >>>>>>>>http://xmlgraphics.apache.org/fop/0.95/output.html#ps-configuration). >>>>>>>> >>>>>>>>Adrian. >>>>>>>> >>>>>>>>Frank Niedermann wrote: >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>>>Hi, >>>>>>>>> >>>>>>>>>we are using Apache FOP to create PS files which should be printed on >>>>>> >>>>>>a >>>>>> >>>>>> >>>>>>>>>HP-Unix machine. >>>>>>>>> >>>>>>>>>Unfortunately this machine only supports version 2.0 PS files: >>>>>>>>>%!PS-Adobe-2.0 >>>>>>>>> >>>>>>>>>Apache FOP creates version 3.0 PS files which are ignored by the >>>>>> >>>>>>HP-Unix >>>>>> >>>>>> >>>>>>>>>print system. >>>>>>>>> >>>>>>>>>Is there a way to tell FOP to generate version 2.0 PS files? >>>>>>>>> >>>>>>>>>Thanks, >>>>>>>>> Frank >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>> >>>>> >>>>> >>>>>Jeremias Maerki >>>>> >>>>> >>>>>--------------------------------------------------------------------- >>>>>To unsubscribe, e-mail: [email protected] >>>>>For additional commands, e-mail: [email protected] >>>>> >>>>> >>>>> >>>> >>>> >>> >>> >>> >>>--------------------------------------------------------------------- >>>To unsubscribe, e-mail: [email protected] >>>For additional commands, e-mail: [email protected] >>> >>> >>> >> >> > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > > -- View this message in context: http://www.nabble.com/How-to-create-version-2.0-PS-files-tp22804932p22846837.html Sent from the FOP - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
