Re: DOCBOOK-APPS: Error: Output character not available

2001-10-24 Thread Jirka Kosek
Gershon L Joseph wrote: I've got Saxon 6.4.3 working with the XSL DocBook stylesheets, and on some XML source files produce nice HTML Help. However, on a large docset I get the following error: Error on line 117 of file:/C:/tools/docbook/docbook-xsl-1.45/html/chunker.xsl: Output

Re: DOCBOOK-APPS: Error: Output character not available

2001-10-24 Thread Gershon L Joseph
Jirka, Thanks for your help. Adding htmlhelp.encoding=windows-1252 helped. But then I get the following error: ... Writing htmlhelp.hhp Error on line 117 of file:/C:/tools/docbook/docbook-xsl-1.45/html/chunker.xsl: Output character not available in this encoding (decimal 174) Transformation

Re: DOCBOOK-APPS: Error: Output character not available

2001-10-24 Thread Gershon L Joseph
Please ignore my previous plea for further assistance. I saved my source XML as iso-8859-1 encoding and put the 3 parameter settings in my driver file instead of on the command line. One or all of these fixed the problem. Thanks Jirka for pointing me in the right direction. I did read that in

Re: DOCBOOK-APPS: Need help including c source

2001-10-24 Thread Eric Richardson
Norman Walsh wrote: / Eric Richardson [EMAIL PROTECTED] was heard to say: | Thanks for the quick response. I found that it is very close. The | first markup works except for some extra leading whitespace on the | first line so perhaps I need to left justify the imagedata tag. The

Re: Re-post: DOCBOOK-APPS: typographical characters encoding

2001-10-24 Thread Ed Nixon
Ok, some progress. The issue appears to be special apostrophes that were an artifact of the text having started out life in MS Word. XMetaL doesn't seem to do much about sorting these characters out or replacing them with correct apostrophes. Nor does it seem very good at finding and

Re: DOCBOOK-APPS: Error: Output character not available

2001-10-24 Thread Jirka Kosek
Gershon L Joseph wrote: Please ignore my previous plea for further assistance. I saved my source XML as iso-8859-1 encoding and put the 3 parameter settings in my driver file instead of on the command line. One or all of these fixed the problem. Thanks Jirka for pointing me in the right