Jump to: navigation, search

Information about the group Translation of the wiki page Typographical Guidelines.
Typographical GuidelinesCurrent message text
...delines/Page display title/zh-cn排版准则
...Typographical Guidelines/1/zh-cn''有个单独的[[Special:myLanguage/Toolbox|常规语法]]页面,包含了示例代码。''
...Typographical Guidelines/2/zh-cnAdhering to these typographic guidelines will ensure that your documentation can be accurately and easily exported for translation purposes.
...Typographical Guidelines/3/zh-cn== Bold Text ==
...Typographical Guidelines/4/zh-cnUse bold text to highlight
* Window titles
* Common labels that are not user-configurable
* Icon captions
* Program names
...Typographical Guidelines/5/zh-cnFor example:
...Typographical Guidelines/6/zh-cn* Highlighting a selection of text will copy it to '''Klipper'''.
...Typographical Guidelines/7/zh-cn== Italic Text ==
...Typographical Guidelines/8/zh-cnUse italic text to emphasise 
* Words or phrases as in general writing.
* Titles when referencing other works.
* The first use of an unfamiliar word.
...Typographical Guidelines/9/zh-cnSome examples:
* ''Save your work at this point.''
* Details can be found in ''Samba 3 by Example''....
* KDE Manuals are in ''Docbook'' format.
...ypographical Guidelines/10/zh-cn{{Tip|1=''Programs'' are launched by users, ''components'' are used by programs}}
...ypographical Guidelines/11/zh-cn== Combined Bold and Italic Text ==
...ypographical Guidelines/12/zh-cnUse this combination for replaceable or variable text.
...ypographical Guidelines/13/zh-cnSome examples:
* To connect to your remote server, type <code>ssh</code> '''''''''' in '''Konsole'''.
* In rpm-based distributions, the command <code>rpm -q</code> '''''packagename''''' will result in '''''package-version-release'''''.
...ypographical Guidelines/14/zh-cn== Mono-spaced Text ==
...ypographical Guidelines/15/zh-cnCode should be presented in mono-spaced text, usually boxed, as shown below.  Input text will be on a pale yellow background.  For output text, the background colour will be violet-grey.
...ypographical Guidelines/16/zh-cn* Code, whether single lines or blocks, use templates to ensure consistency
...ypographical Guidelines/17/zh-cn* Use the  Input template like this: {{Input|1=<nowiki>{{Input|1=<nowiki>
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit
rm -r ~/.kde/share/apps/nepomuk
rm -r ~/.kde4/share/apps/nepomuk
nepomukserver&lt;/nowiki>}}</nowiki>}} This will display like this: {{Input|1=<nowiki>
qdbus org.kde.NepomukServer /nepomukserver org.kde.NepomukServer.quit
rm -r ~/.kde/share/apps/nepomuk
rm -r ~/.kde4/share/apps/nepomuk
...ypographical Guidelines/18/zh-cn* Output works the same way: {{Output|1=<nowiki>{{Output|1=<nowiki>terminal output 
is also shown as code, 
but on a grey background&lt;/nowiki>}}</nowiki>}} which displays as {{Output|1=<nowiki>terminal output 
is also shown as code, 
but on a grey background</nowiki>}}
...ypographical Guidelines/19/zh-cn{{Note|1=Note the use of <code><nowiki>1=<nowiki> some text &lt;/nowiki></nowiki></code> to avoid situations that break the display format}}
...ypographical Guidelines/20/zh-cn* Starting an Input or Output template on a new line will break the display format if it is within lists.  Simply continue on the same line if you need to correct this.
...ypographical Guidelines/21/zh-cn* You can also combine input/output areas with [ GeSHi syntaxhiglighting]. An input area like this {{Input|1=<nowiki>{{Input|<syntaxhighlight lang="php" line>
# Initialise common code
$preIP = dirname( __FILE__ );
require_once( "$preIP/includes/WebStart.php" );
}} will result in {{Input|<syntaxhighlight lang="php" line>
# Initialise common code
$preIP = dirname( __FILE__ );
require_once( "$preIP/includes/WebStart.php" );
...ypographical Guidelines/22/zh-cn* Single code words can be kept in-line by using {{Input|1=<nowiki><code></code></nowiki>}}  It will <code>display</code> like this.
...ypographical Guidelines/23/zh-cn* {{Input|1=<nowiki>&lt;tt> &lt;/tt></nowiki>}} is useful for displaying filenames and paths.  This looks like this: <tt>  a/path/to/here </tt>
...ypographical Guidelines/24/zh-cn== Block Quotes ==
...ypographical Guidelines/25/zh-cnThe tags <nowiki><blockquote></nowiki> and <nowiki></blockquote></nowiki> should be used when quoting other works or other pages.  This produces a proportional italic font, with some padding.
...ypographical Guidelines/26/zh-cn<blockquote>Here is an example of the display that you get by using the blockquote tags.</blockquote>
...ypographical Guidelines/27/zh-cn== Text in Section Headers ==
...ypographical Guidelines/28/zh-cnEven though the criteria above may be met, do not use Bold text in section headers or in links.
...ypographical Guidelines/29/zh-cn== Text in Information, Note, Tip or Warning Templates ==
...ypographical Guidelines/30/zh-cnBold text should be avoided in the text within these templates.  Italic text for emphasis may still be used - use sparingly for maximum effect.
...ypographical Guidelines/31/zh-cn== Lists ==
...ypographical Guidelines/32/zh-cnYou can have various kinds of lists in your pages &mdash; bulleted, numbered or itemized. Find details on the [[Special:myLanguage/Toolbox#Bulleted Lists|Toolbox]] page.
...ypographical Guidelines/33/zh-cn== Keeping things together ==
...ypographical Guidelines/34/zh-cnAfter your text is written some markup is automatically added by the translation system. This means that whenever it sees a blank line, it starts a new unit. When your text is presented to translators, they typically see it one unit at a time, so it is important not to leave a blank lines in the middle of something that should be treated as a unit. Normally an entire paragraph should be kept in a single unit; and under no circumstance should a sentence be split between units!
...ypographical Guidelines/35/zh-cnIf you need a linebreak in the middle of a section, the preferred way to achieve this is without breaking units is to use <nowiki><br /></nowiki> at the end of the line where you want to break to occur (not on a new line). If you need space between the lines add <nowiki><br /><br /></nowiki>.
...ypographical Guidelines/36/zh-cn== Unbalanced brackets ==
...ypographical Guidelines/37/zh-cn<!--}}-->The translation system marks any translated unit as incompletely translated if it contains any kind of unbalanced brackets. If you need to have unbalanced brackets in your text, please add a balancing bracket in a comment tag, like this:<br />
<nowiki><!-- }} -->{{ A line
...ypographical Guidelines/38/zh-cnAnother line}}<!-- {{ --></nowiki>
This goes for all kinds of brackets, even ordinary parentheses. (Of course it is normally better to avoid blank lines within a mark up unit - see [[Special:myLanguage/Typographical_Guidelines#Keeping_things_together|Keeping things together]].)
...ypographical Guidelines/39/zh-cn== Special Tags ==
...ypographical Guidelines/40/zh-cn* <nowiki> <keycap></nowiki> and <nowiki> </keycap> </nowiki> denote (keyboard) key names e.g. <keycap>Enter</keycap>
* <nowiki><keycap></keycap></nowiki> can also be used around groups of keys to be used concurrently, e.g. <keycap>Ctrl + Alt + F1</keycap> to launch a virtual terminal. (Note that "(space)+(space)" is used to link keys to be pressed concurrently).
* Sequences of menu choices should use <nowiki> <menuchoice> </nowiki>and <nowiki> </menuchoice> </nowiki> for example <menuchoice> View -> Message List -> Aggregation -> Standard Mailing List </menuchoice>
* In general, if the user needs to choose an element, even if it is not in a menu, the <nowiki><menuchoice></menuchoiсe></nowiki> markup should be used.
...ypographical Guidelines/41/zh-cn== The Problematic Pipe Symbol ==
...ypographical Guidelines/42/zh-cnIn some situations the pipe symbol cannot be used - for instance when giving parameters in a template - as it has a system meaning.  In such cases please use <nowiki>{{!}}</nowiki>.  For example, if you want to display a command line containing the pipe character using the <nowiki>{{Input|...}}</nowiki> template, the simplest way to do it is this: <code><nowiki>{{Input|1=cmd1 {{!}} cmd2}}</nowiki></code> which displays {{Input|1=cmd1 {{!}} cmd2}}
...ypographical Guidelines/46/zh-cn<br />If you just write <code><nowiki>{{Input|1=cmd1 | cmd2}}</nowiki></code> you get instead {{Input|1=cmd1 | cmd2}}
the problem being, that <code>cmd2</code> is seen as a second parameter to the template, which in this case is not used.
...ypographical Guidelines/47/zh-cnIn many cases, you can also enclose the text containing the pipe character between <nowiki><nowiki>...</nowiki> </nowiki> tags, like this <code><nowiki>{{Input|1=<nowiki>cmd1 | cmd2</nowiki></nowiki><nowiki>}}</nowiki></code>, which also displays {{Input|1=<nowiki>cmd1 | cmd2</nowiki>}}
...ypographical Guidelines/43/zh-cn== Translatable Content ==
...ypographical Guidelines/44/zh-cnEverything that is translatable is contained within <nowiki>&lt;translate> and &lt;/translate></nowiki> tags.  In most cases any images should be contained within the translatable section, as it is sometimes necessary to use localised versions of the images to explain a point.  The rule of thumb is "If in doubt, include it!".
...ypographical Guidelines/45/zh-cn[[Category:Translator_Help]]
NavigationShowing 48 messages.
KDE® and the K Desktop Environment® logo are registered trademarks of KDE e.V.Legal