Skip to content

feat: Georgian translation#149

Draft
SimModer wants to merge 20 commits into42bytes-team:masterfrom
SimModer:master
Draft

feat: Georgian translation#149
SimModer wants to merge 20 commits into42bytes-team:masterfrom
SimModer:master

Conversation

@SimModer
Copy link
Copy Markdown

@SimModer SimModer commented Aug 1, 2025

Georgian translation file, will be updated and completed in future

@SimModer SimModer changed the title Georgian Translation for warframe market feat: add georgian translation Oct 6, 2025
@SimModer SimModer changed the title feat: add georgian translation feat: Georgian translation Oct 10, 2025
@lonnstyle
Copy link
Copy Markdown
Member

@SimModer Hi! Please let me know if it is ready, for now I will convert his as a draft since I can see many of the lines are still not yet translated
Moreover, I would like to remind you:

  • geo is the language code in ISO 639-2, which is considered as deprecated, please use ka instead (correct me if I'm wrong)
  • please double check if Georgian characters can be displayed in game correctly, as currently the game does not support Georgian, which means the characters could be displayed as *****. if the game itself does not support, please don't translate the copy/paste messages

@lonnstyle lonnstyle marked this pull request as draft April 16, 2026 11:52
@SimModer
Copy link
Copy Markdown
Author

SimModer commented Apr 17, 2026

Hello, as checked in ISO 639 is considered geo/kat/ka but not sure how it's standardized but sometimes still used geo could continue with ka. As game doesn't support Georgian. For overall translation was thinking about finished it later + checked how it would work in live version. Or to leave as it is and hope somebody other will continue(with very little chance). Still mostly i am on version to withdraw and later with more courage and with fully finished version

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