xliff-inline — archive

[Arle Lommel]

> 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