Thegreatsuspender: Feature Request: Host strings that can be translated to an online localization platform.

[K0media]

• Extension version: 7.0.109
• Browser name & version: Chrome, 72.0.3626.121 (x64)
• Operating system & version: Windows 10, 17763.379

I think the data above isn't relevant for this request.

I'm a software translator and I'd like to contribute by translating the extension to Brazilian Portuguese. That's what I can help for now.

But I'm still surprised that many years have elapsed and I haven't seen a native translation of this meanwhile.

I usually get the list on AlternativeTo.net to suggest localization platforms. I'd like to advise either Crowdin (paid), which is the most famous and convenient one, or OneSky, which is free and fair to use.
But if you pick something else, I don't mind. I can go ahead and help anyway.

Check alternatives here: https://alternativeto.net/tag/software-localization/

I just can't translate it here right away without a proper consent and knowledge, because I'm not a programmer, but I'm used to work with online localization platforms.

[deanoemcke]

@K0media Thanks for this suggestion. You are correct that the technical hurdle of github might prevent some people from contributing. Although if you are just looking at providing a Brazilian Portuguese translation, it would be fairly simple. All you need to do is copy this file:

https://github.com/deanoemcke/thegreatsuspender/blob/master/src/_locales/en/messages.json

and change the english text into Brazilian Portuguese. You can simply paste your translated version as a comment into this issue if you want, and I can do the technical bit.

A Brazilian Portuguese translation would be great!

[K0media]

Okay, @deanoemcke, it's all done. I've just done, reviewed and revised everything to make sure it's fine.

To make it more convenient to be interpreted, I've made a new post on Pastebin. Down below I'll just list the paste link and some side-notes. (I'd like to comment on the .json file itself, but there's no convenient way to do that within the file. So I'll leave things here.)

Translated strings paste link:
https://pastebin.com/QTsx3K5n

• The Great Suspender label - I've translated the main extension name to something "convenient" in Portuguese, which it's done as well with mobile apps, some of them (at least). If you prefer to swap "O Grande Suspensor" (Portuguese) with the original name without translation, fine. Just tell me asap so I can fix it quickly.

• URL - This term, in specific is translated both to its original form (URL) and (link), which most of people know what is it. Tbh, a few days ago even my mom didn't know what the word "link" stood for, lmao (she's an elder, ofc)
  So I can keep it to URL or translate to "link" (there's a slight difference between male and female for both, URL is treated as female noun here and link is the inverse). Just tell me if it need adaptation.

• (to) whitelist - There are 2 forms to translate this noun/verb. One is "lista branca", which is the literal form, and "lista de permissões" (permission list). The problem here is about the length of words. "Lista branca" is smaller, and "lista de permissões" is bigger. If you prefer something more simple, fine. Just tell me again if it needs adaptation. I've just fixed everything by translating to "lista branca", to make it more simple.

• Line 121 ("html_options_suspend_on_low_memory_tooltip_line1":) - "This option IS will override Chrome's automatic tab discarding functionality." -> There's a typo here. Just fixed in Portuguese. Make sure you fix in English as well.

• Restoring window/tabs - Nvm, just found its context within the codes along.

• { "message": - This is important. I'm almost sure it shouldn't be translated, but I need to confirm first. Otherwise you could replace all those strings with "mensagem" (Portuguese) if you want. As simple as that. (Sorry, I've studied programming logic and played a bit with C++ back in college, but I've dropped out a long time ago.)

• tabs (guides/abas) - This is one of the main terms of the extension itself. That is, you can translate tabs (for browsers) in 2 ways: "abas" (which would literally stand for [browser] "tabs), and "guias" (as "guides", in literal form. Both makes sense in Portuguese, the number of characters is what matters here. However, Google made a point here to translate the "tabs" (English) into "guias", which is less convenient imho. I can change it later if you want.

• Line 148 ("html_recovery_disable_screen_capturing") -> Did you mean "to turn off" ("desligar", infinitive form as option) or just "turn it off" ("desligue")? I didn't see that dialog within the extension, so I'm a bit confused here. Please advise.

• Line 176 ("html_update_title":) - Update = verb or noun?

I think that's all for now. Thanks for everything. If I messed up with any parts of the code, sorry about that. I'm not perfect anyway. I've made everything up with the Windows notepad (LOL).

After the confirmations and fixes of the side-notes, you can push the newest update to public with no problems. 😉

PS: I wanted you guys to add a dark GUI for settings (the whitey theme burns my eyes), but that's a point for another topic. I'll see if there's an issue talking about that, otherwise I'll open one. But you may comment it here too, if you prefer.

[deanoemcke]

This is great work @K0media
I have created a pull request for this which we can make changes to: https://github.com/deanoemcke/thegreatsuspender/pull/900

If you would like to make changes but can't work out how to do that, then you can just add comments on the line you want to change, tell me what you want to change it to, and I'll do it for you.

[deanoemcke]

To address your comments:

The Great Suspender label - I've translated the main extension name to something "convenient" in Portuguese, which it's done as well with mobile apps, some of them (at least). If you prefer to swap "O Grande Suspensor" (Portuguese) with the original name without translation, fine. Just tell me asap so I can fix it quickly.

I will change it to simply "The Great Suspender". That way it is clear exactly which extension it is regardless of the locale. I have made this change already.

URL - This term, in specific is translated both to its original form (URL) and (link), which most of people know what is it. Tbh, a few days ago even my mom didn't know what the word "link" stood for, lmao (she's an elder, ofc)
So I can keep it to URL or translate to "link" (there's a slight difference between male and female for both, URL is treated as female noun here and link is the inverse). Just tell me if it need adaptation.

I trust your judgement here. Use whatever you think most people will understand.

(to) whitelist - There are 2 forms to translate this noun/verb. One is "lista branca", which is the literal form, and "lista de permissões" (permission list). The problem here is about the length of words. "Lista branca" is smaller, and "lista de permissões" is bigger. If you prefer something more simple, fine. Just tell me again if it needs adaptation. I've just fixed everything by translating to "lista branca", to make it more simple.

Once again, I trust you to use your judgement. If a literal translation doesn't make sense, then go with the other option.

Line 121 ("html_options_suspend_on_low_memory_tooltip_line1":) - "This option IS will override Chrome's automatic tab discarding functionality." -> There's a typo here. Just fixed in Portuguese. Make sure you fix in English as well.

Thanks. Somebody else has pointed this out and fixed it for me in another pull request.

{ "message": - This is important. I'm almost sure it shouldn't be translated, but I need to confirm first. Otherwise you could replace all those strings with "mensagem" (Portuguese) if you want. As simple as that. (Sorry, I've studied programming logic and played a bit with C++ back in college, but I've dropped out a long time ago.)

Correct. This should not be translated.

tabs (guides/abas) - This is one of the main terms of the extension itself. That is, you can translate tabs (for browsers) in 2 ways: "abas" (which would literally stand for [browser] "tabs), and "guias" (as "guides", in literal form. Both makes sense in Portuguese, the number of characters is what matters here. However, Google made a point here to translate the "tabs" (English) into "guias", which is less convenient imho. I can change it later if you want.

Use the one that makes sense to you. By "Google made a point here to translate.." do you mean Google translate? I wouldn't trust that. Or do you mean that the actual Google Chrome browser refers to tabs as "guias"? If this is the case (the second option) then I'm not sure what is best to do?

Line 148 ("html_recovery_disable_screen_capturing") -> Did you mean "to turn off" ("desligar", infinitive form as option) or just "turn it off" ("desligue")? I didn't see that dialog within the extension, so I'm a bit confused here. Please advise.

It means "turn it off". Is on a screen that almost never shows.

Line 176 ("html_update_title":) - Update = verb or noun?

Noun

Let me know if there's anything else that needs to be changed based on my answers.

[deanoemcke]

Oh, one more very important question @K0media :
Can I get away with also using this translation for Portuguese (Portugal) ?

[K0media]

Sorry for the late reply. I've been off on this weekend.

Okay, @deanoemcke, it's all set. Everything was commented as you've suggested before.

At this time, to make it (a bit) better for me, I've used Notepad++.

Worked nicely here, but in the end I'll put a final quote.

In case you prefer a raw paste, I've made a new paste on Pastebin so you can copypasta the entire code.
Link: https://pastebin.com/1XK16kS5

Everything was linked to #900, so you can check the comments there.

I could put each exact lines here, but I kept that for my own control. I can report that later if you want me to.

Now to some points.

To address your comments:
[...]
I will change it to simply "The Great Suspender". That way it is clear exactly which extension it is regardless of the locale. I have made this change already.

So I did all the changes to adapt to the original context. Everything seems right now. You can check there if you want.

[...]
I trust your judgement here. Use whatever you think most people will understand.

So, about the "URL" term, I've decided it's better to keep it that way. Although I did some adaptations to some typos that were already in there.

[...]
Once again, I trust you to use your judgement. If a literal translation doesn't make sense, then go with the other option.

I also kept the concept of "whitelist" to literal translation ("lista branca"), it looks shorter, but also comprehensible.

[...]
Correct. This should not be translated.

Fine.

[...]
Use the one that makes sense to you. By "Google made a point here to translate.." do you mean Google translate? I wouldn't trust that. Or do you mean that the actual Google Chrome browser refers to tabs as "guias"? If this is the case (the second option) then I'm not sure what is best to do?

Okay, I guess I missed the language expression here (my English isn't perfect 😅). By "Google made a point here to translate.." I meant that they wanted to translate that on purpose. So instead of "abas" it remains as "guias" for "tabs". Anyway, not a big difference here. But I double checked it to make sure every context looks fine accordingly.

[...]
It means "turn it off". Is on a screen that almost never shows.

Kept it as "desligue" (noun). Although I wanted to see that in action just to make sure if that's correct or not. But it doesn't matter very much. If it's necessary, I'll change that in future.

Line 176 ("html_update_title":) - Update = verb or noun?
Noun

Okay, done.

And about your next reply...

Oh, one more very important question @K0media :
Can I get away with also using this translation for Portuguese (Portugal) ?

Well, you can. There's an app I'm translating that the strings that were translated into PT-BR were also copied to PT-PT. However, you should imagine the same scenario as US English is not equal to UK English. Some things change, but for translation purposes, you can keep overall terms for this.
It's all up to you, but if you want something very precise, I guess some guy from Portugal should show up to correct and adapt several things to Portugal's Portuguese if needed.

...but in the end I'll put a final quote.

Okay, so about this... It wasn't such an easy task for me to get all the context and translate everything I could. Luckily I remembered NP++ so it eased this job, saving me a lot of time.
However, it could be way faster if the strings of interest were hosted on a web localization platform.

So please, next time you want to someone to help with localization, consider hosting the strings on a web based translation platform. That's really handy for global purposes. It's not everyone that has enough knowledge to help translating software like this because of some contexts.

Crowdin is by far the best platform I've used so far, but people complain about the pricing. So OneSky and WebLate have free subscriptions for small projects, which means you can host the strings there without paying a single penny.

WebLate's UI is really confusing, but it's better than nothing. OneSky is fair enough for reasonable tasks.

Oh well, it's all up to you. But don't forget to consider this last point.

Everything is ready to be pushed in live now. You can revise the contexts just to make sure if everything works correctly, so you report back here. I'll keep an eye on the issues and commits. 👍🏻

All of best and take care. 😉

[deanoemcke]

Thanks so much @K0media . You're a legend!
Point taken about the web based translation platform. I'll keep this issue open to retain visibility of this suggestion.

[K0media]

Excuse me @deanoemcke, it's been almost a month since this was completed and I didn't see new updates yet. Is there anything wrong or you're getting it all together with other bug fixes to release in a single big update?