Peter Brooks wrote: > > I was having problems (still am) in getting reliable output to PDF using a > set of tools developed internally in the company here. Setting certain text > to <emphasis> under Simplified DocBook was sometimes emphasizing and > sometimes not, and the only culprit I could see was the unfamiliar file > format, hence my question.
Difficult to help you for this. I just doubt it could have been the unindented output... > One thing I haven't found is a way to set the baseline directory for FO > Converter (it constantly complains about not being able to find graphics > (media)objects despite their presence in the same directory as the .xml file > that references them - so no path should be necessary). If I use absolute > references (the full path, including the drive letter) then all is OK - but > then that prevents the book from being relocatable... If you use "FO Converter - XSL Utility" (the graphical tool): * For generating RTF, then you really use *our* product. Try with Transformation dialog option "Create intermediate FO file in input directory instead of output directory" checked. * For generating PDF, then you in fact use OpenSource tool called FOP ( http://xml.apache.org/fop/ ), even if XSL Utility integrates it. The same remark about option "Create intermediate FO..." applies too. But FOP, which we consider here as alpha quality software, has also the following bug: a graphics file name which should be relative to the FO document is in fact relative to the current working directory (`pwd` in Unix parlance). Workaround 1: use absolute file names. Workaround 2: start XSL Utility in the directory that will contain the generated FO document. We'll of course upgrade the FOP bundled with XSL Utility for the next release of FO Converter, may be this bug will then be fixed.
