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
Some languages, such as Polish, do not usually use the ellipsis with 3 dots character (...), they use 1 character that represents the ellipsis (… or \u2026).
It would be good if ResxManager validated both types of ellipsis as being equal.
The text was updated successfully, but these errors were encountered:
It's possible that it exists in other languages. I saw this in a Polish translation that a customer sent me.
ResxManager started reporting translation differences because the sentences were ending with different characters.
It would be nice if this character was accepted as three dots.
A ligature is a typographic element, not a language element, so it does not exist "in a language", and I would consider not using it everywhere a bug, and I'm not a friend of introducing features that make it easier to ignore bugs…
I would rather disable the punctuation check for this row if you don't want to fix it.
Some languages, such as Polish, do not usually use the ellipsis with 3 dots character (...), they use 1 character that represents the ellipsis (… or \u2026).
It would be good if ResxManager validated both types of ellipsis as being equal.
The text was updated successfully, but these errors were encountered: