Difference between revisions of "Translate a Page/ja"

(Created page with "=== 画像の表示に関する説明 ===")
(Created page with "典型的な例としては、<nowiki>right|160px</nowiki> などがあります。これは全て、画像の表示の仕方をシステムに命...")
Line 37: Line 37:
=== 画像の表示に関する説明 ===  
=== 画像の表示に関する説明 ===  
A typical example is <nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki>.  The whole of this is a system instruction on how to display the image.  None of it is translated.
典型的な例としては、<nowiki>[[Image:Plasma-kickoff.jpg|right|160px]]</nowiki> などがあります。これは全て、画像の表示の仕方をシステムに命令する文です。 翻訳の必要はありません。
=== Category statements ===
=== Category statements ===

Revision as of 10:24, 7 July 2019

Other languages:
English • ‎Nederlands • ‎español • ‎français • ‎italiano • ‎português do Brasil • ‎slovenčina • ‎suomi • ‎čeština • ‎Ελληνικά • ‎русский • ‎українська • ‎मराठी • ‎中文(中国大陆)‎ • ‎日本語



  • Request addition to the Translator group:
    • Click on Get a Translator Account in the sidebar
    • Click on the Edit icon Userbase-edit.png and enter your username, the language you want to translate for and whether you intend to translate off-line
    • Use Save page to save the information
  • 翻訳グループに追加されたら (通知が送られるはずです)、サイドバーの Start Translating をクリックします。
  • Enter the language you want to translate to in Language code and click on Go
全ての原文は英語で書かれているため、en (英語) を言語コードとして入力しても、未翻訳のメッセージが表示されることはありません。

  • 一覧にある、翻訳したいページをクリックします。
  • In the Translate page set View all untranslated message in the first drop-down list
  • Check that the correct language code is showing
  • In the Navigation section, click on the link to the left of the message you want to translate
  • Enter the translation - a Google translation is provided for reference, but your own translation is usually preferred.
  • Click on Save and open next to continue with the next message or Save page to save the translation if you wish to stop working.
翻訳版ページを手動で作成しないで下さい。(ページ名/言語コード を入力して、原文を翻訳しようとするなど) 翻訳システムが崩壊し、翻訳は一切表示されません。



典型的な例としては、[[Image:Plasma-kickoff.jpg|right|160px]] などがあります。これは全て、画像の表示の仕方をシステムに命令する文です。 翻訳の必要はありません。

Category statements

In this context, think of the word "Category" as a system word which therefore should not be translated. For example, [[Category:Administration]] would become [[Category:Administrasi/id]]

For consistency, UserBase has lists of approved translations of categories. Translation teams may find a similar list useful. Such tables can be seen at Translation Help Needed. Please request help if you need it.

Links to other pages on TechBase

These take the form [[Special:myLanguage/Other page|link text]] The link should remain untranslated, whereas the link text should always be translated. If no link text is present, please add suitable (translated) link text.

"myLanguage" will try to load the translated version of the link in the language you have set in your user preferences. If it fails to load it will just load the English original, so it is safe to use it for any internal link.

Links to external sites

These take the form [http://example.com link text]. Like the internal links, retain the actual link and translate the link text.

Links in the Sidebar

Instructions for translating those sidebar links can be found at Modifying_the_Sidebar#Translating_Sidebar_Items


These generally consist of a header word "Information" and an editable information text. If the word "Information" is not recognizable in your language you may need a localized version of the template. Please ask if you need help with this.

Translated units are marked as fuzzy

Sometimes it may happen that you have translated a page, but the translation is marked as incomplete. Certain errors in the markup of the original page can cause this. The most common type of error is the appearance of unbalanced brackets or parentheses. The translation system requires that all opening brackets ('[', '{' or '(' ) have a matching closing bracket (']', '}' or ')' ) in the same translation unit, otherwise the translation is considered incomplete.

The same rule is not enforced by the wiki software, so it is easy for writers to miss those mistakes. If a bracket character is simply missing, just add it. However, sometimes the bracketed content extends over more than one translation unit, so that the matching closing bracket is in later unit. In this case you need to balance brackets in both units, but you can't simply add bracket characters without changing the meaning or formatting, so you must must comment out the added bracket character, like this

<!--}}-->{{Info|1=Beginning of long info box... 

and in a later unit

 ...end of long info box}}<!--{{-->

If the offending bracket is part of a smiley, please replace it with an emoticon icon. For the standard smiley, :-), you can use the template {{Smiley}}

Please also correct the original page so other translators won't have the same problem, or leave a message on the discussion page.

Language Statistics discrepancies

You may notice some slight discrepancy between the percentages stated on your LanguageStats page and the percentage on the language bar. This is normal. LanguageStats compares only the number of messages that are untranslated or outdated. The language bar statistic tries to be more intelligent. For instance, in one page (100 messages) 8 messages had a small (re-branding-releated) change, in each case, a single word was involved. There was 8% difference between the two statistics, since it was a substantial proportion of the messages, but a small proportion of the whole translation.

If you use the Chromium or Chrome browser...

Be aware that there seems to be some sort of caching problem on the Chromium browser. I have noticed that even with forced refreshes, sometimes statistics do not show up as they should (I have seen other things affected, too), yet if I open the same page in Firefox I see the correct stats.

Also See

Content is available under Creative Commons License SA 4.0 unless otherwise noted.