L10n:Teams:tl/Style Guide: Difference between revisions

<span>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. For those definitions of units and grammar that apply document the reference used or how it will be applied to the translation.</span>

<span>The translation should strive to achieve proper unit conversions for currency, measurements, etc. for the target audience.</span>

* <span>Date</span>

** <span>Calendar / Era: Roman / Christian (Anno Domini, AD)</span>

** <span>Name of Days:</span>

*** <span>Monday</span>

*** <span>Tuesday</span>

*** <span>Wednesday</span>

*** <span>Thursday</span>

*** <span>Friday</span>

*** <span>Saturday</span>

*** <span>Sunday</span>

** <span>Short Name of Days:</span>

*** <span>Mon</span>

*** <span>Tue</span>

*** <span>Wed</span>

*** <span>Thu</span>

*** <span>Fri</span>

*** <span>Sat</span>

*** <span>Sun</span>

** <span>Name of Months:</span>

*** <span>January</span>

*** <span>February</span>

*** <span>March</span>

*** <span>April</span>

*** <span>May</span>

*** <span>June</span>

*** <span>July</span>

*** <span>August</span>

*** <span>September</span>

*** <span>October</span>

*** <span>November</span>

*** <span>December</span>

* <span>Short Name of Months:</span>

*** <span>Jan</span>

*** <span>Feb</span>

*** <span>Mar</span>

*** <span>Apr</span>

*** <span>May</span>

*** <span>Jun</span>

*** <span>Jul</span>

*** <span>Aug</span>

*** <span>Sep</span>

*** <span>Oct</span>

*** <span>Nov</span>

*** <span>Dec</span>

** <span>Year Format: English</span>

** <span>Default Short Date Format: MM-dd-yyyy</span>

** <span>Currency</span>

*** <span>Symbol: PHP</span>

*** <span>Format: PHP x,xxx.xx</span>

** <span>Time</span>

*** <span>Time Format: English</span>

*** <span>24-hour Format: NO (12-hour format)</span>

*** <span>Time Separator: colon (:)</span>

*** <span>String for AM Designator: AM</span>

*** <span>String for PM Designator: PM</span>

*** <span>Century: use "ika-" followed by the number</span>

**** <span>e.g. ika-21</span>

** <span>Number</span>

*** <span>When written as English Roman Numeral: as is.</span>

*** <span>When used as part of a sentence (spelled-out) or as an ordinal number: Translate to Tagalog</span>

*** <span>Examples:</span>

**** <span>[EN] Close one tab.</span> | <span>[TL] Isara ang isang tab.</span>

**** <span>[EN] Close the second tab.</span> | <span>[TL] Isara ang pangalawang tab.</span>

*** <span>When written as part of a telephone number: as is.</span>

** <span>Addresses</span>

*** <span>Country / Region:</span>

*** <span>[EN] Republic of the Philippines | [TL] Republika ng Pilipinas</span>

*** <span>[EN] The Philippines | [TL] Pilipinas</span>

*** <span>Address Format:</span>

* <span>House or Building Number</span>

* <span>Building Name</span>

* <span>Street Name</span>

* <span>Village or Subdivision Name</span>

* <span>Barangay Name</span>

* <span>City or Town Name</span>

* <span>Province Name</span>

* <span>Postal Code</span>

* <span>Measurement Units</span>

* <span>Follow the rules on how to translate numbers</span>

* <span>Percentages</span>

* <span>The Tagalog language follows the English rules for percentages. In Mozilla localization, the percentage symbol (%) is frequently used a placeholder. DO NOT modify or remove placeholders. Follow general software localization guidelines and rules.</span>

==== <span class="c18">Spelling And Grammar Checks</span> ====

<span>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. Do you have automated tests for spell checking and grammar? List those tools and dictionaries here and how regularly they should be used.</span>

===== <span class="c7">Tense</span> =====

<span>Do you have standards for verb forms that indicate or express the time, such as past, present, or future, of the action or state? 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? (See:</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Grammatical_tense&sa=D&ust=1472368742769000&usg=AFQjCNHLEloSZGXKIPhNxDWwZ6qFwSEoKg  ]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Grammatical_tense&sa=D&ust=1472368742770000&usg=AFQjCNEtbaKcdsd1YFhRgvHZW-8NqTkIgg https://en.wikipedia.org/wiki/Grammatical_tense]</span><span> )</span>

==== <span class="c18">Word Forms</span> ====

===== <span class="c7">Pluralization </span> =====

<span>What is the appropriate form of expressing pluralization in your language? List all forms of plural forms and examples if there is more than one. Additional discussions can be found Here.</span><span class="c11">[https://www.google.com/url?q=https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals&sa=D&ust=1472368742771000&usg=AFQjCNG1-YqLEhWzSt025YRtBYtqmyBlIg  ]</span><span class="c5">[https://www.google.com/url?q=https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals&sa=D&ust=1472368742772000&usg=AFQjCNGvxMWRxLS-eQbmiwxiXqnNr2F67A https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals]</span><span> and here:</span><span>[https://www.google.com/url?q=http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html&sa=D&ust=1472368742772000&usg=AFQjCNFBhefoAVmSWn6bQuUoKAgH4lc36Q  ]</span><span class="c11">[https://www.google.com/url?q=http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html&sa=D&ust=1472368742773000&usg=AFQjCNF6LbuExAGUJ0lLKYoaKrELCUJDoQ  ]</span><span class="c5">[https://www.google.com/url?q=http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html&sa=D&ust=1472368742773000&usg=AFQjCNF6LbuExAGUJ0lLKYoaKrELCUJDoQ http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html]</span>

* <span>Using "mga" for words using the common pluralization form:</span>

* <span>Example:</span>

<span>Letters</span>

<span>Mga letra</span>

===== <span class="c18">Abbreviations</span> =====

<span class="c7"><br /></span><span>How are abbreviations expressed in your language?</span>

<span>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.). (see:</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Abbreviation%29&sa=D&ust=1472368742776000&usg=AFQjCNE1ZPIb_yC6V2cN96lvkVUjuak_7Q Â ]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Abbreviation%29&sa=D&ust=1472368742776000&usg=AFQjCNE1ZPIb_yC6V2cN96lvkVUjuak_7Q https://en.wikipedia.org/wiki/Abbreviation)]</span>

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

===== <span class="c7">Acronyms</span> =====

<span>Are there standard translations of widely accepted acronyms such as CD, DVD, MB in your language? If not, do they remain in English? (see:</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Acronym&sa=D&ust=1472368742777000&usg=AFQjCNE-Qr_Dz_9W_GoGSA5hqh_AWCHm1g  ]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Acronym&sa=D&ust=1472368742778000&usg=AFQjCNFbky7piCh_jQ_Weth9mIyJwlCytg https://en.wikipedia.org/wiki/Acronym]</span><span> )</span>

===== <span class="c7">Punctuation</span> =====

<span>Follows universal standard.</span>

===== <span class="c7">Emphasis</span> =====

<span>Is there an international/national standard for capitalization in your language?</span>

<span>If so, do those standard rules apply in all product translations?</span>

<span>If this doesn't apply, how do you indicate importance or name of a movie, book title, product UIs (</span><span class="c12">S</span><span>ave, </span><span class="c12">F</span><span>ile...) in your language?</span>

<span>How does your language handle the use of bold, italic, or underline types to express emphasis?  ( See:</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Italic_type&sa=D&ust=1472368742781000&usg=AFQjCNHu3xzFE-eVp6h4Ux6imjYLxbZ44w  ]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Italic_type&sa=D&ust=1472368742782000&usg=AFQjCNF5J0SQ4spmqF7tSuOlDk6-iDfAWQ https://en.wikipedia.org/wiki/Italic_type]</span><span> )</span>

===== <span class="c7">Hyphens and compounds</span> =====

<span>What is the appropriate way of using hyphens and compounds in your language? (</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Compound_%28linguistics%29&sa=D&ust=1472368742783000&usg=AFQjCNFn_qwDyh4ef2oMxGzW1YRqf_MpqA]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Compound_%28linguistics%29&sa=D&ust=1472368742784000&usg=AFQjCNE0f1xdl2wqEQtFGxlMC67LFz7Maw https://en.wikipedia.org/wiki/Compound_(linguistics)]</span>)

===== <span class="c7">Prepositions and articles</span> =====

<span>What is the appropriate form of expressing prepositions and articles in your language?</span>

===== <span class="c7">Diacritics and Special characters </span> =====

<span>most used special character is “ñ”</span>

===== <span class="c7">Quotes </span> =====

<span>Universal Standard for quotes and brackets.</span>

===== <span class="c7">Whitespace</span> =====

<span>Does your language require the use of white space around words, sentences, paragraphs, etc.? If so, in what ways? (see:</span><span class="c11">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides&sa=D&ust=1472368742789000&usg=AFQjCNF2HvBWhjpaPdtqzGxAwgPVwX8AJQ]</span><span class="c5">[https://www.google.com/url?q=https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides&sa=D&ust=1472368742790000&usg=AFQjCNG8ehR5S8E2LPPRcxy7tg8A4SGk4Q https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides]</span>)

===== <span class="c7">User Interface Elements</span> =====

<span>— 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>

<span>— 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>

<span>— 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>

<span>— 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.</span>

<span>- 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>