795661 - Farsi Locale for Fennec is very incomplete

Status: RESOLVED FIXED

(Mozilla Localizations :: fa / Persian, defect)

Description

[Sina Momken]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:14.0) Gecko/20100101 Firefox/14.0.1
Build ID: 20120713134347

Steps to reproduce:

I've made a multi-locale Fennec to compare localization of Fennec in various languages with the help of instructions in https://wiki.mozilla.org/Mobile/Fennec/Android.
however After changing my android language (in this case CM7 language) to Persian, I saw that a lot of UI and settings texts are not translated to Farsi yet.


Actual results:

As you can see in the first and second attachment many UI and settings components have not yet translated to Farsi for fennec and the only visible translated part is translation of button "more" to "بیشتر".


Expected results:

If you compare Farsi locale to some other popular locale (Deutsch for example) you can see that Farsi locale for Fennec is very incomplete and stale.
I've attached Deutsch locale menus to exemplify how complete a locale can be.

Comment 1

[Sina Momken]

Attachment: UI components of Fennec in Farsi Locale (only "more" is translated)

As you can see only "more" is translated to "بیشتر" nothing more

Comment 2

[Sina Momken]

Attachment: Settings activity in Fennec for Farsi Locale (completely untranslated)

As you can see nothing in Settings activity is translated to Farsi for Fennec!

Comment 3

[Sina Momken]

Attachment: UI components of Fennec in Deutsch Locale (completely translated) for comparison

I've uploaded this screenshot for comparison.
You can see that Deutsch locale is almost completely translated.

Comment 4

[(no longer active)]

Fennec was never actively localized into Persian.  It would be great if you could help with this.  :-)

Comment 5

[Sina Momken]

I'm working on Fa localization for Fennec. I'll attach my patch here, when they're ready.

Comment 6

[Sina Momken]

Dear Ehsan and other Mozilla devs
I'm sorry for my delay in delivering the patch I'd made before. I was changing my ISP and had not access to internet. After that I got busy for another personal issue and had not time to continue this issue. I'll update my patch here just right now.

Comment 7

[Sina Momken]

Attachment: Partial patch for adding new tags to files in /mobile/android/chrome and /mobile/android/base

This is my not very complete patch in which I tried to add new tags to files in "/mobile/android/chrome" and "/mobile/android/base" for repository "http://hg.mozilla.org/l10n-central/fa"

Comment 8

[Sina Momken]

Since I'm getting more busy I've uploaded my not very complete patch here, because I may become unable to continue this patch to its ideal position. Additionally because of my lake of time I could not port my changes from "l10n-central/fa" repository back to "releases/l10n/mozilla-aurora" repo. I think the mobile the section of both repositories must be same, so Pike can simply copy my changes back to releases/l10n/mozilla-aurora.
In case of any question I'm online. Feel free to ask them just here under this comment.

Comment 9

[(no longer active)]

Comment on attachment 677713 [details] [diff] [review]
Partial patch for adding new tags to files in /mobile/android/chrome and /mobile/android/base

Review of attachment 677713 [details] [diff] [review]:
-----------------------------------------------------------------

Thanks a lot, Sina, this is great, and extremely high quality!  I have a few comments which caught my eyes.  If you attach a new version of the patch which addresses these, I'd be happy to commit it for you.

::: mobile/android/base/android_strings.dtd
@@ +6,5 @@
> +<!ENTITY  splash_settingup "راه‌اندازی &brandShortName; شما">
> +<!ENTITY  splash_bookmarks_history "ما در حال به‌هنگام‌سازی نشانک‌ها و تاریخچهٔ شما هستیم که ممکن است حدود یک دقیقه طول بکشد.">
> +
> +<!ENTITY  no_space_to_start_error "فضای کافی به منظور شروع برای &brandShortName; دردسترس نیست.">
> +<!ENTITY  error_loading_file "یک خطا در حال تلاش برای بارگذاری فایل‌های مورد نیاز برای اجرای &brandShortName; رخ داد.">

Try using پرونده for consistency with desktop Firefox.

::: mobile/android/base/sync_strings.dtd
@@ +13,5 @@
> +<!ENTITY sync.title.adddevice.label 'اضافه کردن یک حساب &syncBrand.fullName.label;'>
> +<!ENTITY sync.title.pair.label 'جفت کردن یک دستگاه'>
> +
> +<!-- J-PAKE Key Screen -->
> +<!ENTITY sync.subtitle.connect.label 'برای فعالسازی دستگاه جدید خود، «انجام &syncBrand.shortName.label;» را روی آن دستگاه انتخاب کنید.'>

فعال‌سازی

(there are other occurrences of this as well...)

::: mobile/android/chrome/aboutAddons.dtd
@@ +2,5 @@
> +   - License, v. 2.0. If a copy of the MPL was not distributed with this
> +   - file, You can obtain one at http://mozilla.org/MPL/2.0/. -->
> +
> +<!ENTITY aboutAddons.title2                     "افزودنی‌ها">
> +<!ENTITY aboutAddons.header2                    "افزودنی‌های تو">

شما would probably be a better choice :-)

(there are other instances of this as well.)

::: mobile/android/chrome/aboutAddons.properties
@@ +9,5 @@
> +addonAction.options=اختیارات
> +
> +addonsSearchEngine.description=جستجوی یکپارچه
> +
> +addonType.extension=بسط

We call this ضمیمه in desktop Firefox.

not that I personally think either of the names are particularly better than the other... :(

@@ +10,5 @@
> +
> +addonsSearchEngine.description=جستجوی یکپارچه
> +
> +addonType.extension=بسط
> +addonType.theme=پوسته

تم

@@ +11,5 @@
> +addonsSearchEngine.description=جستجوی یکپارچه
> +
> +addonType.extension=بسط
> +addonType.theme=پوسته
> +addonType.locale=محل

زبان

@@ +12,5 @@
> +
> +addonType.extension=بسط
> +addonType.theme=پوسته
> +addonType.locale=محل
> +addonType.search=جستجو

جست‌وجو

Comment 10

[Sina Momken]

Hello dear Ehsan
Thank you for your review and notes. I couldn't find some exact translations of some phrases in desktop version, like extension and etc and in some rare cases I had to put my own translations.
But I think some of your previous translations are completely incorrect. For example:
1- theme -> تم: It's not accepted at all.
2- Cancel -> انصراف: Why didn't you used the shorter term لغو?
3- locale -> زبان: The exact translation of زبان is language. As long as I realized in dictionaries locale means something with combinations of language and the region that language is used in. For example Fa-Iran and Fa-Afghanistan are both locales but Fa is only a language. I know the meaning of locale in mozilla usages is more something like language but I guess that word is not exact.

In the case of any other mistranslations, I'm glad to hear them.
I'll apply the changes you described above and make another patch, although I don't agree completely with you about them. In lieu please tell me clearly whether you've applied or have plans to apply my patch or not.

Comment 11

[(no longer active)]

(In reply to Sina Momken from comment #10)
> Hello dear Ehsan
> Thank you for your review and notes. I couldn't find some exact translations
> of some phrases in desktop version, like extension and etc and in some rare
> cases I had to put my own translations.

Please feel free to ask me if you need help with answering these kinds of questions in the future.  :-)

> But I think some of your previous translations are completely incorrect. For
> example:
> 1- theme -> تم: It's not accepted at all.

This predates me.  :-)

> 2- Cancel -> انصراف: Why didn't you used the shorter term لغو?

No particular reason...

> 3- locale -> زبان: The exact translation of زبان is language. As long as I
> realized in dictionaries locale means something with combinations of
> language and the region that language is used in. For example Fa-Iran and
> Fa-Afghanistan are both locales but Fa is only a language. I know the
> meaning of locale in mozilla usages is more something like language but I
> guess that word is not exact.

"Locale" as used in software terminology doesn't really have a good translation in Persian as far as I know.  In the case of Firefox UI, it mostly means "language", even though the distinction that you mention above is accurate.  I can't think of a term which encapsulates both "language", and "regional conventions", but محل doesn't really do it, and it diverts attention from the "language" side of the term's meaning.

> In the case of any other mistranslations, I'm glad to hear them.

I am not that pedantic about the exact terms being used.  If you can think of better terms, by all means please use them (پوسته is a good choice, for example).  But I do think that consistency matters a lot, so if you're thinking of a new term to use on mobile, please change it everywhere.

> I'll apply the changes you described above and make another patch, although
> I don't agree completely with you about them. In lieu please tell me clearly
> whether you've applied or have plans to apply my patch or not.

