SafaAlfulaij
commented
6 years ago Thanks Manal and thank you for attending the meeting! Sorry that I couldn’t attend. I’ve started with what has happened in the meeting, and you can find it below. There is still work to be done, and rules to be added, but this is first draft. I believe that we must have the guide in Arabic. What do you all say? And since you started this, can you please create the Google Docs page? :) I’ll write about this in the mailing list. And Late Eid Mubarak! :sweat_smile:
Zaid-ibhais-zz
commented
6 years ago Hello Safa, Happy eid for you as well,
We have agreed that the style guide should be written in English.
SafaAlfulaij
commented
6 years ago Hello Zaid.
I couldn’t find any clue anywhere about that, and that’s why I started it in Arabic. I’m not really sure why the style guide must be in English. It seems strange to me as it’s not that easy to write specific things about Arabic in English. For example giving a reason why this form should be used instead of this one, or grammer/I‘rāb, Shadda, Tanween, etc.
I also found that many other languages uses their language for the guide (Armenian, Chinese, Czech, Dutch, Esperanto, Finnish, French, German, Irish, Italian, Korean, Lao, Macedonian, Portuguese (Brazilian), Romanian, Serbian, Sinhala, Slovenian, Spanish, Thai, Turkish and Vietnamese). I believe that this is the correct way for a translation guide, to be written in the target language.
Can you please explain the different opinions for such agreement?
khaledhosny
commented
6 years ago We had a tentative agreement to have the guide available in English since some of the l10n drivers would like to be able to consult the style guide in areas that concern Mozilla like branding guidelines.
I think the locale managers and translators need to discuss this and decide how they want to proceed, nothing is written in stone. One option would to write the style guide in Arabic, and once version 1.0 is ready translate it into English in keep both in sync, but that is more work of course.
cc @gueroJeff
SafaAlfulaij
commented
6 years ago Thanks @khaledhosny. This makes sense now for some parts of the guide, like the units, numbers, date and time formats, currency, phone numbers, addresses and the branding. I don’t see the need for having the whole guide in English, but only parts that concern the l10n drivers and developers. I am open for any comment now so that I can continue building the guide.
Rubaaw
commented
6 years ago Good Evening everyone, hope all is well. Wooow Safa great Job! thanks for your effort.
aboodmanna
commented
6 years ago Great job Safa, I see that the style guide have to be in English as Khaled and Zaid mentioned because that was our agreement with the l10n drivers. Looking forward to hearing from you and start working on it together.
SafaAlfulaij
commented
6 years ago I am still asking for a reason why this must be written in English now. Khlaed said it was a tentative agreement, and that the guide should be available in English (as in providing an English version of it).
Anyway, I will rewrite some of that in English and share it with Google Docs.
gueroJeff
commented
6 years ago I understood that an English version would be provided.
El mar., 25 de sep. de 2018 11:30, Safa Alfulaij notifications@github.com escribió:
I am still asking for a reason why this must be written in English now. Khlaed said it was a tentative agreement, and that the guide should be available in English (as in providing an English version of it).
Anyway, I will rewrite some of that in English and share it with Google Docs.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArabicMozilla/Arabic-Mozilla-StyleGuide/issues/1#issuecomment-424431805, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZDUVjm_vDNDmUMhP08X_glWgDEDQks5uemgegaJpZM4WCjaj .
SafaAlfulaij
commented
6 years ago 
bmlamine
commented
6 years ago السلام عليكم،
عندي ملحوظة فيما يخص تنسيق الأعداد : تستخدم أغلب الدول العربية الأرقام الهندية. بينما تستخدم دول شمال افريقيا الأرقام العربية.
بالتوفيق
SafaAlfulaij
commented
6 years ago (BUG: Most Arab countries use Arabic Eastern numerals, while western Arab countries uses Western Arabic numerals. For real-time generated numbers, there should be an option. But what if the number was hardcoded in the translation?)
gueroJeff
commented
6 years ago I would say that filing a bug to use a plural placeholder instead of a hardcoded numeral would be the right approach.
On Fri, Sep 28, 2018 at 7:22 AM Safa Alfulaij notifications@github.com wrote:
السلام عليكم،
عندي ملحوظة فيما يخص تنسيق الأعداد : تستخدم أغلب الدول العربية الأرقام الهندية. بينما تستخدم دول شمال افريقيا الأرقام العربية.
بالتوفيق
وعليكم السلام أقتبس:
(BUG: Most Arab countries use Arabic Eastern numerals, while western Arab countries uses Western Arabic numerals. For real-time generated numbers, there should be an option. But what if the number was hardcoded in the translation?)
دعنا لا ندخل في متاهات تسمية الأرقام فهي لا تنتهي ولسنا أهلا للبتّ بها.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArabicMozilla/Arabic-Mozilla-StyleGuide/issues/1#issuecomment-425433892, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZAVM94neGSXJM9j5vv1Jh_CY-7bnks5ufiKpgaJpZM4WCjaj .
bmlamine
commented
6 years ago السلام عليكم، عندي ملحوظة فيما يخص تنسيق الأعداد : تستخدم أغلب الدول العربية الأرقام الهندية. بينما تستخدم دول شمال افريقيا الأرقام العربية. بالتوفيق
وعليكم السلام أقتبس:
(BUG: Most Arab countries use Arabic Eastern numerals, while western Arab countries uses Western Arabic numerals. For real-time generated numbers, there should be an option. But what if the number was hardcoded in the translation?)
دعنا لا ندخل في متاهات تسمية الأرقام فهي لا تنتهي ولسنا أهلا للبتّ بها.
اتفق معك، بالتوفيق
SafaAlfulaij
commented
6 years ago I would say that filing a bug to use a plural placeholder instead of a hardcoded numeral would be the right approach.
I was wondering what happened with l20n (or Fluent, no idea). I thought that this can solve the problem without extra work on devs.
gueroJeff
commented
6 years ago Fluent can do a lot of things with placeholder attributes, but I'm not sure about new unique per-locale placeholders all together. Maybe @flod can add insight there. Regardless, even with new attributes, devs need to be made aware that those attributes exist in one of the locales files to add it as a valid placeholder in the source code.
El vie., 28 de sep. de 2018 08:10, Safa Alfulaij notifications@github.com escribió:
I would say that filing a bug to use a plural placeholder instead of a hardcoded numeral would be the right approach.
I was wondering what happened with l20n (or Fluent, no idea). I thought that this can solve the problem without extra work on devs.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArabicMozilla/Arabic-Mozilla-StyleGuide/issues/1#issuecomment-425447827, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZLbMp8RQY3zTv4vINSSYzr6syoAuks5ufi26gaJpZM4WCjaj .
SafaAlfulaij
commented
6 years ago I was testing it fast with the Fluent Playground and it worked with the embedded function NUMBER: (Using the Config tab)
test-1 = {NUMBER(2222.3)}
English: 2,222.3
Arabic: ٢٬٢٢٢٫٣I then checked the backend function Intl.NumberFormat and it worked as well: (note that the fixed-width font is not displaying the thousands separator correctly. Check this)
var number = 123456.789;
console.log(new Intl.NumberFormat('ar').format(number));
console.log(new Intl.NumberFormat('ar-tn').format(number)); // Arabic Tunisia
> "١٢٣٬٤٥٦٫٧٨٩"
> "123.456,789"Oh good! Thanks for verifying.
El vie., 28 de sep. de 2018 08:38, Safa Alfulaij notifications@github.com escribió:
I was testing it fast with the Fluent Playground https://projectfluent.org/play/ and it worked with the embedded function NUMBER: (Using the Config tab)
test-1 = {NUMBER(2222.3)} English: 2,222.3 Arabic: ٢٬٢٢٢٫٣
I then checked the backend function Intl.NumberFormat https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/NumberFormat and it worked as well: (note that the fixed-width font is not displaying the thousands separator correctly. Check this https://screenshots.firefox.com/NIcISmknfkAYT9vf/github.com)
var number = 123456.789;
console.log(new Intl.NumberFormat('ar').format(number)); console.log(new Intl.NumberFormat('ar-tn').format(number)); // Arabic Tunisia
"١٢٣٬٤٥٦٫٧٨٩" "123.456,789"
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/ArabicMozilla/Arabic-Mozilla-StyleGuide/issues/1#issuecomment-425456757, or mute the thread https://github.com/notifications/unsubscribe-auth/AB1yZG6jcZbiHs3k7g4iPyXqPvJF7CzHks5ufjRMgaJpZM4WCjaj .
Goal:
Build the Mozilla Style Guide for Arabic languages
Related Issues & Links:
Google Doc: TBD Etherpad from l10n meetup: https://public.etherpad-mozilla.org/p/arabic-l10n-2018
Roles:
Responsible: Leaders & Translators
Accountable: Leaders
Supporting: Contributors
Consulted: Manel
Informed: Delphine || Jeff || Flod
Required: