L10n:Teams:km/Style Guide

From MozillaWiki
Jump to: navigation, search

របៀប​បកប្រែ (Style Guides) គឺជា​ឯកសារ​ស្តង់ដារ​មួយ​ដែល​ត្រូវបាន​បង្កើត​មក ដើម្បី​ធានា​ឲ្យ​ការ​បកប្រែ​មាន​គុណភាព។ ឯកសារ​ទាំងនេះ​មាន​ក្បួន​ច្បាប់​ដែល Mozilla រួម​ទាំង​សហគមន៍​បកប្រែ Mozilla បាន​កំណត់​មក ដើម្បី​ឲ្យ​ផលិតផល វេបសាយ និង​គម្រោង​ផ្សេងៗ​ទៀត​របស់ Mozilla មាន​គុណភាព។ របៀប​បកប្រែ​នេះ​ត្រូវបាន​ប្រើ​ទាំង​សម្រាប់​ការបកប្រែ និង​សម្រាប់​ការ​ពិនិត្យ​គុណភាព​បកប្រែ។ ដូច្នេះ​ហើយ ការ​អនុវត្ត​តាម​គោលការណ៍​ទាំង​នេះ នឹង​ធ្វើ​ឲ្យ​ការ​បកប្រែ​មាន​គុណភាព​ខ្ពស់ ជា​ការ​បង្ហាញ​ឲ្យ​ឃើញ​អំពី​តម្លៃ​និង​វប្បធម៌​របស់ Mozilla។ ឯកសារ​នេះ​ត្រូវបាន​បែងចែក​ជា​ពីរ​ផ្នែក ដែល​ផ្នែក​ដំបូង​និយាយ​អំពី​គោលការណ៍​នៅ​ក្នុង​ភាសាខ្មែរ ហើយ​ទីពីរ​ស្ដី​អំពី​ក្បួន​ច្បាប់​ទូទៅ​ដែល Mozilla បាន​កំណត់​ជាស្រេច​សម្រាប់​អ្នកបកប្រែ​នៃ​គ្រប់​ភាសា ដើម្បី​ជួយ​ពួកគេ​ឲ្យ​បកប្រែ​បាន​ល្អ​ប្រសើរ។

Contents

របៀប​បកប្រែ​សម្រាប់​ភាសាខ្មែរ

រចនាបទ

រចនា​បទ​ឬ​របៀប​នេះ ត្រូវបាន​បង្កើត​ឡើង​ចំពោះ​តែ​ភាសាខ្មែរ និង​ដោយ​ក្រុម​អ្នក​បកប្រែ​ខ្មែរ​នៃ​សហគមន៍​ Mozilla។

ភាសា​ផ្លូវការ ​និង​របៀបរបប​​និយាយ/សរសេរ

នៅ​ក្នុង​ការ​ប្រែសម្រួល​ជា​ភាសាខ្មែរ ភាព​ត្រឹមត្រូវ​និង​របៀបរបប​​និយាយ មិន​ចោទ​ជា​បញ្ហា​ខ្លាំង​នោះ​ទេ ពីព្រោះ​អ្នក​ប្រើប្រាស់​ភាគច្រើន​ជា​អ្នក​ទូទៅ ដូច្នេះ​ហើយ​ការ​បកប្រែ​យក​ត្រឹម​កម្រិត​កណ្ដាល ពោល​គឺ​មិន​ផ្លូវ​ការ​ពេក​និង​មិន​លេង​សើច​ពេក គឺ​ជា​ជម្រើស​ដ៏​ប្រសើរ​ជាង​គេ​នៅ​ក្នុង​ការ​បកប្រែ​ជា​ភាសាខ្មែរ។ ឧទាហរណ៍​ថា៖ “ចុច​ទី​នេះ” និង “សូម​ចុច​ទី​នេះ” គឺ​មិន​មាន​បញ្ហា​អ្វី​ទាំងអស់​សម្រាប់​ភាសា​ខ្មែរ ប៉ុន្តែ​ជម្រើស​ទី​មួយ​ល្អ​ជាង ពីព្រោះ​ខ្លី​និង​អាច​ទទួល​យក​បាន។ សូម​ចាំ​ថា​កុំ​ប្រើ​ភាសា​ផ្លូវការ​ពេក​ដូចជា “សូម​មេត្តា​បំពេញ​ប្រឡោះ​មួយ​នេះ”, “តើ​លោក​អ្នក​ប្រាកដ​ក្នុង​ចិត្ត​ថា​ចង់​លុប​ការ​ទាញយក​នេះ​ហើយ​មែន​ដែរ​ឬ​ទេ?” ហើយ​មក​ប្រើ​ត្រឹម “សូម​បំពេញ​ប្រឡោះ​នេះ”, “តើ​អ្នក​ពិត​ជា​ចង់​លុប​ការ​ទាញយក​នេះ​មែន​ឬ?”

សំនួន​បែប​ធម្មជាតិ

