[ 
https://issues.apache.org/jira/browse/DERBY-1992?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13198286#comment-13198286
 ] 

Kim Haase commented on DERBY-1992:
----------------------------------

I tried out the 1.5.4 toolkit and found that the bug that made us insert the 
" " characters in the first place has been fixed. It used to be that if 
you didn't put a non-breaking space between a "ph" element and another element, 
the two elements were munged together, so that what you intended as "The Derby 
ij tool" came out "The Derbyij tool". 

The <ph 
conref="../conrefs.dita#prod/productshortname"></ph>&nbsp;<codeph>ij</codeph> 
tool

With 1.5.4, if you replace the "&nbsp;" with a space, the toolkit preserves the 
space in the output. So if we are able to move to this version of the toolkit, 
we can safely remove those characters from the source.

                
> Upgrade to DITA Open Toolkit to the latest version
> --------------------------------------------------
>
>                 Key: DERBY-1992
>                 URL: https://issues.apache.org/jira/browse/DERBY-1992
>             Project: Derby
>          Issue Type: Improvement
>          Components: Build tools
>    Affects Versions: 11.0.0.0
>            Reporter: Laura Stewart
>             Fix For: 11.0.0.0
>
>         Attachments: refderby-raw-dita1_5_4.pdf, 
> refderby-raw-xhtml-dita1_5_4.zip
>
>
> There are major improvements in the DITA Open Toolkit, including improvements 
> in
> the display of index entries.  Derby is currently on version 1.1.2.1 and 
> needs to upgrade to a later version of
> the DITA Open Toolkit. The latest version of the DITA Open Toolkit can be 
> found here: http://sourceforge.net/projects/dita-ot/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to