I tried putting the space as the end of the preceding run and it also got 
removed, so either my test is bad or something else is going on.

I can enhance my generation process to combine runs that have the same 
properties but that's annoying and adds processing time.

Cheers,

E.

--
Eliot Kimber
http://contrext.com
 

On 8/16/18, 8:46 AM, "Murphy, Mark" <[email protected]> wrote:

    Maybe the space is preserved only at the end of the text in the node?
    
    -----Original Message-----
    From: Eliot Kimber [mailto:[email protected]] 
    Sent: Wednesday, August 15, 2018 4:21 PM
    To: POI Users List <[email protected]>
    Subject: Any Idea Why Word Does not Preserve Leading or Trailing Space?
    
    In the DOCX I'm generating I have this pair of runs:
    
    <w:r><w:t>If an applicant under subsection</w:t></w:r><w:r><w:t 
xml:space="preserve"> 38-79</w:t></w:r>
    
    Notice the leading space in the second run (" 38-79").
    
    When I view this with Word for Mac (16.16) the space is not rendered.
    
    This seems like a bug, especially since space is preserve on the w:t 
element.
    
    Any idea why Word behaves this way and if there's a way to avoid it (other 
than merging the two runs, which in this case have the same properties)?
    
    This is DOCX being generated from XML source where the runs reflect 
separate source nodes (in this case a text node and then an inline element).
    
    Thanks,
    
    Eliot
    --
    Eliot Kimber
    http://contrext.com
     
    
    
    
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [email protected] For additional 
commands, e-mail: [email protected]
    
    
    ---------------------------------------------------------------------
    To unsubscribe, e-mail: [email protected]
    For additional commands, e-mail: [email protected]
    



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to