If it's easier for you to work on the fixes on top of your existing patch, and you don't use mq, I can commit this patch as it is.  Otherwise I'd like to hold on until you have the final version of the patch.  (I haven't committed anything yet.)  If you want me to go ahead and commit this version of the patch please just let me know.

Thanks!

Comment 12

[Sina Momken]

First of all I'm eager to know how you could quote my sentences. I don't know how, but I think it's very helpful and can clear my answers to your replies.

Second, about answering this kind of questions: Actually I had many of this questions but this is not a good solution to ask you whether I need. It's time consuming and with many delays. The best solution for this problem is making a glossary or set of <en,fa> translations.

Third, about cancel=انصراف->لغو: In many other Persian software I saw لغو much more frequent than انصراف. Bot terms are correct but لغو is shorter and therefor easier to write, read and listen.

Fourth, I agree with you that translation consistency is more important. But consider that someday we should change existing translations to better ones. But I agree that we should do it in a comprehensive systematic way. The best solution for this is using a glossary in combination with a phrase replacement system among multiple files (with capability of asking at time of replacement). I don't know such a system just right now and so I must make it myself using python or perl. But I don't know that programming languages and this process takes some time, so temporarily I'll apply your corrections to my patch and upload its second version. I'll file a new bug report regarding this in the future.

Fifth, I use mq, but my main concern is that someone else may change the tree in the future and it may cause some time-consuming conflicts for me. hence using little incremental commits seems more reasonable. So please commit my next patch (i.e. revised version of previous patch) which I'll upload in the next comment.

Comment 13

[Sina Momken]

Attachment: Partial patch v2 for adding new tags to files in /mobile/android/chrome and /mobile/android/base (checked in)

This is my not very complete patch in which I tried to add new tags to files in "/mobile/android/chrome" and "/mobile/android/base" for repository "http://hg.mozilla.org/l10n-central/fa". Plus I mentioned corrections of Ehsan Akhgari in comment #9.

Comment 14

[(no longer active)]

(In reply to Sina Momken from comment #12)
> First of all I'm eager to know how you could quote my sentences. I don't
> know how, but I think it's very helpful and can clear my answers to your
> replies.

Click on "reply" next to the number of the comment.

> Second, about answering this kind of questions: Actually I had many of this
> questions but this is not a good solution to ask you whether I need. It's
> time consuming and with many delays. The best solution for this problem is
> making a glossary or set of <en,fa> translations.

I agree.  I never had the time to do that, but it would be great if you can do it.  :-)

> Third, about cancel=انصراف->لغو: In many other Persian software I saw لغو
> much more frequent than انصراف. Bot terms are correct but لغو is shorter and
> therefor easier to write, read and listen.

That's fine by me.

> Fourth, I agree with you that translation consistency is more important. But
> consider that someday we should change existing translations to better ones.
> But I agree that we should do it in a comprehensive systematic way. The best
> solution for this is using a glossary in combination with a phrase
> replacement system among multiple files (with capability of asking at time
> of replacement). I don't know such a system just right now and so I must
> make it myself using python or perl. But I don't know that programming
> languages and this process takes some time, so temporarily I'll apply your
> corrections to my patch and upload its second version. I'll file a new bug
> report regarding this in the future.

Makes sense.  We don't need to solve all problems now.  :-)

> Fifth, I use mq, but my main concern is that someone else may change the
> tree in the future and it may cause some time-consuming conflicts for me.
> hence using little incremental commits seems more reasonable. So please
> commit my next patch (i.e. revised version of previous patch) which I'll
> upload in the next comment.

Nobody else is working on the persian translation for now, but I'll go ahead and commit your patch.

Comment 15

[(no longer active)]

Comment on attachment 677861 [details] [diff] [review]
Partial patch v2 for adding new tags to files in /mobile/android/chrome and /mobile/android/base (checked in)

http://hg.mozilla.org/releases/l10n/mozilla-aurora/fa/rev/fae51cbfcd4b
http://hg.mozilla.org/l10n-central/fa/rev/be5106767e62

Comment 16

[Arash Mousavi [:Arash-M]]

This bug report is not relevant anymore. All translations are happening on Pootle[1] for Firefox for Android and it's fully localized to Persian. Closing it.

[1] http://mozilla.locamotion.org/fa/mobile/