Tasks and Tools/zh-cn: Difference between revisions
No edit summary |
(Created page with ":13px 不针对开发者 - [http://techbase.kde.org Techbase] 才是放开发文章的地方") |
||
Line 16: | Line 16: | ||
:[[Image:dialog-ok32.png|13px]] 针对高级用户 - 但放到一个子页面里。 | :[[Image:dialog-ok32.png|13px]] 针对高级用户 - 但放到一个子页面里。 | ||
:[[Image:edit-delete.png|13px]] | :[[Image:edit-delete.png|13px]] 不针对开发者 - [http://techbase.kde.org Techbase] 才是放开发文章的地方 | ||
== Ways to Contribute == | == Ways to Contribute == |
Revision as of 06:51, 17 June 2011
开始之前
第一点
- 任何人都可以作出贡献,不需要注册帐户。但我们建议创建一个帐户,因为帐号注册提供了实际优势。请访问快速开始页面,那里提供了注册和登录的帮助信息。
- 请注意,您的贡献将被授权为 Gnu Free Document Licence and Creative Commons!点击导航面板上的图片可以阅读详细信息。您需要同意公开贡献并允许其他人在自己网站上使用!
- 使用讨论页面与其他人交流或获得帮助。通常一天之内就会得到回应。
相关性
所有内容应该与 KDE 软件直接或间接的相关。相关的内容包括:
- 不针对开发者 - Techbase 才是放开发文章的地方
Ways to Contribute
Update Existing Content
- Update an image, replacing an outdated image with a newer one.
- Create a screenshot
- Modify existing content, fix a spelling, clarify a description, add more details.
Add New Pages
- Create a new page, showcase an application, introduce a new concept.
- Write a manual. You need to know an application quite well, and probably to be in contact with the author. We can help you.
Working with Languages
- Preparing a page for translation needs more patience than skill. If you can spare short periods of time, frequently, this is a very helpful task.
- Translate a page. You need to be fluent in a language, but not a professional translator to translate a wiki page. Translating manuals is the skill of a special team.
- Translate with Off-Line Tools. Get the essentials for Gettext and Import.
- How To Convert UserBase Manual to Docbook gives you an insight into the process that takes place on your finished manual.
Remember
It's important to be consistent, particularly in Manuals, so here are some general rules:
- Take care with heading levels - we start at second level (Mediawiki uses top level for page-name), using ==
- Make sure you refer frequently to this page, to Tasks and Tools and to Typographical Guidelines
- Check if all table cells have space after the pipe character. This rule conforms with traditional wiki formatting.
- Make application name formatting consistent (avoid using Amaroks, do use Amarok's).
- Ensure that all images are in PNG format (you can use JPEG (.jpeg, not .jpg) as well, but in this case you should convert your images to PNG later. Save work by converting them before you start .
- Remove all non-printable characters from image names.
Hints and Tips
Some Preferences that will help -
- If you don't have [edit] links against the sections, open your (in the section of the sidebar) then look for and in the set
- While you are in those settings, enable - while you are editing you can glance at the original display for reference
- The default display is to show the preview first, with the edit box below. If you prefer the edit box at the top you can change that setting in the same place