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

Localization #180

Open
jobbautista9 opened this issue Jul 10, 2021 · 5 comments
Open

Localization #180

jobbautista9 opened this issue Jul 10, 2021 · 5 comments
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jobbautista9
Copy link

We did a quick text replace on the locale files, but a lot of the links in those files no longer point to working URLs due to the text replace. Some URLs didn't change, but I don't think we should rely on Audacity for localization, because eventually our features will drift off upstream. We should form our own translation teams that will be there to maintain our locales.

Unfortunately I don't speak any of the languages currently localized, but I do speak Tagalog, and I plan on writing a fresh translation for Tagalog. Should take like a week or two to translate all of those 19800+ lines...

Also, someone suggested in the Tenacity fork (tenacityteam/tenacity#145) to add an en locale file. I think this would be a good idea to pursue, to make it easier to work with code by separating logic from content. Another suggestion (tenacityteam/tenacity#125) is to use a web-based software localization tool to make it easier for translators to create and edit translations. We can use Weblate or Mozilla Pontoon for this. Both of them are free software.

@EinBaum
Copy link

EinBaum commented Jul 10, 2021

I volunteer to fix the German and Russian translations (if anything is missing)

@ImGonnaChuck
Copy link
Contributor

Honestly I guarantee you 99.9% of ESL people who find this project will know enough English to get around. The problem might be if they happen to have the OS in their native laguage. In that case it might be better to ask the user what language to use. Translating the documentation isn't very important either IMO, but it doesn't hurt to keep local copies of the pre existing stuff of course.

@Sneedfan115
Copy link

I volunteer to fix the German and Russian translations (if anything is missing)

Look at the translator pulling up with his fancy German tongue

@sneedcat sneedcat added documentation Improvements or additions to documentation enhancement New feature or request labels Jul 10, 2021
@EinBaum
Copy link

EinBaum commented Jul 10, 2021

I volunteer to fix the German and Russian translations (if anything is missing)

Look at the translator pulling up with his fancy German tongue

guatemalan dialect

@comradekingu
Copy link

comradekingu commented Jul 18, 2021

https://hosted.weblate.org/projects/tenacity/ is already on Weblate, the far superior offering.
Using that instance allows sharing the translation memory and not duplicating effort.

@ChucksConsulting Part of the point is to have more eyeballs on the source strings, which in turn improves the stringbase for everyone.

@jobbautista9 Edit: If https://github.com/tenacityteam/tenacity/discussions/382 is indicative of things to come, relying on Tenacity is not an option. I'll invite some translators if you get it set up on https://hosted.weblate.org/hosting/ (no cost).

@ImGonnaChuck ImGonnaChuck added this to the Ongoing maintenance milestone Mar 26, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

6 participants