នៅ​ក្នុង​ការ​បកប្រែ​មកជា​ភាសាខ្មែរ ការ​ប្រើប្រាស់​សំនួន​បែប​ធម្មជាតិ​ជា​ប្រការ​ដែល​មិន​អាច​ចៀស​បាន ដើម្បី​ឲ្យ​ប្រយោគ​ទាំងអស់​នោះ​មាន​លក្ខណៈ​ជា​ខ្មែរ។ ការ​បកប្រែ​ទៅតាម​សំនួន​បែប​ធម្មជាតិ មិនមែន​ជា​កិច្ចការ​ដែល​ងាយស្រួល​នោះ​ទេ គឺ​ទាមទារ​ឲ្យ​អ្នក​បកប្រែ​ត្រូវ​ប្រាកដ​នៅ​ក្នុង​ភាសាខ្មែរ​និង​ភាសា​អង់គ្លេស (បើ​ប្រើ​ភាសា​អង់គ្លេស​ជា​គោល​បកប្រែ)។ ឧទាហរណ៍​ដូចជា “Get connected. Get started.” មិន​អាច​បកប្រែ​ដោយ​ពាក្យៗ​បាន​នោះ​ទេ ដូច្នេះ​ដើម្បី​សម្រួល​មក​ជា​បែប​ខ្មែរ​គឺ “ឲ្យ​តែ​មាន​អ៊ីនធឺណិត អាច​ប្រើ​បាន​ភ្លាម។”

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:

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

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).

ភាពត្រូវគ្នា​នៃ​ការ​បកប្រែ

ជា​ចុងក្រោយ យើង​ត្រូវ​គោរព​តាម​របៀបរបប​បកប្រែ និង​​ម៉ាក​របស់​ Mozilla និង​ភាគី​ទី​បី ចំពោះ​​​គម្រោង​បកប្រែ​ទាំងអស់។ ព័ត៌មាន​បន្ថែម​អំពី​គោលការណ៍​ណែនាំ​​ម៉ាក​ដែល Mozilla បាន​បញ្ជាក់​អាច​ស្វែងរក​នៅ​ទីនេះ៖ https://www.mozilla.org/en-US/styleguide/identity/firefox/branding/។ ឧទាហរណ៍ ឈ្មោះ​ម៉ាក​ខ្លះ​ យើង​មិន​គួរ​បកប្រែ​​ឡើយ ដូចជា "Firefox"។ ចំពោះ​ម៉ាក​ផ្សេងៗ​ដែល​មិន​​មាន​នៅ​ក្នុង​គោលការណ៍​ណែនាំ​អំពី​ម៉ាក​ណា​មួយ​ទេ សហគមន៍​របស់​អ្នក​ត្រូវតែ​កំណត់​ឲ្យ​បាន​ច្បាស់លាស់​​ថា​តើ​គួរ​បកប្រែ​យ៉ា​ងដូចម្ដេច។ សូម​យកចិត្តទុកដាក់​បន្ថេម​លើ​គោលការណ៍​ណែនាំ​អំពី​​ដាក់​ប្រើប្រាស់​ម៉ាក មុន​ពេល​សម្រេច​ចិត្ត​ថា​បកប្រែ​​ឈ្មោះ ឬ​មិន​បកប្រែ (ទាំង​សម្រាប់ Mozilla ឬ​សម្រាប់​ភាគី​ទី​បី)។ ឧទាហរណ៍ Mozilla Firefox ត្រូវ​ទុក​ដដែល កុំ​បកប្រែ​ឲ្យ​សោះ។ Firefox for Android អាច​បកប្រែ​ថា Firefox សម្រាប់ Android។

ពាក្យ​បច្ចេកទេស

Here are a few existing term bases we approve of for software/internet terminology and definitions (though not limited to):

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 for software and internet terminology. Avoid the following:

  • Inconsistent use of terminology within the project
  • Inconsistent use of terminology with term base
  • Inconsistent use of terminology across all of your projects
  • Using terminology from another subject matter (e.g., don't use medical terminology in Firefox).

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.

Developing new term bases

What is your community's process for identifying and creating a new termbase? Here are a few things to keep in mind:

  • Avoid overly borrowing English expressions
  • Referencing another language from the same language family may inspire you to come up with your own terms
  • Consider the product target audience (age, level of literacy, education, social and economic status)
  • Will you use loan words from another language or coin new terms in your language to maintain language purity? Is there government requirement or policy to encourage creating new terms for new concepts, or will loanwords be sufficient to reach broader masses and expedite new technology adoption?
  • 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?

ឯកត្តា​និង​វេយ្យាករណ៍

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.

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

ឯកត្តា​និង​ការ​បំប្លែង​ឯកត្តា

ទម្រង់​កាលបរិច្ឆេទ

How are the date formats for weeks and months expressed in the following forms:

  • 1). Fully spelled out 2). 2 or 3 letters 3). Single letter
  • What is the order of Year, Month and Day?

Reference material can be find here: https://en.wikipedia.org/wiki/Date_format_by_country

