Would be nice if it was that easy. Using chunk.xsl unchanged (import docbook.xsl) gives the same errors and warnings as with our customization.
Mvh. Bergfrid Skaara Dias
> Den 7. des. 2016 kl. 12.43 skrev Dave Pawson <>:
>
>> On 7 December 2016 at 11:34, Radu Coravu <> wrote:
>> Hi,
>>
>> I think the problem is this one:
>>
>>> I already import our custom FO xsl.
>>
>>
>> because the stylesheets which produce customized XSL-FO output have nothing
>> in common with the stylesheets which generate HTML output. Usually the HTML
>> output is modified using a custom CSS.
>
> Or using import precedence to override the standard docbook templates Radu?
>
> regards Dave
>
>
>>
>> Regards,
>> Radu
>>
>> Radu Coravu
>> <oXygen/> XML Editor, Schema Editor and XSLT Editor/Debugger
>> http://www.oxygenxml.com
>>
>>> On 12/7/2016 12:20 PM, wrote:
>>>
>>> Hi, we are planning to add HTML to our output formats. Have created PDFs
>>> exclusively for years with custom FO styles sheets in an offline tech stack.
>>> (1.79.1, db 5.1, oxygen 18.1)
>>>
>>> I tried to create a new transformation scenario in oxygen using
>>> html/chunk.xsl and it spits up over 100 undeclared variables and nonexistent
>>> templates.
>>>
>>> How do I troubleshoot this? The missing variables and templates are used
>>> by chunk-common.xsl and chunk-code.xsl. I already import our custom FO xsl.
>>> Do I need to import something else? Add something to our catalog.xml?
>>>
>>> Mvh. Bergfrid Skaara Dias
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail:
>>> For additional commands, e-mail:
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail:
>> For additional commands, e-mail:
>>
>
>
>
> --
> Dave Pawson
> XSLT XSL-FO FAQ.
> Docbook FAQ.
> http://www.dpawson.co.uk
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail:
> For additional commands, e-mail:
>
