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

Fix Georgian localization #44

Merged
merged 1 commit into from
Nov 9, 2022
Merged

Fix Georgian localization #44

merged 1 commit into from
Nov 9, 2022

Conversation

mpkorstanje
Copy link
Contributor

@mpkorstanje mpkorstanje commented Nov 9, 2022

πŸ€” What's changed?

In cucumber/common#2041 only half a unicode glyph was pasted to create Მოαƒͺαƒ”αƒ›αƒ£αƒšαƒ˜αƒ . This half glyph breaks code generation in other projects, e.g:

https://github.com/cucumber/cucumber-jvm/actions/runs/3429109517/jobs/5714282373

This presumably (based on some searching) should have been მოαƒͺαƒ”αƒ›αƒ£αƒšαƒ˜αƒ.Though I don't speak Georgian. Please send another pull request if this is not correct.

πŸ“‹ Checklist:

  • I agree to respect and uphold the Cucumber Community Code of Conduct
  • I've changed the behaviour of the code
    • I have added/updated tests to cover my changes.
  • My change requires a change to the documentation.
    • I have updated the documentation accordingly.
  • Users should know about my change
    • I have added an entry to the "Unreleased" section of the CHANGELOG, linking to this pull request.

@mpkorstanje mpkorstanje force-pushed the fix-georgian-localisation branch from 1f5d8e9 to bbd7d0e Compare November 9, 2022 15:46
@mpkorstanje
Copy link
Contributor Author

@avsd Did I guess this translation correctly? ☝️

@mpkorstanje mpkorstanje marked this pull request as ready for review November 9, 2022 15:47
In cucumber/common#2041 only half a unicode glyph was
pasted to create `Მოαƒͺαƒ”αƒ›αƒ£αƒšαƒ˜αƒ `. This half glyph breaks code generation in other
projects, e.g:

https://github.com/cucumber/cucumber-jvm/actions/runs/3429109517/jobs/5714282373

This presumably (based on some searching) should have been `მოαƒͺαƒ”αƒ›αƒ£αƒšαƒ˜αƒ`.Though
I don't speak Georgian. Please send another pull request if this is not
correct.
@mpkorstanje mpkorstanje force-pushed the fix-georgian-localisation branch from bbd7d0e to eab7b34 Compare November 9, 2022 15:51
@mpkorstanje mpkorstanje merged commit 7d9d131 into main Nov 9, 2022
@mpkorstanje mpkorstanje deleted the fix-georgian-localisation branch November 9, 2022 15:53
@avsd
Copy link
Contributor

avsd commented Nov 9, 2022

@avsd Did I guess this translation correctly? ☝️

Visually it looks exactly the same! I'm wondering how could I have lost half a glyph :D - and how could it have been rendered correctly with half a glyph lost? Sorry for that!

@avsd
Copy link
Contributor

avsd commented Nov 9, 2022

@mpkorstanje, ok, I know the answer. It contained CAPITAL letter (not used in modern Georgian):

https://www.compart.com/en/unicode/U+1C9B

instead of a correct SMALL letter:

https://www.compart.com/en/unicode/U+10DB

Possible reason why it might have happened is capitalization, which is probably performed by some script when generating the files. If that's the case, it may happen again

image

@avsd
Copy link
Contributor

avsd commented Nov 9, 2022

ok, apparently it was introduced by me, during the very initial commit: cucumber/common@7054aa5

Maybe because I was using some unusual IDE (either Mac's TextEdit or GitHub's built-in editor) that did auto-capitalization after hitting "space". But the problem is that this incorrect "Georgian Capital Letter M" might have been spread to numerous repositories, all of them requiring a fix. What's the best way to do it, @mpkorstanje ?

@mpkorstanje
Copy link
Contributor Author

I don't think anything has to be done.

I've just extracted gherkin from the common repository. Which is why the fix happened here.

The mistake is duplicated in a few other repositories but those are subtrees of common. The mistake there isn't a problem because they're not part of any release.

What has been released will have a patch version to fix it.

@avsd
Copy link
Contributor

avsd commented Nov 9, 2022

Ok, good! :) In that case, here are two more locations this letter appeared: #45

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

Successfully merging this pull request may close these issues.

2 participants