הוויקי של TDF/רב־לשוניות

From The Document Foundation Wiki
Jump to navigation Jump to search
This page is a translated version of the page TDF Wiki/Multilingual and the translation is 43% complete.
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Esperanto • ‎Jawa • ‎Nederlands • ‎dansk • ‎español • ‎français • ‎galego • ‎italiano • ‎lietuvių • ‎português • ‎português do Brasil • ‎română • ‎slovenčina • ‎Ελληνικά • ‎русский • ‎українська • ‎עברית • ‎العربية • ‎فارسی • ‎中文(台灣)‎ • ‎日本語 • ‎한국어

עמוד זה דן בתוכן הוויקי הרב־לשוני שקיים בוויקי של TDF.


לא להשתמש בסוג התרגום OrigLang לדפים חדשים שנוצרים. אנחנו עוברים כרגע להרחבת התרגום של מדיה־ויקי.


עמוד זה מכיל עצות חשובות לעורכי ויקי. נא לקרוא את העמוד הזה בטרם הוספת תרגום או תוכן מתורגם לוויקי.

תוכן עם התמקדות מקומית

העמודים נכתבים בשפה המקומית שלהם בלבד ולא יתורגמו. אלו תת־עמודים של עמוד ששמו כשל קוד השפה באותיות גדולות.



תוכן עם התמקדות גלובלית

עמודים קמים באנגלית והם מתורגמים למגוון שפות. העמודים המתורגמים הם תת־עמודים שנקראים על שם קוד השפה שלהם. תהליך התרגום נערך על ידי הרחבת התרגום.

יש לפעול בהתאם לצעדים האלה כדי להפוך תת־עמוד לזמין לתרגום:

  1. לשים תוכן שדורש עדכון בתוך מקטעי <translate></translate>
  2. להשתמש בתבנית {{#translation:}} כדי להוסיף סיומות שפה לרכיבים כגון תפריטים
  3. להשתמש בקידומת Special:MyLanguage כשמקשרים לעמודים פנימיים שניתן לתרגם
  4. להוסיף את מקטע תפריט השפות <languages/>
  5. לאחר שמירת העמוד, יש ללחוץ על הקישור שלמעלה בו כתוב סימון העמוד הזה לתרגום
  6. יש לבדוק שהכול בסדר וללחוץ על הכפתור בתחתית שאומר סימון הגירסה הזאת לתרגום

After the page is marked for translation, the Translate extension will automatically add markers in the form of <!--T:1--> to denote translatable strings. To become automatically separated into a string, a block of text has to be surrounded by blank lines. To force the separation of strings, you can add more <translate></translate> blocks. Pay attention to bulleted or numbered lists especially.

When you add or change content in the source page, this will appear at the top of the page: This page has changes since it was last marked for translation. Click the link "marked for translation" to bring the translation system up to date following the same process as in the initial marking for translation.

In an ideal situation, translators should see a minimal amount of wiki markup. Having markup for a table or a template in the translatable string is frustrating and confusing for the translator. Try to leave such markup outside the <translate></translate> blocks.

The page title is made translatable by default, but you can control this with the checkbox "Allow translation of page title" when marking a page for translation. The page title is the first translatable string in the list of strings. In the translation system and interface, the string has a name like "Translations:Faq/General/127/Page display title/ru" while the other string names have numeric identifiers like the "4" in "Translations:Faq/General/127/4/ru".

Sometimes there is a need to give a page a display title that is different from the name in the page path. Note that this is not recommended and should be avoided. In these cases, use the Rename template like so: {{Rename|My new name}}. The template will make sure there are no errors in the translated pages regarding the title.

Sometimes you need to access the English wiki source without the <!--T:1--> markers. This can be done by adding /en at the end of the page path and then editing the source. This will allow you to copy a page structure into a new page (such as Release notes).

When you use the {{#translation:}} template to add language suffixes to menus, be sure to use absolute paths and not relative ones that begin with /. If you use it in relative paths, you will end up with two language codes and a broken link.

If you have blocks that only contain a single number, you can use the magic word {{formatnum:1234}} instead of a translate block. The number will automatically be formatted to non-Western styles, when needed. It is best to use the NOSEP parameter for whole numbers to prevent showing thousand separators as they can confuse readers. For decimal numbers it is best to not use NOSEP, because it would skip the localisation of the decimal separator.

Below is an example of a page prepared for translation. Notice the separation of the bulleted list and contents in a table.


 == Hello World ==

 * We must take the world as we find it
 * When we are gone, let the world be flooded
 * The world is as fools wish it to be
 * It's a small world!
 * Crows are black the world over
 * He slipped once and all the world knew about it
 * The world is like a market, the one does business and the other does none
 * Huge though the world is, I always miss when I hit at it

 {| class="wikitable"
 | <translate>Cell content</translate>
 | {{sometemplate|<translate>Text content for a template</translate>}}
 | <bdi>{{formatnum:-1.10714871779409}}</bdi>
 | {{formatnum:110714871779409|NOSEP}}

 [[Special:MyLanguage/Development/Create_a_Hello_World_LibreOffice_extension|<translate>Tutorial on creating a Hello World extension</translate>]]


As table content can be annoying to prepare for translation, a helper script has been created. Use it by copying a wiki article into a local text file and giving the file name as an argument for the script. The file contents will be rewritten in place. The formatnum magic word will be applied for integer, floating point and complex numbers, if they are the only content in a table cell. The script depends on wikitextparser, regex and wcwidth packages. Click Expand to see the script.

#!/usr/bin/env python3
# uses the library https://github.com/5j9/wikitextparser
import sys
import wikitextparser as wtp

def is_float_or_complex(value):
        return True
        return False
        return True
        return False

with open(sys.argv[1]) as f:
    doc = f.read()

p = wtp.parse(doc)
tables = p.get_tables()

for t in tables:
    for row in t.cells():
        for cell in row:
            c = cell.value.lstrip().rstrip()
            if len(c) > 0:
                if c.isnumeric() or is_float_or_complex(c):
                    if c.isnumeric():
                        format_end = '|NOSEP}}'
                        format_end = '}}'
                    # Use bdi element so minuses will stay in place with RTL languages
                    if c[0] == '-':
                        cell.value = ' <bdi>{{formatnum:' + c + format_end + '</bdi> '
                        cell.value = ' {{formatnum:' + c + format_end + ' '
                    cell.value = ' <translate>' + c + '</translate> '

with open(sys.argv[1], 'w') as f:

המרת תוכן מתורגם ישן למערכת הנוכחית

In the past, TDF wiki employed a translation process that used templates called OrigLang and Lang. The templates displayed a menu that linked the source page with the translated ones. You can find all the translated content that use the Lang template in this list: Special:WhatLinksHere/Template:Lang. Likewise, you can list the pages with OrigLang template.

Translate extension has a migration tool, which helps in moving already translated content to the new system. If the source and translation blocks match exactly, the migration will be very easy. Otherwise you have to cut and paste strings between the input boxes.

The migration goes as follows:

  1. After marking a page for translation, wait for some minutes, so the server will have processed the page
  2. Navigate to Special:PageMigration
  3. In the input box, input the language path of the page you want to migrate, like: Mypath/Mypage/de for some imaginary German translation
  4. Click the Import button
  5. Clean up the contents in the input boxes containing the old translations (for example, remove any useless menu templates)
  6. In the column with the translations, you can't leave empty or extra input boxes at the end, so delete them by clicking the trashcan icon next to them
  7. After you cleaned up and put everything in order, click the Save button

Remember that you can always view the old version of a translated page using its View history link and clicking on an old revision.

If you want to view the source of an old revision, copy its link from the history and visit the link after adding this to the end: &action=edit

Sometimes it does not make sense to use the migration tool. Leaving wiki markup outside the translate elements often confuses the tool. In these cases, the suggestions presented by the translation memory can be more useful.

הודעות בסרגל הצד

To translate the messages ”Get Involved” and ”Support LibreOffice!”, you need to send the translations to one of the wiki administrators. The others are system messages which are translated in upstream MediaWiki.

The translation of the additional Sidebar elements has been set up using the steps in the Translate extension help page for unstructured element translation. The administrators just need to visit Special:Translate/wiki-sidebar in order to translate the messages.

The ”Main Page” and ”Get Involved” links use the Special:MyLanguage prefix, which makes them direct to a translated page, if it is available.