このページはEtoJ逐語翻訳フィルタによって翻訳生成されました。

翻訳前ページへ
Unbenannte Seite
Language

The 解放する／自由な and Open 生産性 控訴
解放（する）d: Apache OpenOffice 4.1.15

OpenOffice.org 使用者 Interface Text Style Guide

Dec 2005, 見解／翻訳／版 2.19

Author: Elizabeth Matthis; 修正するd by Christian Jansen

Contents

1. About This Guide

2. 一貫した Text and Terminology

3. 道具s for Text and Terminology

4. Tricky Terminology

5. 一貫した 令状ing

6. Keep Localization in Mind

7. Capitalization

8. Text for Wizards

9. 虫垂 A

10. 見解／翻訳／版 History

1. About This Guide

目的

This guide 述べるs how to design text for the 使用者 interface (UI) of the English 見解／翻訳／版 of OpenOffice.org. There are also 公式文書，認めるs when special 指導基準s are needed for German, because OpenOffice.org is designed and 器具／実施するd in German and English 同時に. Any 指導基準s relating to German are 最高潮の場面d by the colors of the German 旗 in the 権利 利ざや, as seen to the 権利 of this paragraph.

For the 目的s of this guide, the 鮮明度／定義 of text on the 使用者 interface only 含むs menus and submenus, dialogs, tooltips (short ones 陳列する，発揮するd during “What's This?” mouse-over), message boxes, wizards, etc., but not 命令（する） Line Interface, Help or documentation, even though they also appear onscreen and thus 構成するs, in some 鮮明度／定義s, part of the 使用者 interface.

最高の，を越す

Audience

This guide is predominantly for the people who design the German and English UI text of OpenOffice.org: おもに 使用者 experience designers and 使用者 interface linguists. 付加 people for whom these 指導基準s will be important are those working in 質 保証／確信 (QA), 開発 engineers who 令状 specifications or 器具／実施する 資源 strings (text seen on the UI), 翻訳家s who translate (localize) from English as the source language, 同様に as anyone working on documentation that 言及するs to the OpenOffice.org UI.

最高の，を越す

2. 一貫した Text and Terminology

It is 決定的な that 使用者s do not get lost when 横断するing the 使用者 interface. Text is just as important as colors and 形態／調整s in guiding 使用者s to the 権利 elements to 成し遂げる 願望（する）d 仕事s, even more so for blind 使用者s. “Text” 言及するs to any strings, words, phrases or 宣告，判決s, 反して “条件” or “terminology” 言及するs to individual 部隊s of meaning, which may or may not be 限られた／立憲的な to one word. Some example 条件 are “data source”, “plug-in” and “paste special”, but also 重要な verbs like “select”, “二塁打-click” and “示す”. 反して an example of text 含む／封じ込めるing 条件 could be, “Connect to the data source”. For （警察などへの）密告，告訴（状） on 明確な／細部 条件, go to the Tricky Terminology 一時期／支部.

最高の，を越す

Use 存在するing Text and Terminology

Most importantly, all text and terminology already used in OpenOffice.org must be used as the basis for creating 付加 text or introducing new terminology. That means, for example, that if a word is already used in a particular meaning in OpenOffice.org, you cannot introduce a synonym based on a new feature specification, にもかかわらず what the 競争 might 令状. That would 原因（となる） 混乱 not only for 使用者s, but also for 翻訳家s and technical writers. Thus, the feature specification has to be 訂正するd to use the 存在するing terminology.

最高の，を越す

No 多重の Meanings for 条件

One 称する，呼ぶ／期間／用語 must have one meaning (概念) and ,likewise, one meaning must always be identified by the same 称する，呼ぶ／期間／用語. If a usability 実験（する） shows that a particular 称する，呼ぶ／期間／用語 is not understood by the 使用者s, you cannot just change that one instance of the 称する，呼ぶ／期間／用語, but must change every instance in the whole office 控訴. Only then will the terminology be 一貫した and usable. That is why changing already 存在するing UI text is never done without 徹底的な 研究 of the text in OpenOffice.org. In the same way, text used in new features must always be correspond to 存在するing text and terminology or the designer must consciously 始める a change in all old text to correspond with the new text.

最高の，を越す

令状 for 使用者s With Basic Knowledge

If you are reading this guide, then your 仕事 at 手渡す is likely to 確実にする that the English and German text used in OpenOffice.org is grammatically 訂正する and is molded によれば the terminology and style appropriate for an office 控訴. Your 的 audience is end 使用者s of office 控訴 ソフトウェア. 一般に, assume those end 使用者s are familiar with basic functionality of computers and office 控訴s and that they have at least a high school education. In particular parts of OpenOffice.org that are more technical or 前進するd, such as 大型の programming or the database 使用／適用, it is 安全な to assume that the 使用者s are more 前進するd and can understand a more technical vocabulary.

最高の，を越す

How to Make 決定／判定勝ち（する）s on UI Text

The text on the 使用者 interface must be 一貫した, coherent and （疑いを）晴らす, 特に when 橋（渡しをする）ing from one element to another, such as from menu to dialog, or from button to dialog. How can you decide what text or 称する，呼ぶ／期間／用語 to use? Look at the 存在するing OpenOffice.org UI, 研究 OpenOffice.org terminology already used, compare with other 製品s and sources, etc. It is important that the new features coming in fit with the UI around them.

最高の，を越す

Have Dialog 肩書を与えるs Match Menu Items

When choosing the text for the 肩書を与える 妨げる／法廷，弁護士業s of dialogs, the 決定／判定勝ち（する） of how to 指名する them is 平易な: Keep the dialog 指名する the same as the menu item that is used to call the dialog.

訂正する: menu item “弾丸s and Numbering”, dialog 肩書を与える “弾丸s and Numbering”

Incorrect: menu item “Printer Settings”, dialog 肩書を与える “Printer 体制／機構”

If a dialog can be called by several different menu items or buttons, the menu or button labels and the 肩書を与える of the dialog should at least 含む／封じ込める overlapping terminology and thus be 明白に 関係のある.

訂正する: main menu “判型 - 独房s” or 状況 menu “判型 独房s”, dialog 肩書を与える “判型 独房s”

Think About 優先

ーに関して／ーの点でs of terminological 優先 (on a 規模 from high to low), the main menu items are “high”, followed by submenu items and text in main dialogs that are 直接／まっすぐに opened by choosing a menu as “medium-high”. The approx. 800 error messages in OpenOffice.org 範囲 from “medium-high” to “low” depending on how often they appear and how important the 状況／情勢 is in which they appear. Keep the 優先 level in mind when 改訂するing 存在するing text or planning time to create or review new text. A basic 支配する of thumb is: If you come into 接触する with a 確かな menu, dialog or error message every day when doing simple 仕事s with OpenOffice.org, then it is high 優先. If it is a menu, dialog or error message might only appear to a handful of 使用者s, for example because it 取引，協定s with a seldom-used feature, then it is low 優先.

最高の，を越す

3. 道具s for Text and Terminology

Terminologies and Glossaries

OpenOffice.org Developer's Guide

You can find a glossary (=称する，呼ぶ／期間／用語 + 鮮明度／定義) for the OpenOffice.org Developer's Guide on the OpenOffice.org website:

OpenOffice.org English-German Terminology

There is 現在／一般に no English-German terminology 名簿（に載せる）／表（にあげる） (=English 称する，呼ぶ／期間／用語 matched with German 称する，呼ぶ／期間／用語) for the OpenOffice.org UI.

In the 合間, Elizabeth Matthis worked with the German OpenOffice.org 事業／計画（する） volunteer Wolfgang Henderkes to 供給する the German documentation volunteers with a terminology to 容易にする their 令状ing and translation. Wolfgang's HuT-eSaurus, can be 接近d 経由で his website:

You can download the German-English terminology in the HuT-eSaurus, which is not 排除的 to OpenOffice.org and 絶えず 存在 updated, 直接／まっすぐに at the に引き続いて 演説（する）／住所:

SAP Terminology

The German company SAP also produces German and English UIs and documentation in 平行の. They have made some short terminology 名簿（に載せる）／表（にあげる）s 公然と 利用できる:

Gnome Glossaries and Other 資源s

GNOME is also 的d toward end-使用者s, so the terminology is akin to that which is used in OpenOffice.org or could be 可決する・採択するd for use in OpenOffice.org when new 条件 are 存在 研究d. Be careful, however: GNOME terminology is not the same as OpenOffice.org, for historical 同様に as market 推論する／理由s.

最高の，を越す

Internet Dictionaries

最高の，を越す

4. Tricky Terminology

一貫した use of terminology is important for several 推論する／理由s. Not only does it make the UI easier to understand and support a particular 製品 image, but it is also 極端に important when the text is to be the source language for translation into other languages. The （一定の）期間ing 条約s throughout the UI must be the same and the same meaning should be せいにするd to the same word or phrase wherever it is used.

明確な／細部 条件

Only important or problematic words are 現在のd here. As these words appear very frequently, it is 特に important that they are used 終始一貫して and that no synonyms or variations are used instead.

最高の，を越す

“示す” Versus “Select”

“Select” is used to 言及する to the 選択 of 反対するs/items, for example, paragraphs or characters which are then 削除するd, moved, copied, given a new font, etc. It is also used when selecting 選択s from 名簿（に載せる）／表（にあげる）/combo box 減少（する）-負かす／撃墜する 名簿（に載せる）／表（にあげる）s and for 無線で通信する buttons.

To discuss the use of check boxes, use the verbs “示す” and “unmark” or the adjectives “示すd” and “unmarked”. 令状ing “示す” is also in the 利益／興味 of using 国祭的な 受託するd English, because it 味方する-steps the usage of “tick” versus “check”. “Tick” is 容認できない in US English, 反して “check” is いつかs considered incorrect in UK English, where “tick” is more ありふれた. In the past, other words like “select”, “check”, and “活動させる／戦時編成する” were used inconsistently と一緒に “示す”. Our goal is to 避ける using different words to 言及する to the same 機能（する）／行事.

In German, always use “auswählen” whenever “select” is used in English. “Markieren” is not 訂正する either.

訂正する: Wählen Sie den Text aus.

Incorrect: Selektieren Sie den Text.

When to “Choose”

Use “choose” to:

  1. Open a menu.
  2. Choose a menu item.

The German translation of “choose” is “auswählen”, the same as for “select”.

How to “Click”

Use this verb to 述べる the 活動／戦闘 used to 活動させる／戦時編成する icons, さまざまな buttons and other 機能（する）／行事s on the 使用者 interface. 避ける using “click on”. (However, in German always use “auf”: &ldquKlicken Sie auf 承認する”) Variations of click are as follows:

称する，呼ぶ／期間／用語

鮮明度／定義

Click

To quickly 圧力（をかける） and 解放（する） the left mouse button one time, without moving the pointer.

二塁打-click

To quickly 圧力（をかける） and 解放（する） the left mouse button twice in 早い succession.

Left-click

The same 活動／戦闘 as click; to quickly 圧力（をかける） and 解放（する） the left mouse button one time, without moving the pointer. Use the 称する，呼ぶ／期間／用語 left-click to distinguish the 活動／戦闘 from 権利-click when they appear in the same paragraph.

Long-click

To 圧力（をかける） and 持つ／拘留する 負かす／撃墜する the left mouse button for about three seconds, then 解放（する） it. For example, you use a long-click to open a floating toolbar from the main toolbar.

権利-click

To quickly 圧力（をかける） and 解放（する） the 権利 mouse button one time. For example, you use a 権利-click to open 状況 menus.

選び出す／独身-click

The same 活動／戦闘 as click; to quickly 圧力（をかける） and 解放（する） the left mouse button one time, without moving the pointer. Use the 称する，呼ぶ／期間／用語 選び出す／独身-click to distinguish the 活動／戦闘 from 二塁打-click when they appear in the same paragraph.



Left-handers please 公式文書，認める that 権利 mouse button and left mouse button are switched for your mouse if you have a left-mouse, or if you have 修正するd your mouse settings.

“Want” Versus “Wish”

Use the verb “want” instead of “wish”. For example, “You can save the 文書 in a different 判型 if you want.” (even better would be “...if 要求するd” or “...if necessary”)

“Dialog” Versus “Dialog Box”

Instead of using “dialog box” as is done in many other programs, use only the 称する，呼ぶ／期間／用語 “dialog” in OpenOffice.org. There are three 推論する／理由s why this was decided:

  1. “Box” is an unnecessary extra since there are no 相反する 事例／患者s of dialogs without boxes.
  2. This style has been used 終始一貫して throughout the 使用者 interface and end-使用者 documentation up till now so changing it would 背負い込む 抱擁する rework costs with little 利益 to the 使用者s.
  3. GNOME, also only uses “dialog”.

“Drag and 減少（する）”

When used as a modifier, 令状 “drag-and-減少（する）”. For example, "the drag-and-減少（する） 操作／手術".

You can use “drag” as a stand-alone verb. The 活動／戦闘 of dragging 含むs dropping the 反対する so you do not need to 追加する “減少（する）”.

訂正する: Drag the でっちあげる，人を罪に陥れる to another place on the page.

Incorrect: You can drag and 減少（する） the でっちあげる，人を罪に陥れる to another 場所 on the page.

最高の，を越す

5. 一貫した 令状ing

A 肯定的な 使用者 experience depends 大いに on the 一貫した use of language, a 一貫した 令状ing style and 一貫した capitalization of the 使用者 interface elements. The resulting 製品 style 伝えるs the 保証／確信 of serious, reliable, professionally-designed ソフトウェア.

American Versus British English

Use US English (the 基準 in the 部隊d 明言する／公表するs of America) 支配するs of 令状ing and （一定の）期間ing in OpenOffice.org. 言及する to the Merriam Webster Dictionary for meanings and spellings in general. The dictionary is 利用できる online for 解放する／自由な at: www.m-w.com.

最高の，を越す

令状ing Style

The OpenOffice.org ソフトウェア is for end-使用者s, that is, anyone who would like to type a letter or any other everyday 仕事 in countless offices and homes. The audience may 含む, but certainly does not 的 technical people like system 行政官／管理者s or engineers. That means that the 令状ing style should be in a 非，不，無-technical, every-day style. The goal is to have as many people as possible comfortably using OpenOffice.org. Therefore, the UI has to be 平易な to understand and 使用者-friendly. Two other important 面s that writers need to be conscious of are that the English text is the source text used for translations into all other languages, and that a large number of people using the English 見解／翻訳／版 of OpenOffice.org are probably not native （衆議院の）議長s of English. Therefore, be sure to read the 付加 special 令状ing style 指導基準s in the Keep Localization in Mind section of this guide.

最高の，を越す

General Style

令状 完全にする Company or 製品 指名するs

For 合法的な 推論する／理由s, always 令状 out 十分な company 指名するs, 特に when you について言及する another company. This is also good 令状ing style just to make sure that all readers understand 正確に／まさに what you mean, as not all abbreviations are 全世界の／万国共通の.

訂正する: Microsoft Word, Sun Microsystems

Incorrect: MS Word, SMI (or only Sun)

A 類似の 支配する 適用するs to 製品s. Unless there is a 一般的に used short form that is usually even more 井戸／弁護士席-known than the 十分な 指名する, for example “SQL” or “JDBC”, 令状 the 完全にする 指名する. This is also a marketing 問題／発行する.

If the 状況 is a wizard or other 一連の dialogs that the 使用者 will see in a 列／漕ぐ／騒動, at least 令状 out the whole 指名する the first time and put the short form in parentheses behind it. Explaining the short form in parentheses should be used only when necessary to not annoy 使用者s by 絶えず repeating a long 指名する.

訂正する: Java runtime 環境s (JRE) already 任命する／導入するd: xxxxxx

(that was the first について言及する; then the error messages 誘発する／引き起こすd by this dialog only say “Different JRE 要求するd” in the 肩書を与える)

Incorrect: JRE already 任命する／導入するd: xxxxxx

さもなければ, just always 令状 out the 訂正する, 完全にする 指名する. You may know what the short form means, but a 使用者 or 翻訳家 may not. いつかs, however, there are 公式の／役人 short forms.

最高の，を越す

No Abbreviations

Most of the time, abbreviations should not be used on the UI. Even ありふれた abbreviations such as “esp.” (for “特に”) and “no.” (for “number”) are not universally 認めるd by all （衆議院の）議長s of English and make the UI design look 切り開く／タクシー／不正アクセスd. In 新規加入, some abbreviations can be 解釈する／通訳するd in 多重の ways, for example, “min.” can be “最小限” or “minutes”. However, 確かな abbreviations are 許すd if they are 一般的に used in office 控訴s, for example KB, MB, etc.

最高の，を越す

避ける “Please”

Use “please” only rarely, if ever. いつかs 非常に長い 指示／教授／教育s or error messages might need a touch of politeness 追加するd to one of several 宣告，判決s, but 一般に, do not use “please” in English. If you still feel the need, at least 避ける using “please” more than once in one text or group of 宣告，判決s. For example, you could use “please” in the 初期の 指示／教授／教育s on the first page of a wizard, but then not on any of the other pages. Simple imperative 宣告，判決s are always preferred.

訂正する: Click 'Shut 負かす／撃墜する'.

Incorrect: Please click 'Shut 負かす／撃墜する'.

(公式文書，認める: Contrary to the English 支配する, “bitte” is used in German most of the time. 追加する it to the German text even when it is not used in English. (different culture = different 条約s)

最高の，を越す

No 収縮過程s

Never use 収縮過程s such as “can't” or “it's”. The only exception to this 支配する is the menu item “What's This?” (and perhaps that should be 改訂するd). The OpenOffice.org style is （疑いを）晴らす and professional, not chummy or informal, which is the feeling many （衆議院の）議長s of English get when reading 収縮過程s. In 新規加入, they can be misunderstood by both 翻訳家s and 使用者s so it is best to 避ける any ambiguity by 令状ing out the 十分な text.

訂正する: do not

Incorrect: don't

最高の，を越す

No Spaces Before Punctuation

Although it may be ありふれた in other languages like French, there are no spaces before punctuation in English. Nowadays spaces are いつかs used in email communication to 許す particular punctuation to stand out, but that is an informal style that should not be 設立する in a professional ソフトウェア 製品. It is not more helpful to the reader when you leave spaces. It is 簡単に an annoying error. Therefore, do not 挿入する spaces before punctuation 示すs.

訂正する: An error has occurred. Select one of the に引き続いて 選択s:

Incorrect: An error has occurred . Select one of the に引き続いて 選択s :

最高の，を越す

Do Not Use the Em dash

Unlike its cousin, the hyphen (for example, in the modifier “look-a-like”), dashes are not to be used when 令状ing UI text. Often 設立する in informal 令状ing, the em dash 機能（する）／行事s as a “最高の-comma” or 始める，決める of 最高の-commas to 始める，決める apart elements of the text, 特に when those elements have 付加 forms of punctuation or the writer does not know the 訂正する punctuation to use. However, UI text should never 含む／封じ込める thoughts or be so 複雑にするd that an em dash would be necessary to separate さもなければ hard-to-understand parts of a 宣告，判決. If the text you are 熟視する／熟考するing for your design uses an em dash, rewrite it using other punctuation or separate it into two or more 宣告，判決s.

訂正する: Click the button. The dialog appears.

Incorrect: Click the button—the dialog appears.

最高の，を越す

No Space Before Ellipsis (Three Dots)

menu items that 原因（となる） a dialog to open are followed by three dots, also called “ellipsis”. Never put spaces between text and the dots. The extra space is not helpful and is incorrect in English 同様に as German.

訂正する: Browse...

Incorrect: Browse ...

最高の，を越す

Use Spaces Between Text and Arrows on Buttons

In a dialog or wizard, some buttons have 付加 characters aside from the text. Leave one space between the character and the text. For example, there must be a space between "<" and "支援する" and between "Next" and ">".

訂正する: < 支援する

Incorrect: <支援する

最高の，を越す

避ける Ampersands (&)

Do not use the ampersand symbol “&”. It makes those texts that 雇う it stand out more than others, for example when used on a menu, by 混乱に陥れる／中断させるing the 全体にわたる look. 予定 to its 排除的 nature, the ampersand also 原因（となる）s 不確定 in localization 関心ing whether or not it signifies that the text is a proper 指名する and therefore not to be translated.

訂正する: Boys and Girls

Incorrect: Boys & Girls

公式文書，認める: As of OpenOffice.org 2.0, the ampersand is still used in a few 事例／患者s. These should be cleaned up as time goes by.

最高の，を越す

Do Not Use Exclamation Points (!)

Do not use exclamation 示すs, even if you are 令状ing a 警告 or error message. In English, exclamation points show strong emotion or 強調 and are used much いっそう少なく frequently than in German. 使用者s are meant to feel comfortable using OpenOffice.org, not 脅すd. There is no error or problem that 令状s text punctuated by an exclamation point and therefore showing or eliciting strong emotions.

In German, exclamation points can be used, but please do so with an attitudeof “British understatement” to 抑制（する） the German habit of using exclamation points much too often.

最高の，を越す

Have Real Messages in Error Messages

End 使用者s should not have to be 直面するd with messages like “Error 設立する: 中止する now”. If we 陳列する，発揮する a message for our 使用者s, there has to be （警察などへの）密告，告訴（状） in it that says what has occurred and give the 使用者 指示／教授／教育s on what steps to take next.

Error messages, 警告s, 確定／確認 dialogs and other message boxes (いつかs also called “警報s”) must be written in 完全にする 宣告，判決s. They should not have any technical （警察などへの）密告，告訴（状） in them, unless the message 付随するs to a part of OpenOffice.org tailored to a more 前進するd technical audience.

訂正する: The とじ込み／提出する already 存在するs. Do you want to overwrite it?

Incorrect: The とじ込み／提出する already 存在するs. Overwrite?

For more （警察などへの）密告，告訴（状） on 令状ing error messages and other 警報s, 言及する to the 指導基準s:

Use 現在の 緊張した and Imperative

Use the 現在の 緊張した wherever possible. 避ける all other 緊張したs, except where you need to 明示する events ーに関して／ーの点でs of the past or the 未来. Use imperative verbs (without “you”, for example "To 割り当てる ..., click '承認する' ." and not "To 割り当てる ..., you click '承認する'.") for 指示／教授／教育s and most check box labels.

訂正する: 包む text automatically

Incorrect: Wrapping text automatically

In German, do not use the imperative because it 要求するs either the informal “du” form or the formal “Sie” form. In the German 見解／翻訳／版 of OpenOffice.org, we always use the formal “Sie” form of 演説（する）／住所. In the imperative, it is too cumbersome to 令状 the formal imperative. Instead all German text corresponding to English imperatives is written in the infinitive.

訂正する: Einstellungen des übergeordneten Objektes verwenden

Incorrect: Verwenden Sie die Einstellungen des übergeordneten Objektes

Incorrect: Verwende die Einstellungen des übergeordneten Objektes

最高の，を越す

避ける “Thing's” Possessive Forms

避ける using the Saxon genitive ’s for possessive 事例／患者s, 特に for inanimate 反対するs. Use a possessive 宣告，判決 structure with “of” instead.

訂正する: On the left 味方する of the 審査する.

Incorrect: On the 審査する's left 味方する.

最高の，を越す

Do Not Use “May”

As the modal verb “may” is あいまいな, even to native-（衆議院の）議長s of English, in that it can 表明する 許可 to do something, a 可能性 (“might”) or a real ability (“can”), use the words “might” or “can” instead. This will 避ける ambiguity in the English text which is not only better for the readers, but also for the 翻訳家s.

最高の，を越す

Prepositions

There were several different people working on the OpenOffice.org English 見解／翻訳／版 in the past and not all of them were native-（衆議院の）議長s of English. 予定 to this and differences in preposition usage throughout the English-speaking world, 一貫した use of prepositions has always been a problem. We need to 現在の the readers with a 一貫した style, so 確かな prepositions have been defined for 確かな 状況s. These are the most ありふれた 事例／患者s:

最高の，を越す

Use 選び出す／独身 Quotation 示すs, Never 二塁打

When 引用するing other UI text or とじ込み／提出する or 文書 指名するs (or anything 類似の that would be put in quotation 示すs in normal prose), always use 選び出す／独身 quotation 示すs, not 二塁打 ones. This is 予定 to technical 問題／発行するs in 資源 とじ込み／提出するs: For some code the 二塁打 quotation 示すs have to be “escaped” by 先行する them with a 削除する, but the 削除する 原因（となる）s 混乱 in localization so it is not 価値（がある） the hassle. Even if more modern 開発 環境s make the escaping unnecessary, the 令状ing style using 選び出す／独身 quotation 示すs is already 堅固に 堅固に守るd in OpenOffice.org, so the style must continue to remain 一貫した.

訂正する: Click '任命する／導入する' to continue the 取り付け・設備.

Incorrect: Click “任命する／導入する” to continue the 取り付け・設備.

最高の，を越す

Use Quotation 示すs When 引用するing UI Text

It has already been について言及するd that use of 選び出す／独身 quotation 示すs is the 訂正する way to 最高潮の場面 UI strings 存在 引用するd on the UI. Examples of UI text that often gets 引用するd are button labels or check box 指名するs that are referred to within directions in a dialog or message box.

最高潮の場面ing with 選び出す／独身 quotation 示すs is 雇うd rather than only 公式文書，認めるing the label or 指名する as it is seen and 出資するd onscreen. This makes the text more legible, 特に for quick readers scanning to see the words that 直接／まっすぐに 示す UI elements they have to click or take 活動／戦闘 upon.

引用するing UI Text

訂正する: Click '任命する／導入する' to continue the 取り付け・設備.

Incorrect: Click 任命する／導入する to continue the 取り付け・設備.

引用するing 文書 指名するs

訂正する: The 文書 will be saved under the 指名する '%DOCNAME'.

Incorrect: The 文書 will be saved under the 指名する %DOCNAME.

引用するing UI Text in German and Other Languages

The 選び出す／独身 quotation 示すs in OpenOffice.org signal to the 翻訳家 that the text within the quotation 示すs is a UI text 存在 引用するd and that they should を取り引きする it accordingly. The style guide for the 各々の languages should dictate whether or not the 選び出す／独身 quotatation 示すs are kept, 除去するd or altered for that language. (Just because the quotation 示すs, or any other form of 最高潮の場面ing or punctuation for that 事柄, are used in the English source language, does not mean they have to be used in the 的 languages.)

Many languages do not differentiate between 肩書を与える and 宣告，判決 capitalization. The text can even be 解釈する／通訳するd by the reader as a （一定の）期間ing or grammar error when a 引用するd UI text appears without quotation 示すs and is therefore not すぐに identifiable as a 引用するd UI element, for example, a button label. When only capitalization is used to "最高潮の場面" a 引用する from the UI, it can 軍隊 the translation to be grammatically incorrect. In Spanish, a whole 肩書を与える 引用するd within a 宣告，判決 cannot be 出資するd, so the 妥協 is to 出資する the first word of the 肩書を与える. The 残り／休憩（する） of the 肩書を与える blends with the 残り／休憩（する） of the 宣告，判決 and makes reading the text ぎこちない if not 理解できない altogether. (A 肩書を与える would be 強調するd in bold or cursive in a text written 直接／まっすぐに in Spanish.) In German, verbs are not 出資するd within a 宣告，判決, for example, but verbs used on UI buttons are 出資するd. Therefore, the 選び出す／独身 quotation 示すs are used in German UI text, just like in English:

訂正する: Klicken Sie auf 'Abbrechen'.

Incorrect: Klicken Sie auf Abrechen.

最高の，を越す

Intuitive Shorthand

OpenOffice.org uses its own style of intuitive shorthand to quickly and 効果的に 示す menu 選択 and other 活動／戦闘 paths that the 使用者 needs to follow. The OpenOffice.org shorthand to show the 使用者 which steps to take looks like this:

Choose とじ込み／提出する - Print - 所有物／資産／財産s - Paper

Each UI element is separated from the next one by a space, a simple dash and another space. Although descriptions such as this are usually only 設立する in the documentation, it can いつかs be necessary to explain steps in UI messages 同様に. その上に, descriptions of steps to 位置を示す elements on the UI are 要求するd in 問題／発行するs, specifications or localization guides, so using the same shorthand as the documentation can be helpful. If the intuitive shorthand in the documentation were to change, the UI would have to follow 控訴. 接触する the OpenOffice.org technical writers if you are not sure.

最高の，を越す

6. Keep Localization in Mind

As the English text serves as the source language for localization into up to 50 other languages, the text must be chosen very carefully. This section points out 明確な／細部 important 問題／発行するs to take into account when creating UI text for OpenOffice.org.

含む Variables (Placeholders) in Text

含む variables in the text you create. Variables are いつかs also called “placeholders” by developers because the variable 持つ／拘留するs the place for the text that will 取って代わる it on the UI at runtime. The variable is only 明白な in the 資源 string (in the 資源 とじ込み／提出する in the code) and not on the UI. (The preferred 称する，呼ぶ／期間／用語, “variables”, will be used in this guide because “placeholders” is usually used to 言及する to real text seen on the UI which the 使用者 then clicks to overwrite, such as “<fill in your 指名する here>”.)

Do not leave text phrases open-ended or separate two parts of a text into separate 資源 strings. For developers it is 平易な to hard-code the 付加 text, such as a URL, a number or a とじ込み／提出する 指名する, that will be 挿入するd at runtime. They do not have to 含む it in the 資源 string and may think they are saving time or money in doing so. However, if something is going to be 挿入するd at runtime, the 翻訳家 must know it, and should be told what the text will be. Doing so 許すs the translation to have 訂正する grammar and punctuation, which would さもなければ not be possible. 含むing variables also 許すs for easier reviewing of the 初めの text in English, too.

訂正する: The 文書 will be saved under the 指名する '%DOCNAME'.

Incorrect: The 文書 will be saved under the 指名する

最高の，を越す

Keep Variables 一貫した

The 基準 OpenOffice.org form for variables is: "%CAPITALLETTERS".

予定 to the long history of the 開発 of OpenOffice.org and the fact that only within the last 2-3 years was there an 成果／努力 to 限界 the variable style to one 基準, there are 現在／一般に many forms used in the OpenOffice.org code, for example:

Prefix, Suffix
"&", ";"
"%", "%"
"%", 非，不，無
"$(", ")"
"$", "$"
"${", "}"
"#", "#"
"($", ")"
"$[" "]"

Unfortunately, 予定 to different programming languages and 開発 環境s 存在 used, some symbols are 定める／命ずるd or 制限するd. However, it should be possible in most 事例／患者s to use the 基準 style as long as the developer knows the style before starting to code. A 一致した 成果／努力 to 変える (“直す／買収する，八百長をする”) the other variables to the 基準 form will 大いに 減ずる the 量 of time spent explaining the variables to the localization providers at every turn.

再使用する 存在するing Variables

Never create new variables when there are already variables defined to 達成する the same result. When 令状ing specifications, be sure to 協議する LingTool or this 名簿（に載せる）／表（にあげる） first. The most 一般的に occurring variables are:

%PRODUCTNAME

Will be 取って代わるd by OpenOffice.org, StarOffice, etc.

%PRODUCTVERSION

Will be 取って代わるd by the 最新の 見解／翻訳／版 number 8, 2.0, etc.

%MODULENAME

Will be 取って代わるd by “Writer”, “Calc”, “Math”, “Basic”, “Impress”, “Draw” depending on the 状況.

%ORGANIZATIONNAME

In the error 報告（する）／憶測 道具, 取って代わるd by “Sun Microsystems” or “OpenOffice.org”.

%PRODUCTPATCHNAME

Stands for “製品 Update 2” or “製品 Update 3” and later numbers depending on 見解／翻訳／版.

%PRODUCTEXTENSION

Will be 取って代わるd during 取り付け・設備 with EA1, EA2, or BETA (not used in final 見解／翻訳／版=empty

%PRODUCTXMLFILEFORMATNAME

In 名簿（に載せる）／表（にあげる） box of filters or type of 文書, this will be 取って代わるd by “StarOffice”, “OpenOffice”, etc.

%PRODUCTXMLFILEFORMATVERSION

In 名簿（に載せる）／表（にあげる） box of filters or type of 文書, this will be 取って代わるd by “6.0”, “1.0”, etc

Create Variables によれば 指導基準s

Good programming style says to use self-explanatory 指名するs for variables and this is in the 利益／興味 of localization, too. Additionally, if technically possible, good variables:

The 推論する／理由ing behind these 支配するs is that 翻訳家s who localize OpenOffice.org come and go and are not always professionals (for example, OpenOffice.org volunteers). The best 解答 is therefore to 持続する clarity and consistency at the 工学-end of the 過程. To understand the problems 翻訳家s can have identifying variables as something not to translate, remember the に引き続いて:

1) 翻訳家s are not developers and do not やむを得ず know what a variable is. They could think it is a typo. “I'll just leave out the funny character and my translation is at least 訂正する, even if the 初めの is buggy.”

2) A variable very often looks just like a real word with a typing or character encoding error in it. “Is it a bug to 報告（する）／憶測 or perhaps some developer thingy? Hmmmmm...”

3) Some UI strings 含む／封じ込める placeholders or field labels such as “<number>” that have to be translated, for example in German “<Nummer>”. So a variable written “<path>” would look a heck of a lot like something to translate, for example in German “<Pfad>”, but, oops!, the code is broken.

4) If machine translation is 存在 used, the variables have to be fed into the machine in 前進する so it knows not to translate or change them. Keeping 跡をつける of all different forms of variables for the machine is difficult, 特に when new variables get invented all the time.

5) “#” is the symbol for “number” in the USA. This is いつかs used as a button label on a UI. In that 事例／患者, it has to be localized, for example in German “Nummer”. So do not think that a symbol you choose for a variable is going to be 明白に 非，不，無-text, just because you wouldn't use it in your language. A variable such as “#1” could 誤った be translated into German as “Nummer 1”.

6) いつかs it is not （疑いを）晴らす where the variable starts and ends, which symbol is part of the variable and which one is 正規の／正選手 punctuation in the text, for example, brackets <>[], parentheses () or apostrophes ' can all be 混乱させるing for 翻訳家s.

7) A new 翻訳家 will 一般に assume that OpenOffice.org/OOo is one 製品, and that therefore there is one style for text and variables. [one 製品 = one programming language = one style]

最高の，を越す

No Phrases Ending in Prepositions

Do not end phrases with prepositions, for example, 直す／買収する，八百長をするd text introducing a group of check boxes. Prepositions have to be declinated in many languages, 含むing German, and they must therefore be placed with the noun that follows them.

English

German

訂正する: Send 輪郭（を描く）

  • To 贈呈

  • To clipboard

  • As attachment

