RE: [xliff] R37: Revised Validations Module proposal

From
Ryan King <>
Date
2013-03-20T06:41:40+00:00
ID
Thread
RE: [xliff] R37: Revised Validations Module proposal
Hi Yves, all,

 

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.

 

Further comments or suggestions welcome.

 

-----Original Message-----

From: Ryan King 

Sent: Tuesday, March 19, 2013 10:59 PM

To: 'Yves Savourel'; 

Subject: RE: [xliff] R37: Revised Validations Module proposal

 

Thanks Yves for the feedback. All valid and good comments, which we will incorporate into the spec. As for the question on the mustLoc separator, Kevin and I are discussing it and suggest something shortly.

 

Thanks,

ryan

 

-----Original Message-----

From:  [mailto:]
 On Behalf Of Yves Savourel

Sent: Tuesday, March 19, 2013 5:01 AM

To: 

Subject: RE: [xliff] R37: Revised Validations Module proposal

 

Hi Ryan, all,

 

Some feedback on the Validation proposal (nothing major, just possible suggestions):

 

 

-- strbegins and strEnds attributes:

 

Maybe names such as startsWith and endsWith may be a bit more descriptive of the function?

 

 

-- dblSpace:

 

This seems to be a very specific check. Maybe it can be generalized a bit without making it very different? For example, instead of dblSpace="3" we could do occurrence="  |3" (or a better name than 'occurrence'). This would allow to
 check for more than double spaces.

 

 

-- mustLoc:

 

How do you represent the '|' if it needs to be in the left part of the value?

 

 

-- existsInSource, disabled:

 

So far I think XLIFF is using yes|no for Boolean rather than true|false. Maybe we could be consistent?

 

 

cheers,

-yves

 

 

---------------------------------------------------------------------

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:

https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php