Wudooh icon indicating copy to clipboard operation
Wudooh copied to clipboard

Add Internationalization for Arabic and Farsi (Persian)

Open basshelal opened this issue 5 years ago • 4 comments

Add translations for the popup.html UI elements and for description.txt into:

  • Arabic
  • Persian
  • Urdu

basshelal avatar Jun 02 '19 09:06 basshelal

I can help with French and Arabic.

chiinau avatar Jun 09 '19 19:06 chiinau

@chiinau that's awesome! I still haven't figured out how to internationalize the UI elements in popup.html but I would greatly appreciate the description.txt. The UI elements aren't many anyway it's the description that requires a proper translation. Feel free to fork the repository and add the translations below the existing text in description.txt, this is the store listing's description. Many thanks :)

basshelal avatar Jun 09 '19 19:06 basshelal

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:

  • They are not supported by Chrome, such as Urdu
  • The language does not use Arabic script (see below note)

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.

basshelal avatar Aug 15 '19 21:08 basshelal

Is this issue still relevant? If so, I'd be happy to help with Persian.

AshkanArabim avatar Sep 29 '23 02:09 AshkanArabim