RE: [xliff] FS attribute

Hi Christian,

I will take another look at your sample. 

If the TC turned out to prefer the CSS method over the FS method, we'd have some tricky *un-approving* to do.

Thanks,

Bryan
________________________________________
From: Lieske, Christian []
Sent: Sunday, September 30, 2012 10:52 PM
To: Schnabel, Bryan S; Yves Savourel
Cc: 
Subject: RE: [xliff] FS attribute

Hi Bryan and Yves,

I would like to take the opportunity to lobby for a CSS-based approach again (see http://markmail.org/message/yk3pqhz6443v5pcf?q=preview+list:org%2Eoasis-open%2Elists%2Exliff+from:"Lieske%2C+Christian"&page=1).

Cheers,
Christian

-----Original Message-----
From:  [mailto:] On Behalf Of Schnabel, Bryan S
Sent: Montag, 1. Oktober 2012 05:48
To: Yves Savourel; 
Subject: RE: [xliff] FS attribute

Hi Yves,

Thanks. I'll take a look.

I'm pretty sure I can take a sample of an XLIFF 2.0 file, that uses all known elements, apply FS attribute, and XSLT, and get an HTML file perfectly suitable for opening in a browser (i.e., suitable for a just-in-time, in-context browser review). Maybe not, I'll try.

I think that is the *full* intent of the FS attribute. I'm not sure that we have a requirement to create fully valid HTML, maybe we do.

Anyhow, I'll dig into this as soon as I can.

Thanks,

Bryan
________________________________________
From:  [] on behalf of Yves Savourel []
Sent: Saturday, September 29, 2012 7:44 PM
To: 
Subject: [xliff] FS attribute

Hi Bryan, all,

I was trying to use the fs attribute in the toolkit and the more I look at it the more it look not useable the way it is defined.

I'm not against the feature at all, but I just think it doesn't work the way it is currently.

For example, the illustration with the XSLT template in the specification (aside being invalid because it misses the xsl:template root element) generates an HTML document without encoding information, so ISO-8859-1 by default (HTML4) and therefore not working in many cases.

Generating a proper HTML would require more work on the conversion side, or more information in the fs values themselves: Either the fs content should be able to generate a fully valid/working HTML from its values only, or we need expectations on what XLIFF element can be mapped too and limit the fs values to a sub-set of elements.

-ys


---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: 




---------------------------------------------------------------------
To unsubscribe, e-mail: 
For additional commands, e-mail: