MozillaWiki - User contributions [en]

L10n:Meetings/2017 Asuncion Workshop

2017-07-18T18:36:03Z

Deimidis: /* Goals */ Adding es-AR goals

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
;When: 12-13 August
;Lodging:

;Arriving at lodging:

;Telegram group:
;Reimbursement policy:
We are able to reimburse for the following expenses:
*transportation between ASU airport and hotel in Asunción,
*visa fees
Please keep your receipts and deliver them to Jeff during the hackathon. We'll be able to reimburse in either local currency or via PayPal.

Any additional expenses once in Asunción are yours to cover (e.g., hotel room service, hotel laundry service, souvenirs, transportation around the city, etc.).

==Goals==
*Guarani
*Zapoteco:
** Complete 100% of the androidshare folder
** Complete the 5 main Mozilla.org folders
** Create a campaign for the release of the official version in Zapotec
*Triqui
*Mixtepec Mixtec
*Southwestern Tlaxiaco Mixtec

*Maya Kacqhikel
** Creation of computer terminology databases on the Web // Creación de
base de datos terminológica de informática en la Web
** Permanently update the location of Firefox Nightly // Actualización
permanente de la localización de Firefox Nightly
** Dissemination of computer terminology through the social network //
Difusión de la terminología de informática a través de la red social.
** Permanent check of all Cak projects. // Comprobación permanente de
todos los proyectos Cak
** Increase Firefox download from Desktop and Android. // Incremento de
las descargas de Firefox de Escritorio y Android

*Northern Puebla Nahuatl
*Classical Nahuatl
*Spanish Chile
*Spanish Mexico
*Spanish Argentina
** Review of pages to be ready for August 15th launch
** Review and finalize Test Pilot webpages
** Develop a strategy for bringing more contributors to the team
*Esperanto
*Portuguese Brazil
**'''Quality Assurance'''
***Develop a strategy with guidance from l10n-drivers to establish a quality assurance on submitted contributions.
**'''Permissions and Responsibilities'''
***Reset permissions and features of contributors listed on: https://wiki.mozilla.org/L10n:Teams:pt-BR
***Define people responsible for each project in Pontoon
**'''Glossary'''
***Update documentation on the Wiki
**'''Onboarding (Documentation)'''
***Develop a series of short videos about how is the process of localization/translation of products and websites in Pontoon.
*Mozilla Nativo

==Agenda==
===Saturday===
;Morning | Mañana
*Welcome & spectrograms | Bienvenido y espectrogramas
*Mozilla news | Noticias de Mozilla
*Tools and process training | Capacitación de herramientas y proceso
;Lunch | Almuerzo
;Afternoon | Tarde
;15 min tea break | Merienda
;Dinner | Cena

===Sunday===
;Morning | Mañana
*Welcome! | Bienvenido
*Tools and process training | Capacitación de herramientas y proceso
;Lunch | Almuerzo
;Afternoon | Tarde
;15 min tea break | Merienda
*Take [https://www.surveygizmo.com/s3/3452593/Mozilla-L10n-Workshops-in-2017 l10n workshop survey]. | Llenar la encuesta de los tallers de Mozilla l10n.
*Group picture | Foto del grupo
;Dinner | Cena

==Other==
*Hashtag for event: #mozl10nASU
;Notes: https://public.etherpad-mozilla.org/p/Asunion-l10n-2016
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list for products (please subscribe)]
*[https://lists.mozilla.org/listinfo/dev-l10n-web Mozilla l10n mailing list for web projects (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

Participation/Community Gatherings

2017-01-04T19:52:24Z

Deimidis: /* Do you want to organize a Gathering for your local Community? */

{{Participation}}

Events listed here are organized by the Participation team and aim to support the following goal:

''"A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives."''

== Do you want to organize a Gathering for your local Community? ==

Community Gatherings are important events to share learning and knowledge with your communities and align your plans and ideas with Mozilla's goals. Community Gatherings had a set of common goals:

* Align Mozilla’s community with Mozilla’s goals
* Improve mozillians’ team and individual skills

Your local community can add another if you need something specific.

We recommend the following path to propose a Community Gathering:

* Read [https://drive.google.com/open?id=0B5DvZy5sKHH1NWdpMkdEczBKYmM Logistic] and [https://drive.google.com/open?id=0B5DvZy5sKHH1MFVGZkRaYUVlbGM Content] playbook (both have a long version and a slide deck. You can find it in the [https://drive.google.com/open?id=0B5DvZy5sKHH1N0gyaEN3MkVGQVU Drive folder])
* Read Community Gathering FAQ at Discourse (still to be created)
* Write a [https://drive.google.com/open?id=1Ev7L5DjZrhkfF_ihwl4OZf5iCsNr5MZ1Fc9vK-F2nzE Briefing] document with your current plan
* Sent the Briefing to Reps/regional Team and Reps Council
* After their review, begin to work in the rest of documents and planning
* Begin the organization process through Reps program

== 2016 ==
* [[Participation/Community_Gatherings/Brazil_2016|Brazil Community Gathering]]
* [[All_Hands/2016_London|London All Hands]] (volunteer participation)
* [[India/Mozilla_India_Meetup_2016|India Community Gathering]]
* [[Participation/Community_Gatherings/European_Gathering_2016|European Community Gathering]]
* [[Participation/Community_Gatherings/Arabic_Gathering_2016|Arabic Community Gathering]]
* [[Participation/Community_Gatherings/Mozfest2016|Mozfest 2016]] (Volunteer participation at Spaces)
* [[Participation/Community_Gatherings/Mexico_Gathering_2016|Mexico Community Gathering]]

== 2015 ==

Strategy for 2015 was under the [[Participation/Global_Gatherings_2015|Global gatherings]] project.

* [[Mozfest/2015/Volunteers|MozFest]]
* [[Coincidental_work_weeks/2015_Orlando|Orlando All Hands]] (volunteer participation)
* [[Participation/Global Gatherings 2015/Singapore|Leadership Summit]]

Participation/Community Gatherings

2017-01-04T18:27:21Z

Deimidis: /* Do you want to organize a Gathering for your local Community? */ changes to playbooks section

{{Participation}}

Events listed here are organized by the Participation team and aim to support the following goal:

''"A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives."''

== Do you want to organize a Gathering for your local Community? ==

Community Gatherings are important events to share learning and knowledge with your communities and align your plans and ideas with Mozilla's goals. Community Gatherings had a set of common goals:

* Align Mozilla’s community with Mozilla’s goals
* Improve mozillians’ team and individual skills

Your local community can add another if you need something specific.

We recommend the following path to propose a Community Gathering:

* Read [https://drive.google.com/open?id=0B5DvZy5sKHH1NWdpMkdEczBKYmM Logistic] and [https://drive.google.com/open?id=0B5DvZy5sKHH1MFVGZkRaYUVlbGM Content] playbook (both have a long version and a slide deck. You can find it in the [https://drive.google.com/open?id=0B5DvZy5sKHH1N0gyaEN3MkVGQVU Drive folder])
* Read Community Gathering FAQ at Discourse (still to be created)
* Write a [https://drive.google.com/open?id=1Ev7L5DjZrhkfF_ihwl4OZf5iCsNr5MZ1Fc9vK-F2nzE Briefing] document with your current plan
* Sent the Briefing to Reps/regional Team and Reps Council
* After their review, begin to work in the rest of documents and planning
* Begin the organization process through Reps program

A big thank you to [http://haiyya.in/ Haiyya team] that helped us reviewing this material and adding suggestions and templates.

== 2016 ==
* [[Participation/Community_Gatherings/Brazil_2016|Brazil Community Gathering]]
* [[All_Hands/2016_London|London All Hands]] (volunteer participation)
* [[India/Mozilla_India_Meetup_2016|India Community Gathering]]
* [[Participation/Community_Gatherings/European_Gathering_2016|European Community Gathering]]
* [[Participation/Community_Gatherings/Arabic_Gathering_2016|Arabic Community Gathering]]
* [[Participation/Community_Gatherings/Mozfest2016|Mozfest 2016]] (Volunteer participation at Spaces)
* [[Participation/Community_Gatherings/Mexico_Gathering_2016|Mexico Community Gathering]]

== 2015 ==

Strategy for 2015 was under the [[Participation/Global_Gatherings_2015|Global gatherings]] project.

* [[Mozfest/2015/Volunteers|MozFest]]
* [[Coincidental_work_weeks/2015_Orlando|Orlando All Hands]] (volunteer participation)
* [[Participation/Global Gatherings 2015/Singapore|Leadership Summit]]

Participation/Community Gatherings

2017-01-04T18:24:53Z

Deimidis: /* Do you want to organize a Gathering for your local Community? */ modifications to Community Gatherings section

{{Participation}}

Events listed here are organized by the Participation team and aim to support the following goal:

''"A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives."''

== Do you want to organize a Gathering for your local Community? ==

Community Gatherings are important events to share learning and knowledge with your communities and align your plans and ideas with Mozilla's goals. Community Gatherings had a set of common goals:

* Align Mozilla’s community with Mozilla’s goals
* Improve mozillians’ team and individual skills

Your local community can add another if you need something specific.

We recommend the following path to propose a Community Gathering:

* Read Logistic and Content playbook (both have a long version and a slide deck. Read both versions)
* Read Community Gathering FAQ at Discourse (still to be created)
* Write a [https://drive.google.com/open?id=1Ev7L5DjZrhkfF_ihwl4OZf5iCsNr5MZ1Fc9vK-F2nzE Briefing] document with your current plan
* Sent the Briefing to Reps/regional Team and Reps Council
* After their review, begin to work in the rest of documents and planning
* Begin the organization process through Reps program

A big thank you to [http://haiyya.in/ Haiyya team] that helped us reviewing this material and adding suggestions and templates.

== 2016 ==
* [[Participation/Community_Gatherings/Brazil_2016|Brazil Community Gathering]]
* [[All_Hands/2016_London|London All Hands]] (volunteer participation)
* [[India/Mozilla_India_Meetup_2016|India Community Gathering]]
* [[Participation/Community_Gatherings/European_Gathering_2016|European Community Gathering]]
* [[Participation/Community_Gatherings/Arabic_Gathering_2016|Arabic Community Gathering]]
* [[Participation/Community_Gatherings/Mozfest2016|Mozfest 2016]] (Volunteer participation at Spaces)
* [[Participation/Community_Gatherings/Mexico_Gathering_2016|Mexico Community Gathering]]

== 2015 ==

Strategy for 2015 was under the [[Participation/Global_Gatherings_2015|Global gatherings]] project.

* [[Mozfest/2015/Volunteers|MozFest]]
* [[Coincidental_work_weeks/2015_Orlando|Orlando All Hands]] (volunteer participation)
* [[Participation/Global Gatherings 2015/Singapore|Leadership Summit]]

Participation/Community Gatherings

2017-01-03T14:46:41Z

Deimidis: /* Do you want to organize a Gathering for your local Community? */ changing links

{{Participation}}

Events listed here are organized by the Participation team and aim to support the following goal:

''"A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives."''

== Do you want to organize a Gathering for your local Community? ==

Community Gatherings are important events to share learning and knowledge with your communities and align your plans and ideas with Mozilla's goals. As part of 2016 work organizing community gatherings, we developed a set of Playbooks and templates that will help you organizing your local community gathering.

We recommend to start with [https://drive.google.com/open?id=0B5DvZy5sKHH1NWdpMkdEczBKYmM Logistic] document and then read the [https://drive.google.com/open?id=0B5DvZy5sKHH1MFVGZkRaYUVlbGM Content] one. Make a copy of the folder with all the templates and share it with your team. Read both documents before start the planning. Both documents have a Slide deck version, please read both too. These documents have links to the templates.

A big thank you to [http://haiyya.in/ Haiyya team] that helped us reviewing this material and adding suggestions and templates.

== 2016 ==
* [[Participation/Community_Gatherings/Brazil_2016|Brazil Community Gathering]]
* [[All_Hands/2016_London|London All Hands]] (volunteer participation)
* [[India/Mozilla_India_Meetup_2016|India Community Gathering]]
* [[Participation/Community_Gatherings/European_Gathering_2016|European Community Gathering]]
* [[Participation/Community_Gatherings/Arabic_Gathering_2016|Arabic Community Gathering]]
* [[Participation/Community_Gatherings/Mozfest2016|Mozfest 2016]] (Volunteer participation at Spaces)
* [[Participation/Community_Gatherings/Mexico_Gathering_2016|Mexico Community Gathering]]

== 2015 ==

Strategy for 2015 was under the [[Participation/Global_Gatherings_2015|Global gatherings]] project.

* [[Mozfest/2015/Volunteers|MozFest]]
* [[Coincidental_work_weeks/2015_Orlando|Orlando All Hands]] (volunteer participation)
* [[Participation/Global Gatherings 2015/Singapore|Leadership Summit]]

Participation/Community Gatherings

2017-01-03T13:20:57Z

Deimidis: Added Playbook section

{{Participation}}

Events listed here are organized by the Participation team and aim to support the following goal:

''"A focus set of relevant training and learning opportunities for mobilizers are systematized and they regularly access these opportunities to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives."''

== Do you want to organize a Gathering for your local Community? ==

Community Gatherings are important events to share learning and knowledge with your communities and align your plans and ideas with Mozilla's goals. As part of 2016 work organizing community gatherings, we developed a set of Playbooks and templates that will help you organizing your local community gathering. [https://drive.google.com/open?id=0B5DvZy5sKHH1N0gyaEN3MkVGQVU In this folder], you will find guides about logistics and content and templates of the documents we used.

== 2016 ==
* [[Participation/Community_Gatherings/Brazil_2016|Brazil Community Gathering]]
* [[All_Hands/2016_London|London All Hands]] (volunteer participation)
* [[India/Mozilla_India_Meetup_2016|India Community Gathering]]
* [[Participation/Community_Gatherings/European_Gathering_2016|European Community Gathering]]
* [[Participation/Community_Gatherings/Arabic_Gathering_2016|Arabic Community Gathering]]
* [[Participation/Community_Gatherings/Mozfest2016|Mozfest 2016]] (Volunteer participation at Spaces)
* [[Participation/Community_Gatherings/Mexico_Gathering_2016|Mexico Community Gathering]]

== 2015 ==

Strategy for 2015 was under the [[Participation/Global_Gatherings_2015|Global gatherings]] project.

* [[Mozfest/2015/Volunteers|MozFest]]
* [[Coincidental_work_weeks/2015_Orlando|Orlando All Hands]] (volunteer participation)
* [[Participation/Global Gatherings 2015/Singapore|Leadership Summit]]

Participation/Community Gatherings/Mexico Gathering 2016

2016-11-18T22:46:07Z

Deimidis: /* Code of Conduct */ adding spanish version

== Location ==

The Mexico Gathering will take place on November 19th and 20th in Mexico City, Mexico. It will be a two day meeting with volunteers from Mexico.

== Goals ==

The goals of this gathering are:
* Align attendees with what is happening at Mozilla
* Improve individual and team skills to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.

== Agenda ==

=== Saturday, Nov 19th ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-9:30 || Introductions
|-
| 9:30-10:15 || Mozilla and Participation Team Goals
|-
| 10:15-11:15 || Personal Leadership
|-
| 11:15-11:30 || Coffee break
|-
| 11:30-12:30 || How to structure a message
|-
| 12:30-13:15 || Giving feedback
|-
| 13:15-14:00 || Lunch
|-
| 14:00-14:45 || Having difficult conversations
|-
| 14:45-16:00 || Community Health discussion
|-
| 16:00-16:15 || Coffee Break
|-
| 16:15-17:00 || Planning for impact
|-
| 17:00-18:00 || Lightning talks
|}

=== Sunday, Nov 20th ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-10:00 || Reps.Next
|-
| 10:00-11:00 || Mozilla on Campus
|-
| 11:00-11:15 || Break
|-
| 11:15-12:00 || Mozilla's key Internet Issues
|-
| 12:00-13:00 || Diversity & Inclusion
|-
| 13:00-14:00 || Lunch
|-
| 14:00-15:00 || WebVR
|-
| 15:00-15:15 || Break
|-
| 15:15-16:00 || Activate Campaign
|-
| 16:00-16:45 || Rust
|-
| 16:45-18:00 || Planification
|}

== Code of Conduct ==

As for every Mozilla event, we will have a [[Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct|Code of Conduct for all the participants]]. ([https://docs.google.com/document/d/1l5vxLf8q-uVJOxL4H7YtcCYwubcLU2FMQJMDu1RaDtI/edit?ts=58120e62| Spanish version])

== Emergency plan ==
Also, there is an [https://docs.google.com/document/d/1-JJt6MZpY4StrFHZj8_uc7P3TAkNhnbKq_qfqCaqz_U/edit?usp=sharing Emergency plan] in case that something happens, with information about who to contact, where's the local authority and emergency phones.

== Logistics ==

=== Mozilla Staff ===

==== Participation Team ====
* Ruben Martin
* Guillermo Movia

==== Contact persons ====
* Ruben Martin
* Contact offsite: Francisco Picolini

=== Communication ===

* Hashtag: #mozmex16
* Channels:
** Mexico CG Telegram group
** Email

=== Hotel ===
'''[http://www.hotel-regente.com.mx Hotel Regente]'''<br>
Address: París No. 9<br>
Delegación Cuauhtémoc, C.P. 06030 Ciudad de México, Distrito Federal, México.<br>
Phone: (+52) 55 10 848700<br>
Email: hotel@hotel-regente.com.mx

[[image:Hotel_Regente_Mexico_Gathering.png|500px]]

=== Getting from the airport to your hotel ===

=== Venue ===
'''[http://www.homework.com.mx/ Homework]'''<br>
Plaza de la República 9 Col. Tabacalera, 06030 Cuauhtémoc, México, D.F. <br>
[[image:Homework_Mexico_Gathering.png|500px]]

=== Getting from the Hotel to the Venue ===
To go from the hotel to the venue, you will have to walk around 800 mts. It's a 10 min walk.

[[image:Hotel_to_Venue_Mexico.png|500px]]

==Food==

* Breakfast will be at the hotel and it's included.
* Lunch and coffee break snacks will be catered for at the venue

=== Dinners ===
We will be organizing group dinners. If you have any allergie that hasn't been communicated, please contact Francisco Picolini as soon as possible.

Dinners will be at 8 PM each day. You will have free time from event ending until Dinner. Menus will be fixed, and alcohol is not included.

==== Friday Dinner ====

[https://goo.gl/maps/vWiVgNBsXjz Restaurante Barro Negro] - Hamburgo 222 PB, 06600 Juarez, D.F.

==== Saturday Dinner ====

[https://goo.gl/maps/wr29NWaLGNx Porco Rosso Nazas] - Río Nazas 115, Cuauhtémoc, 06500

==== Sunday Dinner ====

[https://goo.gl/maps/QnG7PQhFLu92 Parrilla Leonesa] - Insurgentes Sur 86, Cuauhtémoc, Juárez, 06600

== Weather ==
Averages for November:
* Low Temperature: 8°C
* High Temperature: 22°C
* Sunshine Hours: 11 hrs
* Rainfall: 5,1mm
* Weather last 7 days:
** Max: 21°C
** Min: 10 ° C
** Rainfall: 4.3 mm

Participation/Community Gatherings/Mexico Gathering 2016

2016-11-15T00:00:15Z

Deimidis: /* Agenda */ Adding agenda draft

== Location ==

The Mexico Gathering will take place on November 19th and 20th in Mexico City, Mexico. It will be a two day meeting with volunteers from Mexico.

== Goals ==

The goals of this gathering are:
* Align attendees with what is happening at Mozilla
* Improve individual and team skills to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.

== Agenda ==

=== Saturday, Nov 19th ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-9:30 || Introductions
|-
| 9:30-10:15 || Mozilla and Participation Team Goals
|-
| 10:15-11:15 || Personal Leadership
|-
| 11:15-11:30 || Coffee break
|-
| 11:30-12:30 || How to structure a message
|-
| 12:30-13:15 || Giving feedback
|-
| 13:15-14:00 || Lunch
|-
| 14:00-14:45 || Having difficult conversations
|-
| 14:45-16:00 || Community Health discussion
|-
| 16:00-16:15 || Coffee Break
|-
| 16:15-17:00 || Planning for impact
|-
| 17:00-18:00 || Lightning talks
|}

=== Sunday, Nov 20th ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-10:00 || Reps.Next
|-
| 10:00-11:00 || Mozilla on Campus
|-
| 11:00-11:15 || Break
|-
| 11:15-12:00 || Mozilla's key Internet Issues
|-
| 12:00-13:00 || Diversity & Inclusion
|-
| 13:00-14:00 || Lunch
|-
| 14:00-15:00 || WebVR
|-
| 15:00-15:15 || Break
|-
| 15:15-16:00 || Activate Campaign
|-
| 16:00-16:45 || Rust
|-
| 16:45-18:00 || Planification
|}

== Code of Conduct ==

As for every Mozilla event, we will have a [[Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct|Code of Conduct for all the participants]].

== Emergency plan ==
Also, there is an [https://docs.google.com/document/d/1-JJt6MZpY4StrFHZj8_uc7P3TAkNhnbKq_qfqCaqz_U/edit?usp=sharing Emergency plan] in case that something happens, with information about who to contact, where's the local authority and emergency phones.

== Logistics ==

=== Mozilla Staff ===

==== Participation Team ====
* Ruben Martin
* Guillermo Movia

==== Contact persons ====
* Ruben Martin
* Contact offsite: Francisco Picolini

=== Communication ===

* Hashtag: #mozmex16
* Channels:
** Mexico CG Telegram group
** Email

=== Hotel ===
'''[http://www.hotel-regente.com.mx Hotel Regente]'''<br>
Address: París No. 9<br>
Delegación Cuauhtémoc, C.P. 06030 Ciudad de México, Distrito Federal, México.<br>
Phone: (+52) 55 10 848700<br>
Email: hotel@hotel-regente.com.mx

[[image:Hotel_Regente_Mexico_Gathering.png|500px]]

=== Getting from the airport to your hotel ===

=== Venue ===
'''[http://www.homework.com.mx/ Homework]'''<br>
Plaza de la República 9 Col. Tabacalera, 06030 Cuauhtémoc, México, D.F. <br>
[[image:Homework_Mexico_Gathering.png|500px]]

=== Getting from the Hotel to the Venue ===
To go from the hotel to the venue, you will have to walk around 800 mts. It's a 10 min walk.

[[image:Hotel_to_Venue_Mexico.png|500px]]

==Food==

* Breakfast will be at the hotel and it's included.
* Lunch and coffee break snacks will be catered for at the venue

=== Dinners ===
We will be organizing group dinners. If you have any allergie that hasn't been communicated, please contact Francisco Picolini as soon as possible.

Dinners will be at 8 PM each day. You will have free time from event ending until Dinner. Menus will be fixed, and alcohol is not included.

==== Friday Dinner ====

==== Saturday Dinner ====

==== Sunday Dinner ====

== Weather ==

Participation/Community Gatherings/Mexico Gathering 2016

2016-10-27T13:55:58Z

Deimidis: adding first content (based on template from other CGs)

Participation/Community Gatherings

2016-10-27T13:55:14Z

Deimidis: /* 2016 */ Adding Mexico CG wiki link

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-19T13:30:34Z

Deimidis: /* Contact info */ Adding Manel

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any Arabic Community Gathering participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Rubén Martín, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All Arabic Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Rubén Martín: nukeador[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* Manel Rhaiem: manel.rhaiem92[at]gmail[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-19T02:54:21Z

Deimidis: /* Consequences of Unacceptable Behavior */

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any Arabic Community Gathering participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Rubén Martín, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All Arabic Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Rubén Martín: nukeador[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-19T02:42:30Z

Deimidis: /* Contact info */ Change Brian -> Ruben

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any all hands participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Rubén Martín, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All Arabic Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Rubén Martín: nukeador[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-19T02:41:49Z

Deimidis: /* Scope */

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any all hands participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Rubén Martín, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All Arabic Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Brian King: bking[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-19T02:41:11Z

Deimidis: /* Reporting guidelines */ change Brian -> Rubén

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any all hands participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Rubén Martín, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All European Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Brian King: bking[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016

2016-10-18T20:15:56Z

Deimidis: /* Saturday, Oct 22nd */ Adding Sunday

== Location ==

The Arabic Gathering will take place on October 22nd and 23rd in Casablanca, Morocco. It will be a two day meeting with volunteers from arabic countries.

== Goals ==

The goals of this gathering are:
* Align attendees with what is happening at Mozilla
* Improve individual and team skills to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.

== Agenda ==

=== Saturday, Oct 22nd ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-9:30 || Introductions
|-
| 9:30-10:15 || Mozilla and Participation Team Goals
|-
| 10:15-11:15 || Personal Leadership
|-
| 11:15-11:30 || Coffee break
|-
| 11:30-12:30 || Rust and communities
|-
| 12:30-13:15 || Giving feedback
|-
| 13:15-14:00 || Lunch
|-
| 14:00-14:45 || Cultural differences - unconscious bias
|-
| 14:45-16:00 || Community Health discussion
|-
| 16:00-16:15 || Coffee Break
|-
| 16:15-17:00 || Planning for impact
|-
| 17:00-18:00 || Lightning talks
|}

=== Sunday, Oct 23rd ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-10:00 || Reps.Next
|-
| 10:00-11:00 || Mozilla on Campus
|-
| 11:00-11:15 || Break
|-
| 11:15-12:00 || Mozilla's key Internet Issues
|-
| 12:00-13:00 || Lunch
|-
| 13:00-13:30 || Diversity & Inclusion
|-
| 13:30-14:30 || WebVR
|-
| 14:30-14:45 || Break
|-
| 14:45-15:30 || Activate Campaign
|-
| 15:30-16:00 || Building Partnerships
|-
| 16:00-18:00 || Planification
|}

== Code of Conduct ==

As for every Mozilla event, we will have a [[Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct|Code of Conduct for all the participants]].

== Logistics ==

=== Mozilla Staff ===

==== Participation Team =====
* Brian King
* Christos Bacharakis
* Pierros Papadeas

==== Contact persons ====

=== Communication ===

* Hashtag: #mozarab16
* Channels:
** ''Arabic CG'' Telegram group
** Email

=== Hotel ===

TBD

=== Getting from the airport to your hotel ===

=== Venue ===

TBD

=== Getting from the Hotel to the Venue ===

==Food==

* Breakfast will be at the hotel and it's included.
* Lunch and coffee break snacks will be catered for at the venue

=== Dinners ===

==== Friday Dinner ====

==== Saturday Dinner ====

==== Sunday Dinner ====

== Weather ==

Averages for September:
*Temperature: 19°C (66°F)
*Low Temperature: 15°C (59°F)
*High Temperature: 23°C (73°F)
*Sunshine Hours: 5 hrs
*Rainfall: 33mm
*Rainfall days: 6 days

== Tourist Information ==

Participation/Community Gatherings/Arabic Gathering 2016

2016-10-18T19:18:03Z

Deimidis: /* Saturday, Oct 22nd */

== Location ==

The Arabic Gathering will take place on October 22nd and 23rd in Casablanca, Morocco. It will be a two day meeting with volunteers from arabic countries.

== Goals ==

The goals of this gathering are:
* Align attendees with what is happening at Mozilla
* Improve individual and team skills to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.

== Agenda ==

=== Saturday, Oct 22nd ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-9:30 || Introductions
|-
| 9:30-10:15 || Mozilla and Participation Team Goals
|-
| 10:15-11:15 || Personal Leadership
|-
| 11:15-11:30 || Coffee break
|-
| 11:30-12:30 || Rust and communities
|-
| 12:30-13:15 || Giving feedback
|-
| 13:15-14:00 || Lunch
|-
| 14:00-14:45 || Cultural differences - unconscious bias
|-
| 14:45-16:00 || Community Health discussion
|-
| 16:00-16:15 || Coffee Break
|-
| 16:15-17:00 || Planning for impact
|-
| 17:00-18:00 || Lightning talks
|}

== Code of Conduct ==

As for every Mozilla event, we will have a [[Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct|Code of Conduct for all the participants]].

== Logistics ==

=== Mozilla Staff ===

==== Participation Team =====
* Brian King
* Christos Bacharakis
* Pierros Papadeas

==== Contact persons ====

=== Communication ===

* Hashtag: #mozarab16
* Channels:
** ''Arabic CG'' Telegram group
** Email

=== Hotel ===

TBD

=== Getting from the airport to your hotel ===

=== Venue ===

TBD

=== Getting from the Hotel to the Venue ===

==Food==

* Breakfast will be at the hotel and it's included.
* Lunch and coffee break snacks will be catered for at the venue

=== Dinners ===

==== Friday Dinner ====

==== Saturday Dinner ====

==== Sunday Dinner ====

== Weather ==

Averages for September:
*Temperature: 19°C (66°F)
*Low Temperature: 15°C (59°F)
*High Temperature: 23°C (73°F)
*Sunshine Hours: 5 hrs
*Rainfall: 33mm
*Rainfall days: 6 days

== Tourist Information ==

Participation/Community Gatherings/Arabic Gathering 2016

2016-10-18T19:14:19Z

Deimidis: /* Agenda */ Adding Saturday Agenda

== Location ==

The Arabic Gathering will take place on October 22nd and 23rd in Casablanca, Morocco. It will be a two day meeting with volunteers from arabic countries.

== Goals ==

The goals of this gathering are:
* Align attendees with what is happening at Mozilla
* Improve individual and team skills to be more effective in their contributions and as a result providing more impact to Mozilla’s main initiatives.

== Agenda ==

=== Saturday, Oct 22nd ===

{| class="wikitable"
|-
! Time !! Session
|-
| 9:00-9:30 || Introductions
|-
| 9:30-10:15 || Mozilla and Participation Team Goals
|-
| 10:15-11:15 || Personal Leadership
|
|-
| 11:15-11:30 || Coffee break
|
|-
| 11:30-12:30 || Rust and communities
|
|-
| 12:30-13:15 || Giving feedback
|
|-
| 13:15-14:00 || Lunch
|
|-
| 14:00-14:45 || Cultural differences - unconscious bias
|
|-
| 14:45-16:00 || Community Health discussion
|

|-
| 16:00-16:15 || Coffee Break
|

|-
| 16:15-17:00 || Planning for impact
|

|-
| 17:00-18:00 || Lightning talks
|
}

== Code of Conduct ==

As for every Mozilla event, we will have a [[Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct|Code of Conduct for all the participants]].

== Logistics ==

=== Mozilla Staff ===

==== Participation Team =====
* Brian King
* Christos Bacharakis
* Pierros Papadeas

==== Contact persons ====

=== Communication ===

* Hashtag: #mozarab16
* Channels:
** ''Arabic CG'' Telegram group
** Email

=== Hotel ===

TBD

=== Getting from the airport to your hotel ===

=== Venue ===

TBD

=== Getting from the Hotel to the Venue ===

==Food==

* Breakfast will be at the hotel and it's included.
* Lunch and coffee break snacks will be catered for at the venue

=== Dinners ===

==== Friday Dinner ====

==== Saturday Dinner ====

==== Sunday Dinner ====

== Weather ==

Averages for September:
*Temperature: 19°C (66°F)
*Low Temperature: 15°C (59°F)
*High Temperature: 23°C (73°F)
*Sunshine Hours: 5 hrs
*Rainfall: 33mm
*Rainfall days: 6 days

== Tourist Information ==

Participation/Resources

2016-10-13T13:54:12Z

Deimidis: /* Facilitate your own event */ Adding resources to the wiki

{{Participation}}
<br>
{{admon/important|under construction|This page is under construction, please be patient}}

This wiki page is dedicated to participation mentors - community members that want to help and increase the number of participants involved in their projects.

== Workshops ==
Here you can find workshops that should help designing your project of participation
*[[Participation/Resources/Designing_for_participation | Designing for participation]]
*[[Participation/Resources/Identifying_contributors | Identifying contributors]]

== Dashboards ==
List of dashboard dedicated into the growth and health of the communities
* http://areweamillionyet.org/
* http://www.joshmatthews.net/mentorwatch/
* http://toolness.github.io/bugzilla-dashboard/#
* https://wikiapiary.com/wiki/MozillaWiki
* http://mentorship.mozillareps.org/
* https://support.mozilla.org/en-US/kpi/dashboard
* http://devs.mozillaindia.org/leaderboard/

== Videos ==
Videos created by community leaders for community leaders
*[https://air.mozilla.org/designing-for-participation/ Designing for Participation]
*[https://videos.cdn.mozilla.net/uploads/drafts/Gerv%20How%20to%20work%20in%20a%20Community%20-360p.webm How to work with community]
*[http://popcorn.webmadecontent.org/uxr How To Work With 3 Types of Mozilla Volunteers]
*[https://www.youtube.com/watch?v=rdJx-90qaSA&feature=youtu.be Tips for Mozilla community mentoring, from the pros]
*[https://air.mozilla.org/cm-get-involved-2/ Get Involved 2, interview with contributors]
*[https://air.mozilla.org/cm-get-involved-3/ Get Involved 3, tips for getting involved]

== Facilitate your own event ==
[[Hosting_community_events#Scheduling_your_event | Instructions]] on how to facilitate your own event in a Mozilla office.

=== Playbooks to organize your event ===
At the Participation Team we created these document to compile our learnings organizing events. These are documents on constant evolution process, but we reccomend that you take a look and use it to organize your event. Let us know your feedback.

* [https://drive.google.com/file/d/0B5DvZy5sKHH1N3BZendla1daTmM/view?usp=sharing Events logistics]
* [https://drive.google.com/file/d/0B5DvZy5sKHH1ZlZqZGhsNkxzQnc/view?usp=sharing Content creation]

== Reading ==
The following links are a mix of Mozilla-specific and general open source community building material.
=== Lexicon ===
[[Lexicon:All|Mozilla Lexicon]]

=== Community Survey ===
[[Participation/Resources/2014_Community_Survey | Community Survey]] by David Eaves on several dimensions of contribution

=== General Reading ===
* [https://leanpub.com/community_event_planning Community Event Planning] by Christie Koehler, Sherri Montgomery and Audrey Eschright
* [http://www.artofcommunityonline.org/get/ The Art of Community] by Jono Bacon
* [http://producingoss.com/ Producing Open Source Software] by Karl Fogel
* [http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/ Effective mentoring programs] by Dave Neary
* [http://pyvideo.org/video/719/diversity-in-practice-how-the-boston-python-user Diversity in practice: How the Boston Python User Group grew to 1700 people and over 15% women] by Asheesh Laroia and Jessica McKellar
* [http://www.amazon.com/Building-Successful-Online-Communities-Evidence-Based/dp/0262016575 Building Successful Online Communities: Evidence-Based Social Design] by Robert E. Kraut and Paul Resnick; available online as PDF [http://kraut.hciresearch.org/content/books draft chapters]
* [http://www.idealist.org/info/VolunteerMgmt Volunteer Management Resource Center] from idealist.org
* [http://www.frogdesign.com/collective-action-toolkit Collective Action Toolkit] from frog
* [[FreeSoftwareOnResumes:Writing|How To Put Free Software Experience On Your Resumé]]
* [http://www.amazon.com/Buzzing-Communities-Bigger-Better-Active/dp/0988359901 Buzzing Communities: How to build bigger, better, more active online communities] by Richard Millington.
* [http://www.amazon.com/Building-Reputation-Systems-Randy-Farmer/dp/059615979X Building Web Reputation Systems] by Randy Farmer and Bryce Glass.
* [http://www.amazon.com/Cultivating-Communities-Practice-Etienne-Wenger/dp/1578513308 Cultivating Communities of Practice: A guide to managing knowledge] by Etienne Wenger, Richard McDermott, and William Snyder.
* [http://www.feverbee.com/ The Online Community Guide], blog by Richard Millington.
* [http://www.academia.edu/3836587/A_Preliminary_Study_on_the_Effects_of_Barnstars_on_Wikipedia_Editing A Preliminary Study of the Effects of Barnstars on Wikipedia Editing]; found that number of edits goes down after an editor gets a barnstar, but eventually recovers to the level before the barnstar.
* [https://www.academia.edu/8194567/Understanding_and_Supporting_the_Choice_of_an_Appropriate_Task_to_Start_With_In_Open_Source_Software_Communities Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities] by Igor Steinmacher, Tayana Uchoa Conte, and Marco Aurelio Gerosa.

Participation/Resources

2016-10-13T13:52:43Z

Deimidis: /* Playbooks to organize your event */

{{Participation}}
<br>
{{admon/important|under construction|This page is under construction, please be patient}}

This wiki page is dedicated to participation mentors - community members that want to help and increase the number of participants involved in their projects.

== Workshops ==
Here you can find workshops that should help designing your project of participation
*[[Participation/Resources/Designing_for_participation | Designing for participation]]
*[[Participation/Resources/Identifying_contributors | Identifying contributors]]

== Dashboards ==
List of dashboard dedicated into the growth and health of the communities
* http://areweamillionyet.org/
* http://www.joshmatthews.net/mentorwatch/
* http://toolness.github.io/bugzilla-dashboard/#
* https://wikiapiary.com/wiki/MozillaWiki
* http://mentorship.mozillareps.org/
* https://support.mozilla.org/en-US/kpi/dashboard
* http://devs.mozillaindia.org/leaderboard/

== Videos ==
Videos created by community leaders for community leaders
*[https://air.mozilla.org/designing-for-participation/ Designing for Participation]
*[https://videos.cdn.mozilla.net/uploads/drafts/Gerv%20How%20to%20work%20in%20a%20Community%20-360p.webm How to work with community]
*[http://popcorn.webmadecontent.org/uxr How To Work With 3 Types of Mozilla Volunteers]
*[https://www.youtube.com/watch?v=rdJx-90qaSA&feature=youtu.be Tips for Mozilla community mentoring, from the pros]
*[https://air.mozilla.org/cm-get-involved-2/ Get Involved 2, interview with contributors]
*[https://air.mozilla.org/cm-get-involved-3/ Get Involved 3, tips for getting involved]

== Facilitate your own event ==
[[Hosting_community_events#Scheduling_your_event | Instructions]] on how to facilitate your own event in a Mozilla office.

=== Playbooks to organize your event ===
At the Participation Team we created these document to compile our learnings organizing events. These are documents on constant evolution process, but we reccomend that you take a look and use it to organize your event. Let us know your feedback.

* [[https://drive.google.com/file/d/0B5DvZy5sKHH1N3BZendla1daTmM/view?usp=sharing | Events logistics]]
* [[https://drive.google.com/file/d/0B5DvZy5sKHH1ZlZqZGhsNkxzQnc/view?usp=sharing Content creation]]

== Reading ==
The following links are a mix of Mozilla-specific and general open source community building material.
=== Lexicon ===
[[Lexicon:All|Mozilla Lexicon]]

=== Community Survey ===
[[Participation/Resources/2014_Community_Survey | Community Survey]] by David Eaves on several dimensions of contribution

=== General Reading ===
* [https://leanpub.com/community_event_planning Community Event Planning] by Christie Koehler, Sherri Montgomery and Audrey Eschright
* [http://www.artofcommunityonline.org/get/ The Art of Community] by Jono Bacon
* [http://producingoss.com/ Producing Open Source Software] by Karl Fogel
* [http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/ Effective mentoring programs] by Dave Neary
* [http://pyvideo.org/video/719/diversity-in-practice-how-the-boston-python-user Diversity in practice: How the Boston Python User Group grew to 1700 people and over 15% women] by Asheesh Laroia and Jessica McKellar
* [http://www.amazon.com/Building-Successful-Online-Communities-Evidence-Based/dp/0262016575 Building Successful Online Communities: Evidence-Based Social Design] by Robert E. Kraut and Paul Resnick; available online as PDF [http://kraut.hciresearch.org/content/books draft chapters]
* [http://www.idealist.org/info/VolunteerMgmt Volunteer Management Resource Center] from idealist.org
* [http://www.frogdesign.com/collective-action-toolkit Collective Action Toolkit] from frog
* [[FreeSoftwareOnResumes:Writing|How To Put Free Software Experience On Your Resumé]]
* [http://www.amazon.com/Buzzing-Communities-Bigger-Better-Active/dp/0988359901 Buzzing Communities: How to build bigger, better, more active online communities] by Richard Millington.
* [http://www.amazon.com/Building-Reputation-Systems-Randy-Farmer/dp/059615979X Building Web Reputation Systems] by Randy Farmer and Bryce Glass.
* [http://www.amazon.com/Cultivating-Communities-Practice-Etienne-Wenger/dp/1578513308 Cultivating Communities of Practice: A guide to managing knowledge] by Etienne Wenger, Richard McDermott, and William Snyder.
* [http://www.feverbee.com/ The Online Community Guide], blog by Richard Millington.
* [http://www.academia.edu/3836587/A_Preliminary_Study_on_the_Effects_of_Barnstars_on_Wikipedia_Editing A Preliminary Study of the Effects of Barnstars on Wikipedia Editing]; found that number of edits goes down after an editor gets a barnstar, but eventually recovers to the level before the barnstar.
* [https://www.academia.edu/8194567/Understanding_and_Supporting_the_Choice_of_an_Appropriate_Task_to_Start_With_In_Open_Source_Software_Communities Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities] by Igor Steinmacher, Tayana Uchoa Conte, and Marco Aurelio Gerosa.

Participation/Resources

2016-10-13T13:49:08Z

Deimidis: /* Facilitate your own event */ Adding resources to the wiki

{{Participation}}
<br>
{{admon/important|under construction|This page is under construction, please be patient}}

This wiki page is dedicated to participation mentors - community members that want to help and increase the number of participants involved in their projects.

== Workshops ==
Here you can find workshops that should help designing your project of participation
*[[Participation/Resources/Designing_for_participation | Designing for participation]]
*[[Participation/Resources/Identifying_contributors | Identifying contributors]]

== Dashboards ==
List of dashboard dedicated into the growth and health of the communities
* http://areweamillionyet.org/
* http://www.joshmatthews.net/mentorwatch/
* http://toolness.github.io/bugzilla-dashboard/#
* https://wikiapiary.com/wiki/MozillaWiki
* http://mentorship.mozillareps.org/
* https://support.mozilla.org/en-US/kpi/dashboard
* http://devs.mozillaindia.org/leaderboard/

== Videos ==
Videos created by community leaders for community leaders
*[https://air.mozilla.org/designing-for-participation/ Designing for Participation]
*[https://videos.cdn.mozilla.net/uploads/drafts/Gerv%20How%20to%20work%20in%20a%20Community%20-360p.webm How to work with community]
*[http://popcorn.webmadecontent.org/uxr How To Work With 3 Types of Mozilla Volunteers]
*[https://www.youtube.com/watch?v=rdJx-90qaSA&feature=youtu.be Tips for Mozilla community mentoring, from the pros]
*[https://air.mozilla.org/cm-get-involved-2/ Get Involved 2, interview with contributors]
*[https://air.mozilla.org/cm-get-involved-3/ Get Involved 3, tips for getting involved]

== Facilitate your own event ==
[[Hosting_community_events#Scheduling_your_event | Instructions]] on how to facilitate your own event in a Mozilla office.

=== Playbooks to organize your event ===
At the Participation Team we created these document to compile our learnings organizing events. These are documents on constant evolution process, but we reccomend that you take a look and use it to organize your event. Let us know your feedback.

* [[https://drive.google.com/file/d/0B5DvZy5sKHH1N3BZendla1daTmM/view?usp=sharing | Events logistics]]

== Reading ==
The following links are a mix of Mozilla-specific and general open source community building material.
=== Lexicon ===
[[Lexicon:All|Mozilla Lexicon]]

=== Community Survey ===
[[Participation/Resources/2014_Community_Survey | Community Survey]] by David Eaves on several dimensions of contribution

=== General Reading ===
* [https://leanpub.com/community_event_planning Community Event Planning] by Christie Koehler, Sherri Montgomery and Audrey Eschright
* [http://www.artofcommunityonline.org/get/ The Art of Community] by Jono Bacon
* [http://producingoss.com/ Producing Open Source Software] by Karl Fogel
* [http://blogs.gnome.org/bolsh/2011/05/31/effective-mentoring-programs/ Effective mentoring programs] by Dave Neary
* [http://pyvideo.org/video/719/diversity-in-practice-how-the-boston-python-user Diversity in practice: How the Boston Python User Group grew to 1700 people and over 15% women] by Asheesh Laroia and Jessica McKellar
* [http://www.amazon.com/Building-Successful-Online-Communities-Evidence-Based/dp/0262016575 Building Successful Online Communities: Evidence-Based Social Design] by Robert E. Kraut and Paul Resnick; available online as PDF [http://kraut.hciresearch.org/content/books draft chapters]
* [http://www.idealist.org/info/VolunteerMgmt Volunteer Management Resource Center] from idealist.org
* [http://www.frogdesign.com/collective-action-toolkit Collective Action Toolkit] from frog
* [[FreeSoftwareOnResumes:Writing|How To Put Free Software Experience On Your Resumé]]
* [http://www.amazon.com/Buzzing-Communities-Bigger-Better-Active/dp/0988359901 Buzzing Communities: How to build bigger, better, more active online communities] by Richard Millington.
* [http://www.amazon.com/Building-Reputation-Systems-Randy-Farmer/dp/059615979X Building Web Reputation Systems] by Randy Farmer and Bryce Glass.
* [http://www.amazon.com/Cultivating-Communities-Practice-Etienne-Wenger/dp/1578513308 Cultivating Communities of Practice: A guide to managing knowledge] by Etienne Wenger, Richard McDermott, and William Snyder.
* [http://www.feverbee.com/ The Online Community Guide], blog by Richard Millington.
* [http://www.academia.edu/3836587/A_Preliminary_Study_on_the_Effects_of_Barnstars_on_Wikipedia_Editing A Preliminary Study of the Effects of Barnstars on Wikipedia Editing]; found that number of edits goes down after an editor gets a barnstar, but eventually recovers to the level before the barnstar.
* [https://www.academia.edu/8194567/Understanding_and_Supporting_the_Choice_of_an_Appropriate_Task_to_Start_With_In_Open_Source_Software_Communities Understanding and Supporting the Choice of an Appropriate Task to Start With In Open Source Software Communities] by Igor Steinmacher, Tayana Uchoa Conte, and Marco Aurelio Gerosa.

Participation/Community Gatherings/Arabic Gathering 2016

2016-10-12T15:43:44Z

Deimidis: /* Mozilla Staff */ adding Participatio Team

Participation/Community Gatherings/Arabic Gathering 2016/Code of Conduct

2016-10-12T15:34:28Z

Deimidis: Adding Code of Conduct text, modified from European Gathering Wiki page

''(Guideline based on Leadership Summit)''

= Mozillian Community Event Safety Guidelines =

The heart of Mozilla is people. This guideline is meant to support a happy, productive, and safe event experience that can welcome new ideas and inspiration for all attendees of the Arabic Community Gathering, regardless of gender, sexual orientation, age, ability, ethnicity, socioeconomic status, and religion (or lack thereof).

We gain strength from diversity, and actively seek participation from those who enhance it. These guidelines exist to ensure that diverse groups collaborate to mutual advantage and enjoyment. We will challenge prejudice that could jeopardise the participation of any person in the project, and we outline in this document expected, as well as prohibited behavior.

This Code of Conduct outlines our expectations for all those who participate in our conference, as well as the consequences for unacceptable behavior.

We invite all those who participate in the Arabic Community Gathering to help us create safe and positive experiences for everyone.

== Expected ==

The following behaviors are expected and requested of all event participants, including attendees, speakers, and staff.

=== Lead by example ===

Each individual attending this event does so on behalf of their community. This means being considerate of how your discussions, actions and decisions will represent your community.

=== Be respectful ===

Disagreement is no excuse for poor manners. We will exercise consideration and respect in our speech and actions, and consider collaboration before conflict. Ensure all voices are heard, not just the loudest.

=== Watch your language ===

Refrain from demeaning, discriminatory, or harassing behavior and speech. This includes gestures and online discussions / back-channels (like Telegram).

=== Take responsibility for your words & actions ===

We can all make mistakes; when we do, we take responsibility for them. If someone has been harmed or offended, we listen carefully and respectfully, and work to right the wrong.

=== Look out for each other ===

Be mindful of your surroundings and of your fellow participants. Alert Brian King, Christos Bacharakis or Pierros Papadeas if you notice a dangerous situation, someone in distress, or violations of this Guideline. If something makes you feel concerned, or worried - even if you’re not sure it’s a violation -, it’s better to reach out, than to ignore.

Be mindful of local laws, and protect each other from making public - personal information that may put people at risk of appearing to violate those laws.

Remember that event venues and hotels may be shared with members of the public; please be respectful to all patrons of these locations.

=== Ask for help ===

Everyone is encouraged to ask questions about this guideline, and the Mozilla Participation Guidelines generally.

== Unacceptable Behavior ==

The following behaviors are considered harassment and are unacceptable:
* Violence and threats of violence.
* Incitement of violence towards any individual, including encouraging a person to commit suicide or to engage in self-harm.
* Derogatory comments related to gender, gender identity and expression, sexual orientation, disability, mental illness, neuro(a)typicality, physical appearance, body size, race, religion, age, or socio-economic status.
* Sexual images or behavior.
* Posting or threatening to post other people’s personally identifying information (“doxing”).
* Deliberate misgendering or use of former names, or improper titles.
* Inappropriate photography or recording.
* Physical contact without affirmative consent.
* Unwelcome sexual attention. This includes, sexualized comments or jokes; inappropriate touching, groping, and unwelcomed sexual advances.
* Deliberate intimidation, stalking or following (online or in person).
* Sustained disruption of conference events, including talks and presentations.
* Advocating for, or encouraging, any of the above behavior.

=== Consequences of Unacceptable Behavior ===

Unacceptable behavior from any all hands participant, including those with decision-making authority, will not be tolerated.

Anyone asked to stop unacceptable behavior is expected to comply immediately.

If an event participant engages in unacceptable behavior, the organizers may take any action they deem appropriate, up to and including a temporary ban or permanent expulsion from the event, as well as associated and future events without warning.

=== Reporting guidelines ===

If you are subject to or witness unacceptable behavior, or have any other concerns, please notify Brian King, Christos Bacharakis or Pierros Papadeas as soon as possible by email, or contact them directly.

Additionally, they are available to help community members engage with local law enforcement or to otherwise help those experiencing unacceptable behavior feel safe. In the context of in-person events, organizers will also provide escorts as desired by the person experiencing distress.

==== Addressing Grievances ====

If you feel you have been falsely or unfairly accused of violating this Code of Conduct, you should notify the summit conduct team at bking[at]mozilla[dot]com with a concise description of your grievance.

==== Scope ====

All European Gathering participants (contributors, paid or otherwise; and other guests) are expected to abide by this Code of Conduct in all community venues—online and in-person—as well as in all one-on-one communications pertaining to the event business.

This Guideline and its related procedures also applies to unacceptable behavior occurring outside the scope of Arabic Community Gathering Meetup activities when such behavior has the potential to adversely affect the safety and well-being of Arabic Community Gathering members.

=== Contact info ===

* Brian King: bking[at]mozilla[dot]com
* Christos Bacharakis: christos[at]mozilla[dot]com
* Pierros Papadeas: pierros[at]mozilla[dot]com
* You can also email Diversity Lead, Larissa Shapiro directly: lshapiro[at]mozilla[dot]com.

'''License and attribution'''

This Code of Conduct is distributed under a Creative Commons Attribution-ShareAlike license (http://creativecommons.org/licenses/by-sa/3.0/).

It has been adapted with few modifications from Ubuntu Code of Conduct (http://www.ubuntu.com/about/about-ubuntu/conduct), Mozilla’s View Source Conference (https://viewsourceconf.org/code-of-conduct/), which is based on Stumptown Syndicate’s Citizen Code of Conduct (http://citizencodeofconduct.org/), portions of which are derived from the Django Code of Conduct and the Geek Feminism Anti-Harassment Policy. Additional text from LGBTQ in Technology Code of Conduct (http://lgbtq.technology/coc.html).

Participation/Community Gatherings/Arabic Gathering 2016

2016-10-12T15:33:30Z

Deimidis: /* Code of Conduct */ Adding Code of Conduct webpage

Participation/Community Gatherings/Brazil 2016

2016-05-26T22:06:12Z

Deimidis: /* Food */ adding alcoholic clarification

< [[Participation/Community_Gatherings]]

= Brazil 2016 =

== Overview ==

Brazil is the biggest community in Latin America, and one of our 10 focus countries. Is difficult that a great number of Brazilian community members participate on big Mozilla’s events at the same time, so we think is a great place to begin the work on Regional Institutes.

At the same time is a community with several layers that don’t always integrate well. There are community members that participate in the community for the last 10 years, and new ones with lots of new ideas. But they are struggling to organize.

=== Goals ===
* Clear participation plans for our two major initiatives (Campus Campaign and Connected Devices)
* All the participants agree on a communication process and channel
* Participants report having learned at the event and are motivated to work on the initiatives
* There is an improvement in the health in the Brazilian community. This will be measure with before and after surveys

=== Code of Conduct ===
* As for every Mozilla event, we have a [[Participation/Community Gatherings/Brazil 2016/Code of Conduct|Code of Conduct for all the participants]].

== When ==
* Friday May 27th- Arrival Day (dinner with all participants)
* Saturday - May 28th - First day of meetup
* Sunday - May 29th - Second day of meetup
* Sunday evening/ Monday May 30th - Departure day.

==Schedule ==
* Schedule can be consulted [[Participation/Community Gatherings/Brazil 2016/Schedule|here]].
* Highlights:

== Logistics ==

=== Accommodation ===
* Participants will stay at [http://www.atlanticahotels.com.br/hotel/sao-paulo/quality-faria-lima Quality Hotel Faria Lima]
** Address: Rua Diogo Moreira, 247 - Pinheiros, São Paulo - SP, 05423-010, Brazil
** All participants will share double rooms

=== Venue ===
The event will take place at the [http://www.mutuacoworking.com.br/ Mutua Coworking]
* Address: Rua Dona Maria Dulce Nogueira Garcez, 55 - Pinheiros, São Paulo - SP, 05424-070, Brazil

=== How to get from Hotel to Venue ===
* Venue is located 550 mts away from the hotel.
* You can check the directions on [https://goo.gl/maps/y5B222f7pVA2 Google Maps here].
* Or check this map below to see how to get there:
[[image:Brazil_Meetup_Venue_to_Hotel.png|600px]]

=== How to get from Airport to Hotel ===
* Details in [https://goo.gl/maps/Vm4keFWtJxz Google Maps].
** Take the bus at the Airport direction to Praça República
** Make the connection in Praça República with the subway, Line 4 (Butanta).
** Faria Lima is the third stop.
** Cross the avenue and walk on Av. Brg. Faria Lima.
** Turn on Rua Diogo Moreira until the number 247.

=== Food ===
Food during the event will be included. Coffee Breaks and Lunch will be served at the venue. Breakfast is included at the hotel.

For dinners will be organized and paid by Mozilla:
* Friday: TBD
* Saturday: TBD
* Sunday: TBD

On dinners (jantar) alcoholic drinks will not be included. Is totally ok if you want to drink but it will not be cover by Mozilla.

=== Weather ===
*[https://weather.com/weather/tenday/l/BRSP1524:1:BR Weather.com says:]
** Friday May 27th Partly Cloudy High: 26°C Low: 16°C Precipitations: 20% Hum: 63%
** Saturday May 28th Mostly Sunny High: 26°C Low: 16°C Precipitations: 10% Hum: 59%
** Sunday May 29th Mostly Sunny High: 26°C Low: 15°C Precipitations: 20% Hum: 59%

=== Reimbursement policy ===
* All participants who requesting reimbursement for their expenses need to add their expenses on [https://bugzilla.mozilla.org/show_bug.cgi?id=1274573 bug #1274573]. If you have any questions, please contact Guillermo or Francisco Picolini about it.

== Participants ==
=== Contributors ===
* This is a list of all participants of the event: <br><br>
** [https://mozillians.org/en-US/u/dricupello/ Adriano Cupello]
** [https://mozillians.org/en-US/u/andregarzia/ Andre Garzia]
** [https://mozillians.org/en-US/u/du.barros/ Eduardo Barros]
** [https://mozillians.org/en-US/u/Zuardi/ Fabrizio Zuardi]
** [https://mozillians.org/en-US/u/felipez3r0/ Felipe do Espirito Santo]
** [https://mozillians.org/en-US/u/geraldobarros/ Geraldo Barros]
** [https://mozillians.org/en-US/u/tortoyoyo/ Guilherme Berghauser]
** [https://mozillians.org/en-US/u/jaimemaretoli/ Jaime Maretoli]
** [https://mozillians.org/en-US/u/lennoazevedo/ Lenno Azevedo]
** [https://mozillians.org/en-US/u/luiguild/ Luigi Delyer]
** [https://mozillians.org/en-US/u/FxHelp/ Marco Aurelio Krause]
** [https://mozillians.org/en-US/u/marinalimeira/ Marina Limeira]
** [https://mozillians.org/en-US/u/samuelmoraesf/ Samuel Moraes]
** Brenno Leal
** [https://mozillians.org/es/u/FabioBeneditto/ Fabio Beneditto]
** [https://mozillians.org/es/u/cynthiapereira/ Cynthia Pereira]
** Diego Gonzaga
** [https://mozillians.org/es/u/eme3mil/ Emerson Engroff]
** [https://mozillians.org/es/u/dutrafox/ Nelson Dutra Junior]
** [https://mozillians.org/es/u/RodrigoSilva/ Rodrigo Silva]
** [https://mozillians.org/es/u/edivania.edc/ Edivania Dias]
** [https://mozillians.org/es/u/julianadfg/ Juliana Goncalves]

=== Mozilla Staff ===
* Participation Team: [https://mozillians.org/en-US/u/deimidis/ Guillermo Movia],[https://mozillians.org/en-US/u/nukeador/ Rubén Martin]

== Contact persons ==
* Guillermo Movia (gmovia[at]mozilla[dot]com) - phone numbers will be provided in mails.

== Communication ==
* Hashtag: #mozbrazil16
* Brazil Mailing list

Participation/Community Gatherings/Brazil 2016

2016-05-26T15:14:14Z

Deimidis: /* Participants */ added collaborators

< [[Participation/Community_Gatherings]]

= Brazil 2016 =

== Overview ==

Brazil is the biggest community in Latin America, and one of our 10 focus countries. Is difficult that a great number of Brazilian community members participate on big Mozilla’s events at the same time, so we think is a great place to begin the work on Regional Institutes.

At the same time is a community with several layers that don’t always integrate well. There are community members that participate in the community for the last 10 years, and new ones with lots of new ideas. But they are struggling to organize.

=== Goals ===
* Clear participation plans for our two major initiatives (Campus Campaign and Connected Devices)
* All the participants agree on a communication process and channel
* Participants report having learned at the event and are motivated to work on the initiatives
* There is an improvement in the health in the Brazilian community. This will be measure with before and after surveys

=== Code of Conduct ===
* As for every Mozilla event, we have a [[Participation/Community Gatherings/Brazil 2016/Code of Conduct|Code of Conduct for all the participants]].

== When ==
* Friday May 27th- Arrival Day (dinner with all participants)
* Saturday - May 28th - First day of meetup
* Sunday - May 29th - Second day of meetup
* Sunday evening/ Monday May 30th - Departure day.

==Schedule ==
* Schedule can be consulted [[Participation/Community Gatherings/Brazil 2016/Schedule|here]].
* Highlights:

== Logistics ==

=== Accommodation ===
* Participants will stay at [http://www.atlanticahotels.com.br/hotel/sao-paulo/quality-faria-lima Quality Hotel Faria Lima]
** Address: Rua Diogo Moreira, 247 - Pinheiros, São Paulo - SP, 05423-010, Brazil
** All participants will share double rooms

=== Venue ===
The event will take place at the [http://www.mutuacoworking.com.br/ Mutua Coworking]
* Address: Rua Dona Maria Dulce Nogueira Garcez, 55 - Pinheiros, São Paulo - SP, 05424-070, Brazil

=== How to get from Hotel to Venue ===
* Venue is located 550 mts away from the hotel.
* You can check the directions on [https://goo.gl/maps/y5B222f7pVA2 Google Maps here].
* Or check this map below to see how to get there:
[[image:Brazil_Meetup_Venue_to_Hotel.png|600px]]

=== How to get from Airport to Hotel ===
* Details in [https://goo.gl/maps/Vm4keFWtJxz Google Maps].
** Take the bus at the Airport direction to Praça República
** Make the connection in Praça República with the subway, Line 4 (Butanta).
** Faria Lima is the third stop.
** Cross the avenue and walk on Av. Brg. Faria Lima.
** Turn on Rua Diogo Moreira until the number 247.

=== Food ===
Food during the event will be included. Coffee Breaks and Lunch will be served at the venue. Breakfast is included at the hotel.

For dinners will be organized and paid by Mozilla:
* Friday: TBD
* Saturday: TBD
* Sunday: TBD

=== Weather ===
*[https://weather.com/weather/tenday/l/BRSP1524:1:BR Weather.com says:]
** Friday May 27th Partly Cloudy High: 26°C Low: 16°C Precipitations: 20% Hum: 63%
** Saturday May 28th Mostly Sunny High: 26°C Low: 16°C Precipitations: 10% Hum: 59%
** Sunday May 29th Mostly Sunny High: 26°C Low: 15°C Precipitations: 20% Hum: 59%

=== Reimbursement policy ===
* All participants who requesting reimbursement for their expenses need to add their expenses on [https://bugzilla.mozilla.org/show_bug.cgi?id=1274573 bug #1274573]. If you have any questions, please contact Guillermo or Francisco Picolini about it.

== Participants ==
=== Contributors ===
* This is a list of all participants of the event: <br><br>
** [https://mozillians.org/en-US/u/dricupello/ Adriano Cupello]
** [https://mozillians.org/en-US/u/andregarzia/ Andre Garzia]
** [https://mozillians.org/en-US/u/du.barros/ Eduardo Barros]
** [https://mozillians.org/en-US/u/Zuardi/ Fabrizio Zuardi]
** [https://mozillians.org/en-US/u/felipez3r0/ Felipe do Espirito Santo]
** [https://mozillians.org/en-US/u/geraldobarros/ Geraldo Barros]
** [https://mozillians.org/en-US/u/tortoyoyo/ Guilherme Berghauser]
** [https://mozillians.org/en-US/u/jaimemaretoli/ Jaime Maretoli]
** [https://mozillians.org/en-US/u/lennoazevedo/ Lenno Azevedo]
** [https://mozillians.org/en-US/u/luiguild/ Luigi Delyer]
** [https://mozillians.org/en-US/u/FxHelp/ Marco Aurelio Krause]
** [https://mozillians.org/en-US/u/marinalimeira/ Marina Limeira]
** [https://mozillians.org/en-US/u/samuelmoraesf/ Samuel Moraes]
** Brenno Leal
** [https://mozillians.org/es/u/FabioBeneditto/ Fabio Beneditto]
** [https://mozillians.org/es/u/cynthiapereira/ Cynthia Pereira]
** Diego Gonzaga
** [https://mozillians.org/es/u/eme3mil/ Emerson Engroff]
** [https://mozillians.org/es/u/dutrafox/ Nelson Dutra Junior]
** [https://mozillians.org/es/u/RodrigoSilva/ Rodrigo Silva]
** [https://mozillians.org/es/u/edivania.edc/ Edivania Dias]
** [https://mozillians.org/es/u/julianadfg/ Juliana Goncalves]

=== Mozilla Staff ===
* Participation Team: [https://mozillians.org/en-US/u/deimidis/ Guillermo Movia],[https://mozillians.org/en-US/u/nukeador/ Rubén Martin]

== Contact persons ==
* Guillermo Movia (gmovia[at]mozilla[dot]com) - phone numbers will be provided in mails.

== Communication ==
* Hashtag: #mozbrazil16
* Brazil Mailing list

Participation/Community Gatherings/Brazil 2016

2016-05-26T01:02:23Z

Deimidis: /* Contributors */

< [[Participation/Community_Gatherings]]

= Brazil 2016 =

== Overview ==

Brazil is the biggest community in Latin America, and one of our 10 focus countries. Is difficult that a great number of Brazilian community members participate on big Mozilla’s events at the same time, so we think is a great place to begin the work on Regional Institutes.

At the same time is a community with several layers that don’t always integrate well. There are community members that participate in the community for the last 10 years, and new ones with lots of new ideas. But they are struggling to organize.

=== Goals ===
* Clear participation plans for our two major initiatives (Campus Campaign and Connected Devices)
* All the participants agree on a communication process and channel
* Participants report having learned at the event and are motivated to work on the initiatives
* There is an improvement in the health in the Brazilian community. This will be measure with before and after surveys

=== Code of Conduct ===
* As for every Mozilla event, we have a [[Participation/Community Gatherings/Brazil 2016/Code of Conduct|Code of Conduct for all the participants]].

== When ==
* Friday May 27th- Arrival Day (dinner with all participants)
* Saturday - May 28th - First day of meetup
* Sunday - May 29th - Second day of meetup
* Sunday evening/ Monday May 30th - Departure day.

==Schedule ==
* Schedule can be consulted [[Participation/Community Gatherings/Brazil 2016/Schedule|here]].
* Highlights:

== Logistics ==

=== Accommodation ===
* Participants will stay at [http://www.atlanticahotels.com.br/hotel/sao-paulo/quality-faria-lima Quality Hotel Faria Lima]
** Address: Rua Diogo Moreira, 247 - Pinheiros, São Paulo - SP, 05423-010, Brazil
** All participants will share double rooms

=== Venue ===
The event will take place at the [http://www.mutuacoworking.com.br/ Mutua Coworking]
* Address: Rua Dona Maria Dulce Nogueira Garcez, 55 - Pinheiros, São Paulo - SP, 05424-070, Brazil

=== How to get from Hotel to Venue ===
* Venue is located 550 mts away from the hotel.
* You can check the directions on [https://goo.gl/maps/y5B222f7pVA2 Google Maps here].
* Or check this map below to see how to get there:
[[image:Brazil_Meetup_Venue_to_Hotel.png|600px]]

=== How to get from Airport to Hotel ===
* Details in [https://goo.gl/maps/Vm4keFWtJxz Google Maps].
** Take the bus at the Airport direction to Praça República
** Make the connection in Praça República with the subway, Line 4 (Butanta).
** Faria Lima is the third stop.
** Cross the avenue and walk on Av. Brg. Faria Lima.
** Turn on Rua Diogo Moreira until the number 247.

=== Food ===
Food during the event will be included. Coffee Breaks and Lunch will be served at the venue. Breakfast is included at the hotel.

For dinners will be organized and paid by Mozilla:
* Friday: TBD
* Saturday: TBD
* Sunday: TBD

=== Weather ===
*[https://weather.com/weather/tenday/l/BRSP1524:1:BR Weather.com says:]
** Friday May 27th Partly Cloudy High: 26°C Low: 16°C Precipitations: 20% Hum: 63%
** Saturday May 28th Mostly Sunny High: 26°C Low: 16°C Precipitations: 10% Hum: 59%
** Sunday May 29th Mostly Sunny High: 26°C Low: 15°C Precipitations: 20% Hum: 59%

=== Reimbursement policy ===
* All participants who requesting reimbursement for their expenses need to add their expenses on [https://bugzilla.mozilla.org/show_bug.cgi?id=1274573 bug #1274573]. If you have any questions, please contact Guillermo or Francisco Picolini about it.

== Participants ==
=== Mozilla Staff ===
* Participation Team: [https://mozillians.org/en-US/u/deimidis/ Guillermo Movia],[https://mozillians.org/en-US/u/nukeador/ Rubén Martin]

== Contact persons ==
* Guillermo Movia (gmovia[at]mozilla[dot]com) - phone numbers will be provided in mails.

== Communication ==
* Hashtag: #mozbrazil16
* Brazil Mailing list

L10n:Meetings/2016 BuenosAires hackathon

2016-05-22T16:59:25Z

Deimidis: /* Goals */

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
Lezica 4358 Buenos Aires

Map: https://goo.gl/maps/cMtL34vSBMC2

;When:
May21-22

;Lodging:
'''AirBNB Cype:'''

Map: http://bit.ly/1WBlTFg

Who: Fernando, Vedran, <b>RICHARD</b>, Alcides

'''AirBNB Juan:'''

Map: http://bit.ly/1WBlTFg

Who: Marcelo, Abelardo, <b>JEFF</b>

'''AirBNB Fernando:'''

Map: http://bit.ly/1WBlTFg

Who: Zulma, Limpia, <b>DELPHINE</b>

'''AirBNB Victoria:'''

Map: http://bit.ly/1WBlTFg

Who: <b>HUGO</b> y familia

;Arriving at lodging:
From Guillermo, "I use to use to the airport is [http://www.tiendaleon.com/resultados/busqueda/bus/ Manuel Tienda Leon bus] (Ezeiza to Terminal Madero). If you take the bus, you will need a taxi from Manuel Tienda León office, but still will be lot cheaper than the taxi from Ezeiza. (A$300 max / US$21).

You could find the place for this service just outside customs. At Ezeiza you have two doors between customs and the real exit, in the middle of those two doors, you will find all the cabs and transport service, Manuel Tienda Leon is at the left. You could pay with credit card and price is fixed."

Another option is to hire a prepaid taxi (remis), also located just outside of customs. Taxi EZE is one service that would be good to use. The price is A$580 max / US$41.

;Reimbursements:

We're able to reimburse your transport expenses between the airport, autobus, and your lodging. Save your receipts! Reimbursement offers are only good for up to one month after the hackathon. Please notify Jeff or Delphine in advance if you will need reimbursement for these expenses.

;Communication with Telegram:
* Join the Telegram group here: https://telegram.me/joinchat/BNisygggAOrdAE4o69cAeQ

==Goals==
;Esperanto (probably not present)
* Goal for this year: complete style guide
* Recruit new members

;Spanish (Argentina)
* Transition to a new responsible for Web repositories
* Start using Pontoon as a default Web translation tool -Done - Projects requested and approved
** have a tutorial session (useful for all communities present)
** manage pontoon permissions -Done- Gabriela and Marcelo have approval permissions
* Create a transition plan for the community
* Finish everything that is in this webpage: https://l10n.mozilla-community.org/webdashboard/?locale=es-AR - Done
* Start review process of Web page translations (to have consistency between pages)
* Define between "formal" and "informal" translation for products and web and align those categories -Done- moving to informal. Now we have to define process.
** We decide to work with Translator students for this
** And this will be made independently, working outside Pontoon (because of the time it will take will be more than 6 weeks)
* Plan to recruit new localizers
** We have a list of people interested in collaborate
** Collaborate with a translator school
* Create first draft of l10n style guide into es-AR.

;Spanish (Chile)
* Start Firefox for Android localization. Goal is to make good progress during the hackathon, so that it is finished by August. Tool: Pontoon
* Discuss possible change of "usted" to "tu" for Firefox Desktop (because the use is inconsistent with other products at the time)
* Learn more about "accesskeys", that in es-CL we maintain with it's English variation
* Create first draft of l10n style guide into es-CL.

;Guaraní
* Start Firefox for Android localization.
* Make a step-by-step guide to introduce new groups to using pootle for localization into Guaraní.
* Create first draft of l10n style guide into Guaraní.

;Mozilla Nativo
* Receive training on the full localization process for each Mozilla product.
* Recruit new members and localizer.
* Review and finish the Mozilla Nativo Wiki Page.
* Complete the Mozilla Nativo manual.

==Agenda==
===Friday May 20 ===
For anyone arriving early, [https://public.etherpad-mozilla.org/p/Bs_As_Sightseeing here are some sightseeing suggestions from Pablo.]
;Dinner - 2100
*[http://theoldest.com.ar/ The Oldest] Dirección: Ambrosetti 33
===Saturday May 21 ===
;Morning - 900AM
*Introductions, spectrograms & goals review -- Jeff & Delphine
*Mozilla mission and org updates applied to your locales -- Jeff & Delphine
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
**Localization quality discussion
*L10n updates from each community (10 minutes each)
**Active projects
**Translation workflow
**Successes
**Challenges
;Lunch -- TBD
;Afternoon
*Breakouts
**Creating glossaries & style guides for translation quality
**Pootle & Pontoon How-to
**Firefox for Android/iOS l10n testing
*Review of breakout session outcomes
;Dinner -- 2030
* El Patio de Liliana, Bartolomé Mitre 3986 https://goo.gl/maps/e9wxvvv8tq72

===Sunday May 22===
;Morning -- 900AM
*Breakouts
**Style guides
***https://wiki.mozilla.org/L10n:Teams:es-AR/Style_Guide
***https://wiki.mozilla.org/L10n:Teams:es-CL/Style_Guide
***https://wiki.mozilla.org/L10n:Teams:gn-PY/Style_Guide
**Localization community planning
***Sustainability
***Product launches
***Recruitment
**Localization work focused on l10n community hackathon goals
;Lunch -- 1300 Empanadas en Lezica
;Afternoon
*Breakouts
**l10n community goals for hackathon
*Update team wiki pages
*Take [http://www.surveygizmo.com/s3/2607845/6a540ca0c4ca l10n hackathon survey].
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- 2230
* El Club de la Milanesa, Av. Rivadavia 4945 https://goo.gl/maps/HQxyg26XArP2

==Other==
*Hashtag for event: #mozl10nbuenosaires
*Event on Reps Page: https://reps.mozilla.org/e/l10n-meetings-2016-buenos-aires-hackathon/
;Weather
*Friday 9° min 15° max
*Saturday 9° min 14° max
*Sunday 8° min 14° max
*Monday 9° min 14° max
;Notes: https://public.etherpad-mozilla.org/p/BuenosAires-l10n-meetup-notes
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://pontoon.mozilla.org/ Pontoon translation tool]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://transvision.mozfr.org/ Transvision QA tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

L10n:Teams:es-AR/Style Guide

2016-05-22T14:38:05Z

Deimidis: /* Brands, copyright, and trademark */ Adding paragraph and small code edits

== Intro ==

Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla's localization communities on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. Some examples of international style guides created by other organizations are:

* https://help.apple.com/asg/mac/2013/ASG_2013.pdf
* https://www.microsoft.com/Language/en-US/StyleGuides.aspx

This style guide is broken up into two main parts: the first contains rules that are language-specific and must be defined by each Mozilla l10n community (covering language-specific style, terminology, and units); the second contains general rules that Mozilla has defined for translators of all languages that can help you translate well (covering principles of accuracy and fluency). Please adapt part one of this style guide to your l10n community's rules for style, terminology, and units. Wherever possible, refer to existing national standards for units, spelling, and grammar in your community's adaptation of the first part of this style guide.

== Language-specific Mozilla style ==

== Style ==

<div id="magicdomid16">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Your localization community's style is largely up to you to define. It is a part of your community's instructions and standards for translating strings within each project type. Style encompasses various elements, such as formality, tone, natural expression, handling cultural references, idioms, or slang, and maintaining consistency with Mozilla and 3rd party branding and style guides. Your localization community should define these style elements for localizing Mozilla projects into your language. Let's go through these main aspects of Style.</span>

</div>
<div id="magicdomid17">

</div>
===== Formality and Tone =====

We currently use formal tone on Firefox Desktop and informal tone on Firefox for Android and web content.
This will change in a recent future, so please check later.
If it's possible, begin with the verb. For example "haga clic aquí" instead of "usted haga clic aquí"

===== Natural expression =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Using natural expressions make your localization sound natural to a native speaker. If your translation does not follow the community defined language guidelines for translating content that contains local or natural expressions, this results in a mediocre and/or awkward translation. Teams should be careful to address those and keep them in mind while translating, which is why it is an important section to address in a Style Guide. An example of a natural expression in a translation would be translating the Spanish phrase, "En ocho días." In English, one might translate this as, "in eight days" or "in a week." The latter is the more natural translation, although both could be considered correct. </span>

</div>
<div>

</div>
<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In this section, form guidelines for how to perform a natural sounding localization. This might take some time and experience to find the right examples to include or create the right guidelines for your language.</span>

</div>
<div>

</div>
===== Handling cultural references, idioms, and slang =====
Cultural references, idioms, and slang require a full understanding of these references between the cultures of your source and target languages. An example of a cultural reference in English would be the phrase, "kick-off meeting." This is a reference that uses an American football term. It means a meeting to begin a project. To translate it, you can follow one of two approaches:

# Find an equivalent reference phrase in your language.
# Remove the cultural reference and translate the core meaning (e.g., "a commencement meeting")

If you can't find an equivalent, then you may remove the reference.
Even in the informal products, you shouldn't use argentinian slang.

===== Style consistency =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Finally, adherence to Mozilla and third-party branding and style guides should be respected throughout a localization project. More information on Mozilla-specific branding rules can be found here: </span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z url">https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/</span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">. For example, some brand names should never be translated, such as "Firefox". For other brands that do not have any branding guidelines, your localization community must define whether to translate them. Be extra careful to check on branding rules before deciding to translate a name or not (whether for Mozilla or for a third-party) and to list them here in your community's l10n style guide.</span>

</div>
<div>

</div>
<div>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''Terminology'''</span> ===

<div id="magicdomid29">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):</span>

</div>
<ul>
<li><div id="magicdomid30">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Microsoft key terms and target languages </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://www.microsoft.com/Language/en-US/Default.aspx</span></li>
<li><div id="magicdomid31">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Pootle's own term list: </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://mozilla.locamotion.org/xx/terminology/essential.po</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> (replace *xx* with a locale code)</span></li></ul>

<div id="magicdomid33">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">You should be consistent in the use of existing reliable appropriate term bases in your language. These term bases could be developed and approved by the community, or leveraged from another party that adhere to national, international or local standards</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> for software and internet terminology</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">. Avoid</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> the following:</span>

</div>
<ul>
<li><div id="magicdomid34">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology within the project</span></li>
<li><div id="magicdomid35">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology with term base</span></li>
<li><div id="magicdomid36">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology across all of your projects</span></li>
<li><div id="magicdomid37">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">U</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">sing terminology from another subject matter (e.g., don't use medical terminology in Firefox)</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">.</span></li></ul>

===== '''Tips on translating difficult concepts''' =====
Translating terms representing difficult concepts is a tricky task. Here are some ideas to help you translate terms that do not have equivalents in your language:

* Understand the meaning of the term in English. Definitions of a few key terms http://techterms.com/category/internet
* Know your product and understand the function of the feature.
* Consider similar ideas for those functions in your culture.
* Associate a culturally specific image with the meaning and function of the term.
* Ask to another member of the team

===== '''Developing new term bases''' =====
If you find a term that was never translated, please keep in mind the following.
* Avoid overly borrowing English expressions, only use them when it's a common use and there's no word in our language (e.g. You should use the word clic instead of click)
* Referencing another language from the same language family may inspire you to come up with your own terms

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and Grammar </span> ===

<div id="magicdomid57">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many elements of unit or grammar do not exist or apply to all languages. If you find one of these elements that does not apply to your language, please remove it from your style guide.</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

</div>
<div id="magicdomid58">

</div>
<div id="magicdomid59">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

</div>
<div id="magicdomid60">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Units and Unit Conversion</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Date Format</span> =====

<div id="magicdomid64">

The date formats for weeks and months are expressed in the following form:

</div>
<ul>
Fully spelled out
<li><div id="magicdomid65">

The order of Year, Month and Day is day, month, year.

<div id="magicdomid66">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Reference material can be find here: </span>https://en.wikipedia.org/wiki/Date_format_by_country

</div>
<div>

</div>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">C</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">alendar</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> view: </span> =====

<ul>
<li><div id="magicdomid68">

</div>
The first day of the week is Sunday
<li><div id="magicdomid69">

</div>
No other regional calendar is observed.

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Time Format</span> =====

<div id="magicdomid72">

Time is expressed in hours, minutes and seconds.

</div>
<div>

</div>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Numerals </span> =====

<div id="magicdomid76">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are numerals an</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">d percentages</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> expressed in your language? </span>

</div>
<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. </span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Currency </span> =====

<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are other widely used currency and symbols used in your country/language for paid apps. </span>

</div>
<div id="magicdomid79">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span> =====

<div id="magicdomid81">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their measurement system.</span>

</div>
<div id="magicdomid82">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Name</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">s</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid84">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are the order of family name and given name in your language</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> Here is the guideline on the naming convention from w3c.org:</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Address and Postal Code Format </span> =====

<div id="magicdomid87">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the format in your language?  </span>

</div>
<div id="magicdomid88">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: most Asian countries start from big to small: [Country] [postal code][state/province][city][district][street number and name][building and suite numbers][addressee]</span>

</div>
<div id="magicdomid89">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Countries of European languages start from small to big: [addressee][street number and name][building and suite numbers][district][city][state/province][postal code][Country]</span>

</div>
<div id="magicdomid90">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   </span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Telephone Number format</span> =====

<div id="magicdomid92">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Space separators between digits can be different for area codes such as State (Province) and City, </span>

</div>
<div id="magicdomid94">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Spelling And Grammar Checks'''</span> ====

<div id="magicdomid96">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many languages have national or international standards that define spelling and grammar rules. When defining these rules for your community, make reference to those standards wherever possible. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have automated tests for spell checking and grammar</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">List those tools and dictionaries here and how regularly they should be used.</span>

</div>
<div id="magicdomid97">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Tense'''</span> =====

<div id="magicdomid99">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">? What is your policy on tense consistency for certain use cases? For example, for phrases that ask a user to make an action (like "Download Firefox"), do you use a future tense, a command tense, or a neutral tense? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Grammatical_tense</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid100">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Word Forms'''</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Pluralization  </span> =====

<div id="magicdomid106">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing pluralization in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">L</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ist all forms of plural forms and examples if there is more than one. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Additional discussions can be found Here. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and here: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html</span>

</div>
<div id="magicdomid107">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Abbreviations  </span> =====

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are abbreviations expressed in your language?</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span><br />
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example, in English, abbreviations are made by removing most vowels and only using the first 3-5 consonants followed by a period (e.g., abbreviation = abbr.).</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">[https://en.wikipedia.org/wiki/Abbreviation%29 https://en.wikipedia.org/wiki/Abbreviation)]</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If your language does not have a standard way of expressing abbreviations, do you simply leave them in English?</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Acronyms </span> =====

<div id="magicdomid113">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Are there standard</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> translat</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ions of</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> widely accepted acronyms such as CD, DVD, MB</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language? If not, do they remain in English?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Acronym</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Punctuation'''</span> =====

<div id="magicdomid117">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use different punctuation rules in your Firefox localization than what your language standard defines? </span>

</div>
<div>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example: do you use a period at the end of every user interface element translation or only some? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">W</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">hat is the international/national standard for punctuation in your language</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">?</span>

</div>
<div id="magicdomid118">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Emphasis</span> =====

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Is there an international/national standard for capitalization</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> in your language? </span>

* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If so, do those standard rules apply in all product translations? </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">f this doe</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">sn</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">'t apply, how </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">do you</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> indicate importance or name of a movie, book title, product UIs (</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq u">S</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ave, </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj u">F</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ile...)</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">How does your language handle the use of bold, italic, or underline types to express emphasis?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ( See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Italic_type</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Hyphens and compounds </span> =====

<div id="magicdomid123">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">way</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> of </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">using</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> hyphens and compounds in your language? ( </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Compound_%28linguistics%29</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ) </span>

</div>
<div id="magicdomid124">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Prepositions and articles</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span> =====

<div id="magicdomid126">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing prepositions and articles in your language?</span>

</div>
<div id="magicdomid127">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Diacritics and </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Special characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid129">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language use</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> any special </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or accented characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and will they be applied and preserved in sort orders, and other aspects of the translation</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Diacritic</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid130">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Quotes  </span> =====

<div id="magicdomid132">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language have a standard use for quotation marks, parenthesis, or brackets?</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Whitespace </span> =====

<div id="magicdomid135">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language require the</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> use of white space around words, sentences, paragraphs, etc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">.? If so, in what ways?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== '''User Interface Elements''' =====
* '''Titles''' : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text.
* '''Buttons''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancelar", "Borrar historial", "Agregar correo electrónico", "Seleccionar todo", etc.
* '''Value Selector Lists''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words.
* '''Articles''': Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface.
* '''Ellipsis''': Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such. It's preferable to use the ellipsis character (…) instead of three dots.

== General Mozilla l10n style ==

=== Accuracy ===

==== Meaning-based translation ====

When it comes to translation, meaning is everything. A translator needs to understand the source text's meaning exactly. You then find its most closely linked equivalent in your own language, without adding or subtracting meaning in your translation. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:

* What does this word/sentence/string mean in English?
* What is the message the author is trying to send?
* How would I express that meaning in my own language?

Sometimes translation memory and machine translation tools can offer bad suggestions for a translation. If you use either as part of your translation workflow, make sure to correct the suggestions before submitting them. Avoid literal translation at all costs. Watch out for words that might sound or look the same between English and your language, but have a different meaning.

On technical documents, take a look to some words that had a standard localization. If you are unsure, you could ask on the localization mailing list.

==== Should not be translated ====

===== Access Keys =====

Access keys allow a computer to immediately jump to a particular part in a web page by combining keystrokes. They can be adapted to suit your language by selecting a single character to be used in the combined keystroke. Access keys have their own lines within .dtd and .properties files and are identified by being named ".accesskey" in the line.

===== Variables =====

Variables should never be translated. You can recognize a variable within a string by its beginning with a specific character (e.g., $, #, %, etc.) followed by a combination of words without spacing. For example, $BrandShortName and %S are variables. You can move a variable around within a string, if the translation of the string requires it.

===== Brands, copyright, and trademark =====

Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the [https://www.mozilla.org/en-US/styleguide/communications/translation/ Mozilla branding guide] for more details.

===== Translating culture-specific references =====

At times there will be English content included in Mozilla products or web projects (e.g., marketing campaigns) that makes references to American culture and concepts. When translating these, it is best to find an equivalent cultural reference within your own culture that accurately conveys the meaning of the English reference.

For example, an US citizen might say, "Good job, home run!" A home run is a baseball reference for a successful outcome. An appropriate translation would be an equivalent metaphor within your culture. Using soccer as an example, you might translate "Good job, home run!" into "Good job, nice goal!" in your language.

Also, there are specific Mozilla related concepts and localization, based on projects names and cultures. A person that participate in the organization is known like: "Mozillian", and these concepts had their own localized version. In this case "Mozillian" is translated liked "Mozillero".

Mozilla events names are not localized. E.g: "Mozilla Summit" or "Mozilla All Hands" are events names that we maintained in their original form.

==== Legal content ====

Mozilla projects will often contain legal content in the form of user agreements, privacy statements, etc. When reviewing the translation of legal content, Mozilla localizers should do so according to the criteria concerning accuracy, fluency, style, and terminology found within this style guide and according to Mozilla culture and values.

=== Fluency ===

To produce a fluent translation, not only should the translation follow the language's standard grammar, punctuation, and spelling rules, but it should avoid being ambiguous, incoherent, or inconsistent, and unintelligible.

To avoid ambiguity, the translator must thoroughly understand the meaning behind the source text, including any references that text might include. For example, if the English source text uses the word, "it", the translator must know what "it" is to avoid an ambiguous translation. Clearly understanding the source text will also allow a translator to make the source text's logical connections in their own translation. This helps to keep the translation coherent.

Inconsistency can pop up in many forms. A translator must be consistent in their use of abbreviations, references, and links within each localization project. They must also be consistent with Mozilla and the localization communities' style guides and approved terminology. Abbreviations, like terminology, should come from either a standard reference (like a dictionary of abbreviations) or should follow your language's rules for creating abbreviations. Once used, the abbreviation must remain consistent every place that it is used in the translation. Cross-references (or links) must also be consistently used within a translation. If a text contains a hyperlink URL to a support article in English, the translation should also contain a hyperlink to a translation of that support article (if available) or the English version. Links should not redirect to other pages nor should they be broken and unusable.

Finally, there are times that a translation simply doesn't make sense. It's hard to put your finger on what exactly is wrong with it, but you know it is unintelligible and not fluent. While this is uncommon, it's important to report these unintelligible translations and offer suggestions to correct them.

L10n:Teams:es-AR/Style Guide

2016-05-22T14:21:22Z

Deimidis: /* Meaning-based translation */

== Intro ==

Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla's localization communities on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. Some examples of international style guides created by other organizations are:

* https://help.apple.com/asg/mac/2013/ASG_2013.pdf
* https://www.microsoft.com/Language/en-US/StyleGuides.aspx

This style guide is broken up into two main parts: the first contains rules that are language-specific and must be defined by each Mozilla l10n community (covering language-specific style, terminology, and units); the second contains general rules that Mozilla has defined for translators of all languages that can help you translate well (covering principles of accuracy and fluency). Please adapt part one of this style guide to your l10n community's rules for style, terminology, and units. Wherever possible, refer to existing national standards for units, spelling, and grammar in your community's adaptation of the first part of this style guide.

== Language-specific Mozilla style ==

== Style ==

<div id="magicdomid16">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Your localization community's style is largely up to you to define. It is a part of your community's instructions and standards for translating strings within each project type. Style encompasses various elements, such as formality, tone, natural expression, handling cultural references, idioms, or slang, and maintaining consistency with Mozilla and 3rd party branding and style guides. Your localization community should define these style elements for localizing Mozilla projects into your language. Let's go through these main aspects of Style.</span>

</div>
<div id="magicdomid17">

</div>
===== Formality and Tone =====

We currently use formal tone on Firefox Desktop and informal tone on Firefox for Android and web content.
This will change in a recent future, so please check later.
If it's possible, begin with the verb. For example "haga clic aquí" instead of "usted haga clic aquí"

===== Natural expression =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Using natural expressions make your localization sound natural to a native speaker. If your translation does not follow the community defined language guidelines for translating content that contains local or natural expressions, this results in a mediocre and/or awkward translation. Teams should be careful to address those and keep them in mind while translating, which is why it is an important section to address in a Style Guide. An example of a natural expression in a translation would be translating the Spanish phrase, "En ocho días." In English, one might translate this as, "in eight days" or "in a week." The latter is the more natural translation, although both could be considered correct. </span>

</div>
<div>

</div>
<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In this section, form guidelines for how to perform a natural sounding localization. This might take some time and experience to find the right examples to include or create the right guidelines for your language.</span>

</div>
<div>

</div>
===== Handling cultural references, idioms, and slang =====
Cultural references, idioms, and slang require a full understanding of these references between the cultures of your source and target languages. An example of a cultural reference in English would be the phrase, "kick-off meeting." This is a reference that uses an American football term. It means a meeting to begin a project. To translate it, you can follow one of two approaches:

# Find an equivalent reference phrase in your language.
# Remove the cultural reference and translate the core meaning (e.g., "a commencement meeting")

If you can't find an equivalent, then you may remove the reference.
Even in the informal products, you shouldn't use argentinian slang.

===== Style consistency =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Finally, adherence to Mozilla and third-party branding and style guides should be respected throughout a localization project. More information on Mozilla-specific branding rules can be found here: </span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z url">https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/</span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">. For example, some brand names should never be translated, such as "Firefox". For other brands that do not have any branding guidelines, your localization community must define whether to translate them. Be extra careful to check on branding rules before deciding to translate a name or not (whether for Mozilla or for a third-party) and to list them here in your community's l10n style guide.</span>

</div>
<div>

</div>
<div>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''Terminology'''</span> ===

<div id="magicdomid29">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):</span>

</div>
<ul>
<li><div id="magicdomid30">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Microsoft key terms and target languages </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://www.microsoft.com/Language/en-US/Default.aspx</span></li>
<li><div id="magicdomid31">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Pootle's own term list: </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://mozilla.locamotion.org/xx/terminology/essential.po</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> (replace *xx* with a locale code)</span></li></ul>

<div id="magicdomid33">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">You should be consistent in the use of existing reliable appropriate term bases in your language. These term bases could be developed and approved by the community, or leveraged from another party that adhere to national, international or local standards</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> for software and internet terminology</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">. Avoid</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> the following:</span>

</div>
<ul>
<li><div id="magicdomid34">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology within the project</span></li>
<li><div id="magicdomid35">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology with term base</span></li>
<li><div id="magicdomid36">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology across all of your projects</span></li>
<li><div id="magicdomid37">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">U</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">sing terminology from another subject matter (e.g., don't use medical terminology in Firefox)</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Tips on translating difficult concepts'''</span> =====

<div id="magicdomid40">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Translating terms representing difficult concepts is a tricky task. Here are some ideas to help you translate terms that do not have equivalents in your language:</span>

</div>
<ul>
<li><div id="magicdomid41">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Understand the meaning of the term in English. Definitions of a few key terms </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">http://techterms.com/category/internet</span></li>
<li><div id="magicdomid42">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Know your product and understand the function of the feature. </span></li>
<li><div id="magicdomid43">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider similar ideas for those functions in your culture.</span></li>
<li><div id="magicdomid44">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Associate a culturally specific image with the meaning and function of the term.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Developing new term base'''</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''s'''</span> =====

<div id="magicdomid47">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">What is your </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">community's</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> process </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">for</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> identifying and creating a new t</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ermbase</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">? Here are a few things to keep in mind:</span>

</div>
<ul>
<li><div id="magicdomid48">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Avoid </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">verly borrowing English expressions</span></li>
<li><div id="magicdomid49">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Referenc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ing</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> another language f</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">rom</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> the same language </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">family</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> may inspire you to come up with your own terms</span></li>
<li><div id="magicdomid50">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider the product target audience (age</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> level of literacy, education</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> social </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> economic status)</span></li>
<li><div id="magicdomid51">

</div>
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Will you use l</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">oan words</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> from another language</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or coin new terms in your language to maintain</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">language purity?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> Is there government requirement or policy to encourage creating new terms for new concepts</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">, o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">r </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">will </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">loan words </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">be sufficient to</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> reach broader masses </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> expedite new technology adoption</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span></li>
<li><div id="magicdomid52">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">If there are two acceptable scripts commonly used by the general public, what is the commonly used script on the web or government sites? What is the script used by major web technology companies?</span></li></ul>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and Grammar </span> ===

<div id="magicdomid57">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many elements of unit or grammar do not exist or apply to all languages. If you find one of these elements that does not apply to your language, please remove it from your style guide.</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

</div>
<div id="magicdomid58">

</div>
<div id="magicdomid59">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

</div>
<div id="magicdomid60">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Units and Unit Conversion</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Date Format</span> =====

<div id="magicdomid64">

The date formats for weeks and months are expressed in the following form:

</div>
<ul>
Fully spelled out
<li><div id="magicdomid65">

The order of Year, Month and Day is day, month, year.

<div id="magicdomid66">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Reference material can be find here: </span>https://en.wikipedia.org/wiki/Date_format_by_country

</div>
<div>

</div>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">C</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">alendar</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> view: </span> =====

<ul>
<li><div id="magicdomid68">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Which date is considered the first day of the week, Sunday or Monday?  </span></li>
<li><div id="magicdomid69">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Is Lunar calendar observed? Other regional calendar observed?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span></li></ul>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Time Format</span> =====

<div id="magicdomid72">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How is time expressed in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ncluding 0-24 hr expression, hour, minute and second.</span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Numerals </span> =====

<div id="magicdomid76">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are numerals an</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">d percentages</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> expressed in your language? </span>

</div>
<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. </span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Currency </span> =====

<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are other widely used currency and symbols used in your country/language for paid apps. </span>

</div>
<div id="magicdomid79">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span> =====

<div id="magicdomid81">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their measurement system.</span>

</div>
<div id="magicdomid82">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Name</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">s</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid84">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are the order of family name and given name in your language</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> Here is the guideline on the naming convention from w3c.org:</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Address and Postal Code Format </span> =====

<div id="magicdomid87">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the format in your language?  </span>

</div>
<div id="magicdomid88">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: most Asian countries start from big to small: [Country] [postal code][state/province][city][district][street number and name][building and suite numbers][addressee]</span>

</div>
<div id="magicdomid89">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Countries of European languages start from small to big: [addressee][street number and name][building and suite numbers][district][city][state/province][postal code][Country]</span>

</div>
<div id="magicdomid90">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   </span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Telephone Number format</span> =====

<div id="magicdomid92">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Space separators between digits can be different for area codes such as State (Province) and City, </span>

</div>
<div id="magicdomid94">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Spelling And Grammar Checks'''</span> ====

<div id="magicdomid96">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many languages have national or international standards that define spelling and grammar rules. When defining these rules for your community, make reference to those standards wherever possible. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have automated tests for spell checking and grammar</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">List those tools and dictionaries here and how regularly they should be used.</span>

</div>
<div id="magicdomid97">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Tense'''</span> =====

<div id="magicdomid99">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">? What is your policy on tense consistency for certain use cases? For example, for phrases that ask a user to make an action (like "Download Firefox"), do you use a future tense, a command tense, or a neutral tense? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Grammatical_tense</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid100">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Word Forms'''</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Pluralization  </span> =====

<div id="magicdomid106">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing pluralization in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">L</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ist all forms of plural forms and examples if there is more than one. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Additional discussions can be found Here. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and here: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html</span>

</div>
<div id="magicdomid107">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Abbreviations  </span> =====

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are abbreviations expressed in your language?</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span><br />
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example, in English, abbreviations are made by removing most vowels and only using the first 3-5 consonants followed by a period (e.g., abbreviation = abbr.).</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">[https://en.wikipedia.org/wiki/Abbreviation%29 https://en.wikipedia.org/wiki/Abbreviation)]</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If your language does not have a standard way of expressing abbreviations, do you simply leave them in English?</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Acronyms </span> =====

<div id="magicdomid113">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Are there standard</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> translat</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ions of</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> widely accepted acronyms such as CD, DVD, MB</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language? If not, do they remain in English?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Acronym</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Punctuation'''</span> =====

<div id="magicdomid117">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use different punctuation rules in your Firefox localization than what your language standard defines? </span>

</div>
<div>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example: do you use a period at the end of every user interface element translation or only some? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">W</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">hat is the international/national standard for punctuation in your language</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">?</span>

</div>
<div id="magicdomid118">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Emphasis</span> =====

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Is there an international/national standard for capitalization</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> in your language? </span>

* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If so, do those standard rules apply in all product translations? </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">f this doe</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">sn</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">'t apply, how </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">do you</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> indicate importance or name of a movie, book title, product UIs (</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq u">S</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ave, </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj u">F</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ile...)</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">How does your language handle the use of bold, italic, or underline types to express emphasis?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ( See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Italic_type</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Hyphens and compounds </span> =====

<div id="magicdomid123">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">way</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> of </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">using</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> hyphens and compounds in your language? ( </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Compound_%28linguistics%29</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ) </span>

</div>
<div id="magicdomid124">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Prepositions and articles</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span> =====

<div id="magicdomid126">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing prepositions and articles in your language?</span>

</div>
<div id="magicdomid127">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Diacritics and </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Special characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid129">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language use</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> any special </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or accented characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and will they be applied and preserved in sort orders, and other aspects of the translation</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Diacritic</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid130">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Quotes  </span> =====

<div id="magicdomid132">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language have a standard use for quotation marks, parenthesis, or brackets?</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Whitespace </span> =====

<div id="magicdomid135">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language require the</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> use of white space around words, sentences, paragraphs, etc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">.? If so, in what ways?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== '''User Interface Elements''' =====
* '''Titles''' : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text.
* '''Buttons''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancelar", "Borrar historial", "Agregar correo electrónico", "Seleccionar todo", etc.
* '''Value Selector Lists''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words.
* '''Articles''': Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface.
* '''Ellipsis''': Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such. It's preferable to use the ellipsis character (…) instead of three dots.

== General Mozilla l10n style ==

=== Accuracy ===

==== Meaning-based translation ====

When it comes to translation, meaning is everything. A translator needs to understand the source text's meaning exactly. You then find its most closely linked equivalent in your own language, without adding or subtracting meaning in your translation. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:

* What does this word/sentence/string mean in English?
* What is the message the author is trying to send?
* How would I express that meaning in my own language?

Sometimes translation memory and machine translation tools can offer bad suggestions for a translation. If you use either as part of your translation workflow, make sure to correct the suggestions before submitting them. Avoid literal translation at all costs. Watch out for words that might sound or look the same between English and your language, but have a different meaning.

On technical documents, take a look to some words that had a standard localization. If you are unsure, you could ask on the localization mailing list.

==== Should not be translated ====

===== Access Keys =====

Access keys allow a computer to immediately jump to a particular part in a web page by combining keystrokes. They can be adapted to suit your language by selecting a single character to be used in the combined keystroke. Access keys have their own lines within .dtd and .properties files and are identified by being named ".accesskey" in the line.

===== Variables =====

Variables should never be translated. You can recognize a variable within a string by its beginning with a specific character (e.g., $, #, %, etc.) followed by a combination of words without spacing. For example, $BrandShortName and %S are variables. You can move a variable around within a string, if the translation of the string requires it.

===== Brands, copyright, and trademark =====

Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the [https://www.mozilla.org/en-US/styleguide/communications/translation/ Mozilla branding guide] for more details.

'''Translating culture-specific references'''

At times there will be English content included in Mozilla products or web projects (e.g., marketing campaigns) that makes references to American culture and concepts. When translating these, it is best to find an equivalent cultural reference within your own culture that accurately conveys the meaning of the English reference. For example, an American might say, "Good job, home run!" A home run is a baseball reference for a successful outcome. An appropriate translation would be an equivalent metaphor within your culture. Using soccer as an example, you might translate "Good job, home run!" into "Good job, nice goal!" in your language.

[Add a note about Mozilla culture.]

==== Legal content ====

Mozilla projects will often contain legal content in the form of user agreements, privacy statements, etc. When reviewing the translation of legal content, Mozilla localizers should do so according to the criteria concerning accuracy, fluency, style, and terminology found within this style guide and according to Mozilla culture and values.

=== Fluency ===

To produce a fluent translation, not only should the translation follow the language's standard grammar, punctuation, and spelling rules, but it should avoid being ambiguous, incoherent, or inconsistent, and unintelligible.

To avoid ambiguity, the translator must thoroughly understand the meaning behind the source text, including any references that text might include. For example, if the English source text uses the word, "it", the translator must know what "it" is to avoid an ambiguous translation. Clearly understanding the source text will also allow a translator to make the source text's logical connections in their own translation. This helps to keep the translation coherent.

Inconsistency can pop up in many forms. A translator must be consistent in their use of abbreviations, references, and links within each localization project. They must also be consistent with Mozilla and the localization communities' style guides and approved terminology. Abbreviations, like terminology, should come from either a standard reference (like a dictionary of abbreviations) or should follow your language's rules for creating abbreviations. Once used, the abbreviation must remain consistent every place that it is used in the translation. Cross-references (or links) must also be consistently used within a translation. If a text contains a hyperlink URL to a support article in English, the translation should also contain a hyperlink to a translation of that support article (if available) or the English version. Links should not redirect to other pages nor should they be broken and unusable.

Finally, there are times that a translation simply doesn't make sense. It's hard to put your finger on what exactly is wrong with it, but you know it is unintelligible and not fluent. While this is uncommon, it's important to report these unintelligible translations and offer suggestions to correct them.

L10n:Teams:es-AR/Style Guide

2016-05-22T14:04:14Z

Deimidis: /* General Mozilla l10n style */

== Intro ==

Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla's localization communities on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. Some examples of international style guides created by other organizations are:

* https://help.apple.com/asg/mac/2013/ASG_2013.pdf
* https://www.microsoft.com/Language/en-US/StyleGuides.aspx

This style guide is broken up into two main parts: the first contains rules that are language-specific and must be defined by each Mozilla l10n community (covering language-specific style, terminology, and units); the second contains general rules that Mozilla has defined for translators of all languages that can help you translate well (covering principles of accuracy and fluency). Please adapt part one of this style guide to your l10n community's rules for style, terminology, and units. Wherever possible, refer to existing national standards for units, spelling, and grammar in your community's adaptation of the first part of this style guide.

== Language-specific Mozilla style ==

== Style ==

<div id="magicdomid16">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Your localization community's style is largely up to you to define. It is a part of your community's instructions and standards for translating strings within each project type. Style encompasses various elements, such as formality, tone, natural expression, handling cultural references, idioms, or slang, and maintaining consistency with Mozilla and 3rd party branding and style guides. Your localization community should define these style elements for localizing Mozilla projects into your language. Let's go through these main aspects of Style.</span>

</div>
<div id="magicdomid17">

</div>
===== Formality and Tone =====

<div id="magicdomid18">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">When determining the formality or tone of a Mozilla l10n project in your language, ask yourself these questions:</span>

</div>
* Who is the target user for this project and what is their background?
* How would a target user for this project expect to interact with this project? For example, would they expect a friendly, casual interaction?
* Is formal language appropriate for all of your language's Mozilla l10n projects, or only some of them? Which ones?
* Is informal language appropriate for all of your language's Mozilla l10n projets, or only some of them? Which ones?

<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In fact, localization should not use a level of formality higher or lower than required by this community-defined style guideline. An example of this would be using "click here" (not formal) vs. "please click here" (more formal). Also, the tone employed throughout a l10n project(s) should stay consistent within itself. </span>

</div>
<div>

</div>
===== Natural expression =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Using natural expressions make your localization sound natural to a native speaker. If your translation does not follow the community defined language guidelines for translating content that contains local or natural expressions, this results in a mediocre and/or awkward translation. Teams should be careful to address those and keep them in mind while translating, which is why it is an important section to address in a Style Guide. An example of a natural expression in a translation would be translating the Spanish phrase, "En ocho días." In English, one might translate this as, "in eight days" or "in a week." The latter is the more natural translation, although both could be considered correct. </span>

</div>
<div>

</div>
<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In this section, form guidelines for how to perform a natural sounding localization. This might take some time and experience to find the right examples to include or create the right guidelines for your language.</span>

</div>
<div>

</div>
===== Handling cultural references, idioms, and slang =====

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Cultural references, idioms, and slang require a full understanding of these references between the cultures of your source and target languages. An example of a cultural reference in English would be the phrase, "kick-off meeting." This is a reference that uses an American football term. It means a meeting to begin a project. To translate it, you can follow one of two approaches:</span>

# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Find an equivalent reference phrase in your language.</span>
# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Remove the cultural reference and translate the core meaning (e.g., "a commencement meeting") </span>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Define a policy for handling these cultural references, idioms, and slang that you can make standard across all projects. Consider resources you can refer back to in order to find cultural equivalents and list them in this section of your style guide (e.g., a slang dictionary in your language).  </span>

===== Style consistency =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Finally, adherence to Mozilla and third-party branding and style guides should be respected throughout a localization project. More information on Mozilla-specific branding rules can be found here: </span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z url">https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/</span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">. For example, some brand names should never be translated, such as "Firefox". For other brands that do not have any branding guidelines, your localization community must define whether to translate them. Be extra careful to check on branding rules before deciding to translate a name or not (whether for Mozilla or for a third-party) and to list them here in your community's l10n style guide.</span>

</div>
<div>

</div>
<div>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''Terminology'''</span> ===

<div id="magicdomid29">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):</span>

</div>
<ul>
<li><div id="magicdomid30">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Microsoft key terms and target languages </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://www.microsoft.com/Language/en-US/Default.aspx</span></li>
<li><div id="magicdomid31">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Pootle's own term list: </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://mozilla.locamotion.org/xx/terminology/essential.po</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> (replace *xx* with a locale code)</span></li></ul>

<div id="magicdomid33">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">You should be consistent in the use of existing reliable appropriate term bases in your language. These term bases could be developed and approved by the community, or leveraged from another party that adhere to national, international or local standards</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> for software and internet terminology</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">. Avoid</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> the following:</span>

</div>
<ul>
<li><div id="magicdomid34">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology within the project</span></li>
<li><div id="magicdomid35">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology with term base</span></li>
<li><div id="magicdomid36">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology across all of your projects</span></li>
<li><div id="magicdomid37">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">U</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">sing terminology from another subject matter (e.g., don't use medical terminology in Firefox)</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Tips on translating difficult concepts'''</span> =====

<div id="magicdomid40">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Translating terms representing difficult concepts is a tricky task. Here are some ideas to help you translate terms that do not have equivalents in your language:</span>

</div>
<ul>
<li><div id="magicdomid41">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Understand the meaning of the term in English. Definitions of a few key terms </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">http://techterms.com/category/internet</span></li>
<li><div id="magicdomid42">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Know your product and understand the function of the feature. </span></li>
<li><div id="magicdomid43">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider similar ideas for those functions in your culture.</span></li>
<li><div id="magicdomid44">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Associate a culturally specific image with the meaning and function of the term.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Developing new term base'''</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''s'''</span> =====

<div id="magicdomid47">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">What is your </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">community's</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> process </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">for</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> identifying and creating a new t</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ermbase</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">? Here are a few things to keep in mind:</span>

</div>
<ul>
<li><div id="magicdomid48">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Avoid </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">verly borrowing English expressions</span></li>
<li><div id="magicdomid49">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Referenc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ing</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> another language f</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">rom</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> the same language </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">family</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> may inspire you to come up with your own terms</span></li>
<li><div id="magicdomid50">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider the product target audience (age</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> level of literacy, education</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> social </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> economic status)</span></li>
<li><div id="magicdomid51">

</div>
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Will you use l</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">oan words</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> from another language</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or coin new terms in your language to maintain</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">language purity?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> Is there government requirement or policy to encourage creating new terms for new concepts</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">, o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">r </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">will </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">loan words </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">be sufficient to</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> reach broader masses </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> expedite new technology adoption</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span></li>
<li><div id="magicdomid52">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">If there are two acceptable scripts commonly used by the general public, what is the commonly used script on the web or government sites? What is the script used by major web technology companies?</span></li></ul>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and Grammar </span> ===

<div id="magicdomid57">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many elements of unit or grammar do not exist or apply to all languages. If you find one of these elements that does not apply to your language, please remove it from your style guide.</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

</div>
<div id="magicdomid58">

</div>
<div id="magicdomid59">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

</div>
<div id="magicdomid60">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Units and Unit Conversion</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Date Format</span> =====

<div id="magicdomid64">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are the date formats for weeks and months expressed in the following forms: </span>

</div>
<ul>
<li><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">1). Fully spelled out</span> 2).<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> 2 or 3 letters </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">3). Single letter</span></li>
<li><div id="magicdomid65">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the order of Year, Month and Day?  </span></li></ul>

<div id="magicdomid66">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Reference material can be find here: </span>https://en.wikipedia.org/wiki/Date_format_by_country

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">C</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">alendar</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> view: </span> =====

<ul>
<li><div id="magicdomid68">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Which date is considered the first day of the week, Sunday or Monday?  </span></li>
<li><div id="magicdomid69">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Is Lunar calendar observed? Other regional calendar observed?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span></li></ul>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Time Format</span> =====

<div id="magicdomid72">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How is time expressed in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ncluding 0-24 hr expression, hour, minute and second.</span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Numerals </span> =====

<div id="magicdomid76">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are numerals an</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">d percentages</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> expressed in your language? </span>

</div>
<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. </span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Currency </span> =====

<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are other widely used currency and symbols used in your country/language for paid apps. </span>

</div>
<div id="magicdomid79">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span> =====

<div id="magicdomid81">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their measurement system.</span>

</div>
<div id="magicdomid82">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Name</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">s</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid84">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are the order of family name and given name in your language</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> Here is the guideline on the naming convention from w3c.org:</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Address and Postal Code Format </span> =====

<div id="magicdomid87">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the format in your language?  </span>

</div>
<div id="magicdomid88">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: most Asian countries start from big to small: [Country] [postal code][state/province][city][district][street number and name][building and suite numbers][addressee]</span>

</div>
<div id="magicdomid89">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Countries of European languages start from small to big: [addressee][street number and name][building and suite numbers][district][city][state/province][postal code][Country]</span>

</div>
<div id="magicdomid90">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   </span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Telephone Number format</span> =====

<div id="magicdomid92">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Space separators between digits can be different for area codes such as State (Province) and City, </span>

</div>
<div id="magicdomid94">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Spelling And Grammar Checks'''</span> ====

<div id="magicdomid96">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many languages have national or international standards that define spelling and grammar rules. When defining these rules for your community, make reference to those standards wherever possible. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have automated tests for spell checking and grammar</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">List those tools and dictionaries here and how regularly they should be used.</span>

</div>
<div id="magicdomid97">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Tense'''</span> =====

<div id="magicdomid99">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">? What is your policy on tense consistency for certain use cases? For example, for phrases that ask a user to make an action (like "Download Firefox"), do you use a future tense, a command tense, or a neutral tense? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Grammatical_tense</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid100">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Word Forms'''</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Pluralization  </span> =====

<div id="magicdomid106">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing pluralization in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">L</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ist all forms of plural forms and examples if there is more than one. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Additional discussions can be found Here. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and here: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html</span>

</div>
<div id="magicdomid107">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Abbreviations  </span> =====

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are abbreviations expressed in your language?</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span><br />
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example, in English, abbreviations are made by removing most vowels and only using the first 3-5 consonants followed by a period (e.g., abbreviation = abbr.).</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">[https://en.wikipedia.org/wiki/Abbreviation%29 https://en.wikipedia.org/wiki/Abbreviation)]</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If your language does not have a standard way of expressing abbreviations, do you simply leave them in English?</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Acronyms </span> =====

<div id="magicdomid113">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Are there standard</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> translat</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ions of</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> widely accepted acronyms such as CD, DVD, MB</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language? If not, do they remain in English?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Acronym</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Punctuation'''</span> =====

<div id="magicdomid117">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use different punctuation rules in your Firefox localization than what your language standard defines? </span>

</div>
<div>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example: do you use a period at the end of every user interface element translation or only some? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">W</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">hat is the international/national standard for punctuation in your language</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">?</span>

</div>
<div id="magicdomid118">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Emphasis</span> =====

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Is there an international/national standard for capitalization</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> in your language? </span>

* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If so, do those standard rules apply in all product translations? </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">f this doe</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">sn</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">'t apply, how </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">do you</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> indicate importance or name of a movie, book title, product UIs (</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq u">S</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ave, </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj u">F</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ile...)</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">How does your language handle the use of bold, italic, or underline types to express emphasis?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ( See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Italic_type</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Hyphens and compounds </span> =====

<div id="magicdomid123">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">way</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> of </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">using</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> hyphens and compounds in your language? ( </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Compound_%28linguistics%29</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ) </span>

</div>
<div id="magicdomid124">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Prepositions and articles</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span> =====

<div id="magicdomid126">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing prepositions and articles in your language?</span>

</div>
<div id="magicdomid127">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Diacritics and </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Special characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid129">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language use</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> any special </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or accented characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and will they be applied and preserved in sort orders, and other aspects of the translation</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Diacritic</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid130">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Quotes  </span> =====

<div id="magicdomid132">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language have a standard use for quotation marks, parenthesis, or brackets?</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Whitespace </span> =====

<div id="magicdomid135">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language require the</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> use of white space around words, sentences, paragraphs, etc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">.? If so, in what ways?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== '''User Interface Elements''' =====
* '''Titles''' : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text.
* '''Buttons''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancelar", "Borrar historial", "Agregar correo electrónico", "Seleccionar todo", etc.
* '''Value Selector Lists''': Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words.
* '''Articles''': Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface.
* '''Ellipsis''': Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such. It's preferable to use the ellipsis character (…) instead of three dots.

== General Mozilla l10n style ==

=== Accuracy ===

==== Meaning-based translation ====

When it comes to translation, meaning is everything. A translator needs to understand the source text's meaning exactly. You then find its most closely linked equivalent in your own language, without adding or subtracting meaning in your translation. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:

* What does this word/sentence/string mean in English?
* What is the message the author is trying to send?
* How would I express that meaning in my own language?

Sometimes translation memory and machine translation tools can offer bad suggestions for a translation. If you use either as part of your translation workflow, make sure to correct the suggestions before submitting them. Avoid literal translation at all costs. Watch out for words that might sound or look the same between English and your language, but have a different meaning.

==== Should not be translated ====

===== Access Keys =====

Access keys allow a computer to immediately jump to a particular part in a web page by combining keystrokes. They can be adapted to suit your language by selecting a single character to be used in the combined keystroke. Access keys have their own lines within .dtd and .properties files and are identified by being named ".accesskey" in the line.

===== Variables =====

Variables should never be translated. You can recognize a variable within a string by its beginning with a specific character (e.g., $, #, %, etc.) followed by a combination of words without spacing. For example, $BrandShortName and %S are variables. You can move a variable around within a string, if the translation of the string requires it.

===== Brands, copyright, and trademark =====

Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the [https://www.mozilla.org/en-US/styleguide/communications/translation/ Mozilla branding guide] for more details.

'''Translating culture-specific references'''

At times there will be English content included in Mozilla products or web projects (e.g., marketing campaigns) that makes references to American culture and concepts. When translating these, it is best to find an equivalent cultural reference within your own culture that accurately conveys the meaning of the English reference. For example, an American might say, "Good job, home run!" A home run is a baseball reference for a successful outcome. An appropriate translation would be an equivalent metaphor within your culture. Using soccer as an example, you might translate "Good job, home run!" into "Good job, nice goal!" in your language.

[Add a note about Mozilla culture.]

==== Legal content ====

Mozilla projects will often contain legal content in the form of user agreements, privacy statements, etc. When reviewing the translation of legal content, Mozilla localizers should do so according to the criteria concerning accuracy, fluency, style, and terminology found within this style guide and according to Mozilla culture and values.

=== Fluency ===

To produce a fluent translation, not only should the translation follow the language's standard grammar, punctuation, and spelling rules, but it should avoid being ambiguous, incoherent, or inconsistent, and unintelligible.

To avoid ambiguity, the translator must thoroughly understand the meaning behind the source text, including any references that text might include. For example, if the English source text uses the word, "it", the translator must know what "it" is to avoid an ambiguous translation. Clearly understanding the source text will also allow a translator to make the source text's logical connections in their own translation. This helps to keep the translation coherent.

Inconsistency can pop up in many forms. A translator must be consistent in their use of abbreviations, references, and links within each localization project. They must also be consistent with Mozilla and the localization communities' style guides and approved terminology. Abbreviations, like terminology, should come from either a standard reference (like a dictionary of abbreviations) or should follow your language's rules for creating abbreviations. Once used, the abbreviation must remain consistent every place that it is used in the translation. Cross-references (or links) must also be consistently used within a translation. If a text contains a hyperlink URL to a support article in English, the translation should also contain a hyperlink to a translation of that support article (if available) or the English version. Links should not redirect to other pages nor should they be broken and unusable.

Finally, there are times that a translation simply doesn't make sense. It's hard to put your finger on what exactly is wrong with it, but you know it is unintelligible and not fluent. While this is uncommon, it's important to report these unintelligible translations and offer suggestions to correct them.

L10n:Teams:es-AR/Style Guide

2016-05-22T13:47:16Z

Deimidis: /* Intro */

== Intro ==

Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla's localization communities on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. Some examples of international style guides created by other organizations are:

* https://help.apple.com/asg/mac/2013/ASG_2013.pdf
* https://www.microsoft.com/Language/en-US/StyleGuides.aspx

This style guide is broken up into two main parts: the first contains rules that are language-specific and must be defined by each Mozilla l10n community (covering language-specific style, terminology, and units); the second contains general rules that Mozilla has defined for translators of all languages that can help you translate well (covering principles of accuracy and fluency). Please adapt part one of this style guide to your l10n community's rules for style, terminology, and units. Wherever possible, refer to existing national standards for units, spelling, and grammar in your community's adaptation of the first part of this style guide.

== Language-specific Mozilla style ==

== Style ==

<div id="magicdomid16">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Your localization community's style is largely up to you to define. It is a part of your community's instructions and standards for translating strings within each project type. Style encompasses various elements, such as formality, tone, natural expression, handling cultural references, idioms, or slang, and maintaining consistency with Mozilla and 3rd party branding and style guides. Your localization community should define these style elements for localizing Mozilla projects into your language. Let's go through these main aspects of Style.</span>

</div>
<div id="magicdomid17">

</div>
===== Formality and Tone =====

<div id="magicdomid18">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">When determining the formality or tone of a Mozilla l10n project in your language, ask yourself these questions:</span>

</div>
* Who is the target user for this project and what is their background?
* How would a target user for this project expect to interact with this project? For example, would they expect a friendly, casual interaction?
* Is formal language appropriate for all of your language's Mozilla l10n projects, or only some of them? Which ones?
* Is informal language appropriate for all of your language's Mozilla l10n projets, or only some of them? Which ones?

<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In fact, localization should not use a level of formality higher or lower than required by this community-defined style guideline. An example of this would be using "click here" (not formal) vs. "please click here" (more formal). Also, the tone employed throughout a l10n project(s) should stay consistent within itself. </span>

</div>
<div>

</div>
===== Natural expression =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Using natural expressions make your localization sound natural to a native speaker. If your translation does not follow the community defined language guidelines for translating content that contains local or natural expressions, this results in a mediocre and/or awkward translation. Teams should be careful to address those and keep them in mind while translating, which is why it is an important section to address in a Style Guide. An example of a natural expression in a translation would be translating the Spanish phrase, "En ocho días." In English, one might translate this as, "in eight days" or "in a week." The latter is the more natural translation, although both could be considered correct. </span>

</div>
<div>

</div>
<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In this section, form guidelines for how to perform a natural sounding localization. This might take some time and experience to find the right examples to include or create the right guidelines for your language.</span>

</div>
<div>

</div>
===== Handling cultural references, idioms, and slang =====

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Cultural references, idioms, and slang require a full understanding of these references between the cultures of your source and target languages. An example of a cultural reference in English would be the phrase, "kick-off meeting." This is a reference that uses an American football term. It means a meeting to begin a project. To translate it, you can follow one of two approaches:</span>

# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Find an equivalent reference phrase in your language.</span>
# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Remove the cultural reference and translate the core meaning (e.g., "a commencement meeting") </span>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Define a policy for handling these cultural references, idioms, and slang that you can make standard across all projects. Consider resources you can refer back to in order to find cultural equivalents and list them in this section of your style guide (e.g., a slang dictionary in your language).  </span>

===== Style consistency =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Finally, adherence to Mozilla and third-party branding and style guides should be respected throughout a localization project. More information on Mozilla-specific branding rules can be found here: </span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z url">https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/</span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">. For example, some brand names should never be translated, such as "Firefox". For other brands that do not have any branding guidelines, your localization community must define whether to translate them. Be extra careful to check on branding rules before deciding to translate a name or not (whether for Mozilla or for a third-party) and to list them here in your community's l10n style guide.</span>

</div>
<div>

</div>
<div>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''Terminology'''</span> ===

<div id="magicdomid29">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):</span>

</div>
<ul>
<li><div id="magicdomid30">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Microsoft key terms and target languages </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://www.microsoft.com/Language/en-US/Default.aspx</span></li>
<li><div id="magicdomid31">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Pootle's own term list: </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://mozilla.locamotion.org/xx/terminology/essential.po</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> (replace *xx* with a locale code)</span></li></ul>

<div id="magicdomid33">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">You should be consistent in the use of existing reliable appropriate term bases in your language. These term bases could be developed and approved by the community, or leveraged from another party that adhere to national, international or local standards</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> for software and internet terminology</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">. Avoid</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> the following:</span>

</div>
<ul>
<li><div id="magicdomid34">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology within the project</span></li>
<li><div id="magicdomid35">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology with term base</span></li>
<li><div id="magicdomid36">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology across all of your projects</span></li>
<li><div id="magicdomid37">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">U</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">sing terminology from another subject matter (e.g., don't use medical terminology in Firefox)</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Tips on translating difficult concepts'''</span> =====

<div id="magicdomid40">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Translating terms representing difficult concepts is a tricky task. Here are some ideas to help you translate terms that do not have equivalents in your language:</span>

</div>
<ul>
<li><div id="magicdomid41">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Understand the meaning of the term in English. Definitions of a few key terms </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">http://techterms.com/category/internet</span></li>
<li><div id="magicdomid42">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Know your product and understand the function of the feature. </span></li>
<li><div id="magicdomid43">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider similar ideas for those functions in your culture.</span></li>
<li><div id="magicdomid44">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Associate a culturally specific image with the meaning and function of the term.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Developing new term base'''</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''s'''</span> =====

<div id="magicdomid47">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">What is your </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">community's</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> process </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">for</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> identifying and creating a new t</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ermbase</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">? Here are a few things to keep in mind:</span>

</div>
<ul>
<li><div id="magicdomid48">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Avoid </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">verly borrowing English expressions</span></li>
<li><div id="magicdomid49">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Referenc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ing</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> another language f</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">rom</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> the same language </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">family</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> may inspire you to come up with your own terms</span></li>
<li><div id="magicdomid50">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider the product target audience (age</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> level of literacy, education</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> social </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> economic status)</span></li>
<li><div id="magicdomid51">

</div>
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Will you use l</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">oan words</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> from another language</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or coin new terms in your language to maintain</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">language purity?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> Is there government requirement or policy to encourage creating new terms for new concepts</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">, o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">r </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">will </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">loan words </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">be sufficient to</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> reach broader masses </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> expedite new technology adoption</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span></li>
<li><div id="magicdomid52">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">If there are two acceptable scripts commonly used by the general public, what is the commonly used script on the web or government sites? What is the script used by major web technology companies?</span></li></ul>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and Grammar </span> ===

<div id="magicdomid57">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many elements of unit or grammar do not exist or apply to all languages. If you find one of these elements that does not apply to your language, please remove it from your style guide.</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

</div>
<div id="magicdomid58">

</div>
<div id="magicdomid59">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

</div>
<div id="magicdomid60">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Units and Unit Conversion</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Date Format</span> =====

<div id="magicdomid64">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are the date formats for weeks and months expressed in the following forms: </span>

</div>
<ul>
<li><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">1). Fully spelled out</span> 2).<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> 2 or 3 letters </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">3). Single letter</span></li>
<li><div id="magicdomid65">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the order of Year, Month and Day?  </span></li></ul>

<div id="magicdomid66">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Reference material can be find here: </span>https://en.wikipedia.org/wiki/Date_format_by_country

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">C</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">alendar</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> view: </span> =====

<ul>
<li><div id="magicdomid68">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Which date is considered the first day of the week, Sunday or Monday?  </span></li>
<li><div id="magicdomid69">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Is Lunar calendar observed? Other regional calendar observed?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span></li></ul>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Time Format</span> =====

<div id="magicdomid72">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How is time expressed in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ncluding 0-24 hr expression, hour, minute and second.</span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Numerals </span> =====

<div id="magicdomid76">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are numerals an</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">d percentages</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> expressed in your language? </span>

</div>
<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. </span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Currency </span> =====

<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are other widely used currency and symbols used in your country/language for paid apps. </span>

</div>
<div id="magicdomid79">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span> =====

<div id="magicdomid81">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their measurement system.</span>

</div>
<div id="magicdomid82">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Name</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">s</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid84">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are the order of family name and given name in your language</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> Here is the guideline on the naming convention from w3c.org:</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Address and Postal Code Format </span> =====

<div id="magicdomid87">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the format in your language?  </span>

</div>
<div id="magicdomid88">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: most Asian countries start from big to small: [Country] [postal code][state/province][city][district][street number and name][building and suite numbers][addressee]</span>

</div>
<div id="magicdomid89">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Countries of European languages start from small to big: [addressee][street number and name][building and suite numbers][district][city][state/province][postal code][Country]</span>

</div>
<div id="magicdomid90">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   </span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Telephone Number format</span> =====

<div id="magicdomid92">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Space separators between digits can be different for area codes such as State (Province) and City, </span>

</div>
<div id="magicdomid94">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Spelling And Grammar Checks'''</span> ====

<div id="magicdomid96">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many languages have national or international standards that define spelling and grammar rules. When defining these rules for your community, make reference to those standards wherever possible. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have automated tests for spell checking and grammar</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">List those tools and dictionaries here and how regularly they should be used.</span>

</div>
<div id="magicdomid97">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Tense'''</span> =====

<div id="magicdomid99">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">? What is your policy on tense consistency for certain use cases? For example, for phrases that ask a user to make an action (like "Download Firefox"), do you use a future tense, a command tense, or a neutral tense? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Grammatical_tense</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid100">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Word Forms'''</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Pluralization  </span> =====

<div id="magicdomid106">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing pluralization in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">L</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ist all forms of plural forms and examples if there is more than one. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Additional discussions can be found Here. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and here: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html</span>

</div>
<div id="magicdomid107">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Abbreviations  </span> =====

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are abbreviations expressed in your language?</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span><br />
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example, in English, abbreviations are made by removing most vowels and only using the first 3-5 consonants followed by a period (e.g., abbreviation = abbr.).</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">[https://en.wikipedia.org/wiki/Abbreviation%29 https://en.wikipedia.org/wiki/Abbreviation)]</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If your language does not have a standard way of expressing abbreviations, do you simply leave them in English?</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Acronyms </span> =====

<div id="magicdomid113">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Are there standard</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> translat</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ions of</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> widely accepted acronyms such as CD, DVD, MB</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language? If not, do they remain in English?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Acronym</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Punctuation'''</span> =====

<div id="magicdomid117">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use different punctuation rules in your Firefox localization than what your language standard defines? </span>

</div>
<div>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example: do you use a period at the end of every user interface element translation or only some? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">W</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">hat is the international/national standard for punctuation in your language</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">?</span>

</div>
<div id="magicdomid118">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Emphasis</span> =====

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Is there an international/national standard for capitalization</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> in your language? </span>

* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If so, do those standard rules apply in all product translations? </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">f this doe</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">sn</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">'t apply, how </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">do you</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> indicate importance or name of a movie, book title, product UIs (</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq u">S</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ave, </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj u">F</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ile...)</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">How does your language handle the use of bold, italic, or underline types to express emphasis?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ( See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Italic_type</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Hyphens and compounds </span> =====

<div id="magicdomid123">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">way</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> of </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">using</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> hyphens and compounds in your language? ( </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Compound_%28linguistics%29</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ) </span>

</div>
<div id="magicdomid124">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Prepositions and articles</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span> =====

<div id="magicdomid126">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing prepositions and articles in your language?</span>

</div>
<div id="magicdomid127">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Diacritics and </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Special characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid129">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language use</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> any special </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or accented characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and will they be applied and preserved in sort orders, and other aspects of the translation</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Diacritic</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid130">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Quotes  </span> =====

<div id="magicdomid132">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language have a standard use for quotation marks, parenthesis, or brackets?</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Whitespace </span> =====

<div id="magicdomid135">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language require the</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> use of white space around words, sentences, paragraphs, etc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">.? If so, in what ways?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''User Interface Elements'''</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">        </span> =====

<div id="magicdomid139">

</div>
<ul>
<li><div id="magicdomid140">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Titles : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text.         </span></li>
<li><div id="magicdomid142">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Buttons: Capitalize the first letter of each word. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancel", "Clear History", "Add Email", "Select All", etc.          </span></li>
<li><div id="magicdomid144">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Value Selector Lists: Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. </span></li>
<li><div id="magicdomid147">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Articles: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface.              </span></li>
<li><div id="magicdomid149">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Ellipsis: Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such.     </span></li></ul>

</div>
== General Mozilla l10n style ==

=== Accuracy ===

==== <span class="author-p-1460 b">'''Meaning-based translation'''</span> ====

<div id="magicdomid3">

<span class="author-p-1460">When it comes to translation, meaning is everything. A translator needs to understand the source text's meaning exactly. You then find its most closely linked equivalent in your own language, without adding or subtracting meaning in your translation. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:</span>

</div>
* <span class="author-p-1460">What does this word/sentence/string mean in English?</span>
* <span class="author-p-1460">What is the message the author is trying to send?</span>
* <span class="author-p-1460">How would I express that meaning in my own language?</span>

<span class="author-p-1460">Sometimes translation memory and machine translation tools can offer bad suggestions for a translation. If you use either as part of your translation workflow, make sure to correct the suggestions before submitting them. Avoid literal translation at all costs. Watch out for words that might sound or look the same between English and your language, but have a different meaning. </span>

==== Should not be translated ====

===== <span class="author-p-1460">Access Keys</span> =====

<span class="author-p-1460">Access keys allow a computer to immediately jump to a particular part in a web page by combining keystrokes. They can be adapted to suit your language by selecting a single character to be used in the combined keystroke. Access keys have their own lines within .dtd and .properties files and are identified by being named ".accesskey" in the line.</span>

===== <span class="author-p-1460">Variables</span> =====

<span class="author-p-1460">Variables should never be translated. You can recognize a variable within a string by its beginning with a specific character (e.g., <span class="author-p-1460">$, #, %, etc.)</span> followed by a combination of words without spacing. For example, $BrandShortName and %S are variables. </span>You can move a variable around within a string, if the translation of the string requires it.

===== '''<span class="author-p-1460">Brands, copyright, and trademark</span>''' =====

<span class="author-p-1460">Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the [https://www.mozilla.org/en-US/styleguide/communications/translation/ Mozilla branding guide] for more details.</span>

<span style="font-family:open sans light,helvetica,arial,sans-serif; font-size:1.286rem; letter-spacing:-0.014em; line-height:1">Translating c</span><span style="font-family:open sans light,helvetica,arial,sans-serif; font-size:1.286rem; letter-spacing:-0.014em; line-height:1">ulture-specific references</span>

At times there will be English content included in Mozilla products or web projects (e.g., marketing campaigns) that makes references to American culture and concepts. When translating these, it is best to find an equivalent cultural reference within your own culture that accurately conveys the meaning of the English reference. For example, an American might say, "Good job, home run!" A home run is a baseball reference for a successful outcome. An appropriate translation would be an equivalent metaphor within your culture. Using soccer as an example, you might translate "Good job, home run!" into "Good job, nice goal!" in your language.

[Add a note about Mozilla culture.]

==== Legal content ====

Mozilla projects will often contain legal content in the form of user agreements, privacy statements, etc. When reviewing the translation of legal content, Mozilla localizers should do so according to the criteria concerning accuracy, fluency, style, and terminology found within this style guide and according to Mozilla culture and values.

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Fluency</span> ===

<div id="magicdomid153">

</div>
<div id="magicdomid154">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">To produce a fluent translation, not only should the translation follow the language's standard grammar, punctuation, and spelling rules, but it should avoid being ambiguous, incoherent, or inconsistent, and unintelligible.</span>

</div>
<div id="magicdomid155">

</div>
<div id="magicdomid156">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">To avoid ambiguity, the translator must thoroughly understand the meaning behind the source text, including any references that text might include. For example, if the English source text uses the word, "it", the translator must know what "it" is to avoid an ambiguous translation. Clearly understanding the source text will also allow a translator to make the source text's logical connections in their own translation. This helps to keep the translation coherent.</span>

</div>
<div id="magicdomid157">

</div>
<div id="magicdomid158">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Inconsistency can pop up in many forms. A translator must be consistent in their use of abbreviations, references, and links within each localization project. They must also be consistent with Mozilla and the localization communities' style guides and approved terminology. Abbreviations, like terminology, should come from either a standard reference (like a dictionary of abbreviations) or should follow your language's rules for creating abbreviations. Once used, the abbreviation must remain consistent every place that it is used in the translation. Cross-references (or links) must also be consistently used within a translation. If a text contains a hyperlink URL to a support article in English, the translation should also contain a hyperlink to a translation of that support article (if available) or the English version. Links should not redirect to other pages nor should they be broken and unusable.</span>

</div>
<div id="magicdomid159">

</div>
<div id="magicdomid160">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Finally, there are times that a translation simply doesn't make sense. It's hard to put your finger on what exactly is wrong with it, but you know it is unintelligible and not fluent. While this is uncommon, it's important to report these unintelligible translations and offer suggestions to correct them.</span>

</div>

L10n:Teams:es-AR/Style Guide

2016-05-22T13:37:05Z

Deimidis: change to wikimedia format

== Intro ==

=== Intro ===

<div id="magicdomid8">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Style guides define the standard against which we determine a translation's quality. They contain rules that are both defined by Mozilla and by Mozilla's localization communities on how to best translate text in Mozilla products, websites, and other projects. Style guides are used to both translate and evaluate a translation's quality. By following these rules, a translator has a better chance of producing a high quality translation that represents Mozilla values and culture. Some examples of international style guides created by other organizations are:</span>

</div>
*https://help.apple.com/asg/mac/2013/ASG_2013.pdf *https://www.microsoft.com/Language/en-US/StyleGuides.aspx

<div id="magicdomid11">

</div>
<div id="magicdomid12">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">This style guide is broken up into two main parts: the first contains rules that are language-specific and must be defined by each Mozilla l10n community (covering language-specific style, terminology, and units); the second contains general rules that Mozilla has defined for translators of all languages that can help you translate well (covering principles of accuracy and fluency). Please adapt part one of this style guide to your l10n community's rules for style, terminology, and units. Wherever possible, refer to existing national standards for units, spelling, and grammar in your community's adaptation of the first part of this style guide.</span>

</div>
== Language-specific Mozilla style ==

== Style ==

=== Style ===

<div id="magicdomid16">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Your localization community's style is largely up to you to define. It is a part of your community's instructions and standards for translating strings within each project type. Style encompasses various elements, such as formality, tone, natural expression, handling cultural references, idioms, or slang, and maintaining consistency with Mozilla and 3rd party branding and style guides. Your localization community should define these style elements for localizing Mozilla projects into your language. Let's go through these main aspects of Style.</span>

</div>
<div id="magicdomid17">

</div>
===== Formality and Tone =====

<div id="magicdomid18">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">When determining the formality or tone of a Mozilla l10n project in your language, ask yourself these questions:</span>

</div>
* Who is the target user for this project and what is their background?
* How would a target user for this project expect to interact with this project? For example, would they expect a friendly, casual interaction?
* Is formal language appropriate for all of your language's Mozilla l10n projects, or only some of them? Which ones?
* Is informal language appropriate for all of your language's Mozilla l10n projets, or only some of them? Which ones?

<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In fact, localization should not use a level of formality higher or lower than required by this community-defined style guideline. An example of this would be using "click here" (not formal) vs. "please click here" (more formal). Also, the tone employed throughout a l10n project(s) should stay consistent within itself. </span>

</div>
<div>

</div>
===== Natural expression =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Using natural expressions make your localization sound natural to a native speaker. If your translation does not follow the community defined language guidelines for translating content that contains local or natural expressions, this results in a mediocre and/or awkward translation. Teams should be careful to address those and keep them in mind while translating, which is why it is an important section to address in a Style Guide. An example of a natural expression in a translation would be translating the Spanish phrase, "En ocho días." In English, one might translate this as, "in eight days" or "in a week." The latter is the more natural translation, although both could be considered correct. </span>

</div>
<div>

</div>
<div>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">In this section, form guidelines for how to perform a natural sounding localization. This might take some time and experience to find the right examples to include or create the right guidelines for your language.</span>

</div>
<div>

</div>
===== Handling cultural references, idioms, and slang =====

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Cultural references, idioms, and slang require a full understanding of these references between the cultures of your source and target languages. An example of a cultural reference in English would be the phrase, "kick-off meeting." This is a reference that uses an American football term. It means a meeting to begin a project. To translate it, you can follow one of two approaches:</span>

# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Find an equivalent reference phrase in your language.</span>
# <span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Remove the cultural reference and translate the core meaning (e.g., "a commencement meeting") </span>

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Define a policy for handling these cultural references, idioms, and slang that you can make standard across all projects. Consider resources you can refer back to in order to find cultural equivalents and list them in this section of your style guide (e.g., a slang dictionary in your language).  </span>

===== Style consistency =====

<div id="magicdomid22">

<span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">Finally, adherence to Mozilla and third-party branding and style guides should be respected throughout a localization project. More information on Mozilla-specific branding rules can be found here: </span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z url">https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/</span><span class="author-a-nz76zz86zs2xc75rz78zz66zz80zxz85zz71z">. For example, some brand names should never be translated, such as "Firefox". For other brands that do not have any branding guidelines, your localization community must define whether to translate them. Be extra careful to check on branding rules before deciding to translate a name or not (whether for Mozilla or for a third-party) and to list them here in your community's l10n style guide.</span>

</div>
<div>

</div>
<div>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''Terminology'''</span> ===

<div id="magicdomid29">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):</span>

</div>
<ul>
<li><div id="magicdomid30">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Microsoft key terms and target languages </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://www.microsoft.com/Language/en-US/Default.aspx</span></li>
<li><div id="magicdomid31">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Pootle's own term list: </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">https://mozilla.locamotion.org/xx/terminology/essential.po</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> (replace *xx* with a locale code)</span></li></ul>

<div id="magicdomid33">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">You should be consistent in the use of existing reliable appropriate term bases in your language. These term bases could be developed and approved by the community, or leveraged from another party that adhere to national, international or local standards</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> for software and internet terminology</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">. Avoid</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> the following:</span>

</div>
<ul>
<li><div id="magicdomid34">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology within the project</span></li>
<li><div id="magicdomid35">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology with term base</span></li>
<li><div id="magicdomid36">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Inconsistent use of terminology across all of your projects</span></li>
<li><div id="magicdomid37">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">U</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">sing terminology from another subject matter (e.g., don't use medical terminology in Firefox)</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Tips on translating difficult concepts'''</span> =====

<div id="magicdomid40">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Translating terms representing difficult concepts is a tricky task. Here are some ideas to help you translate terms that do not have equivalents in your language:</span>

</div>
<ul>
<li><div id="magicdomid41">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Understand the meaning of the term in English. Definitions of a few key terms </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq url">http://techterms.com/category/internet</span></li>
<li><div id="magicdomid42">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Know your product and understand the function of the feature. </span></li>
<li><div id="magicdomid43">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider similar ideas for those functions in your culture.</span></li>
<li><div id="magicdomid44">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Associate a culturally specific image with the meaning and function of the term.</span></li></ul>

===== <span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq b">'''Developing new term base'''</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd b">'''s'''</span> =====

<div id="magicdomid47">

<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">What is your </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">community's</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> process </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">for</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> identifying and creating a new t</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ermbase</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">? Here are a few things to keep in mind:</span>

</div>
<ul>
<li><div id="magicdomid48">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Avoid </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">verly borrowing English expressions</span></li>
<li><div id="magicdomid49">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Referenc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ing</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> another language f</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">rom</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> the same language </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">family</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> may inspire you to come up with your own terms</span></li>
<li><div id="magicdomid50">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">Consider the product target audience (age</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> level of literacy, education</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">,</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> social </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> economic status)</span></li>
<li><div id="magicdomid51">

</div>
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Will you use l</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">oan words</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> from another language</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or coin new terms in your language to maintain</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">language purity?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> Is there government requirement or policy to encourage creating new terms for new concepts</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">, o</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">r </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">will </span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">loan words </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">be sufficient to</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> reach broader masses </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">and</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> expedite new technology adoption</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span></li>
<li><div id="magicdomid52">

</div>
<span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">If there are two acceptable scripts commonly used by the general public, what is the commonly used script on the web or government sites? What is the script used by major web technology companies?</span></li></ul>

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and Grammar </span> ===

<div id="magicdomid57">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many elements of unit or grammar do not exist or apply to all languages. If you find one of these elements that does not apply to your language, please remove it from your style guide.</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

</div>
<div id="magicdomid58">

</div>
<div id="magicdomid59">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

</div>
<div id="magicdomid60">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Units and Unit Conversion</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Date Format</span> =====

<div id="magicdomid64">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are the date formats for weeks and months expressed in the following forms: </span>

</div>
<ul>
<li><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">1). Fully spelled out</span> 2).<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> 2 or 3 letters </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">3). Single letter</span></li>
<li><div id="magicdomid65">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the order of Year, Month and Day?  </span></li></ul>

<div id="magicdomid66">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Reference material can be find here: </span>https://en.wikipedia.org/wiki/Date_format_by_country

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">C</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">alendar</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> view: </span> =====

<ul>
<li><div id="magicdomid68">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Which date is considered the first day of the week, Sunday or Monday?  </span></li>
<li><div id="magicdomid69">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   Is Lunar calendar observed? Other regional calendar observed?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span></li></ul>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Time Format</span> =====

<div id="magicdomid72">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How is time expressed in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ncluding 0-24 hr expression, hour, minute and second.</span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Numerals </span> =====

<div id="magicdomid76">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are numerals an</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">d percentages</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> expressed in your language? </span>

</div>
<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. </span>

</div>
<div>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Currency </span> =====

<div>

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are other widely used currency and symbols used in your country/language for paid apps. </span>

</div>
<div id="magicdomid79">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Units</span> =====

<div id="magicdomid81">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use the imperial, metric or nautical system for measuring weight, distance, etc.? Source strings will use the imperial system (e.g., miles, pounds, feet, gallons, etc.). Target translations should convert imperial metrics to their measurement system.</span>

</div>
<div id="magicdomid82">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Name</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">s</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid84">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What are the order of family name and given name in your language</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> Here is the guideline on the naming convention from w3c.org:</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Address and Postal Code Format </span> =====

<div id="magicdomid87">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the format in your language?  </span>

</div>
<div id="magicdomid88">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Example: most Asian countries start from big to small: [Country] [postal code][state/province][city][district][street number and name][building and suite numbers][addressee]</span>

</div>
<div id="magicdomid89">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    Countries of European languages start from small to big: [addressee][street number and name][building and suite numbers][district][city][state/province][postal code][Country]</span>

</div>
<div id="magicdomid90">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">   </span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Telephone Number format</span> =====

<div id="magicdomid92">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Space separators between digits can be different for area codes such as State (Province) and City, </span>

</div>
<div id="magicdomid94">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Spelling And Grammar Checks'''</span> ====

<div id="magicdomid96">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Many languages have national or international standards that define spelling and grammar rules. When defining these rules for your community, make reference to those standards wherever possible. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have automated tests for spell checking and grammar</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">List those tools and dictionaries here and how regularly they should be used.</span>

</div>
<div id="magicdomid97">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Tense'''</span> =====

<div id="magicdomid99">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">? What is your policy on tense consistency for certain use cases? For example, for phrases that ask a user to make an action (like "Download Firefox"), do you use a future tense, a command tense, or a neutral tense? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Grammatical_tense</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid100">

</div>
==== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Word Forms'''</span> ====

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Pluralization  </span> =====

<div id="magicdomid106">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing pluralization in your language? </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">L</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ist all forms of plural forms and examples if there is more than one. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Additional discussions can be found Here. </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and here: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html</span>

</div>
<div id="magicdomid107">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Abbreviations  </span> =====

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">How are abbreviations expressed in your language?</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span><br />
<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example, in English, abbreviations are made by removing most vowels and only using the first 3-5 consonants followed by a period (e.g., abbreviation = abbr.).</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">[https://en.wikipedia.org/wiki/Abbreviation%29 https://en.wikipedia.org/wiki/Abbreviation)]</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">    </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> </span>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If your language does not have a standard way of expressing abbreviations, do you simply leave them in English?</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Acronyms </span> =====

<div id="magicdomid113">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Are there standard</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> translat</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">ions of</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> widely accepted acronyms such as CD, DVD, MB</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language? If not, do they remain in English?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Acronym</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''Punctuation'''</span> =====

<div id="magicdomid117">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Do you use different punctuation rules in your Firefox localization than what your language standard defines? </span>

</div>
<div>

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">    Example: do you use a period at the end of every user interface element translation or only some? </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">W</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">hat is the international/national standard for punctuation in your language</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">?</span>

</div>
<div id="magicdomid118">

</div>
===== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Emphasis</span> =====

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Is there an international/national standard for capitalization</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> in your language? </span>

* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">If so, do those standard rules apply in all product translations? </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">I</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">f this doe</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq">sn</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">'t apply, how </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">do you</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> indicate importance or name of a movie, book title, product UIs (</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq u">S</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ave, </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj u">F</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">ile...)</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd"> in your language?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> </span>
* <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">How does your language handle the use of bold, italic, or underline types to express emphasis?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ( See: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Italic_type</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Hyphens and compounds </span> =====

<div id="magicdomid123">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">way</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> of </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">using</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> hyphens and compounds in your language? ( </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Compound_%28linguistics%29</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> ) </span>

</div>
<div id="magicdomid124">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Prepositions and articles</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span> =====

<div id="magicdomid126">

<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">What is the appropriate form of expressing prepositions and articles in your language?</span>

</div>
<div id="magicdomid127">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Diacritics and </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Special characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">  </span> =====

<div id="magicdomid129">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language use</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> any special </span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">or accented characters</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> and will they be applied and preserved in sort orders, and other aspects of the translation</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">?</span><span class="author-a-z87zt8dz75zn14z76zz71z8z82zz86z2uq"> </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Diacritic</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
<div id="magicdomid130">

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Quotes  </span> =====

<div id="magicdomid132">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language have a standard use for quotation marks, parenthesis, or brackets?</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Whitespace </span> =====

<div id="magicdomid135">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Does your language require the</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> use of white space around words, sentences, paragraphs, etc</span><span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">.? If so, in what ways?</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> (see: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj url">https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj"> )</span>

</div>
===== <span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj b">'''User Interface Elements'''</span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">        </span> =====

<div id="magicdomid139">

</div>
<ul>
<li><div id="magicdomid140">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Titles : Should be brief and precise. Localizers can assume that source content reaches 2/3 of the total available line space. This allows localization text to expand and not be truncated or resolved through ellipsis. Title on the final page (meaning no more click through) should allow enough room to display full text.         </span></li>
<li><div id="magicdomid142">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Buttons: Capitalize the first letter of each word. Limit to one or two words. Use verbs that precisely describe the button's action. For example, "Cancel", "Clear History", "Add Email", "Select All", etc.          </span></li>
<li><div id="magicdomid144">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Value Selector Lists: Capitalize the first letter of the first word and the first letter of any proper nouns. Limit to one or two words. </span></li>
<li><div id="magicdomid147">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Articles: </span><span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Avoid them where possible. Articles (such as the word "the" in English) should be avoided wherever possible. User interface elements have limited space available for text. Avoiding articles will help ensure that your translations will be accommodated within the user interface.              </span></li>
<li><div id="magicdomid149">

</div>
<span class="author-a-z66zuz70zqiz67zz73z3z90zhp4z68zz73zpj">Ellipsis: Ellipsis are often inserted automatically in the UI where strings are truncated. Ellipsis should only be used at high level of UI pages, but not be on the final page (after a series of click-through) where detailed instruction is given. Ellipsis should not be used as a way to solve truncation issue. Focus on making the UI short and precise. The sequence of the sentence structure in another language may not translate well, when a sentence is half finished as such.     </span></li></ul>

</div>
== General Mozilla l10n style ==

=== Accuracy ===

==== <span class="author-p-1460 b">'''Meaning-based translation'''</span> ====

<div id="magicdomid3">

<span class="author-p-1460">When it comes to translation, meaning is everything. A translator needs to understand the source text's meaning exactly. You then find its most closely linked equivalent in your own language, without adding or subtracting meaning in your translation. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:</span>

</div>
* <span class="author-p-1460">What does this word/sentence/string mean in English?</span>
* <span class="author-p-1460">What is the message the author is trying to send?</span>
* <span class="author-p-1460">How would I express that meaning in my own language?</span>

<span class="author-p-1460">Sometimes translation memory and machine translation tools can offer bad suggestions for a translation. If you use either as part of your translation workflow, make sure to correct the suggestions before submitting them. Avoid literal translation at all costs. Watch out for words that might sound or look the same between English and your language, but have a different meaning. </span>

==== Should not be translated ====

===== <span class="author-p-1460">Access Keys</span> =====

<span class="author-p-1460">Access keys allow a computer to immediately jump to a particular part in a web page by combining keystrokes. They can be adapted to suit your language by selecting a single character to be used in the combined keystroke. Access keys have their own lines within .dtd and .properties files and are identified by being named ".accesskey" in the line.</span>

===== <span class="author-p-1460">Variables</span> =====

<span class="author-p-1460">Variables should never be translated. You can recognize a variable within a string by its beginning with a specific character (e.g., <span class="author-p-1460">$, #, %, etc.)</span> followed by a combination of words without spacing. For example, $BrandShortName and %S are variables. </span>You can move a variable around within a string, if the translation of the string requires it.

===== '''<span class="author-p-1460">Brands, copyright, and trademark</span>''' =====

<span class="author-p-1460">Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the [https://www.mozilla.org/en-US/styleguide/communications/translation/ Mozilla branding guide] for more details.</span>

<span style="font-family:open sans light,helvetica,arial,sans-serif; font-size:1.286rem; letter-spacing:-0.014em; line-height:1">Translating c</span><span style="font-family:open sans light,helvetica,arial,sans-serif; font-size:1.286rem; letter-spacing:-0.014em; line-height:1">ulture-specific references</span>

At times there will be English content included in Mozilla products or web projects (e.g., marketing campaigns) that makes references to American culture and concepts. When translating these, it is best to find an equivalent cultural reference within your own culture that accurately conveys the meaning of the English reference. For example, an American might say, "Good job, home run!" A home run is a baseball reference for a successful outcome. An appropriate translation would be an equivalent metaphor within your culture. Using soccer as an example, you might translate "Good job, home run!" into "Good job, nice goal!" in your language.

[Add a note about Mozilla culture.]

==== Legal content ====

Mozilla projects will often contain legal content in the form of user agreements, privacy statements, etc. When reviewing the translation of legal content, Mozilla localizers should do so according to the criteria concerning accuracy, fluency, style, and terminology found within this style guide and according to Mozilla culture and values.

=== <span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Fluency</span> ===

<div id="magicdomid153">

</div>
<div id="magicdomid154">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">To produce a fluent translation, not only should the translation follow the language's standard grammar, punctuation, and spelling rules, but it should avoid being ambiguous, incoherent, or inconsistent, and unintelligible.</span>

</div>
<div id="magicdomid155">

</div>
<div id="magicdomid156">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">To avoid ambiguity, the translator must thoroughly understand the meaning behind the source text, including any references that text might include. For example, if the English source text uses the word, "it", the translator must know what "it" is to avoid an ambiguous translation. Clearly understanding the source text will also allow a translator to make the source text's logical connections in their own translation. This helps to keep the translation coherent.</span>

</div>
<div id="magicdomid157">

</div>
<div id="magicdomid158">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Inconsistency can pop up in many forms. A translator must be consistent in their use of abbreviations, references, and links within each localization project. They must also be consistent with Mozilla and the localization communities' style guides and approved terminology. Abbreviations, like terminology, should come from either a standard reference (like a dictionary of abbreviations) or should follow your language's rules for creating abbreviations. Once used, the abbreviation must remain consistent every place that it is used in the translation. Cross-references (or links) must also be consistently used within a translation. If a text contains a hyperlink URL to a support article in English, the translation should also contain a hyperlink to a translation of that support article (if available) or the English version. Links should not redirect to other pages nor should they be broken and unusable.</span>

</div>
<div id="magicdomid159">

</div>
<div id="magicdomid160">

<span class="author-a-w6z79zlakz82zxz85zz65zz86zz78zz89zz122zz89zd">Finally, there are times that a translation simply doesn't make sense. It's hard to put your finger on what exactly is wrong with it, but you know it is unintelligible and not fluent. While this is uncommon, it's important to report these unintelligible translations and offer suggestions to correct them.</span>

</div>

L10n:Meetings/2016 BuenosAires hackathon

2016-04-06T21:46:11Z

Deimidis: /* Goals */

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
Buenos Aires

Map:

;When:
May21-22

;Lodging:
'''AirBNB1:'''

Phone:

Map:

Who:

'''AirBNB2:'''

Phone:

Map:

Who:

;Arriving at lodging:

;Reimbursements:

;Communication with Telegram:
* Join the Telegram group here: https://telegram.me/joinchat/BNisygggAOrdAE4o69cAeQ

==Goals==
;Esperanto (probably not present)
* Goal for this year: complete style guide
* Recruit new members

;Spanish (Argentina)
* Transition to a new responsible for Web repositories
* Start using Pontoon as a default Web translation tool
** have a tutorial session (useful for all communities present)
** manage pontoon permissions
* Create a transition plan for the community
* Finish everything that is in this webpage: https://l10n.mozilla-community.org/webdashboard/?locale=es-AR
* Start review process of Web page translations (to have consistency between pages)
* Define between "formal" and "informal" translation for products and web and align those categories
* Plan to recruit new localizers

;Spanish (Chile)
* Start Firefox for Android localization. Goal is to make good progress during the hackathon, so that it is finished by August. Tool: Pontoon
* Discuss possible change of "usted" to "tu" for Firefox Desktop (because the use is inconsistent with other products at the time)
* Learn more about "accesskeys", that in es-CL we maintain with it's English variation

*

;Guaraní
* Start Firefox for Android localization.
* Make a step by step guide to form new groups using pootle location

==Agenda==
===Saturday May 21 ===
;Morning - 900AM
*Introductions, spectrograms & goals review -- Jeff & Delphine
*Mozilla mission and org updates applied to your locales -- Jeff & Delphine
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
**Localization quality discussion
*L10n updates from each community (10 minutes each)
**Active projects
**Translation workflow
**Successes
**Challenges
;Lunch -- TBD
;Afternoon
*Breakouts
**Creating glossaries & style guides for translation quality
**Pootle HowTo
**
*Review of breakout session outcomes
;Dinner -- TBD

===Sunday May 22===
;Morning -- 900AM
*Localization community planning
**Sustainability
**Product launches
**Recruitment
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
;Lunch -- TBD
;Afternoon
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
*Update team wiki pages
*Take l10n hackathon survey.
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- TBD

==Other==
*Hashtag for event: #mozl10nbuenosaires
;Notes: https://public.etherpad-mozilla.org/p/BuenosAires-l10n-meetup-notes
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://pontoon.mozilla.org/ Pontoon translation tool]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://transvision.mozfr.org/ Transvision QA tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

L10n:Meetings/2016 BuenosAires hackathon

2016-04-06T21:44:16Z

Deimidis: /* Goals */

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
Buenos Aires

Map:

;When:
May21-22

;Lodging:
'''AirBNB1:'''

Phone:

Map:

Who:

'''AirBNB2:'''

Phone:

Map:

Who:

;Arriving at lodging:

;Reimbursements:

;Communication with Telegram:
* Join the Telegram group here: https://telegram.me/joinchat/BNisygggAOrdAE4o69cAeQ

==Goals==
;Esperanto (probably not present)
* Goal for this year: complete style guide
* Recruit new members

;Spanish (Argentina)
* Transition to a new responsible for Web repositories
* Start using Pontoon as a default Web translation tool
** have a tutorial session (useful for all communities present)
** manage pontoon permissions
* Create a transition plan for the community
* Finish everything that is in this webpage: https://l10n.mozilla-community.org/webdashboard/?locale=es-AR
* Start review process of Web page translations (to have consistency between pages)
* Define between "formal" and "informal" translation for products and web and align those categories
* Plan to find new localizers

;Spanish (Chile)
* Start Firefox for Android localization. Goal is to make good progress during the hackathon, so that it is finished by August. Tool: Pontoon
* Discuss possible change of "usted" to "tu" for Firefox Desktop (because the use is inconsistent with other products at the time)
* Learn more about "accesskeys", that in es-CL we maintain with it's English variation

*

;Guaraní
* Start Firefox for Android localization.
* Make a step by step guide to form new groups using pootle location

==Agenda==
===Saturday May 21 ===
;Morning - 900AM
*Introductions, spectrograms & goals review -- Jeff & Delphine
*Mozilla mission and org updates applied to your locales -- Jeff & Delphine
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
**Localization quality discussion
*L10n updates from each community (10 minutes each)
**Active projects
**Translation workflow
**Successes
**Challenges
;Lunch -- TBD
;Afternoon
*Breakouts
**Creating glossaries & style guides for translation quality
**Pootle HowTo
**
*Review of breakout session outcomes
;Dinner -- TBD

===Sunday May 22===
;Morning -- 900AM
*Localization community planning
**Sustainability
**Product launches
**Recruitment
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
;Lunch -- TBD
;Afternoon
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
*Update team wiki pages
*Take l10n hackathon survey.
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- TBD

==Other==
*Hashtag for event: #mozl10nbuenosaires
;Notes: https://public.etherpad-mozilla.org/p/BuenosAires-l10n-meetup-notes
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://pontoon.mozilla.org/ Pontoon translation tool]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://transvision.mozfr.org/ Transvision QA tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

L10n:Meetings/2016 BuenosAires hackathon

2016-04-06T21:36:06Z

Deimidis: /* Goals */ adding goals for es-AR

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
Buenos Aires

Map:

;When:
May21-22

;Lodging:
'''AirBNB1:'''

Phone:

Map:

Who:

'''AirBNB2:'''

Phone:

Map:

Who:

;Arriving at lodging:

;Reimbursements:

;Communication with Telegram:
* Join the Telegram group here: https://telegram.me/joinchat/BNisygggAOrdAE4o69cAeQ

==Goals==
;Esperanto (probably not present)
* Goal for this year: complete style guide
* Recruit new members

;Spanish (Argentina)
* Transition to a new responsible for Web repositories
* Start using Pontoon as a default Web translation tool
** have a tutorial session (useful for all communities present)
** manage pontoon permissions
* Create a transition plan for the community
* Finish everything that is in this webpage: https://l10n.mozilla-community.org/webdashboard/?locale=es-AR
* Start review process of Web page translations (to have consistency between pages)
* Define between "formal" and "informal" translation for products and web and align those categories

;Spanish (Chile)
* Start Firefox for Android localization. Goal is to make good progress during the hackathon, so that it is finished by August. Tool: Pontoon
* Discuss possible change of "usted" to "tu" for Firefox Desktop (because the use is inconsistent with other products at the time)
* Learn more about "accesskeys", that in es-CL we maintain with it's English variation

*

;Guaraní
* Start Firefox for Android localization.
* Make a step by step guide to form new groups using pootle location

==Agenda==
===Saturday May 21 ===
;Morning - 900AM
*Introductions, spectrograms & goals review -- Jeff & Delphine
*Mozilla mission and org updates applied to your locales -- Jeff & Delphine
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
**Localization quality discussion
*L10n updates from each community (10 minutes each)
**Active projects
**Translation workflow
**Successes
**Challenges
;Lunch -- TBD
;Afternoon
*Breakouts
**Creating glossaries & style guides for translation quality
**Pootle HowTo
**
*Review of breakout session outcomes
;Dinner -- TBD

===Sunday May 22===
;Morning -- 900AM
*Localization community planning
**Sustainability
**Product launches
**Recruitment
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
;Lunch -- TBD
;Afternoon
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
*Update team wiki pages
*Take l10n hackathon survey.
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- TBD

==Other==
*Hashtag for event: #mozl10nbuenosaires
;Notes: https://public.etherpad-mozilla.org/p/BuenosAires-l10n-meetup-notes
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://pontoon.mozilla.org/ Pontoon translation tool]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://transvision.mozfr.org/ Transvision QA tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

L10n:Meetings/2016 BuenosAires hackathon

2016-04-06T21:32:16Z

Deimidis: /* Goals */

[[Category:L10n meetings|{{SUBPAGENAME}}]]
__NOTOC__
==Logistics==
;Where:
Buenos Aires

Map:

;When:
May21-22

;Lodging:
'''AirBNB1:'''

Phone:

Map:

Who:

'''AirBNB2:'''

Phone:

Map:

Who:

;Arriving at lodging:

;Reimbursements:

;Communication with Telegram:
* Join the Telegram group here: https://telegram.me/joinchat/BNisygggAOrdAE4o69cAeQ

==Goals==
;Esperanto (probably not present)
* Goal for this year: complete style guide
* Recruit new members

;Spanish (Argentina)
* Transition to a new responsible for Web repositories
* Start using Pontoon as a default Web translation tool
** have a tutorial session (useful for all communities present)
** manage pontoon permissions
* Create a transition plan for the community
* Finish everything that is in this webpage: https://l10n.mozilla-community.org/webdashboard/?locale=es-AR
* Start review process of Web page translations (to have consistency between pages)

;Spanish (Chile)
* Start Firefox for Android localization. Goal is to make good progress during the hackathon, so that it is finished by August. Tool: Pontoon
* Discuss possible change of "usted" to "tu" for Firefox Desktop (because the use is inconsistent with other products at the time)
* Learn more about "accesskeys", that in es-CL we maintain with it's English variation

*

;Guaraní
* Start Firefox for Android localization.
* Make a step by step guide to form new groups using pootle location

==Agenda==
===Saturday May 21 ===
;Morning - 900AM
*Introductions, spectrograms & goals review -- Jeff & Delphine
*Mozilla mission and org updates applied to your locales -- Jeff & Delphine
**L10n updates from [https://blog.mozilla.org/l10n/2016/01/08/mozlando-localization-sessions/ Mozlando]
**Localization quality discussion
*L10n updates from each community (10 minutes each)
**Active projects
**Translation workflow
**Successes
**Challenges
;Lunch -- TBD
;Afternoon
*Breakouts
**Creating glossaries & style guides for translation quality
**Pootle HowTo
**
*Review of breakout session outcomes
;Dinner -- TBD

===Sunday May 22===
;Morning -- 900AM
*Localization community planning
**Sustainability
**Product launches
**Recruitment
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
;Lunch -- TBD
;Afternoon
*Localization work
**Resolving bugs
**Translating strings
**Signing off on products
**Creating language resources
*Update team wiki pages
*Take l10n hackathon survey.
*Begin plans for next l10n meetup.
*Group pictures.
;Dinner -- TBD

==Other==
*Hashtag for event: #mozl10nbuenosaires
;Notes: https://public.etherpad-mozilla.org/p/BuenosAires-l10n-meetup-notes
;Resources:
*[https://l10n.mozilla.org Mozilla l10n home page]
*[https://pontoon.mozilla.org/ Pontoon translation tool]
*[http://mozilla.locamotion.org Pootle translation tool]
*[https://transvision.mozfr.org/ Transvision QA tool]
*[https://addons.mozilla.org/En-us/firefox/language-tools/ Firefox language pack add-ons]
*[https://lists.mozilla.org/listinfo/dev-l10n Mozilla l10n mailing list (please subscribe)]
*[https://twitter.com/mozilla_l10n @mozilla_l10n Twitter account]

Participation/Global Gatherings 2015/Singapore/Content/conflict resolution

2016-01-18T15:56:28Z

Deimidis: /* Session Title: Conflict Resolution for Community Leaders */ - Adding goals and description

=Session Title: Conflict Resolution for Community Leaders=

[http://tiptoes.ca/wp-content/uploads/2015/08/2015-08-28_1244.png Leadership Framework Component]: Empowering Teams & People

'''Session Description (this will appear on the sched app, so please edit to reflect clarity):'''

''An introduction to techniques to solve conflicts in your community. ''

'''Session Objectives:'''
* Introduce Non Violent Communication techniques to solve conflicts in communities

'''Learning Objectives"'''
* 4 steps to create honest conversations
* How to communicate with others (individual or groups) to have better success

'''Agenda (draft is fine!):'''
* Introduction to NVC concepts
* NVC four main concepts
* Exercise to understand those concepts
* Challenge to continue Cohort work

'''Facilitators:''':

* [https://mozillians.org/en-US/u/deimidis/ Guillermo Movia]

'''Session documents & Relevant Links:'''

* [https://en.wikipedia.org/wiki/Nonviolent_Communication Non violent communication, Wikipedia definition]
* [http://mozilla.org Link to Doc]
* [http://mozilla.org Link 1]

Template:Participation

2016-01-04T13:27:17Z

Deimidis: update logo

<div style="clear:both; border: 4px solid rgb(40, 40, 40); text-align:center; padding: 2px; background: #dddddd; border-collapse: separate; border-radius: 10px; margin-top:20px; height:40px;">
<div style="float:left;">[[image:Mozilla_Participation.svg|130px]]</div>
[[Participation|Home]] | [[Participation/Meetings|Meetings]] | [[Participation/Lab|Mozilla Participation Lab]] | [[Participation/Resources | Resources]]
</div>

__NOTOC__
[[Category:Participation]]

Participation

2016-01-04T13:20:22Z

Deimidis: Update logo

{{Participation}}

==Participation at Mozilla==

<div style="display:block;border-radius:10px;background-color:rgb(227, 220, 200);padding:20px;margin-top:20px;">
[[Image:Mozilla_Participation.svg|right]]

== Who We Are ==

=== Our Mission ===

To have Mozilla succeed through openness and participation

=== Participation Team Principles ===

These are the principles that guide our actions. We chose a manifesto in order to capture the many complex elements of our participatory mission.

# Participation is when people can freely contribute their energies, time and ideas to support Mozilla’s mission
# In order to keep the web open and participatory it must be shaped by organizations, like Mozilla, who are equally open and participatory
# Participation is at the core of Mozilla’s history and identity and provides a key advantage for Mozilla as an organization
# Participation cannot exist without a culture of openness that allows contributors the opportunity to shape and build Mozilla’s programs and products at every level
# Participation must provide value for both Mozilla and Mozillians (participants)
</div>
=== The Team ===
[[File:ParticipationTeam2015.jpg|500px|none|right]]
==== Head of Core Contributors, Participation ====

* [https://mozillians.org/u/geroter/ George Roter], Team Leader

==== Participation Partners ====

* [https://mozillians.org/u/williamq/ William Quiviger]
* [https://mozillians.org/u/kinger/ Brian King]

==== Global-Local Organizing ====

* [https://mozillians.org/u/rosana/ Rosana Ardila]
* [https://mozillians.org/u/nukeador/ Rubén Martín]
* [https://mozillians.org/u/deimidis/ Guillermo Movia]
* [https://mozillians.org/u/couci/ Konstantina Papadea]
* [https://mozillians.org/u/FrancJP/ Francisco Picolini]

==== Developing Leaders ====

* [https://mozillians.org/u/emmairwin/ Emma Irwin]

==== [[Participation/Infrastructure|Participation Infrastructure]] ====

* [https://mozillians.org/u/pierros/ Pierros Papadeas]
* [https://mozillians.org/en-US/u/jgiannelos/ John Giannelos]
* [https://mozillians.org/en-US/u/akatsoulas/ Anastasios Katsoulas]
* [https://mozillians.org/en-US/u/comzeradd/ Nikos Roussos]

==== Team Performance and Learning ====

* [https://mozillians.org/u/lucyeoh/ Lucy Harris]

== What We Do ==

'''2015 Strategy and Plans''' The [https://docs.google.com/document/d/1NdR3ODkvBHBfv3V36uASBhvrY1dcA_D0h5QW6jGI8Wk/edit#heading=h.rpsjw8wfw2oz 2015 Participation Strategic Plan] guides our work for the year.

Quarterly Goals - 2015

* [https://docs.google.com/presentation/d/1CGAAPpYSgxSeA8y_PrulIgEjIti_ldwbC7yDMWaEd4Q/edit#slide=id.g594221f97_2_26 Q1 Goals]
* [https://docs.google.com/document/d/104oW93mvtfLvI5ZKFeKsH9OEqdqyug8DJHDvGDgQnvE/edit Q2 Goals]
* [https://docs.google.com/spreadsheets/d/1fD7KNzK-Y1DheVQ8uCztnL3MhJiJuqa_L7KUVG_O_Ls/edit#gid=0 Q3 Goals] ''In process''
* Q4 Goals: will be updated shortly.

'''Working in the open'''

The team is using an agile, scrum-like process called Heartbeats (modeled from the Mozilla Foundation team) to manage our week-to-week work. This involves 3-week Heartbeats, with a number of focused projects during each Heartbeat that link to the quarter goals.

Our workflow uses GitHub + Google Docs + Etherpads. Anyone can comment, follow-along or get involved — [https://github.com/mozilla/participation-org/issues the workflow is here]. We welcome feedback on the process and approach. Also, we have a section on [https://discourse.mozilla-community.org/c/participation Mozilla’s discourse], where anyone could create topics and collaborate.

You can also follow along with what we’re doing on the [https://blog.mozilla.org/community/category/participation/ Blog] and by following [https://twitter.com/mozparticipate @MozParticipate on Twitter].

=== Current Quarter ===

You could find our [https://github.com/mozilla/participation-org/milestones/Final%20Q3%20Heartbeat%20-%20October%202nd current heartbeat work here]. ''Until October 2nd''

== How To Participate ==

We always welcome participation in our work. We mark issues on Github with «Volunteer task» tag, so it’s clear where people can help and lead tasks. You could find [https://github.com/mozilla/participation-org/labels/Volunteer%20Task those issues in this link].

If you'd like to get regular updates and discussions about Participation at Mozilla we have a [https://discourse.mozilla-community.org/c/participation section at Mozilla’s discourse] that you can use as a mailing list as well as an online forum. In fact, once it’s set up you respond to threads by emails and it will be publish directly into the topic.

Directions for Using Discourse as a Mailing List:
* Register as a user on discourse
* Once you have a username go to your profile by clicking on the avatar, in the upper right corner of the screen
* Click on Preferences - You should see a section called «Email», where you could chose which notifications receive by email.

Once you’re set up you’ll be able to easily stay informed and join participation conversations directly from your email!

File:Mozilla Participation.svg

2016-01-04T13:16:17Z

Deimidis: Participation Logo made by Elio Qoshi

Participation Logo made by Elio Qoshi

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T20:05:25Z

Deimidis: /* Hotel */

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===
Singapore's currency is the Singaporean Dollar. you could check the value at [https://www.oanda.com oanda.com]. At Dec. 17th, 1 US dollar is equivalent to 1,40788 SGD

=== Customs ===
Singapore has strong regulations and taxes for alcohol and tobacco. We recommend that you don't bring alcohol to Singapore. Also, the quantity for tobacco is small:

«Tobacco is heavily taxed, and you are not allowed to bring more than one opened pack (not carton, but a single pack!) of cigarettes into the country. This is particularly strictly enforced on the land borders with Malaysia.»

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===
All participants will be at [https://www.parkroyalhotels.com/en/hotels-resorts/singapore/kitchener.html ParkRoyal Kitchener Road Hotel].

Address:

181 Kitchener Road,
Singapore 208533

=== Venue ===

The event will be [http://scape.sg/venues held on Scape], a non-profit organisation with its mission and vision rooted in support of youth, talent and leadership development.

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T20:04:32Z

Deimidis: /* Hotel */ hotel information

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===
Singapore's currency is the Singaporean Dollar. you could check the value at [https://www.oanda.com oanda.com]. At Dec. 17th, 1 US dollar is equivalent to 1,40788 SGD

=== Customs ===
Singapore has strong regulations and taxes for alcohol and tobacco. We recommend that you don't bring alcohol to Singapore. Also, the quantity for tobacco is small:

«Tobacco is heavily taxed, and you are not allowed to bring more than one opened pack (not carton, but a single pack!) of cigarettes into the country. This is particularly strictly enforced on the land borders with Malaysia.»

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===
All participants will be at [https://www.parkroyalhotels.com/en/hotels-resorts/singapore/kitchener.html ParkRoyal Kitchener Road Hotel].

=== Venue ===

The event will be [http://scape.sg/venues held on Scape], a non-profit organisation with its mission and vision rooted in support of youth, talent and leadership development.

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T19:39:15Z

Deimidis: /* Venue */ adding venue information

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===
Singapore's currency is the Singaporean Dollar. you could check the value at [https://www.oanda.com oanda.com]. At Dec. 17th, 1 US dollar is equivalent to 1,40788 SGD

=== Customs ===
Singapore has strong regulations and taxes for alcohol and tobacco. We recommend that you don't bring alcohol to Singapore. Also, the quantity for tobacco is small:

«Tobacco is heavily taxed, and you are not allowed to bring more than one opened pack (not carton, but a single pack!) of cigarettes into the country. This is particularly strictly enforced on the land borders with Malaysia.»

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Venue ===

The event will be [http://scape.sg/venues held on Scape], a non-profit organisation with its mission and vision rooted in support of youth, talent and leadership development.

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T19:29:45Z

Deimidis: /* Customs */

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===
Singapore's currency is the Singaporean Dollar. you could check the value at [https://www.oanda.com oanda.com]. At Dec. 17th, 1 US dollar is equivalent to 1,40788 SGD

=== Customs ===
Singapore has strong regulations and taxes for alcohol and tobacco. We recommend that you don't bring alcohol to Singapore. Also, the quantity for tobacco is small:

«Tobacco is heavily taxed, and you are not allowed to bring more than one opened pack (not carton, but a single pack!) of cigarettes into the country. This is particularly strictly enforced on the land borders with Malaysia.»

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Venue ===

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T19:25:28Z

Deimidis: /* Currency */

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===
Singapore's currency is the Singaporean Dollar. you could check the value at [https://www.oanda.com oanda.com]. At Dec. 17th, 1 US dollar is equivalent to 1,40788 SGD

=== Customs ===

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Venue ===

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T19:22:29Z

Deimidis: /* Transportation */

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T19:18:34Z

Deimidis: /* Logistics information Leadership Summit */ added some text

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

'' Voltage ''
The standard voltage in Singapore is 220V/240V, 50 Hz. If you have equipment that runs on a higher voltage, you should not connect it to Singaporean power unless you have the correct transformer (voltage adaptor).

'' Power Plugs ''
Singapore uses the [https://en.wikipedia.org/wiki/AC_power_plugs_and_sockets#BS_1363_.28Type_G.29 British BS1363 three-pronged square pin type socket]. Plugs from the US, Western and Eastern Europe, and Asia will not fit into a Singapore power plug.

If you need a plug adaptor or transformer, we advise buying one before your arrival. Some hotels will be able to lend you an adaptor, but not all.

=== Currency ===

=== Customs ===

=== Health Care ===

Tap water is safe for drinking, and sanitation standards are very high. As a tropical country, Singapore is hot and humid so drink a lot of water. The lowest temperature ever recorded in Singapore was way back in 1934, when it hit a low of 19.4°C (66.9°F).

Malaria is not an issue, but dengue fever is endemic to the region. Singapore maintains strict mosquito control (leaving standing water around will get you fined), but the government's reach does not extend into the island's nature reserves, so if you're planning on hiking bring along mosquito repellent.

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

If you are arriving earlier than 4 PM on the 6th, you have two options:
* Wait until that time (if you arrive 30-50 minutes before that time).
* Book a shuttle: http://www.mearstransportation.com/global/orlando/
** If you book online, you will save 10% with Promo Code WEB10. You will have to select the hotel where you stay (please double check your hotel letter), and indicate your flight number/arrival time. Transfer should be around 30 minutes to the Hotel.

There’s public buses, but you will have to go to Orlando city, and then to the hotel (estimated travel time more than 2 hours).

Note that we won’t reimburse taxis, so please use the shuttle service indicated.

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Venue ===

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T18:46:43Z

Deimidis: adding items

== Goals ==

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

=== Currency ===

=== Customs ===

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

If you are arriving earlier than 4 PM on the 6th, you have two options:
* Wait until that time (if you arrive 30-50 minutes before that time).
* Book a shuttle: http://www.mearstransportation.com/global/orlando/
** If you book online, you will save 10% with Promo Code WEB10. You will have to select the hotel where you stay (please double check your hotel letter), and indicate your flight number/arrival time. Transfer should be around 30 minutes to the Hotel.

There’s public buses, but you will have to go to Orlando city, and then to the hotel (estimated travel time more than 2 hours).

Note that we won’t reimburse taxis, so please use the shuttle service indicated.

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Venue ===

=== Calendar ===

=== Dinners ===

== Expenses ==

=== What is cover by Mozilla ===

=== What you could ask like reimbursement and how ===

Participation/Global Gatherings 2015/Singapur/Logistics Information

2015-12-17T18:42:39Z

Deimidis: First page iteration

== Logistics information Leadership Summit ==

=== Useful Information ===

=== Power plugs ===

=== Currency ===

=== Customs ===

=== Transportation ===

'''Getting from the Airport to the Hotel'''

'''Arrivals to Singapur'''

'''People arriving early'''

If you are arriving earlier than 4 PM on the 6th, you have two options:
* Wait until that time (if you arrive 30-50 minutes before that time).
* Book a shuttle: http://www.mearstransportation.com/global/orlando/
** If you book online, you will save 10% with Promo Code WEB10. You will have to select the hotel where you stay (please double check your hotel letter), and indicate your flight number/arrival time. Transfer should be around 30 minutes to the Hotel.

There’s public buses, but you will have to go to Orlando city, and then to the hotel (estimated travel time more than 2 hours).

Note that we won’t reimburse taxis, so please use the shuttle service indicated.

'''Getting from the Hotel back to the Airport'''

If you stay longer, we won’t cover hotel costs, nor transportation expenses.

=== Hotel ===

=== Calendar ===

=== Dinners ===