-
-
Notifications
You must be signed in to change notification settings - Fork 8
Add Internationalization for Arabic and Farsi (Persian) #3
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
Comments
I can help with French and Arabic. |
@chiinau that's awesome! |
The only currently relevant languages are Arabic, Farsi (Persian) and Urdu, others are much less relevant (see below why). Chrome only supports Arabic and Farsi and doesn't support Urdu (for some stupid fucking reason) so we only need full i18n for those 2 languages, that includes store listings as well as UI elements. I'll try and do Arabic myself, I'll attempt to do as much Farsi as I can (I know very little Farsi) using whatever free tools I have but I will need someone to check it over. This will be done when the new update I'm working on (probably called 2.0 because it's huge) is finished and the marketing materials and finishing touches are being done. Other languages are not necessary because either:
Non Arabic script languages do not matter to us right now because the target audience will be people who can actually read an Arabic script language (duh lol). So German is irrelevant to us (for now) because if a German speaking person will use the extension they will usually be using it for an Arabic written language like Arabic or Farsi, so if they can't use English they'll use their Arabic script language. This is a huge simplification obviously and not having certain languages prevents the extension from being listed on the chrome store of those languages (as far as I know), which is why we want to do this eventually, at least for languages with large numbers of Arabic script using people such as Turkish, German, French and Swedish. Luckily though English covers the vast majority anyway. Anyway TL;DR is we need i18n only for Arabic and Farsi for now until we decide later to add some of the other popular languages. |
Is this issue still relevant? If so, I'd be happy to help with Persian. |
Add translations for the
popup.html
UI elements and fordescription.txt
into:The text was updated successfully, but these errors were encountered: