Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Compare ellipses character #655

Open
digocesar opened this issue Aug 27, 2024 · 3 comments
Open

Compare ellipses character #655

digocesar opened this issue Aug 27, 2024 · 3 comments

Comments

@digocesar
Copy link

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.

@tom-englert
Copy link
Collaborator

tom-englert commented Aug 27, 2024

I don't think the ellipsis ligature is unique to Polish, you should just use it everywhere

@digocesar
Copy link
Author

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.

@tom-englert
Copy link
Collaborator

tom-englert commented Aug 28, 2024

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants