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/id/mozilla/localization/index.html | 30 ---- .../localizing_with_verbatim/index.html | 158 ----------------- .../localization/quick_start_guide/index.html | 50 ------ .../quick_start_guide/qa_phase/index.html | 197 --------------------- .../localization/web_localizability/index.html | 33 ---- 5 files changed, 468 deletions(-) delete mode 100644 files/id/mozilla/localization/index.html delete mode 100644 files/id/mozilla/localization/localizing_with_verbatim/index.html delete mode 100644 files/id/mozilla/localization/quick_start_guide/index.html delete mode 100644 files/id/mozilla/localization/quick_start_guide/qa_phase/index.html delete mode 100644 files/id/mozilla/localization/web_localizability/index.html (limited to 'files/id/mozilla/localization') diff --git a/files/id/mozilla/localization/index.html b/files/id/mozilla/localization/index.html deleted file mode 100644 index ea5809653c..0000000000 --- a/files/id/mozilla/localization/index.html +++ /dev/null @@ -1,30 +0,0 @@ ---- -title: Pelokalan di Mozilla -slug: Mozilla/Localization -tags: - - ButuhPenerjemahan - - Landing - - Localization - - Mozilla - - NeedsTranslation - - Pelokalan - - Pendaratan - - Penerjemahan - - RintisanTopik - - TopicStub - - Translation - - l10n -translation_of: Mozilla/Localization ---- -

Pelokalan (L10n) adalah proses menerjemahkan antarmuka pengguna sebuah perangkat lunak dari satu bahasa ke bahasa yang lain, dan menyesuaikannya agar sesuai dengan kultur setempat. Semua sumber daya tersedia bagi siapa saja yang berminat dalam aspek teknis untuk terlibat dalam pelokalan, bagi para pengembang dan semua kontributor.

- -

Lihat pula

- -
-
Pelokalan MDN
-
Sumber daya ini mencakup pelokalan dokumentasi di MDN.
-
Pelokalan aplikasi
-
Kumpulan dokumen ini secara khusus digunakan untuk pelokalan aplikasi, termasuk aplikasi Firefox OS.
-
L10n
-
Dokumen referensi untuk API L10n yang digunakan Mozilla dalam pelokalan Firefox OS.
-
diff --git a/files/id/mozilla/localization/localizing_with_verbatim/index.html b/files/id/mozilla/localization/localizing_with_verbatim/index.html deleted file mode 100644 index 14e7d665b6..0000000000 --- a/files/id/mozilla/localization/localizing_with_verbatim/index.html +++ /dev/null @@ -1,158 +0,0 @@ ---- -title: Pelokalan dengan Verbatim -slug: Mozilla/Localization/Localizing_with_Verbatim -translation_of: Mozilla/Localization/Localizing_with_Pontoon ---- -

Verbatim adalah suatu alat berbasis web (khususnya Pootle yang dihosting Mozilla) untuk melokalkan konten web Mozilla. Alat tersebut dapat digunakan untuk melokalkan berbagai proyek Mozilla dan mampu mendukung bahasa apa saja. Panduan ini akan membantu Anda melakukan pelokalan proyek Mozilla pada umumnya. Tutorial yang disediakan di sini akan memberi Anda landasan yang bermanfaat dalam penggunaan Verbatim untuk melokalkan setiap proyek Mozilla yang ingin Anda ikut sertakan dalam upaya komunitas pelokalan Anda. Kita akan membahas proyek-proyek khusus yang sedang menggunakan Verbatim, cara untuk mulai menggunakan Verbatim, dan pekerjaan-pekerjaan yang umumnya dapat diselesaikan dengan Verbatim.

- -

Mulai menggunakan Verbatim

- -

Being that it is web-based, localizers must be online to use Verbatim. There are essentially two ways to get started with Verbatim: start a new localization or join an existing localization community's efforts. Either way, you will need to follow these steps to start working on a Verbatim project.

