Thank you for the explanation, Hussein. (And thanks for the clarification on "USLetter"-that question was in the back of my mind as well!) A couple of follow-up questions now that I have a better understanding:
1) Is there an xxeconvert command or parameter I can enter to set the paper.type to use at the time of build? We have an automated build system that uses some scripting to invoke the xxeconvert command on a VM, and I'm looking for a way to be able to tell a given build to use A4, another given build to use USLetter, etc. (One that preferably does not involve logging into the build system VM, opening the XMLmind GUI, and going through the motions of converting a document to PDF just to set the paper.type in the Document Conversion Parameters pane every time I want to print a document with a different paper.type specification.) 2) Is it safe to assume that the Document Conversion Parameters settings modify the background file that XMLmind/xxeconvert calls for a specific conversion (in my case, db51.toPSFile)? I.e., my custom transformation file should really not include any parameters that are part of the Document Conversion Parameters pane for a particular conversion (because the Conversion Parameters take precedence over the custom transformation file)? Thanks, Bryan Pettit -----Original Message----- From: Hussein Shafie <huss...@xmlmind.com> Sent: Wednesday, June 19, 2024 12:26 AM To: Bryan Pettit <bryan_pet...@selinc.com> Cc: xmleditor-support@xmlmind.com Subject: Re: [XXE] GUI Document Conversion Parameters Set Once Override Future Transformation File Changes [Caution - External] On 6/17/24 19:20, Bryan Pettit wrote: > > I'm experiencing an issue with specifying the paper.type > parameter when building PDF documents via *xxeconvert* from the > command line. We typically print PDFs in "letter" format but would > also like the option of printing in A4. In the XMLmind Editor, I have > paper.type set to "letter" in the Document Conversion Parameters under > *DocBook >* *Convert Document > Convert to PDF* per our default. The > custom transformation file we use also includes <xsl:param > name="paper.type">letter</xsl:param>. > > After changing the paper.type parameter in our transformation file to > <xsl:param name="paper.type">A4</xsl:param>, subsequent builds from > the command line via *xxeconvert* are /not/ picking up that change in > the transformation file-the builds are still using > paper.type="letter", as shown below. That's right. I've reproduced your issue here at XMLmind Software. > > It appears that the Document Conversion Parameters in XMLmind's GUI is > overriding my custom transformation file parameters when building via > *xxeconvert* from the command line. Is that intended? Yes, this is the intended behavior. xxeconvert is *really* XXE without a GUI. Hence this program will behave exactly like the XXE desktop app. XSLT parameters specified in the "Document Conversion Parameters" pane of "DocBook > Convert Document > Convert to PDF" have priority over those specified in the XSLT transformation files, whether the stock ones or custom ones. The idea here is that the "Document Conversion Parameters" pane of "DocBook > Convert Document > Convert to PDF" lets the user quickly and interactively experiment/change XSLT parameters. > I know xxeconvert > is part of of the XMLmind Editor program as a whole, but I would > expect any parameter explicitly specified in my custom transformation > file to override that same parameter configured (at some point in the > past) in the Document Conversion Parameters. > I'm sorry but this is not the case for the reasons explained above. --- PS: It seems that the correct value for "paper.type" is "USletter", not "letter". "letter" seems to work because the size of an US letter is used as a fallback for unknown "paper.type" values. -- XMLmind XML Editor Support List xmleditor-support@xmlmind.com http://www.xmlmind.com/mailman/listinfo/xmleditor-support
