Translations
Info
All page names need to be in English.
en da  de  fr  it  ja  km  nl  ru  zh

Japanese-translation-common-vocabulary

From TYPO3Wiki
Jump to: navigation, search
This page belongs to the TYPO3 Core & Extensions Translation project (category Project)
Japanese-Translation-Team へ戻る

単語集

日本語 - 翻訳 共通単語
英語 日本語 コメント 著者
module モジュール humanook
extension 拡張機能 humanook
extension manager 拡張機能マネージャー humanook
The page tree ページツリー humanook
the filelist ファイルリスト humanook
Recursive Copy/Delete 再帰コピー/削除 humanook
subpages サブページ humanook
Admin functions 管理者機能 humanook
Install Tool インストールツール humanook
Install Tool Enable File インストールツール許可ファイル humanook

フレーズ集

Phrasing examples: active/passive
English 日本語 コメント
Are you sure you want to ~ ~してもよろしいですか?


Active vs. passive

Please watch your usage of active vs. passive. In English documentation, it is quite common to directly address users. Doing so in German doesn't exactly help to create an air of respectability -- it's not "seriös". Specific instructions on how to achieve a certain task are an exception. In that case, not addressing the user can sound like a drill instructor.

Phrasing examples: active/passive
English correct wrong
You can use this module to get an overview of the available items.  ??????????????????????????????????????  ?????????????
To adjust the access rights, choose the Web>Page module in the left navigation and the "News Storage" sysfolder in the page tree. Then click the "Edit" icon of the "Dummy news" item, and select the desired group under "Access". Click "Save and close".  ????????????  ?????????????

Commands

For commands, e.g., menu items, always use the order

  <subject> <object> <action>

Otherwise it will sound like you are talking to your computer.

Phrasing examples: commands
English correct wrong
Copy file to folder  ??????????????  ?????????????
Paste clipboard content  ??????????????????  ?????????????

Messages

For messages by the system, e.g., confirmation, error, and success messages, always use a passive construction. The computer is not a person and thus cannot talk to the user. Also, the user should not be addressed directly (see above).

There is one exception: If the user has to be addressed because of properties or circumstances that are specific to the user.

Messages should be short and to the point.

Phrasing examples: Messages
English correct wrong
Error: Cannot write to file LocalConfiguration.php.  ??????????  ?????????????
Are you sure you want to delete the files?  ??????????  ?????????????

Hyphenation

Please don't be sloppy about hyphenation. Also, please mind the rules regarding foreign compound words.

Examples:

English Japanese
TYPO3 backend login TYPO3-??????-????
user administration  ??????
web site Web???

Spelling