diff options
Diffstat (limited to 'files/bn/mozilla/localization/l10n_style_guide/index.html')
-rw-r--r-- | files/bn/mozilla/localization/l10n_style_guide/index.html | 115 |
1 files changed, 0 insertions, 115 deletions
diff --git a/files/bn/mozilla/localization/l10n_style_guide/index.html b/files/bn/mozilla/localization/l10n_style_guide/index.html deleted file mode 100644 index f586ff2a60..0000000000 --- a/files/bn/mozilla/localization/l10n_style_guide/index.html +++ /dev/null @@ -1,115 +0,0 @@ ---- -title: Mozilla L10n স্টাইল গাইড -slug: Mozilla/Localization/L10n_Style_Guide -translation_of: Mozilla/Localization/L10n_Style_Guide ---- -<p>{{draft}}</p> - -<h3 id="অর্থ_ভিত্তিক_অনুবাদ"><span class="author-p-1460 b"><strong>অর্থ ভিত্তিক অনুবাদ</strong></span></h3> - -<div id="magicdomid3"><span class="author-p-1460">When it comes to translation, </span><span class="author-p-1460">meaning is everything. We encourage you to consider the source text's meaning and find its most closely linked equal in your own language. Avoid literal translation at all costs. Finding meaning-based equivalents between languages can be difficult. To help concentrate your thoughts, ask yourself questions like:</span></div> - -<ul style="margin-left: 40px;"> - <li id="magicdomid4"><span class="author-p-1460">What does this word/sentence/string mean in English?</span></li> - <li id="magicdomid5"><span class="author-p-1460">What is the message the author is trying to send?</span></li> - <li id="magicdomid6"><span class="author-p-1460">How would I express that meaning in my own language?</span></li> -</ul> - -<h3 id="ব্যবহার"><span class="author-p-1460 b"><strong>ব্যবহার</strong></span></h3> - -<div id="magicdomid10"><span class="author-p-1460"> The target audience and their relationship with the Mozilla product determines a translation's usage. A determined translation usage is often maintained throughout a product localization, and even across various products within a single category.</span></div> - -<ul style="margin-left: 40px;"> - <li><span class="author-p-1460">For Mozilla desktop products, the target audience is general users with all levels of technical ability. This could indicate more formal language in the UI as the target audience's relationship with desktop products is less frequent. </span>It could, however, indicate informal language due to the level of implied trust between a user and their browser.</li> - <li id="magicdomid11"><span class="author-p-1460">For Mozilla mobile products, the target audience is general users carrying mobile devices. This could indicate more informal language in the UI as the target audience's relationship with a mobile device is interpreted to be more intimate and an extension of oneself. </span></li> - <li id="magicdomid12"><span class="author-p-1460">For Mozilla web pages, the target audience will vary according to the purpose of the web page. Seek to identify the web project's purpose and intended audience before translating strings.</span></li> -</ul> - -<h3 id="Brevity"><span class="author-p-1460 b"><strong>Brevity</strong></span></h3> - -<div id="magicdomid15"><span class="author-p-1460"> Space is limited in product user interfaces. There may be specific space limitations for each string. Pay close attention to where the string is being used within the product you are localizing. When selecting an accurate translation, keep in mind that your translation should be brief while still maintaining the original meaning.</span></div> - -<div> </div> - -<h3 id="অনুবাদযোগ্য_বনাম_অনুবাদের_জন্যে_নহে"><span class="author-p-1460 b"><strong>অনুবাদযোগ্য বনাম অনুবাদের জন্যে নহে</strong></span></h3> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Access_Keys"><span class="author-p-1460"> Access Keys</span></dt> -</dl> - -<dl> - <dd id="magicdomid19"><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></dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Variables"><span class="author-p-1460"> Variables</span></dt> -</dl> - -<dl> - <dd id="magicdomid21"><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.</dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Brands_and_Products"><span class="author-p-1460"> Brands and Products</span></dt> -</dl> - -<dl> - <dd id="magicdomid23"><span class="author-p-1460"> Brand and product names should never be translated, nor transliterated into a non-Latin based script.</span></dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Copyright.2Ftrademark"><span class="author-p-1460"> Copyright/Trademark</span></dt> -</dl> - -<dl> - <dd id="magicdomid25"><span class="author-p-1460"> Copyrights and trademarks should never be translated.</span></dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Code"><span class="author-p-1460"> Code</span></dt> -</dl> - -<dl> - <dd id="magicdomid27"><span class="author-p-1460"> Lines of code do not require translation. You will recognize a line of code by its use of angled and curly brackets. Anything contained within these brackets should not be translated. For example, <code>{moz:domain}+{searchTerms}</code> or <code><a target='_' href='</code></span><code><span class="author-p-1460 url"><a href="https://developer.mozilla.org/docs/Tools/Debugger#Remote_Debugging">https://developer.mozilla.org/docs/Tools/Debugger#Remote_Debugging</a></span></code><span class="author-p-1460"><code>'></code> should not be translated. However, if there is a localized equivalent content, change the URL to point to the target language site/page.</span></dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Blank.2FEmpty_strings"><span class="author-p-1460"> Blank/Empty Strings</span></dt> -</dl> - -<dl> - <dd id="magicdomid29"><span class="author-p-1460"> </span>Blank or empty strings are pieces of constructed UI that are available for localized text that needs to trail UI elements. This is a common need for RTL languages. The localization comments for these strings will describe the reason for the empty string and what localizers should do with it.</dd> -</dl> - -<dl> - <dt id=".C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0.C2.A0_Trailing_whitespace"><span class="author-p-1460"> Trailing Whitespace</span></dt> -</dl> - -<dl> - <dd id="magicdomid31"><span class="author-p-1460"> Trailing whitespace often indicates a break between two strings that will be brought together at runtime. Generally speaking this is a poor development practice, however, there are exceptions that permit developers to generate strings this way. When translating strings with trailing whitespaces before or after a string's text, seek to identify the corresponding string to learn how to appropriately translate the content. If you are unsure where the corresponding string is, ask around in the mozilla.dev.l10n newsgroup or file a bug in the appropriate product.</span><span class="author-p-1460"> </span></dd> - <dt style="margin-left: 40px;"><span class="author-p-1460">Keyboard shortcuts</span></dt> - <dd style="margin-left: 40px;"><span class="author-p-1460">Lorem ipsum https://developer.mozilla.org/en-US/docs/XUL_Accesskey_FAQ_and_Policies</span></dd> -</dl> - -<h3 id="Terminology"><span class="author-p-1460 b"><strong>Terminology</strong></span></h3> - -<h4 id="Translating_difficult_concepts"><span class="author-p-1460"> Translating difficult concepts</span></h4> - -<div id="magicdomid62"><span class="author-p-1460"> 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> - -<ol style="margin-left: 80px;"> - <li id="magicdomid63"><span class="author-p-1460">Understand the meaning of the term in English.</span></li> - <li id="magicdomid64"><span class="author-p-1460">Understand the function of the feature.</span></li> - <li id="magicdomid65"><span class="author-p-1460">Consider similar ideas for those functions in your culture.</span></li> - <li id="magicdomid66"><span class="author-p-1460">Associate a culturally specific image with the meaning and function of the term.</span></li> -</ol> - -<div> </div> - -<h4 id="Consistency_across_products_modules"><span class="author-p-1460"> Consistency across products & modules</span></h4> - -<div id="magicdomid68"><span class="author-p-1460"> Consistency in terminology use is supremely important as you translate terms and sentences that have the same meaning and application throughout the product. Once you have decided on a term for a given function (for example, the term "tab"), register it in a glossary for future use in other areas of the product.</span></div> - -<div id="magicdomid69"> </div> - -<div style="text-align: right;"><a href="https://developer.mozilla.org/en-US/docs/L10n_Style_Guide/Mozilla_Content_Localized_in_Your_Language" title="/en-US/docs/">Next: Mozilla content in your language</a></div> |