From a065e04d529da1d847b5062a12c46d916408bf32 Mon Sep 17 00:00:00 2001 From: Peter Bengtsson Date: Tue, 8 Dec 2020 21:46:22 -0500 Subject: update based on https://github.com/mdn/yari/issues/2028 --- files/bn/mozilla/localization/index.html | 17 --- .../localization/l10n_style_guide/index.html | 115 --------------------- 2 files changed, 132 deletions(-) delete mode 100644 files/bn/mozilla/localization/index.html delete mode 100644 files/bn/mozilla/localization/l10n_style_guide/index.html (limited to 'files/bn/mozilla/localization') diff --git a/files/bn/mozilla/localization/index.html b/files/bn/mozilla/localization/index.html deleted file mode 100644 index 73cded6c42..0000000000 --- a/files/bn/mozilla/localization/index.html +++ /dev/null @@ -1,17 +0,0 @@ ---- -title: Localization at Mozilla -slug: Mozilla/Localization -translation_of: Mozilla/Localization ---- -

In progress. Localization (L10n) is the process of translating software user interfaces from one language to another and adapting it to suit a foreign culture. These resources are for anyone with an interest in the technical aspects involved in localization. They are for developers and all contributors.

- -

See also

- -
-
Localizing MDN
-
This resource covers localization of the documentation here on MDN.
-
App localization
-
This set of documents applies more specifically to localizing apps, including Firefox OS apps.
-
L10n
-
Reference docs for the L10n API that Mozilla uses to localise Firefox OS.
-
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 ---- -

{{draft}}

- -

অর্থ ভিত্তিক অনুবাদ

- -
When it comes to translation, 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:
- - - -

ব্যবহার

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

Brevity

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

অনুবাদযোগ্য বনাম অনুবাদের জন্যে নহে

- -
-
        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 and Products
-
- -
-
            Brand and product names should never be translated, nor transliterated into a non-Latin based script.
-
- -
-
        Copyright/Trademark
-
- -
-
            Copyrights and trademarks should never be translated.
-
- -
-
        Code
-
- -
-
            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, {moz:domain}+{searchTerms} or <a target='_' href='https://developer.mozilla.org/docs/Tools/Debugger#Remote_Debugging'> should not be translated.  However, if there is a localized equivalent content, change the URL to point to the target language site/page.
-
- -
-
        Blank/Empty Strings
-
- -
-
            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.
-
- -
-
        Trailing Whitespace
-
- -
-
            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.           
-
Keyboard shortcuts
-
Lorem ipsum https://developer.mozilla.org/en-US/docs/XUL_Accesskey_FAQ_and_Policies
-
- -

Terminology

- -

        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:
- -
    -
  1. Understand the meaning of the term in English.
    2. -
  2. Understand the function of the feature.
    3. -
  3. Consider similar ideas for those functions in your culture.
    4. -
  4. Associate a culturally specific image with the meaning and function of the term.
    5. -
- -
 
- -

        Consistency across products & modules

- -
            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.
- -
 
- -
Next: Mozilla content in your language
-- cgit v1.2.3-54-g00ecf