ប្រតិទិន

  • Which date is considered the first day of the week, Sunday or Monday?
  • Is Lunar calendar observed? Other regional calendar observed?

ទម្រង់​ម៉ោង

How is time expressed in your language? Including 0-24 hr expression, hour, minute and second.

តួលេខ

How are numerals and percentages expressed in your language?

   Example: 1.23 (decimal separator) or 1,000 (thousand separator) using comma or period. 

រូបិយបណ្ណ

What are other widely used currency and symbols used in your country/language for paid apps.

ឯកត្តា

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.

ឈ្មោះ

What are the order of family name and given name in your language? Here is the guideline on the naming convention from w3c.org:

ទម្រង់​អាសយដ្ឋាន​និង​លេខ​ប្រៃសណីយ៍

What is the format in your language?

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

ទម្រង់​លេខ​ទូរសព្ទ

Space separators between digits can be different for area codes such as State (Province) and City,

ការប្រកប​និង​វេយ្យាករណ៍

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.

កាល

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: https://en.wikipedia.org/wiki/Grammatical_tense )

ទម្រង់​ពាក្យ

ពហុវចនៈ

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. https://developer.mozilla.org/en-US/docs/Mozilla/Localization/Localization_and_Plurals and here: http://www.unicode.org/cldr/charts/latest/supplemental/language_plural_rules.html

អក្សរ​កាត់

How are abbreviations expressed in your language?

   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: https://en.wikipedia.org/wiki/Abbreviation)    

If your language does not have a standard way of expressing abbreviations, do you simply leave them in English? Acronyms Are there standard translations of widely accepted acronyms such as CD, DVD, MB in your language? If not, do they remain in English? (see: https://en.wikipedia.org/wiki/Acronym )

វណ្ណយុត្តិ

Do you use different punctuation rules in your Firefox localization than what your language standard defines?

   Example: do you use a period at the end of every user interface element translation or only some? What is the international/national standard for punctuation in your language?

Emphasis

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

  • If so, do those standard rules apply in all product translations?
  • If this doesn't apply, how do you indicate importance or name of a movie, book title, product UIs (Save, File...) in your language?
  • How does your language handle the use of bold, italic, or underline types to express emphasis? ( See: https://en.wikipedia.org/wiki/Italic_type )

Hyphens and compounds

What is the appropriate way of using hyphens and compounds in your language? ( https://en.wikipedia.org/wiki/Compound_%28linguistics%29 )

Prepositions and articles

What is the appropriate form of expressing prepositions and articles in your language?

Diacritics and Special characters

Does your language use any special or accented characters and will they be applied and preserved in sort orders, and other aspects of the translation? (see: https://en.wikipedia.org/wiki/Diacritic )

Quotes

Does your language have a standard use for quotation marks, parenthesis, or brackets? Whitespace Does your language require the use of white space around words, sentences, paragraphs, etc.? If so, in what ways? (see: https://en.wikipedia.org/wiki/Sentence_spacing_in_language_and_style_guides )

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 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.
  • 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.

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.

មិនគួរបកប្រែ

អក្សរ​កាត់ និង គ្រាប់ចុច​ចូល​ដំណើរ​ការ

In Firefox and other software it's possible to use keyboard shortcuts to invoke a specific command. For example, to open a file in Firefox you can press the combination of keys CTRL+O (Cmd+O on Mac). The accelerator key depends on the operative system, but the letter itself is normally localizable. This is what is called a shortcut, or commandkey. For example, the Open File… menu item is stored as

 <!ENTITY openFileCmd.label "Open File…">
 <!ENTITY openFileCmd.accesskey "O">
 <!ENTITY openFileCmd.commandkey "o">

The commandkey is stored in openFileCmd.commandkey (sometimes the string has .key in the identifier). Normally you should not localize this key, since shortcuts are often common across the entire operative system (e.g. CTRL+S to Save) or similar products (CTRL+T to open a new tab in most browsers). But it needs to be localized if the letter is not available in your keyboard layout. For example, in Italian the character [ can be accessed through ALT+è, a command key [ would not work.

In the code fragment above you see also an accesskey defined for Open File…. Accesskeys are used to access a UI element from the keyboard. Example: if File menu has an accesskey F, and the Open file… menu has O, you can press ALT+F to access the menu, and then O to open a file.

If the label is File, and the accesskey is F, it will be displayed as "File" on Windows and Linux, with an underscored F. If the accesskey was "O", so a character not available in the original label, it will be displayed underlined between parenthesis: "File (O)".

One important thing to determine is if, for your locale, it makes sense to have localized accesskeys: for example, if most users will use a keyboard with a different layout (English), it might make sense to keep the English original accesskey instead of using a letter available in your localization. Accesskeys, like commandkeys, have their own lines within .dtd and .properties files and are usually identified by .accesskey in the string ID.

អថេរ

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.

យីហោ, រក្សាសិទ្ធិ, និង​សញ្ញា​ពាណិជ្ជកម្ម

Brand names, as well as copyright and trademarks should never be translated, nor transliterated into a non-Latin based script. See the 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.