OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

xliff-inline message

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


Subject: Re: [xliff-inline] Storing native data


> Cons:
>
> - preserving whitespaces may require some efforts
One potential way we could deal with this would be to require that any 
significant white space be prefixed with a back slash, just as is done 
in path names in Unix, i.e., “\”. This would require that a true 
backslash be represented as “\\”. This sort of escaping (particularly of 
spaces and backslashes) is well known and understood, and it would allow 
multiple spaces to be included unambiguously, e.g., “\ \ \ \ #AD23” 
(starting with four spaces). It would mean a certain amount of 
processing would be required, but it would not be unreasonable and it 
would solve the problem.

-Arle



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