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

Turkish localization 🇹🇷 #1809

Open
bitigchi opened this issue Mar 22, 2021 · 9 comments
Open

Turkish localization 🇹🇷 #1809

bitigchi opened this issue Mar 22, 2021 · 9 comments
Assignees
Labels
community i18n Internationalization

Comments

@bitigchi
Copy link

Greetings!

I would like start working on the Turkish localisation. Excited to be able to directly contribute to my (hopefully) future communications device!

I noticed that some of the Turkish letters are not yet supported in the current character set, after finishing the localisation, I hope to take a shot at that too.

@bitigchi bitigchi added i18n Internationalization community labels Mar 22, 2021
@wojtekidd
Copy link
Contributor

Thanks so much! On my side I'll do some research regarding Turkish characters and will keep you updated in this ticket as soon as I'll find anything 👍🏻

@bitigchi
Copy link
Author

I have noticed that some of the lines require a newline tag. How many characters can we fit into a single line for these cases?

@wojtekidd
Copy link
Contributor

👋🏻
The good news is that our current font will support Turkish characters. Please confirm that these are the only ones that are missing when comparing to the current characters list: Ğ, ğ, Ş, ş?

Please use the <br></br> as your new line tag - it should work OK.

@bitigchi
Copy link
Author

Also ı İ. Also having the Turkish Lira sign would be nice .

Thanks for the info, I'm afraid I couldn't explain it properly. I assume that since in some screens newline is needed, I need to cut the line at around 35-40 characters I guess? I just don't want it to look awful by mistake :).

@wojtekidd
Copy link
Contributor

Actually, I was mistaken :) Please use the \n - here's an example from English.json

"app_settings_bluetooth_searching_devices": "Searching devices... \nIt may take a moment."

@bitigchi
Copy link
Author

bitigchi commented Mar 24, 2021

Thanks for your reply.

Does the local QuickStart work on macOS as well? What would you suggest for the easiest set-up? I am done with the translations, and I would like to test them before opening a pull request.

Okay, I tried building the thing on a Linux installation, stumbled upon following errors:

  • Cannot clone most of the submodules, just giving an error that it was not found
  • Could not configure, says that -static-libasan is not found

@wojtekidd
Copy link
Contributor

Sorry to hear this - please let me know which submodule was that exactly? I'll see how I can help you!

@bitigchi
Copy link
Author

Hi. I am in the middle of a move right now, and I don't have access to that particular machine, but I'll try to update you as soon as I can.

@wojtekidd wojtekidd linked a pull request Mar 31, 2021 that will close this issue
@wojtekidd
Copy link
Contributor

Here's an important message about the improvements in localization processes that came out thanks to your attention to detail - please make sure that you acknowledge these changes before continuing your work. Thank you!

@wojtekidd wojtekidd removed their assignment Dec 22, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
community i18n Internationalization
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants