RE: [docbook-apps] Olinking and Chunked HTML Transformations
Yes, it should, and it does why I test it with the html/chunk.xsl stylesheet. Are you using a customization layer with the chunking stylesheet? If so, you have to construct it carefully to get the import sequence right. If you don't, then you get a mix of chunked and non-chunked behavior, and I suspect that is what happened in your target.db file. See:
http://www.sagehill.net/docbookxsl/ChunkingCustomization.html If you were following those guidelines, then something else is going on that will require more information. << Commented out all customizations; issues unchanged. For some yet unknown reason when utilizing oXygen (eclipse plugin) on the Linux side, the extended characters €œ<text>€� to not appear surrounding the section text of <xreftext>, Windows side only; will resolve on the oXygen list. Using UTF-8 encoding. The <i> tags persist at the chapter <xref> sections surrounding chapter text. Also <span class="trademark"/> appears in the map within the <ttl> element (just began using the trademark element in a section element). Lastly, when the aforementioned tags are deleted, the olinkdb.xml map validates on the Linux side and subsequent HTML transformations behave as expected. From the Windows side, validation complains “Invalid byte 1 of 1-byte UTF-8 sequence.” Again, this issue is probably best addressed on the oXygen list but any help would be appreciated. Using docbook-rng-5.0b5, docbook-xsl-snapshot (4/30/06), oxygen-7.1.0 (eclipse-3.1.2 plugin), saxon-6.5.5 Ray
Hello Ray, The extended characters are not displayed correctly because the current font of the editor is not able to render them. It is an <oXygen/> FAQ (question 6 in the list): http://www.oxygenxml.com/doc/ug-standalone/common-problems.html To change the editor font in the <oXygen/> Eclipse plugin go to Window -> Preferences -> oXygen -> Editor -> Change font panel. The second error message is caused by an XML file created with one encoding and read with another one or a file starting with an incorrect byte order mark. If you are sure that the file is written and read with the same encoding and the start bytes are not corrupted please attach a small sample file for reproducing the error. Best regards, Sorin http://www.oxygenxml.com/ Ray Miller wrote:
For some yet unknown reason when utilizing oXygen (eclipse plugin) on the Linux side, the extended characters €œ<text>€� to not appear surrounding the section text of <xreftext>, Windows side only; will resolve on the oXygen list. Using UTF-8 encoding.
From the Windows side, validation complains “Invalid byte 1 of 1-byte UTF-8 sequence.” Again, this issue is probably best addressed on the oXygen list but any help would be appreciated.
participants (2)
-
Ray Miller -
Sorin Ristache