Closed MKoen closed 5 years ago
@8BitPit also I can translate to Urdu (English letters tho)
I'd be willing to contribute with a Swedish translation if need be.
@MKoen, @587saboor & @Montell2099 thank you. I did not setup any Translation management system for Niagara yet, but I will.
I'd be willing to help with the German translation.
Whoops, accidentallyclosed this issue. Reopening it...
@MKoen lol
I'd be willing to help with the Czech translation.
Hello, I'd be willing to help with the French translation.
Hi, I'd love to help with the Polish translation.
I can help with Spanish translation
I could do a pull request looking into this, I'd just need to know how it should be implemented, as how would the dev like translations to work.
I can help with Italian translation
@MKoen Count me in for European Portuguese (pt-pt) translation.
I'd like to help translating into Catalan; Spanish too if needed :)
Love the app -- I can help translate into Chinese (simplified and traditional, zh-CN and zh-HK respectively).
I can help with Spanish translation if needed
Hello, Simplified Chinese translator here!
I can work on the Finnish translation
Hi, I can help with Brazilian Portuguese translation!
Hi, I can do Hindi (hi-IN) translation.
Hi I can help with Turkish translation.
Thanks a lot for volunteering everyone. I’m almost done with settings up the translation management system :) The service is called Crowdin and you can also log in with your GitHub account: I tried my best to provide helpful context (documentation & screenshots) for every string, please take a look: https://crowdin.com/project/niagara-launcher
Hi, I can help with Russian translation.
@8bitPit please increase the char limit, it's now set to 200 but some strings to translate are already bigger then 200.
@MKoen Sorry, I didn't know that Crowdin also takes the length of xml tags into account. Should be fixed now.
@disacrol good thought. For button labels I set the char limit to 20 chars, so "Adicionar favoritos" would barely fit (19 chars). I agree, just "Adicionar" would also work in that case. I will do some testing today, to better estimate char limits. Sometimes the UI wouldn't be broken, but I believe button labels longer than 20 chars wont look appealing to the user.
I deleted my post hoping it would be unnoticed, I missed the "CHAR_LIMIT" annotation in the end, I was looking at the number of chars of the original, my bad. I'll keep "Adicionar favoritos" for now.
Hello, I don't understand a thing. Currently, I am making a Turkish translation and I don't know which order should I put the %1$s sign into the translation. Like should I put it in order or should it be the same as in the English version? For example, should I use the exact values for exact buttons( such as using %1$s for the word Agree and continue, or should I write it in order as I write the translation? I am asking this because the order of the words can change due to languages differences between Turkish and English.
On Sun, Dec 9, 2018 at 2:54 PM disacrol notifications@github.com wrote:
I deleted my post hoping it would be unnoticed, I missed the "CHAR_LIMIT" annotation in the end, I was looking at the number of chars of the original, my bad. I'll keep "Adicionar favoritos" for now.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/8bitPit/Niagara-Issues/issues/254#issuecomment-445530952, or mute the thread https://github.com/notifications/unsubscribe-auth/Ab5BR2a_fCEEZIHaeohGbn-RhKLVpO6vks5u3PnZgaJpZM4WzikZ .
Nothing between <xliff:g and </xliff:g> should be translated. Other than that, you can and should adapt the text around it - before <xliff:g and after </xliff:g> - according to your language. In my case, I also had to handle that specific string, because "Tap Agree and continue to agree to Niagara Launcher's Privacy policy and Terms of Service" in Portuguese had to be rephrased as something like "Tap Agree and continue to agree to the Privacy policy and Terms of Service of Niagara Launcher".
Can I translate to Lithuanian?
I would make the Hungarian translation
@Vv2233Bb sry for my late reply, added Lithuanian.
@pvojnisek I think translating into Hungary should already be possible.
Finnish translation is 100% done
Thanks a lot @koenek :)
I can help translate to Tamil.
thx @purushothamn
I'll close this issue, but feel free to comment if you want to translate Niagara in a language which isn't available yer. Thank you everyone for helping!
I'd love to help translate to Norwegian.
Thank you very much @Gauteweb :) Here's how you can participate: https://help.niagaralauncher.app/article/80-help-translate
Thank you very much @Gauteweb :) Here's how you can participate: https://help.niagaralauncher.app/article/80-help-translate
OK, so this is strange. Norwegian is marked as 100% finished, but Niagara is in english on my device (Oneplus Nord 2 5G). I have systems settings to Norwegian Bokmål (we have two written languages, "bokmål" and "nynorsk").
@Gauteweb oh, thanks for reporting. Do the translations show up if you switch to Nynorsk?
@Gauteweb oh, thanks for reporting. Do the translations show up if you switch to Nynorsk?
That is not an option on my phone, only Bokmål.
Oh okay. I can select to both written languages but I it doesn't apply the translations either. I think I have found the culprit, there are several ways to categorize Norwegian strings: https://stackoverflow.com/questions/5153674/android-localization-question/5155857. . I'll fix this with the next update; thanks again for pointing it out @Gauteweb!
A big part of the settings and the notification window are hard coded in English.
Please make this support the user's native language.
Since I'm from Belgium, I'd love to translate the app to Dutch. Just give me a list of the stuff that needs to be translated, and it'll be done in no time.
Current translation volunteers: