Japanese-translation-common-vocabulary
From TYPO3Wiki
| List Projects | The TYPO3 Core & Extensions Translation-project list pages | See Current Project Members, Wishlist |
| you can help if you like! |
back to Japanese-Translation-Team
This is a draft version subject to discussion.
Contents |
Vocabulary
| Japanese - translation common vocabulary | |||
| English | Japanese | Comment | Author |
| to browse | depends on context | ??? | |
| button | ??? | chennecke | |
| caption (of a table, image, file download) | ?????? | depends on context | ??? |
| check box | ???????? | depends on context | hodota |
Phrasing
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 localconf.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
???????????????????
