You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resolve#185.
Resolve#187.
Add new `charactersEscapedInAttributes` and `charactersEscapedInElements` properties on `XMLEncoder` that allow customizing how certain characters are escaped.
Hi @owenzhao, thanks for reporting this. With the new API in master you can do something like encoder.charactersEscapedInAttributes += [("\n", " ")] to make it work for your case.
ResolveCoreOffice#185.
ResolveCoreOffice#187.
Add new `charactersEscapedInAttributes` and `charactersEscapedInElements` properties on `XMLEncoder` that allow customizing how certain characters are escaped.
In xliff exported by Xcode, is a replacement for \n. However, when decoded and encoded by XMLCoder, the is replaced by a hard line break
original by Xcode
decoded and encoded by XMLEncoder
However, the latter is then not accepted by Xcode as a valid translation.
My Question
Should I think this as a bug of XMLCoder or something that I should deal with in my own app?
The text was updated successfully, but these errors were encountered: