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] Issues

Yes. Absolutely. That's exactly what I had in mind. It helps to enforce what I think of as two important design goals  we've talked about.

1. The fs attribute is for hints about formatting a just-in-time, in context HTML review. It MUST not be used as a devise to prescribe a round trip.

2. The fs attribute should be simple, and comprehensible by a human. (this is subjective for sure, but I think a reasonable design goal).

I think limiting the fs to a single HTML element will prevent really ugly overloading, like trying to escape an entire complex table into a single fs attribute. Elements with content would be an even worse abuse of the design goals.
From: xliff@lists.oasis-open.org [xliff@lists.oasis-open.org] on behalf of Yves Savourel [ysavourel@enlaso.com]
Sent: Friday, April 12, 2013 1:03 PM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] Issues

> I'll take it even further, what value does the "<"
> and the ">" add? It is clear in the spec that we're
> talking about HTML elements.
> Why not fs="img src='smileface.png'" ?

With that notation you would lose the capability to set several elements, or elements with content.
Not sure if this is something you wish to have or not.


To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail.  Follow this link to all your TCs in OASIS at:

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