OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: RE: [xliff] Syntext and indentations


Hi Yves,

As you probably know, space is irrelevant in XML. But the prescribed way to make it relevant is with xml:space (http://www.w3.org/TR/xml11/#sec-white-space). I'm not sure if Syntext honors xml:space, but in the distant past I've had success with other XML editors by adding a doctype subset and added xml:space (preserve) attributes. Also, if there's a default XSLT stylesheet Sytnext uses, you can set the <xsl:preserve-space elements="olink"> element.

I'll try to goof with this a bit and see if I can get it to work in Sytext.

- Bryan
________________________________________
From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] On Behalf Of Yves Savourel [ysavourel@enlaso.com]
Sent: Tuesday, December 06, 2011 5:25 AM
To: 'XLIFF TC'
Subject: [xliff] Syntext and indentations

Hi everyone,

I'm using the open-source Syntext editor to edit the 2.0 draft files and I'm running into a problem: Syntext seems to be automatically trying to do some "pretty printing" when it saves the files. For example a section that is originally like this:

<para><emphasis>Used in:</emphasis> <olink targetdoc="../elements/inline/ph.xml" targetptr="ph">      <code>&lt;ph&gt;</code></olink>.</para>

(no line breaks)

Ends up like this:

<para><emphasis>Used in:</emphasis>
 <olink targetdoc="../elements/inline/ph.xml" targetptr="ph">
    <code>&lt;ph&gt;</code>
 </olink>
</para>

(extra line breaks and indentation)

This is a problem because it adds at least one space between <olink> and <code> and result in weirdly spaced links in the PDF/HTML output.

Does anyone knows how to turn off this auto-indentation feature in Syntext? I haven't find the option, and I can't believe there is no way to not do this.

Obviously I'm guessing Rodolfo could come up with a clever extra XSLT step to remove the extra white spaces between <olink> and <code> when doing the merge, but it would be better to avoid the problem altogether.

Thanks,
-yves



---------------------------------------------------------------------
To unsubscribe, e-mail: xliff-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: xliff-help@lists.oasis-open.org





[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]