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] R37: Revised Validations Module proposal

Hi Yves, all,

Yes, escaping the pipe would be a much simpler solution to the original proposal. However, I think parenthesis is a better solution because it rules out ambiguity. For example, the following are not the same:

mustLoc="World | Welt"
mustLoc=" World | Welt "

But I might think they are and the only difference between them is making the value more human readable. Whereas, the following is less ambiguous:

mustLoc="(World) (Welt)"
mustLoc="( World ) ( Welt )"

Other opinions are welcome, of course.


-----Original Message-----
From: xliff@lists.oasis-open.org [mailto:xliff@lists.oasis-open.org] On Behalf Of Yves Savourel
Sent: Wednesday, March 20, 2013 7:37 AM
To: xliff@lists.oasis-open.org
Subject: RE: [xliff] R37: Revised Validations Module proposal

Hi Ryan,

> We suggest that for mustLoc, we enclose the source and replacement 
> target values in parenthesis, like so: mustLoc="(World) (Welt)"
> If for any reason, a parenthesis is required to be translated, as a 
> brace for example, we could escape it like so:
> mustLoc="(\(World\)) ({Welt})" 
> Since we are generalizing the dblSpace to occurrences, then we could 
> do something similar there as well: occurrences="(|) (3)"
> For example, where 3 pipes need to occur in the target for whatever reason.

Wouldn't it be simpler if we were to escape '|' with '\':
That would be only less escaping to do.


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]