訂正する: Gliederung versenden

  • Zur Präsentation

  • Zur Zwischenablage

  • Als Anhang

Incorrect: Send 輪郭（を描く） to

  • 贈呈

  • Clipboard

  • Attachment

Incorrect: Gliederung versenden zur

  • Präsentation

  • Zwischenablage

  • Anhang

最高の，を越す

No 非，不，無-international Symbols Like "#"

Although localization specialists should be able to identify symbols 一般的に used in English, they may not be able to understand the 状況 and find the applicable localization. Often symbols are used when there is a 欠如（する） of space, which is just asking for trouble because the localization is 保証（人）d to be longer, 一般に having to use words to localize the symbol used in English.

Not all symbols, such as “#”, are 認めるd as having the same meaning all over the world---even amoung native-（衆議院の）議長s of English. For example, “#” to mean “number” is very 一般的に used in the USA, but has been 報告（する）／憶測d as hardly known in the UK. As it is hard to know which symbols are universally 認めるd, it is best to use words instead of symbols.

最高の，を越す

Be Aware of Text Length

English text is much shorter than most of the localizations which correspond to it. In fact, the localized text can be three times as long. As a 支配する of thumb, check the Brazilian Portuguese translation (by searching in LingTool) to see how many characters and spaces will have to be 明白な on the button or in the space of the dialog. いつかs, however, Italian or French can 現在の the longest translation. In OpenOffice.org languages, Finnish seems to do a good 職業 of competing with Brazilian Portuguese for longest text. In the end, 質 実験（する）ing of localized builds is the only way to find any imperfect UI text that would call for a spatial 調整 in the design, so just do your best.

Until OpenOffice.org gets a layout 経営者／支配人 which would automatically adjust the space needed to 融通する the text in different languages, the UI designer must leave enough room on the 審査する to 許す space for the longest translation. That is also why most of the text is positioned above a 支配（する）／統制する, such as a text box, or after a 支配（する）／統制する, such as a check box.

最高の，を越す

No Spaces Before or After Text

Do not start a text with a space or 追加する an 付加 space after the text. Unfortunately, this was done in the past by developers when 器具／実施するing the text. They 追加するd spaces to the text as a way of 供給するing formatting or spacing of text 部隊s on the UI. Not only is that not good coding, but it will 原因（となる） errors in the translation database 同様に as begs for errors in localizations, where the 翻訳家 will usually not 含む the extra spaces and therefore lose the “formatting” on the UI. If the UI design 定める／命ずるs indentation or other spacing of text, then it must accounted for in the code, not as part of the text string.

最高の，を越す

7. Capitalization

The consistency of capitalization gives the ソフトウェア 使用者 interface a professional, 円熟した look and also 供給するs 一貫した and いつかs 価値のある input for 翻訳家s working on the localization.

最高の，を越す

Basic 支配するs

The basic 支配するs regarding 肩書を与える and 宣告，判決 capitalization 要約するd below only 適用する to English, not to German.

In German, use the 正規の／正選手 支配するs of capitalization as you would in any normal text. Start with a 資本／首都 letter as if it were a 宣告，判決, even if it is only a phrase, such as a check box label. に引き続いて this same 概念, all button labels also start with a 資本／首都 letter, even if they are a verb.

最高の，を越す

肩書を与える Capitalization

In the 肩書を与える capitalization style, 出資する every word except articles ("a," "an," and "the"), 調整するing 合同s (for example, "and," "or," "but," "so," "yet," and "nor"), and prepositions with より小数の than four letters ("in").

訂正する: Coding Without Your 注目する，もくろむs

Incorrect: Coding without your 注目する，もくろむs

In 肩書を与える capitalization, always 出資する the first and last words, even if they are prepositions or any other word that would 普通は be lowercase within a 肩書を与える.

訂正する: Save As

Incorrect: Save as

宣告，判決 Capitalization

In 宣告，判決 capitalization, only 出資する the first word. Exceptions are proper nouns, abbreviations, or acronyms that are always 出資するd, 同様に as quotations of UI text.

訂正する: Click '拒絶する／低下する' if you do not 受託する the 条件 of the License 協定.

Incorrect: Click '拒絶する／低下する' if you do not 受託する the 条件 of the license 協定.

In the example above, “License 協定” is considered a proper noun because it is defined in the 協定 and always referred to in 資本／首都 letters to make it （疑いを）晴らす that that 明確な／細部 合法的な 鮮明度／定義 is 合法的に binding for that 協定.

使用者 Interface Elements

Most elements on the 使用者 interface, いつかs also called “支配（する）／統制するs”, have text labels, tooltips or accessibility descriptions (read to visually impaired 使用者s 経由で assistive 科学（工学）技術, 審査する readers, for example) associated with them.

The 目的 of the に引き続いて （米）棚上げする／（英）提議する 詳細（に述べる）ing how さまざまな UI elements are 出資するd is to 促進する consistency throughout the 製品 in dialogs, menus, etc. and その結果 in any 関係のある documentation that 引用するs the UI text.

The 指名するs in the second column below correspond to the 指名するs developers see in the source code (資源 とじ込み／提出するs) 同様に as to the “Types” 公式文書，認めるd in the translation database “LingTool”.


（米）棚上げする／（英）提議する 1 Capitalization of UI Strings によれば String Type


There may be exceptions to these capitalization 支配するs in older parts of the ソフトウェア that were designed before the style 指導基準s were written. In such 事例／患者s, keep that already 存在するing style 一貫した until an 適切な時期 arises (for example, a new feature 要求するs the dialog to be redesigned) to 改訂する the strings to 固執する to the style in these 指導基準s. The goal is to have all inconsistent strings 取って代わるd or 削除するd as time goes by.

A 類似の （米）棚上げする／（英）提議する is 公然と 利用できる for OOo:

最高の，を越す

One Text Only for Menu, Tooltip and Customize Dialog

As of OpenOffice.org 8, a central とじ込み／提出する was created so that only one 資源 text (string) would 存在する for all main menu items, the tooltips of the corresponding icons, and the corresponding 指名するs in the 名簿（に載せる）／表（にあげる） in the Customize Toolbar dialog (1=3). Therefore, changing the text of a menu item in the central とじ込み／提出する also changes the corresponding tooltip text and 入ること／参加（者） in the Customize dialog and 副／悪徳行為 versa. This is in the 利益／興味 of 持続するing terminological consistency, in English and all other languages. There are very few exceptions (maybe 2) where the tooltip has to have a わずかに different text than the menu item. These exceptions have to be supported by extra 機械装置s in the code. Exceptions to this 1=3 扱うing are only 許すd when 絶対 necessary, 予定 to the extra 維持／整備 成果／努力.

最高の，を越す

8. Text for Wizards

引用するd from sections 5.3 and 5.5 in the specification: specs.openoffice.org/取り付け・設備/wizards/Wizards_NewConcept.sxw

肩書を与える 妨げる／法廷，弁護士業

The 肩書を与える of the 肩書を与える 妨げる／法廷，弁護士業 代表するs the 指名する of the wizard. Use 肩書を与える capitalization style. It remains the same over all pages of the wizard.

Left Pane (Roadmap)

The roadmap steps may be 拡大するd over two lines, but they should be kept as short and 正確な as possible. Verb phrases are preferred, but noun phrases can be used instead. You should use the same grammatical type 終始一貫して for the whole roadmap.

Each roadmap step must correspond to the 長，率いるing of the page it calls in the 権利 pane. That means that the words of the roadmap step are used in the 長，率いるing, if at all possible. Use 宣告，判決 capitalization but do not put a period or other punctuation at the end even if it is 宣告，判決. The 宣告，判決 capitalization makes it possible to have shorter 同様に as longer text for the roadmap, depending on the 目的 of the wizard. If 肩書を与える capitalization were 定める／命ずるd, then longer text, for example a 宣告，判決, would look ridiculous and not be as legible. For the same 推論する／理由, we leave the period out: Only 十分な 宣告，判決s should end with 宣告，判決 punctuation, but most of the time the roadmap will not 含む／封じ込める 宣告，判決s. Therefore by never using the period, we 避ける inconsistency in the 全体にわたる look for all wizards.

権利 Pane

The 長，率いるing of the page in the 権利 pane must correspond to the roadmap 入ること／参加（者） that calls that page. The 長，率いるing should be in the imperative (not a question). The imperative form introduces the （警察などへの）密告，告訴（状） dealt with on the active dialog page by directing the 使用者 to do what is to be done on that page. For example “Enter 指名する, 演説（する）／住所 and telephone number” or “Select 資産 types”.

Use 宣告，判決 capitalization but do not put a period or other punctuation at the end of the 宣告，判決, since this is a 長，率いるing. The 宣告，判決 capitalization makes it possible to have shorter 同様に as longer text at the 最高の，を越す of a dialog or wizard page. If 肩書を与える capitalization were 定める／命ずるd, then longer text, for example a 宣告，判決, would look ridiculous and not be as legible. For the same 推論する／理由, we leave the period out: Only 十分な 宣告，判決s should end with 宣告，判決 punctuation, but いつか headings are not 十分な 宣告，判決s. Therefore by never using the period, we 避ける inconsistency in the 全体にわたる look.






Mnemonics

Make sure the mnemonics (hotkeys) are defined for every 支配（する）／統制する label (not for text without a 支配（する）／統制する, such as group headings in dialogs). Mnemonics are necessary to make the 支配（する）／統制するs accessible 経由で keyboard instead of only 経由で mouse. This is very important because it enables the ソフトウェア to 従う with accessibility 必要物／必要条件s in “Section 508”.

Mnemonics only have to be 始める，決める manually in English strings, not German or other foreign languages, as there is a 大型の that 生成するs the mnemonics at runtime for other languages. In Asian languages, the English mnemonic will automatically be 始める，決める in parentheses に引き続いて the Asian string. The 大型の could also be used to create mnemonics for English, as is indeed the 事例／患者 if they are accidentally not 始める，決める by 手渡す, but because the English mnemonics 直接／まっすぐに 影響する／感情 other languages, they have to be carefully chosen and not 生成するd 無作為に.

Use the mockup of the dialog or menu in the design specification to 補助装置 you in finding which letters to use. The mnemonic in the string 資源 とじ込み／提出する is denoted by a tilde in 前線 of the letter that will be 強調するd onscreen.

最高の，を越す

9. 虫垂 A

Checklist

This checklist is meant to 供給する quick input for people creating UI text. The points below are arranged starting with the most important ones and ending with the lesser important ones. To learn more about why UI text must 適合する to the points on the checklist, read the corresponding sections in this guide.

The checklist does not 含む every 支配する you should follow when creating text, only the most 批判的な and obvious ones. 付加 （警察などへの）密告，告訴（状） can be 設立する in the さまざまな sections of this guide, 含むing examples and 明確な／細部 詳細（に述べる）s.

10. 見解／翻訳／版 History

見解／翻訳／版

Date

Who

What
2.19 16.12.05 Christian Jansen Created OpenOffice.org 見解／翻訳／版

The ASF

Copyright & License | Privacy | 接触する Us | 寄付する | Thanks

Apache, OpenOffice, OpenOffice.org and the seagull logo are 登録（する）d trademarks of The Apache ソフトウェア 創立／基礎. The ASF logo is a trademark of The Apache ソフトウェア 創立／基礎. Other 指名するs appearing on the 場所／位置 may be trademarks of their 各々の owners.