- - - - - - - - - - - - - - - - - - - - - - -
Start a new localization on VerbatimJoin an existing localization on Verbatim
-
    -
  1. Point your browser to http://localize.mozilla.org. This is where Verbatim is hosted.
    2. -
- 		-
    -
  1. Point your browser to http://localize.mozilla.org. This is where Verbatim is hosted.
    2. -
-
-
    -
  1. If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.
    2. -
- 		-
    -
  1. If you have a Mozilla LDAP account, simply sign in using your LDAP credentials. If not, register for an account and sign in once you've completed registration. The links for both are located in the upper right-hand corner of the page.
    2. -
-
-
    -
  1. File a bug using this prefilled bugzilla template. Add your locale code and language name to the description field, as well as any other information you'd like to share. See the following example.
    2. -
- -
Example: I would like to request that you add the en-US as a new localization in Verbatim. The langauge is English. Also, I like cookies. Lots and lots of cookies. I can easily be motivated by any and all baked goods.
- 		-
    -
  1. Contact the community to find out which projects they need you to concentrate your efforts on. See the following example for what you could include in your email to the community leaders.
    2. -
- -
Example: I would like to join your localization efforts on Verbatim for this locale. Where would be the best place for me to begin? Also, I would like to buy you a drink to encourage you to let me join the team!
-
- -

Now that you're registered and logged in, we'll outline the general translation workflow, using the MDN project page as our example.

- -

Translating

- -

First thing's first, you need to find untranslated source strings to translate.

- -
    -
  1. Navigate to the MDN project page.
    2. -
  2. Select your language from the Overview tab.
    3. -
  3. Now click on the the Translate tab. This tab will display the directories for the MDN user interface.
    4. -
  4. Select the LC Messages directory. This is where the project's .po files containing translatable strings are located. You will now see an overview of each .po file.
    5. -
  5. In the summary column, the number of words untranslated will be shown as a link. Click on that link to be taken directly to the first string that needs to be translated.
    6. -
- -

Now you're ready to contribute translations and you won't believe how easy it is. Check it out, you can contribute translations in two simple steps:

- -
    -
  1. Simply type your translation in the box to below the English string
    2. -
  2. Select Suggest. If you have approval permission, select Submit. You will then be taken to the next string that needs translating.
    3. -
  3. Hooray! You're translating! Repeat steps one and two for the remainder of the untranslated strings.
    4. -
- -
Note: If you come across a string that already has a suggested translation, you can still suggest your own translation if you feel it is more accurate.
- -

Some extra cool features on Verbatim

- -

Here are a few additional items about the Verbatim interface that you should be aware of. Some of these can be seen in the screen shot below.

- -

Translate Tab.png

- - - -

Additional tasks

- -

If you are a localizer with approval priviledges, here are a few more tasks that you should be aware of.

- -

Review suggested translations

- -
    -
  1. Click on the Review tab. It will show how many strings are waiting for review for each .po file.Review Tab1.png
    2. -
  2. Select Review suggestions to start approving suggestions. It will take you to the first string that needs to be reviewed.
    3. -
  3. You can accept the suggestion by clicking the green checkmark or reject the suggestion by clicking the red X (see the screen shot from the previous section).
    4. -
- -

It is important to note that only submitted strings will appear in your localized pages. Neither suggestions nor fuzzy strings will appear. Before commiting your final localized product, make sure all strings have been submitted.

- -

Using VCS on Verbatim

- -

VCS (Version Control System) is the repository system we use to update the project's strings as well as push your translated content onto the web. The difference between the two tasks is simply a matter of which link to click.

- -

VCS.pngTo push your strings onto the web and see your changes, simply select the Commit to VCS link underneath each file name. It usually takes about an hour before you can see your changes on the project site.

- -

To update your .po files with new untranslated strings, simple select the Update from VCS link underneath each file name.

- -

 

- -

-Note: Some projects are automatically updated nightly while others require you to manually update them to receive new source content. Be sure to pay close attention to this, as it can alter your workflow.
- -

Translating Verbatim files with an external application

- -

While in the Translate tab, you have the option to export the .po and .xliff files and translate the strings with an external application (i.e., a text editor or translation memory tool).

- -
    -
  1. To download the .po file, select the Download link found underneath each file name. To download the .xliff file, select the Download XLIFF link.
    2. -
  2. Proceed to translate the strings using your selected tool.
    3. -
- -

Once you've finished your translations, you'll need to upload your file to Verbatim. You can do this from the Translate tab.

- -
    -
  1. Navigate to the bottom of the files list to the Upload File section.
    2. -
  2. Click on the Browse button and select the file you wish to upload.
    3. -
  3. Select an upload setting from the options provided.
    4. -
  4. Once your upload setting has been selected, click Upload.
    5. -
- -
-

Important: There have been some problems in the past with community members updating their source strings while others are in the process of localizing the previous updated files. This can cause community members to overlook new source strings, producing untranslated strings in a localized project. Be sure to coordinate these manual updates within your community to avoid this problem.

-
- -

You're ready to go!

- -

Whew! You've arrived at the end! Time to take what you've learned and put it to good use spreading Mozilla to everyone in your region. Have fun and let us know if you run into any difficulties. We'll be happy to help in any way we can.

- -

 

- -

Back: Quick Start Guide

diff --git a/files/id/mozilla/localization/quick_start_guide/index.html b/files/id/mozilla/localization/quick_start_guide/index.html deleted file mode 100644 index 216207c9c4..0000000000 --- a/files/id/mozilla/localization/quick_start_guide/index.html +++ /dev/null @@ -1,50 +0,0 @@ ---- -title: Panduan memulai cepat pelokalan -slug: Mozilla/Localization/Quick_start_guide -tags: - - ButuhPenerjemahan - - Guide - - Localization - - Mozilla - - NeedsTranslation - - Panduan - - Pelokalan - - Penerjemahan - - RintisanTopik - - TopicStub - - Translation -translation_of: Mozilla/Localization/Quick_start_guide ---- -

Selamat datang di pelokalan Mozilla (singkatnya L10n)!

- -

Entah Anda berada di sini untuk memulai pelokalan Anda sendiri dalam proyek Mozilla ataupun untuk bergabung dalam upaya pelokalan yang sedang berlangsung, Anda datang ke tempat yang tepat! Panduan ini memuat semua informasi dasar dan teknis yang Anda perlukan untuk terlibat dalam program L10n Mozilla. Kami akan menunjukkan kepada Anda langkah-langkah untuk memulainya, dari pengaturan awal hingga pengetesan dan perilisan pelokalan Anda sendiri. Dalam prosesnya, Anda akan mempelajari berbagai proyek yang di dalamnya Anda dapat berkontribusi dan semua alat yang digunakan untuk pelokalan.

- -

Bilamana kita berhadapan dengan kasus-kasus khusus, kita mengambilnya dari proyek Firefox sebagai proyek yang paling banyak dilakukan pelokalan di Mozilla. Dan ketika Anda hampir menyelesaikan panduan ini, Anda seharusnya mampu melakukan perubahan pada pengaturan lokal Firefox Anda dan menyaksikan perubahan pada antarmukanya. Akhir kata, setelah Anda menyelesaikan panduan ini, Anda akan memiliki semua alat yang diperlukan untuk mulai berkontribusi!

- -

Ingat, panduan ini hanya memuat instruksi seputar aspek teknis L10n Mozilla saja. Kunjungi halaman Proses L10n untuk mempelajari keseluruhan prosesnya.

- -
-

Pengaturan awal

-Persiapan teknis sebelum melakukan pelokalan.
- -
-

Tahap penerjemahan

-Tutorial penggunaan alat L10n untuk penerjemahan.
- -
-

Tahap QA

-Tutorial pengetesan L10n.
- -
-

Tahap perilisan

-Langkah-langkah mengirimkan pekerjaan pelokalan Anda.
- -
Keempat tahap ini merupakan sisi teknis dari program L10n. Untuk mempelajari lebih lanjut tentang semua ini, silakan klik salah satu tautan di atas. Untuk mendapatkan gambaran besarnya, kami sarankan Anda memulai dengan boks hijau dan melanjutkannya secara bertahap.
- -

 

- -
Note: This guide is written for two types of contributors: those starting a new localization and those joining an existing localization. It is important to know which information applies to which type of contributor. To help you filter through to the most applicable information, note that all information that is unique to those starting a new localization will be in orange font. All information that is unique to those joining an existing localization will be in blue font.
- -

 

- -

{{ Next("Localization_Quick_Start_Guide/Initial_setup") }}

diff --git a/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html b/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html deleted file mode 100644 index 0ee69f43e4..0000000000 --- a/files/id/mozilla/localization/quick_start_guide/qa_phase/index.html +++ /dev/null @@ -1,197 +0,0 @@ ---- -title: Tahap QA -slug: Mozilla/Localization/Quick_start_guide/QA_phase -translation_of: Mozilla/Localization/Quick_start_guide/QA_phase ---- -

Setelah hasil kerja keras anda dalam melokalisasi kami yakin bahwa anda tidak hanya ingin melihat hasil kerja anda tapi juga ingin memastikan bahwa itu tepat! Jika anda tidak begitu awam dengan kode, anda pasti khawatir akan merusak sesuatu (oops!). Sekarang kami akan menuntun anda melakukan test kualitas pekerjaan anda untuk memastikan anda berada di jalur yang tepat.

- -

Jika anda melokalisasi halaman Mozilla, hasil pekerjaan anda akan ditampilkan segera setelah anda menyelesaikannya tanpa membutuhkan paket bahasa. Seperti halnya kasus ini, bagian dari pedoman ini tidak sepenuhnya dapat di aplikasikan oleh anda. Silahkan tekan tombol Next pada bagian paling bawah laman jika anda ingin melewati.

- -

Untuk melihat hasil pekerjaan anda di Firefox (atau dalam aplikasi Mozilla yang lain), anda butuh paket bahasa yang terinstal pada direktori anda.

- -

Manual & automated builds

- -

Dengan menekan tombol, beberapa alat L10n (seperti Narro and Koala) secara otomatis membuat paket bahasa untuk anda. Jika anda menggunakan salah satu dari alat tersebut, silahkan menuju ke bagian Melihat pekerjaan anda, Sekarang mari menuju ke pembuatan paket bahasa anda sendiri secara manual.

- -
Note: Remember all of those pre-requisite tools we asked you to install in the initial setup? Here's where you'll need almost all of them. If you haven't installed them yet, now is the time to do it.
- -

Persiapan

- -

Kita akan menggunakan file direktori berikut sebagai contoh:

- -
your working directory (root)/
-    mozilla-aurora (en-US source, pulled from http://hg.mozilla.org/releases/mozilla-aurora  )/
-    l10n-central (directory for L10n directories, one per L10n; often referred to as "l10n base")/
-       your-locale-code (a directory with your L10n files, in this example we'll use x-testing)
-
-Example: root/mozilla-aurora & root/l10n-central/x-testing
-
- -

Additionally, you will need to c

- -

Please either follow the above structure closely or adjust the commands below according to your custom setup.

- -

To copy this file to the appropriate directory, do the following:

- -
    -
  1. Navigate to your working directory from your command-line terminal (i.e., where you created the folder structure described above).
    2. -
  2. Enter the following commands:
    3. -
- -
mkdir -p l10n-central/x-testing/toolkit/
-
-cp mozilla-aurora/toolkit/locales/en-US/defines.inc l10n-central/x-testing/toolkit/defines.inc
-
- -

Tah-dah! Copied!

- -

Finally, you will need a file called .mozconfig to proceed with manual builds. This file contains the necessary build instructions.

- -

To create and configure this file, follow these instructions:

- -
    -
  1. Update the Mozilla source code:
    2. -
- -

$ cd mozilla-aurora
- $ hg pull -u

- -
    -
  1. Enter the following command to create the .mozconfig file: $ nano -w .mozconfig
    2. -
  2. Enter the following lines in your .mozconfig file:
    3. -
- -
mk_add_options MOZ_OBJDIR=@TOPSRCDIR@/../firefox-build
-ac_add_options --disable-compile-environment
-ac_add_options --with-l10n-base=../l10n-central # path relative to MOZ_OBJDIR
-ac_add_options --enable-application=[browser or mail]
-
- -

You will need to specify which application you're localizing in the fourth line (e.g., for Firefox, that's browser, Thunderbird would be mail).

- -
    -
  1. Enter the following command to perform the configuration: $ mach configure
    2. -
  2. Once your command-line finishes spitting out the config command's output, navigate to the newy created directory: $ cd ../firefox-build/browser/locales
    3. -
- -

Now you're ready to build! At this point you can choose between two build options. You can either:

- - - -

Visit the links above to learn how to make these testing builds.

- -

Testing your L10n & seeing your work

- -

Now that you have your langpack or L10n repack, let's discuss seeing your work and testing it in the application.

- -

Testing the langpack will put you one step closer to having your localization added to the L10n releases. Follow the steps below to test your localization:

- -
    -
  1. Install Aurora in your preferred language.
    2. -
  2. Install the .xpi langpack you just created (or exported).
    3. -
  3. Set your language using the Quick Locale Switcher or Locale Switcher add-ons by navigating to Tools->Language->Your localization's language code.
    4. -
  4. Restart your browser and start testing!
    5. -
- -

Now you should be able to see all of your work up to this point. Click here for guidelines on how to test your localization.

- -

Don't lose your work!

- -

You're work is SO important! We would really hate to see you lose any of it. After you test your localization, you should send it to a remote repository, which will serve as a backup for your work and will let others follow your progress. We're going to go through the process below.

- -

The official localization teams use repositories at hg.mozilla.org. Before a team becomes official, we like to get the localizers comfortable with the Hg commands that allow for cloning, pulling, committing, and pushing work to an experimental repository.  We use a web service called Bit Bucket to start the learning process.

- -
Note: You must have Mercurial configured before you begin. That step is back on the initial setup page. If you haven't done that yet, don't worry, we'll wait for you!
- -

Pushing to your repository

- -

There are a couple of things you should take note of before you push to your repository:

- - - -

The instructions below will help you learn how to use your Hg repository.

- -
    -
  1. After your new repository is created by the l10n-drivers, please visit the URL for your repo. We'll use x-testing here for our example. You can do this by entering the following URL into your browser: http://hg.mozilla.org/l10n-central/x-testing
    2. -
  2. Now, navigate to your locale's directory on your local machine.
    3. -
- -

If you're using Koala, this should be located at /path/to/your/koala.project/locale/3.6/x-testing, otherwise, it should be located at /path/to/your/working_dir/l10n_base/x-testing.

- -

In this directory, you should have an hg repository. You might have created it yourself by running hg init or hg clone or you might have had it created by Koala when you were setting up a new localization project. Also at this point, you shouldn't have any uncommitted changes (i.e., running the hg status command should show nothing). Let's see what the last revision in this repository is.

- -
    -
  1. Enter the following command: $ hg log -l 1
    2. -
- -

You should see an output similar to the one below:

- -
changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Now compare the local repository on your machine with the remote Hg repository by entering this command: $ hg outgoing http://hg.mozilla.org/l10n-central/x-testing
    2. -
- -

The hg outgoing command compares the two repositories and lists all changesets that are present locally, but not in the remote repository. These changesets will need to be "pushed" to the remote repository. You can expect to see output like this:

- -
comparing with http://hg.mozilla.org/l10n-central/x-testing
-searching for changes
-
-changeset:   0:7c543e8f3a6a
-tag:         tip
-user:        Your Name <email@example.com>
-date:        Mon Nov 23 18:08:25 2009 +0100
-summary:     Added search bar strings
-
- -
    -
  1. Let's now push this changeset. Enter the following command: hg push http://hg.mozilla.org/l10n-central/x-testing
    2. -
  2. Mercurial will connect to your repo and ask you to provide your account information (i.e., the username and the password).
    3. -
- -
real URL is http://hg.mozilla.org/l10n-central/x-testing
-pushing to http://hg.mozilla.org/l10n-central/x-testing
-searching for changes
-http authorization required
-realm: hg.mozilla.org HTTP
-user: your_id
-password:
-
- -

After you enter your account information, the changeset will be pushed.

- -
adding changesets
-adding manifests
-adding file changes
-added 1 changesets with 2 changes to 2 files
-bb/acl: your_id is allowed. accepted payload.
-quota: 979.7 KB in use, 150.0 MB available (0.64% used)
-
- -

Your changeset has been successfully pushed to your repository!

- -

As you begin to move through your translations, you should commit the changes locally and push your work to this experimental repository. For instance, if you have finished translating all the .dtd and .properties files in your x-testing/browser/chrome/browser/ directory, then you should run these commands:

- -
$ hg status
-$ hg commit -m "Translated browser/chrome/browser/"
-$ hg outgoing
-$ hg push http://hg.mozilla.org/l10n-central/x-testing
- -

Note that due to the distributed nature of Hg, hg commit saves the changes locally (i.e., in your computer's Hg repository). You can see the history of commits with hg log. After doing hg commit, you still need to send the changes to the remote repository. This is where hg push comes in. This sends your commits to the remote repository.

- -

Now you're ready to proceed to the release phase!

- -

 

- -

{{ PreviousNext("Localization_Quick_Start_Guide/Translation_phase", "Localization_Quick_Start_Guide/Release_phase") }}

diff --git a/files/id/mozilla/localization/web_localizability/index.html b/files/id/mozilla/localization/web_localizability/index.html deleted file mode 100644 index e4ff426a11..0000000000 --- a/files/id/mozilla/localization/web_localizability/index.html +++ /dev/null @@ -1,33 +0,0 @@ ---- -title: Kemampulokalan Web -slug: Mozilla/Localization/Web_Localizability -tags: - - Internationalization - - Localizability - - Localization - - NeedsTranslation - - TopicStub - - Web Development -translation_of: Mozilla/Localization/Web_Localizability ---- -

Kemampulokalan (atau singkatnya l12y) adalah karakteristik yang terkandung dalam suatu aplikasi atau konten yang memungkinkan untuk dilakukan pelokalan. Daftar berikut ini berisi tautan ke halaman yang menjabarkan langkah-langkah untuk membuat konten web dapat dilokalkan.  Dokumentasi dibagi menjadi 4 bagian:

- -
    -
  1. How to create localizable content.
    2. -
  2. How to choose the right localization format.
    3. -
  3. How to create localizable web applications.
    4. -
  4. How to set up the infrastructure for localization.
    5. -
- -

Why localizability is important

- -

There are many reasons why you should start thinking about making your web app localizable as soon as possible.

- -
    -
  1. You will make localizer's life easier, for which they will be grateful.
    2. -
  2. You will have quality content, localized and adapted to the needs of the local market.
    3. -
  3. Extending you web app to support new languages will be easy.
    4. -
  4. The content will be easier to maintain and update.
    5. -
  5. You will end up writing more semanticly-correct code, which is good for your SEO.
    6. -
  6. By reviewing your content and code for l12y, you will find and fix bugs in your original language too.
    7. -
-- cgit v1.2.3-54-g00ecf