RE: [xliff] Online validation for XLIFF

["Yoshito Umaoka" <yoshito_umaoka@us.ibm.com>]

Rodolfo,

Thank you for your quick response.

> Section "4.2.2.12 source" says that <source> contains
text and may 
> contain other optional stuff.  It does not say that text content
is 
> also optional.
> 

I saw the explanation. It's not really
clear to me that "text" here explicitly excludes "empty
text".

> The specification generally
indicates that something is optional 
> when it is optional, but this is not done in a consistent way. This
> is something that certainly needs review.

For clarity, for this case, we should
probably explicitly specify text must not be empty (length > 0).
However, I think it should allow
empty value for <source> and <target> for the reason below:

> 
> OpenXLIFF treats empty source elements as error because that would
> be a a useless element in most cases. Do you have a good use case
> for an empty <source>?
> 

We often see prefix/suffix on UI
text might be empty in a language, while non-empty value is used in another
language.
In our case, we use Okapi XLIFF toolkit
and it does not invalidate the case.

-Yoshito