/[KDE]/trunk/l10n-kf5/zh_CN/messages/websites-docs-krita-org/docs_krita_org_contributors_manual___krita_manual_readme.po

Contents of /trunk/l10n-kf5/zh_CN/messages/websites-docs-krita-org/docs_krita_org_contributors_manual___krita_manual_readme.po

Parent Directory Parent Directory | Revision Log Revision Log

Revision 1660347 - (show annotations) (download)
Sun Sep 17 01:24:01 2023 UTC (2 months, 2 weeks ago) by scripty
File size: 67466 byte(s) 
SVN_SILENT made messages (.po file)
1 msgid ""
2 msgstr ""
3 "Project-Id-Version: kdeorg\n"
4 "Report-Msgid-Bugs-To: \n"
5 "POT-Creation-Date: 2023-07-26 00:40+0000\n"
6 "PO-Revision-Date: 2023-09-16 10:09\n"
7 "Last-Translator: \n"
8 "Language-Team: Chinese Simplified\n"
9 "Language: zh_CN\n"
10 "MIME-Version: 1.0\n"
11 "Content-Type: text/plain; charset=UTF-8\n"
12 "Content-Transfer-Encoding: 8bit\n"
13 "Plural-Forms: nplurals=1; plural=0;\n"
14 "X-Crowdin-Project: kdeorg\n"
15 "X-Crowdin-Project-ID: 269464\n"
16 "X-Crowdin-Language: zh-CN\n"
17 "X-Crowdin-File: /kf5-trunk/messages/websites-docs-krita-org/"
18 "docs_krita_org_contributors_manual___krita_manual_readme.pot\n"
19 "X-Crowdin-File-ID: 9940\n"
20
21 #: ../../contributors_manual/krita_manual_readme.rst:None
22 msgid ".. image:: images/gitlab/screenshot_editmode.png"
23 msgstr ".. image:: images/gitlab/screenshot_editmode.png"
24
25 #: ../../contributors_manual/krita_manual_readme.rst:1
26 msgid "Contributor's Readme for the Krita Manual."
27 msgstr "介绍如何参加 Krita 文档的写作。"
28
29 #: ../../contributors_manual/krita_manual_readme.rst:26
30 msgid "Krita Manual Contribution Guide"
31 msgstr "Krita 文档写作指南"
32
33 #: ../../contributors_manual/krita_manual_readme.rst:28
34 msgid "Welcome to the Krita Manual Contribution Guide!"
35 msgstr "欢迎来到 Krita 文档写作指南页面。"
36
37 #: ../../contributors_manual/krita_manual_readme.rst:30
38 msgid ""
39 "If you're interested in contributing to Krita's documentation, you're in the "
40 "right place."
41 msgstr "如果你想要参加 Krita 英文版文档的编写工作，可参考本页面提供的信息。"
42
43 #: ../../contributors_manual/krita_manual_readme.rst:32
44 msgid ""
45 "Krita is (free) open source software, which effectively makes us a community "
46 "project with dozens of volunteers pitching in to make it better. This, of "
47 "course, requires we keep track of manuals and how-to's for new volunteers to "
48 "come in and help us. The various places we’ve done this have been rather "
49 "spread out, so the contributors' manual is an attempt to consolidate all the "
50 "information. It is therefore very technical in places."
51 msgstr ""
52 "Krita 是一个自由、开源的软件项目，这也意味着我们是一个由社区驱动的项目，有众"
53 "多志愿者们在为 Krita 的发展贡献力量。对于新加入的志愿者，我们准备了参与者手册"
54 "来指导他们如何参与项目工作。请注意：Krita 是一个国际性的协作项目，除当地社区"
55 "工作外，绝大多数情况下需要使用英语交流。参与者手册中有一部分技术性的内容是硬"
56 "性保留为英语的，它们不进行翻译。"
57
58 #: ../../contributors_manual/krita_manual_readme.rst:34
59 msgid "This documentation will include:"
60 msgstr "Krita 文档包含以下内容："
61
62 #: ../../contributors_manual/krita_manual_readme.rst:36
63 msgid "A reference manual for Krita"
64 msgstr "使用手册/参考手册"
65
66 #: ../../contributors_manual/krita_manual_readme.rst:37
67 msgid ""
68 "This one is probably what everyone is expecting when they look up Krita's "
69 "documentation. Dry, basic, 'what does this button do' type of information."
70 msgstr ""
71 "使用手册从日常使用的角度出发，按自然步骤介绍使用过程中遇到的功能，相当于按功"
72 "能分类的教程。参考手册相当于 Krita 的“说明书”。它按照软件的界面结构，逐一说明"
73 "每个功能的用法和选项的含义，便于速查和知识补遗。"
74
75 #: ../../contributors_manual/krita_manual_readme.rst:39
76 msgid ""
77 "We've found over the past two years that for certain types of users, a "
78 "reference manual, even with some examples, just isn't enough. The manual "
79 "should also provide fast and concise explanations for things, and provide a "
80 "basic workflow for preparing an image for the web."
81 msgstr ""
82 "使用手册和参考手册假设读者对数字绘画本身有基本认识。如果用户不只是 Krita 的新"
83 "手，而是对数字绘画，甚至是绘画本身都一无所知的菜鸟，那么我们就要从数字绘画基"
84 "础讲起了。这部分的文档会介绍美术、数字影像技术的关键知识，让用户理解各种相关"
85 "的名词、概念和基本操作流程。这些知识不仅适用于 Krita，也适用于任何数字绘画软"
86 "件。"
87
88 #: ../../contributors_manual/krita_manual_readme.rst:41
89 msgid ""
90 "We also have found that certain concepts, such as color management and layer "
91 "handling are far more advanced in Krita than the average artist is used to. "
92 "Krita is free and many of its users will not have formal training in digital "
93 "artwork. So there is no pre-existing artist-focused knowledge on how to use "
94 "color management or filter layers."
95 msgstr ""
96 "Krita 中的某些概念，如色彩管理和滤镜图层等，对于有经验的画师来说不难搞懂，可"
97 "对于外行人而言却非常抽象复杂。在网上并没有专门面向画师介绍这些知识的教程，因"
98 "此我们也在这里准备了相关章节。"
99
100 #: ../../contributors_manual/krita_manual_readme.rst:42
101 msgid "General concept tutorials."
102 msgstr "数字绘画基础知识"
103
104 #: ../../contributors_manual/krita_manual_readme.rst:43
105 msgid ""
106 "In addition there are systems that are unique to Krita, for example the "
107 "brush system, the transform masks, the alpha inheritance and the perspective "
108 "assistants. Finally, there are users who aren't familiar with even standard "
109 "painting workflows, and are not flexible enough to understand how to port a "
110 "tutorial for SAI or Photoshop to Krita."
111 msgstr ""
112 "除此之外，Krita 有许多方面与其他软件有所区别。例如笔刷系统、变形蒙版、透明度"
113 "继承方式和透视辅助尺等。考虑到许多用户对最基本的数字绘画流程都不熟悉，他们很"
114 "难拿着一篇面向 SAI 或者 Photoshop 教程，然后把里面的思路套用到 Krita 下面使"
115 "用。因此我们也要针对这些方面专门编写 Krita 自己的教程。"
116
117 #: ../../contributors_manual/krita_manual_readme.rst:44
118 msgid "A list of known tutorials and video tutorials"
119 msgstr "实例教程"
120
121 #: ../../contributors_manual/krita_manual_readme.rst:45
122 msgid ""
123 "Apparently, one of the great things about Krita's team is how we connect "
124 "with artists and acknowledge that they're doing cool stuff. The same should "
125 "count for tutorials, especially because there are ways of using Krita and "
126 "ways of approaching painting that are unique and we should encourage people "
127 "to share their knowledge."
128 msgstr ""
129 "实例教程可以带着用户从头到尾完成一个作品的绘制，以自然直观的方式介绍一个典型"
130 "绘画流程中要用到的各种工具，对于入门期的用户很有帮助。我们相信每位画师都有自"
131 "己惯用的独特流程，我们可以鼓励他们在这里分享这些经验。"
132
133 #: ../../contributors_manual/krita_manual_readme.rst:46
134 msgid "Contributors' Manual"
135 msgstr "参与者手册"
136
137 #: ../../contributors_manual/krita_manual_readme.rst:47
138 msgid "What you're reading right now!"
139 msgstr ""
140 "你正在阅读的就是贡献者手册，它为想要参与 Krita 工作的人员准备了各种指导性文"
141 "章。"
142
143 #: ../../contributors_manual/krita_manual_readme.rst:48
144 msgid "krita.org tutorials"
145 msgstr "扩展包和第三方教程"
146
147 #: ../../contributors_manual/krita_manual_readme.rst:49
148 msgid ""
149 "There have been a bunch of tutorials on the krita.org and the krita-"
150 "foundation.tumblr.com, the former focusing on explaining how to use a new "
151 "feature and the later stimulated by user request."
152 msgstr ""
153 "把用户提供的各种笔刷包、纹理包、外部教程和视频、Python 插件等在这个分类中列"
154 "出，方便其他用户利用。"
155
156 #: ../../contributors_manual/krita_manual_readme.rst:51
157 msgid "FAQ"
158 msgstr "常见问题解答"
159
160 #: ../../contributors_manual/krita_manual_readme.rst:51
161 msgid ""
162 "This one is already online and a merger of the different FAQs that we had. "
163 "It's currently being translated and we hope to keep this one the primary one "
164 "to update."
165 msgstr ""
166 "此页面罗列了可以简单解答的常见问题。它的内容会根据我们收到的社区反馈持续更"
167 "新。"
168
169 #: ../../contributors_manual/krita_manual_readme.rst:54
170 msgid "For first timers"
171 msgstr "新手指引"
172
173 #: ../../contributors_manual/krita_manual_readme.rst:56
174 msgid "Unlike Mediawiki, Sphinx works more like how we write code for Krita."
175 msgstr ""
176 "与 Mediawiki 不同，为 Sphinx 编写文档的流程更像是我们为 Krita 编写代码的流"
177 "程。"
178
179 #: ../../contributors_manual/krita_manual_readme.rst:58
180 msgid ""
181 "First things first, you will want to talk to us! For this you can join us in "
182 "the chatroom \"#krita\" via matrix. A introduction about Matrix is given "
183 "`here <https://community.kde.org/Matrix>`_. Create a matrix on webchat.kde."
184 "org account and join the #krita:kde.org channel. Or more importantly, make "
185 "an account at `identity.kde.org <https://identity.kde.org/>`_. The account "
186 "you make at identity can be used to both access invent.kde.org as well as "
187 "the `phabricator`_, where we organise Krita development."
188 msgstr ""
189 "首先你要与我们建立联系。你可以通过 Matrix 加入我们的 \"#krita\" 网络聊天室。"
190 "先前往 webchat.kde.org 网站并创建一个 Matrix 账户，然后加入 #krita:kde.org 频"
191 "道。Matrix 的详细使用方式请访问\\ `此页面 <https://community.kde.org/"
192 "Matrix>`_\\ 。但更重要的是在 `KDE Identity 网站 <https://identity.kde.org/"
193 ">`_ 上面创建一个账户，这个账户可以用来访问我们的开发平台：invent.kde.org 和 "
194 "`Phabricator`_ 网站。"
195
196 #: ../../contributors_manual/krita_manual_readme.rst:60
197 msgid ""
198 "Sphinx works by writing simple text files with reStructuredText mark up, and "
199 "then it takes those text files and turns them into the manual. We keep track "
200 "of changes in the manual by putting them into a version control system "
201 "called :program:`Git`."
202 msgstr ""
203 "Sphinx 文档是通过基于 reStructuredText 标记语言的纯文本编写的。在你贡献的新内"
204 "容同步后，Sphinx 程序会自动把你编写的纯文本代码转换成网页版手册和电子书。我们"
205 "通过一个叫做 :program:`Git` 的版本控制系统来跟踪 Krita 文档的内容变化。"
206
207 #: ../../contributors_manual/krita_manual_readme.rst:65
208 msgid "Making changes"
209 msgstr "更改内容"
210
211 #: ../../contributors_manual/krita_manual_readme.rst:67
212 msgid ""
213 "Because we use Git, there's only a few people who can put things into the "
214 "version control system, so if you want to make changes you will need to put "
215 "it up for review."
216 msgstr ""
217 "在 Git 系统下面，只有部分开发人员有权限向文档源代码的主要分支推送内容。如果你"
218 "想要对手册内容作出更改，你必须把作出的改动提交审核。"
219
220 #: ../../contributors_manual/krita_manual_readme.rst:73
221 msgid "Creating merge requests using Edit mode"
222 msgstr "使用网站的 Edit 模式创建合并请求"
223
224 #: ../../contributors_manual/krita_manual_readme.rst:77
225 msgid ""
226 "This method is only suitable if you have no push access to KDE repositories. "
227 "Otherwise it would commit your changes directly to the repository, which is "
228 "against the current guidelines."
229 msgstr ""
230 "此方法面向没有 KDE 代码仓库的 push 权限的用户。因为按照我们的代码贡献指导方"
231 "针，一般用户不应该对代码仓库的内容进行直接更改。"
232
233 #: ../../contributors_manual/krita_manual_readme.rst:80
234 msgid "Recommended for users without a technical knowledge."
235 msgstr "如果你不了解相关技术，请使用此方式进行协作。"
236
237 #: ../../contributors_manual/krita_manual_readme.rst:82
238 msgid ""
239 "Not recommended when you want to change more than one file at once. (See :"
240 "ref:`merge-request-webide` or :ref:`merge-request-terminal` if you want to "
241 "change more files, or simply edit only one per merge request)."
242 msgstr ""
243 "不推荐需要同时更改多个文件时使用。（如需更改多个文件，请参见 :ref:`merge-"
244 "request-webide` ，如使用每次合并请求编辑一个文件的方式，请参见 :ref:`merge-"
245 "request-terminal` ）。"
246
247 #: ../../contributors_manual/krita_manual_readme.rst:85
248 msgid ""
249 "If you have a lot of changes you want to contribute, we recommend trying to "
250 "follow these instructions."
251 msgstr "如果你打算对文档进行大量改动，我们建议你按照下述方法进行协作。"
252
253 #: ../../contributors_manual/krita_manual_readme.rst:87
254 msgid "Get a KDE identity."
255 msgstr "注册一个 KDE Identity 账户。"
256
257 #: ../../contributors_manual/krita_manual_readme.rst:88
258 msgid "Login to `KDE_gitlab`_."
259 msgstr "登录到 `KDE_gitlab`_ 网站。"
260
261 #: ../../contributors_manual/krita_manual_readme.rst:89
262 msgid "Go to the `repository`_ and press :guilabel:`fork`."
263 msgstr "访问 `repository`_ 页面并点击 :guilabel:`fork` 。"
264
265 #: ../../contributors_manual/krita_manual_readme.rst:90
266 msgid ""
267 "You should be redirected to the fork of your repository now. Typically it's "
268 "located at ``invent.kde.org/YOUR_KDE_LOGIN_NAME/docs-krita-org``."
269 msgstr ""
270 "你会被跳传到你的 fork 所在的代码仓库页面。它通常位于 ``invent.kde.org/你的 "
271 "KDE 登录名/docs-krita-org``\\ 。"
272
273 #: ../../contributors_manual/krita_manual_readme.rst:92
274 msgid ""
275 "Come back to the official repository. Make sure you're browsing "
276 "``Documentation > Krita.org Documentation``, not your own fork. Otherwise "
277 "this method won't work correctly."
278 msgstr ""
279 "返回官方代码仓库，确保你浏览的是 ``Documentation > Krita.org "
280 "Documentation`` ，而不是你自己的 fork ，否则本方法将不能正确工作。"
281
282 #: ../../contributors_manual/krita_manual_readme.rst:94
283 msgid ""
284 "Gitlab has an option to Edit files in the gitlab itself. To access this, go "
285 "to :menuselection:`Repository --> Files`."
286 msgstr ""
287 "Gitlab 提供了直接在网页中编辑文件的功能。要使用该功能，请前往 :menuselection:"
288 "`Repository --> Files` 。"
289
290 #: ../../contributors_manual/krita_manual_readme.rst:96
291 msgid ""
292 "At the top of the page you should see a dropbox with ``master`` as a chosen "
293 "item."
294 msgstr "在页面靠上方显示了一个选单，它已经选中了 ``master`` 。"
295
296 #: ../../contributors_manual/krita_manual_readme.rst:98
297 msgid ""
298 "Find the file you want to edit, open it and then click :guilabel:`Edit`."
299 msgstr "找到你想要编辑的文件，打开它然后点击 :guilabel:`Edit` 。"
300
301 #: ../../contributors_manual/krita_manual_readme.rst:100
302 msgid ""
303 "Make your changes. (Note: in this mode you can edit only one file at a time)."
304 msgstr "对文件进行更改。(注意：在此模式下你只能每次编辑一个文件)。"
305
306 #: ../../contributors_manual/krita_manual_readme.rst:102
307 msgid ""
308 "Go to the smaller textbox below and write a nice message in the commit "
309 "message section with the changes you've made. When done, press :guilabel:"
310 "`Commit changes`. This will make a merge request for you, just fill in all "
311 "of the fields as explained here: :ref:`new-merge-request`."
312 msgstr ""
313 "转到下方较小的文本框，在 commit message 处将你所做的更改总结为一则简要的描"
314 "述。填好后，点击 :guilabel:`Commit changes` 即可创建合并请求，请按照 :ref:"
315 "`new-merge-request` 填写所需字段。"
316
317 #: ../../contributors_manual/krita_manual_readme.rst:104
318 msgid ""
319 "The downside is that right now there's no way to tell if you made errors "
320 "with the mark up using this method. Please check your changes with the "
321 "`Online Sphinx Editor <https://livesphinx.herokuapp.com/>`_ (just copy and "
322 "paste the entire file you're editing)."
323 msgstr ""
324 "这个方法有一个缺点，那就是在编辑时不能自动检测并提示 Sphinx 标记的错误。你可"
325 "以使用\\ `在线 Sphinx 编辑器 <https://livesphinx.herokuapp.com/>`_\\ ，将编辑"
326 "后的整段文字粘贴进去，检查是否存在问题。"
327
328 #: ../../contributors_manual/krita_manual_readme.rst:108
329 msgid ""
330 ":guilabel:`Edit` and :guilabel:`WebIDE` are two different things! Make sure "
331 "you select :guilabel:`Edit`."
332 msgstr ""
333 ":guilabel:`Edit` 和 :guilabel:`WebIDE` 是完全不同的功能！确保你选中的是 :"
334 "guilabel:`Edit` 。"
335
336 #: ../../contributors_manual/krita_manual_readme.rst:117
337 msgid "Creating merge requests using WebIDE"
338 msgstr "使用 WebIDE 来创建合并请求"
339
340 #: ../../contributors_manual/krita_manual_readme.rst:119
341 msgid ""
342 "Recommended for users with a bit of knowledge about Git that want to edit "
343 "multiple files at once."
344 msgstr "如果你略懂 Git ，而且想要同时修改多个文件，我们推荐你使用此方式。"
345
346 #: ../../contributors_manual/krita_manual_readme.rst:121
347 #: ../../contributors_manual/krita_manual_readme.rst:160
348 msgid ""
349 "Not recommended when you don't know what a branch is (see :ref:`merge-"
350 "request-edit` instead)."
351 msgstr ""
352 "如果你不懂什么叫做 branch ，我们不推荐你使用此方式 (请改用 :ref:`merge-"
353 "request-edit` 方式)。"
354
355 #: ../../contributors_manual/krita_manual_readme.rst:124
356 #: ../../contributors_manual/krita_manual_readme.rst:162
357 msgid ""
358 "Follow the instructions above to login to `KDE_gitlab`_ and create your fork."
359 msgstr "按照前面介绍过的方法登录 `KDE_gitlab`_ 网站，并建立你的 fork 。"
360
361 #: ../../contributors_manual/krita_manual_readme.rst:126
362 msgid "Go to your fork (make sure the url contains your username)."
363 msgstr "前往你的 fork 页面，如前文所述，确保 URL 包含你的用户名。"
364
365 #: ../../contributors_manual/krita_manual_readme.rst:128
366 msgid "Make sure you're on the ``master`` branch."
367 msgstr "确保你在 ``master`` branch 上。"
368
369 #: ../../contributors_manual/krita_manual_readme.rst:130
370 msgid ""
371 "Click :guilabel:`WebIDE`. This should take you to a page that has a list of "
372 "files on the left side and a big empty space for file contents on the right "
373 "side."
374 msgstr ""
375 "点击 :guilabel:`WebIDE` 。这将跳传到一个网页，页面的左侧有一个文件列表，右侧"
376 "较大的空间用于显示文件的内容。"
377
378 #: ../../contributors_manual/krita_manual_readme.rst:132
379 msgid "Open the files you want to edit and make the changes."
380 msgstr "打开你需要编辑的文件，进行修改。"
381
382 #: ../../contributors_manual/krita_manual_readme.rst:134
383 msgid ""
384 "Click :guilabel:`Commit...`. Double-click on all files in the :guilabel:"
385 "`Unstaged changes` category to move them to :guilabel:`Staged changes`."
386 msgstr ""
387 "点击 :guilabel:`Commit...` 。在 :guilabel:`Unstaged changes` 分类里双击每个文"
388 "件，把他们移动到 :guilabel:`Staged changes` 中去。"
389
390 #: ../../contributors_manual/krita_manual_readme.rst:136
391 msgid ""
392 "Click :guilabel:`Commit...` again - it will expand a commit message textbox. "
393 "Write commit message that explains what changes have you made and why."
394 msgstr ""
395 "再次点击 :guilabel:`Commit...` ，这将展开一个 commit message 文本框。请填写你"
396 "修改了什么，并说明原因。"
397
398 #: ../../contributors_manual/krita_manual_readme.rst:138
399 msgid ""
400 "Make sure the settings are correct: you need to select :guilabel:`Create a "
401 "new branch` (the name of the branch should be: ``[username]/[very short "
402 "description of your changes]``). If you finished your changes, make sure "
403 "that :guilabel:`Start a new merge request` is checked. Otherwise you'll need "
404 "to make a new merge request manually later."
405 msgstr ""
406 "确保设置正确：你必须点击 :guilabel:`Create a new branch` (branch 名称为： "
407 "``[用户名]/[概括更改内容的短语]``)。在完成更改后，确保勾选了 :guilabel:"
408 "`Start a new merge request` ，否则你事后还要手动创建一个新的合并请求。"
409
410 #: ../../contributors_manual/krita_manual_readme.rst:140
411 msgid "Click :guilabel:`Stage & Commit`."
412 msgstr "点击 :guilabel:`Stage & Commit` 。"
413
414 #: ../../contributors_manual/krita_manual_readme.rst:142
415 msgid "Fill all of the fields correctly: see :ref:`new-merge-request`."
416 msgstr "正确填写所有字段：参见 :ref:`new-merge-request` 。"
417
418 #: ../../contributors_manual/krita_manual_readme.rst:144
419 msgid ""
420 "To create a new merge request manually, go to Krita Manual official "
421 "repository (make sure the url *doesn't* contain your username now) and "
422 "click :guilabel:`Create a new merge request` (bright green button at the "
423 "left). Select your fork and select the branch that you've created in WebIDE."
424 msgstr ""
425 "如需手动创建一个新的合并请求，请前往 Krita Manual 的官方代码库 (确保 URL **不"
426 "** 包含你的用户名) 并点击 :guilabel:`Create a new merge request` (左侧的亮绿"
427 "色按钮)。选择你的 fork，然后选择你在 WebIDE 中创建的 branch 。"
428
429 #: ../../contributors_manual/krita_manual_readme.rst:148
430 msgid ""
431 "If you don't have a push access to the official repository, gitlab won't "
432 "allow you to save your changes if you were editing the official repository "
433 "by mistake (and :guilabel:`Create a merge request` won't help with that: you "
434 "still need to commit your changes to your branch, but if you don't have push "
435 "access, you can't do it). It will just show the message: *An error occurred "
436 "whilst committing your changes. Please try again.*"
437 msgstr ""
438 "如果你不具备在官方代码库中执行 push 的权限，又不小心在官方代码库中进行了编"
439 "辑，Gitlab 网站不会允许你保存更改 ( :guilabel:`Create a merge request` 也没有"
440 "作用：因为你依然需要把你的更改提交到你的 branch ，但如果你不具备 push 权限，"
441 "你是提交不了的)。页面将显示下述信息： *An error occurred whilst committing "
442 "your changes. Please try again.*"
443
444 #: ../../contributors_manual/krita_manual_readme.rst:150
445 msgid ""
446 "In this case, simply copy contents of all of the files you changed, go to "
447 "your fork and paste them in the fork WebIDE."
448 msgstr ""
449 "在这种情况下，请将你更改过的所有文件的内容复制下来，然后前往你的 fork ，找到"
450 "同名文件，通过 WebIDE 进行粘贴。"
451
452 #: ../../contributors_manual/krita_manual_readme.rst:156
453 msgid "Creating merge requests using command line"
454 msgstr "通过命令行创建合并请求"
455
456 #: ../../contributors_manual/krita_manual_readme.rst:158
457 msgid ""
458 "Recommended for users that know how Git works and how to use command line."
459 msgstr "如果你了解 Git 的工作方式，而且能够使用命令行，我们推荐你使用此方式。"
460
461 #: ../../contributors_manual/krita_manual_readme.rst:164
462 msgid ""
463 "Clone the repository locally with :guilabel:`git clone`. The repository page "
464 "has the urls you can perform git clone from, and you can then push to your "
465 "fork. The advantage of this is that you can use all the tools on your "
466 "computer to edit these text files as well as build the manual locally to "
467 "check for errors. (You need to do this step only once)."
468 msgstr ""
469 "使用 :guilabel:`git clone` 把代码库克隆到本地。代码库的页面显示了用于 git "
470 "clone 的 URL，你可以在之后通过该 URL 将改动 push 回你的 fork。此方式的优点是"
471 "你可以使用本地系统中的任意工具来编辑这些源文件，也可以在本地手动构建 Krita 文"
472 "档项目来检查错误。(你只需执行本步骤一次)。"
473
474 #: ../../contributors_manual/krita_manual_readme.rst:167
475 msgid ""
476 "# for ssh access\n"
477 "git clone [email protected]:<username>/docs-krita-org.git\n"
478 "git remote add upstream [email protected]:documentation/docs-krita-org.git\n"
479 "\n"
480 "# for https access\n"
481 "git clone https://invent.kde.org/<username>/docs-krita-org.git\n"
482 "git remote add upstream https://invent.kde.org/documentation/docs-krita-org."
483 "git"
484 msgstr ""
485 "# 通过 SSH 访问\n"
486 "git clone [email protected]:<username>/docs-krita-org.git\n"
487 "git remote add upstream [email protected]:documentation/docs-krita-org.git\n"
488 "\n"
489 "# 通过 HTTPS 访问\n"
490 "git clone https://invent.kde.org/<username>/docs-krita-org.git\n"
491 "git remote add upstream https://invent.kde.org/documentation/docs-krita-org."
492 "git"
493
494 #: ../../contributors_manual/krita_manual_readme.rst:177
495 msgid ""
496 "Remember to always pull changes from the official repository before making "
497 "new changes:"
498 msgstr "每次编辑之前，请务必从官方代码库将其最新改动 pull 到本机："
499
500 #: ../../contributors_manual/krita_manual_readme.rst:179
501 msgid "git pull upstream master"
502 msgstr "git pull upstream master"
503
504 #: ../../contributors_manual/krita_manual_readme.rst:184
505 msgid ""
506 "Make sure you create a new branch for your changes, since september 2019, "
507 "all changes should be branched from ``master``."
508 msgstr ""
509 "请确保你更改的内容创建一个新 branch 。自 2019 年起，所有的改动都必须从 "
510 "``master`` branch 出来。"
511
512 #: ../../contributors_manual/krita_manual_readme.rst:187
513 msgid ""
514 "git checkout master\n"
515 "\n"
516 "# and then:\n"
517 "git checkout -b \"<username>/<description of the new feature>\""
518 msgstr ""
519 "git checkout master\n"
520 "\n"
521 "# 然后执行：\n"
522 "git checkout -b \"<用户名>/<新改动内容概括短语>\""
523
524 #: ../../contributors_manual/krita_manual_readme.rst:196
525 msgid ""
526 "After you make your changes, commit them and push to your fork. For a "
527 "detailed description of how to use Git in terminal in case of this workflow, "
528 "go to :ref:`forking_gitlab`."
529 msgstr ""
530 "在你完成修改后，commit 这些改动，并将它们 push 到你的 fork 中。想要了解如何在"
531 "命令行中操作 Git 以完成此流程，请参见 :ref:`forking_gitlab` 页面。"
532
533 #: ../../contributors_manual/krita_manual_readme.rst:198
534 msgid ""
535 "# install the python3-sphinx package for your system. For example for "
536 "Ubuntu:\n"
537 "sudo apt install python3-sphinx\n"
538 "# build the manual (reports potential errors, allows to inspect changes in "
539 "the browser)\n"
540 "make html\n"
541 "# make sure everything is correct\n"
542 "git status\n"
543 "git diff\n"
544 "# add all of the files\n"
545 "git add .\n"
546 "# commit your changes\n"
547 "git commit\n"
548 "# submit your changes to your fork\n"
549 "git push"
550 msgstr ""
551 "# 为本机安装 python3-sphinx 软件包。以 Ubuntu 为例：\n"
552 "sudo apt install python3-sphinx\n"
553 "# 构建使用手册 (它将报告可能遇到的错误，并方便在浏览器中检查更改)\n"
554 "make html\n"
555 "# 检查所有源代码是否正确\n"
556 "git status\n"
557 "git diff\n"
558 "# 添加所有文件\n"
559 "git add .\n"
560 "# commit 你的更改\n"
561 "git commit\n"
562 "# push 你的更改到你的 fork\n"
563 "git push"
564
565 #: ../../contributors_manual/krita_manual_readme.rst:214
566 msgid ""
567 "Finally, go to the website of the original repository, and then to Merge "
568 "Requests. Select your fork and the correct branch and create a new merge "
569 "request. For instruction on how to fill the fields, see :ref:`new-merge-"
570 "request`."
571 msgstr ""
572 "最后，访问原始代码库的网站，然后访问 Merge Request。选择你的 fork，然后选中正"
573 "确的 branch ，创建一个新的 merge request 。想要了解如何填写这些字段，请参见 :"
574 "ref:`new-merge-request` 。"
575
576 #: ../../contributors_manual/krita_manual_readme.rst:220
577 msgid "Guidelines for new merge requests"
578 msgstr "新建合并请求规范"
579
580 #: ../../contributors_manual/krita_manual_readme.rst:222
581 msgid ""
582 "Your commit messages should conform to standards explained here: `How to "
583 "Write a Git Commit Message <https://chris.beams.io/posts/git-commit/>`_"
584 msgstr ""
585 "请按照： `How to Write a Git Commit Message <https://chris.beams.io/posts/"
586 "git-commit/>`_ 页面介绍的规范填写 Commit Message 栏。"
587
588 #: ../../contributors_manual/krita_manual_readme.rst:224
589 msgid ""
590 ":guilabel:`Title` and :guilabel:`Description` should explain what changes "
591 "did you make and why did you make them, just like a commit message, so "
592 "follow the guidelines from the link above in this case, too."
593 msgstr ""
594 "在 :guilabel:`Title` 和 :guilabel:`Description` 栏填写你改动的内容和原因，它"
595 "们和 commit message 的填写要求是一样的，请按照上面链接内的规范填写。"
596
597 #: ../../contributors_manual/krita_manual_readme.rst:226
598 msgid ":guilabel:`Target` should point to ``master``."
599 msgstr ":guilabel:`Target` 应该指向 ``master`` 。"
600
601 #: ../../contributors_manual/krita_manual_readme.rst:228
602 msgid ""
603 "If you're sure the merge request will demand some changes later, start the "
604 "title of your merge request with :code:`[WIP]`."
605 msgstr ""
606 "如果你觉得这个 merge request 还要进行修改，请在 merge request 的 title 前方加"
607 "入 :code:`[WIP]` 前缀。"
608
609 #: ../../contributors_manual/krita_manual_readme.rst:230
610 msgid ""
611 "Make sure you checked :guilabel:`Allow commits from members who can merge to "
612 "the target branch.` -- it is often needed for technical reasons that merge "
613 "request is rebased on master, which technically changes the merge request, "
614 "but it doesn't change the actual content of it. Rebase can be done by you or "
615 "by the reviewer -- if you don't want to be bothered later too much, better "
616 "check this checkbox so the reviewer can do it themselves with only a few "
617 "clicks."
618 msgstr ""
619 "确保你选中了 :guilabel:`Allow commits from members who can merge to the "
620 "target branch.` 项。这是因为 merge request 经常因为技术原因需要被 rebase 到 "
621 "master，而这个操作被系统视作对该 merge request 进行了改动 (尽管它的实际内容并"
622 "未改动)。你本人和审核人都可以 rebase ，所以如果想减少日后的麻烦，请勾选此选"
623 "项，以便审核人自行完成所需操作。"
624
625 #: ../../contributors_manual/krita_manual_readme.rst:232
626 msgid ""
627 "You can safely check :guilabel:`Delete source branch when merge request is "
628 "accepted` in most cases."
629 msgstr ""
630 "在大多数情况下，勾选 :guilabel:`Delete source branch when merge request is "
631 "accepted` 项是安全的。"
632
633 #: ../../contributors_manual/krita_manual_readme.rst:234
634 msgid ""
635 "Unless your reviewers tell you otherwise, check :guilabel:`Squash commits "
636 "when merge request is accepted`. The first line of the commit message will "
637 "come from the :guilabel:`Title` of your merge request and the rest of it "
638 "will be taken from the :guilabel:`Description` of the merge request."
639 msgstr ""
640 "除非你的审核人告诉你不要这样做，请勾选 :guilabel:`Squash commits when merge "
641 "request is accepted` 。commit message 的第一行来自 merge request 的 :"
642 "guilabel:`Title` 栏中填写的内容，其余部分则是 :guilabel:`Description` 栏中填"
643 "写的内容。"
644
645 #: ../../contributors_manual/krita_manual_readme.rst:236
646 msgid ""
647 "When you finish creating your merge request, go to IRC (see :ref:"
648 "`internet_relay_chat`) and ask someone with push access to add the ``Needs "
649 "Review`` label on your merge request."
650 msgstr ""
651 "创建 merge request 后，请访问Krita 的 IRC (参见 :ref:`internet_relay_chat` 页"
652 "面)，找一位具备 push 权限的开发人员为该 merge request 添加 ``Needs Review`` "
653 "标签。"
654
655 #: ../../contributors_manual/krita_manual_readme.rst:238
656 msgid ""
657 "You might get feedback on your merge request if it has mistakes. Just fix "
658 "the mistakes in your branch in one of the following ways."
659 msgstr ""
660 "如果别人在你的 merge request 中发现了错误，请在你的 branch 下面按下述方式进行"
661 "订正："
662
663 #: ../../contributors_manual/krita_manual_readme.rst:240
664 msgid ""
665 "If you want to use :guilabel:`Edit` mode, just go to :guilabel:`Changes` "
666 "section of the merge request and click on the pencil icon (with a tooltip "
667 "that says *Edit*) to use the Edit mode again."
668 msgstr ""
669 "如果你想使用 :guilabel:`Edit` 模式进行修改，请前往该 merge request 的 :"
670 "guilabel:`Changes` 栏目，点击“铅笔”图标 (鼠标悬浮时显示 *Edit*) 即可进入 "
671 "Edit 模式。"
672
673 #: ../../contributors_manual/krita_manual_readme.rst:242
674 msgid ""
675 "If you want to use :guilabel:`WebIDE` mode, go to your fork, select the "
676 "branch your changes are on and go to the WebIDE."
677 msgstr ""
678 "如果你想使用 :guilabel:`WebIDE` 模式，请前往你的 fork 页面，选中你的更改所在"
679 "的 branch，然后进入它的 WebIDE 模式。"
680
681 #: ../../contributors_manual/krita_manual_readme.rst:244
682 msgid ""
683 "If you edit files on your computer and work with terminal, make sure you're "
684 "on the correct branch and push your changes - gitlab will update your merge "
685 "request automatically."
686 msgstr ""
687 "如果你想在本机或者通过命令行终端编辑文件，请确保你在正确的 branch 上进行编"
688 "辑，然后 push 你的更改。Gitlab 会自动更新你的 merge request。"
689
690 #: ../../contributors_manual/krita_manual_readme.rst:246
691 msgid ""
692 "After making changes, make sure you ask someone to change the label to "
693 "``Needs Review`` again."
694 msgstr ""
695 "在进行上述改动后，请记得找人把该 merge request 的标签重新改为 ``Needs "
696 "Review`` 。"
697
698 #: ../../contributors_manual/krita_manual_readme.rst:249
699 msgid ""
700 "For more detailed information, check out :ref:`forking_gitlab` in the "
701 "technical section."
702 msgstr "想要了解更多信息，请参考 :ref:`forking_gitlab` 页面的介绍。"
703
704 #: ../../contributors_manual/krita_manual_readme.rst:253
705 msgid ""
706 "At the time of writing this guide setting labels on merge requests is only "
707 "possible by contributors with write access to the official repository. (If "
708 "you don't know what that means, you're most probably not one of them). "
709 "Because of that, when you create or change your merge request you need to "
710 "get on IRC (see :ref:`the_krita_community`) and ask someone to label it for "
711 "you."
712 msgstr ""
713 "在本文写作期间，只有具备 write 权限的贡献者才可以为官方库的合并请求设置标签。"
714 "(如果你不知道这是什么意思，你大概也不会有这个权限)。因此，在你创建或更改合并"
715 "请求后，必须到 IRC 上 (参见 :ref:`the_krita_community`) 找其他人帮你设置标"
716 "签。"
717
718 #: ../../contributors_manual/krita_manual_readme.rst:256
719 msgid "Building the manual in the command line"
720 msgstr "使用命令行模式构建文档"
721
722 #: ../../contributors_manual/krita_manual_readme.rst:258
723 msgid ""
724 "For those that first want to try out some changes before embarking on a "
725 "merge request right away (and already know how to use git and the command "
726 "line) this is described as part of step 5. in :ref:`merge-request-terminal`."
727 msgstr ""
728 "对于那些打算先测试更改再提交合并请求的编写者 (同时懂得如何使用 git 和命令行模"
729 "式)，请参考 :ref:`merge-request-terminal` 第 5 小节的介绍。"
730
731 #: ../../contributors_manual/krita_manual_readme.rst:264
732 msgid "General philosophy"
733 msgstr "指导思想"
734
735 #: ../../contributors_manual/krita_manual_readme.rst:266
736 msgid ""
737 "This is for determining what is an appropriate writing style. A writing "
738 "style, whether we consider its practical or aesthetic qualities, is usually "
739 "underpinned by a goal or general philosophy. What do we want to achieve with "
740 "the manual, and for whom is the manual meant?"
741 msgstr ""
742 "任何一篇文章都会表现出一定的文风，它同时体现在文字的实用层面和审美层面。文章"
743 "的写作目的和作者秉持的指导思想都会对文风造成影响。为了确定 Krita 文档的文风，"
744 "我们首必须确定文档是写来干什么的，它的读者又是哪些人。"
745
746 #: ../../contributors_manual/krita_manual_readme.rst:269
747 msgid "Demographics and target audience(s)"
748 msgstr "用户群体特性分析"
749
750 #: ../../contributors_manual/krita_manual_readme.rst:271
751 msgid ""
752 "We cannot talk about a demographic in the sense that we know all Krita users "
753 "are 55 year old men. Krita is used by a hugely different amount of people, "
754 "and we are actually kind of proud that we have such a varied userbase."
755 msgstr ""
756 "Krita 的用户基数庞大，来自五湖四海、各行各业，我们为拥有如此多样化的用户群体"
757 "而感到自豪。但也正因如此，我们不能粗暴地将 Krita 的用户群体当成是同一类人。"
758
759 #: ../../contributors_manual/krita_manual_readme.rst:273
760 msgid "Despite that, we know a couple of things about our users:"
761 msgstr "尽管如此，我们的用户群体还是具有一些共同点："
762
763 #: ../../contributors_manual/krita_manual_readme.rst:275
764 msgid "They are artists. This is explicitly the type of users that we target."
765 msgstr "他们都是画师，而画师就是我们要服务的目标人群。"
766
767 #: ../../contributors_manual/krita_manual_readme.rst:277
768 msgid "Therefore, we know they prefer pretty pictures."
769 msgstr "他们喜欢精美的画作。"
770
771 #: ../../contributors_manual/krita_manual_readme.rst:278
772 msgid "They are visual."
773 msgstr "他们以视觉方式思考。"
774
775 #: ../../contributors_manual/krita_manual_readme.rst:279
776 msgid "They are trying to achieve pretty pictures."
777 msgstr "他们想要创作出精美的画作。"
778
779 #: ../../contributors_manual/krita_manual_readme.rst:281
780 msgid ""
781 "Therefore, the implicit goal of each page would be to get the feature used "
782 "for pretty pictures."
783 msgstr ""
784 "所以，Krita 文档的目标应该是教会用户活用 Krita 的特性去创作出精美的画作。"
785
786 #: ../../contributors_manual/krita_manual_readme.rst:283
787 msgid "Other than that, we've observed the following groups:"
788 msgstr "在上面的基础上，我们还可以对 Krita 的用户群体进一步细分："
789
790 #: ../../contributors_manual/krita_manual_readme.rst:285
791 msgid ""
792 "High-school and college students trying out drawing software for "
793 "illustrations. These usually have some previous experience with drawing "
794 "software, like Paint Tool SAI or Photoshop, but need to be introduced to "
795 "possibilities in :program:`Krita`. This group's strength is that they share "
796 "a lot of information with each other like tips and tricks and tutorials."
797 msgstr ""
798 "学生群体，尤其是那些正在尝试各种不同绘画软件的高中生和大学生。他们一般对绘画"
799 "软件并不陌生，可能已经用过 Paint Tool SAI 或 Photoshop 等软件，但对 :program:"
800 "`Krita` 的用法并不熟悉。这个群体的优势在于他们会积极地探讨问题，分享知识，如"
801 "绘画技巧和教程等。"
802
803 #: ../../contributors_manual/krita_manual_readme.rst:286
804 msgid ""
805 "Professionals, people who earn their money with digital drawing software. "
806 "The strength of this group is that they have a lot of know-how and are "
807 "willing to donate to improve the program. These come in two types:"
808 msgstr ""
809 "从业人员，这些人使用绘画软件谋生。这个群体的优势是他们具备丰富的行业经验，具"
810 "备一定的经济能力，更有可能为了 Krita 的发展提供捐款。他们又可以被进一步细分为"
811 "两类："
812
813 #: ../../contributors_manual/krita_manual_readme.rst:288
814 msgid ""
815 "Non technical professionals. These are people who do not really grasp the "
816 "more mathematical bits of a piece of software, but have developed solid "
817 "workflows over the years and work with software using their finely honed "
818 "instincts. These tend to be illustrators, painters and people working with "
819 "print."
820 msgstr ""
821 "非技术性从业人员。这些人不一定能理解软件里面比较数学化的部分，不过他们在长年"
822 "累月与软件打交道的过程里磨练出了敏锐的直觉，建立了可靠的工作流程。他们大多是"
823 "画师和负责印刷环节的人员。"
824
825 #: ../../contributors_manual/krita_manual_readme.rst:289
826 msgid ""
827 "Technical professionals. These are people who use :program:`Krita` as part "
828 "of a pipeline, and care about the precise maths and pixel pushing. These "
829 "tend to be people working in the games and VFX industry, but occasionally "
830 "there's a scientist in there as well."
831 msgstr ""
832 "技术性从业人员。他们把 :program:`Krita` 部署在工作流水线的一个环节，往往会更"
833 "加关注色彩运算的精确性和像素信息的处理方式。他们大多供职于游戏和电影特效行"
834 "业，但我们有时也会发现科研人员的身影。"
835
836 #: ../../contributors_manual/krita_manual_readme.rst:291
837 msgid ""
838 "Adult and elderly hobbyists. This group doesn't know much about computers, "
839 "and they always seem to get snagged on that one little step missing from a "
840 "tutorial. Their strength as a group is that they adapt unconventional "
841 "workflows from real life that the student wouldn't know about and the "
842 "professional has no time for and create cool stuff with that, as well as "
843 "that they have a tempering effect on the first group in the larger community."
844 msgstr ""
845 "绘画爱好者，尤其是未经系统培训的成年和老年人。他们不熟悉计算机技术，容易被教"
846 "程忽略的某个步骤给卡住。相比起欠缺人生经验的学生和无暇探索未知的从业人员，他"
847 "们的优势是可以从生活实际出发建立一套独辟蹊径的工作流程。他们在社区中还能对浮"
848 "躁的学生群体起一定的稳定作用。"
849
850 #: ../../contributors_manual/krita_manual_readme.rst:293
851 msgid "From these four groups..."
852 msgstr "在这四个群体中，我们可以发现下述情况："
853
854 #: ../../contributors_manual/krita_manual_readme.rst:295
855 msgid ""
856 "there's only one that is technical. Which is why we need the concept pages, "
857 "so that we can create a solid base to write our manual texts on top of."
858 msgstr ""
859 "只有一个群体熟悉计算机技术。因此我们必须要为其他三个群体撰写数字绘画基础知识"
860 "章节，让他们可以读懂文档的其他部分。"
861
862 #: ../../contributors_manual/krita_manual_readme.rst:296
863 msgid ""
864 "three of them likely have previous experience with software and may need "
865 "migration guides and be told how."
866 msgstr ""
867 "有三个群体很有可能已经使用过别的绘画软件。他们在改用 Krita 时可能需要一些引"
868 "导，介绍原本熟悉的功能如何在 Krita 中找到/复现。"
869
870 #: ../../contributors_manual/krita_manual_readme.rst:297
871 msgid ""
872 "two of them need to know how to get Krita to cooperate with other software."
873 msgstr "有两个群体需要学习如何配合 Krita 使用其他软件。"
874
875 #: ../../contributors_manual/krita_manual_readme.rst:298
876 msgid ""
877 "two of them have no clue what they are doing and may need to be guided "
878 "through the most basic of steps."
879 msgstr ""
880 "有两个群体严重缺乏数字绘画的经验和知识，可能需要在最基础的环节开始为他们提供"
881 "指引。"
882
883 #: ../../contributors_manual/krita_manual_readme.rst:300
884 msgid "From that we can get the following rules:"
885 msgstr "总结上面的分析，我们可以得出下列写作规范："
886
887 #: ../../contributors_manual/krita_manual_readme.rst:303
888 msgid "General Writing"
889 msgstr "文字规范"
890
891 #: ../../contributors_manual/krita_manual_readme.rst:305
892 msgid "Use American English if possible."
893 msgstr "文档原文以用美式英语为准，中文翻译以标准现代汉语为准"
894
895 #: ../../contributors_manual/krita_manual_readme.rst:306
896 msgid ""
897 "We use American English in the manual, in accordance to Krita's UI being "
898 "American English by default."
899 msgstr ""
900 "Krita 的界面默认使用美式英语，所以 Krita 的文档以美式英语为准。中文翻译以现代"
901 "汉语的书面语为准。"
902
903 #: ../../contributors_manual/krita_manual_readme.rst:307
904 msgid "Keep the language polite, but do not use academic language."
905 msgstr "避免粗俗，也要避免学究"
906
907 #: ../../contributors_manual/krita_manual_readme.rst:308
908 msgid ""
909 "As a community, we want to be welcoming to the users, so we try to avoid "
910 "language that is unwelcoming. Swearing is already not condoned by KDE, but "
911 "going to the far other end, an academic style where neither writer nor "
912 "reader is acknowledged might give the idea that the text is far more complex "
913 "than necessary, and thus scare away users."
914 msgstr ""
915 "无论是粗俗的语言还是过于学究的语言，都不是友好的语言。文档就是说明书，它应当"
916 "以尽可能友好、易懂的方式帮助 Krita 用户，而不是把他们吓跑。"
917
918 #: ../../contributors_manual/krita_manual_readme.rst:309
919 msgid "Avoid using GIFs (open for debate)"
920 msgstr "避免使用 GIF 动画"
921
922 #: ../../contributors_manual/krita_manual_readme.rst:310
923 msgid ""
924 "The reason is that people with epilepsy may be affected by fast moving "
925 "images. Similarly, GIFs can sometimes carry too much of the burden of "
926 "explanation. If you can't help but use GIFs, at the least notify the reader "
927 "of this in the introduction of the page."
928 msgstr ""
929 "癫痫患者易受快速移动的图像影响而发病。如果非得使用 GIF，或许应该在页面的导入"
930 "部分对读者进行相关提示。GIF 动图制作起来也很麻烦，而且离线文档被转换为 PDF "
931 "后 GIF 动图将失效。这并不是一个硬性要求，我们明白某些情况下动图是最好的说明方"
932 "式。我们欢迎更多人就此进一步讨论。"
933
934 #: ../../contributors_manual/krita_manual_readme.rst:312
935 msgid "Keep it translation compatible"
936 msgstr "让文章便于翻译"
937
938 #: ../../contributors_manual/krita_manual_readme.rst:312
939 msgid ""
940 "This consists of using SVG for infographics, and using the appropriate "
941 "markup for a given text."
942 msgstr "这包括在信息图中使用 SVG 图像，为文字选用合适的 Sphinx 标记等。"
943
944 #: ../../contributors_manual/krita_manual_readme.rst:315
945 msgid "Regarding photos and paintings"
946 msgstr "传统画作和照片使用规范"
947
948 #: ../../contributors_manual/krita_manual_readme.rst:317
949 msgid ""
950 "We would like to discourage photos and traditional paintings in the manual "
951 "if they are not illustrating a concept. The reason is that it is very silly "
952 "and a little dishonest to show Rembrandt's work inside the Krita GUI, when "
953 "we have so many modern works that were made in Krita. All of the "
954 "Pepper&Carrot artwork was made in Krita and the original files are "
955 "available, so when you do not have an image handy, start there. Photos "
956 "should be avoided because Krita is a painting program. Too many photos can "
957 "give the impression Krita is trying to be a solution for photo retouching, "
958 "which really isn't the focus."
959 msgstr ""
960 "我们不鼓励大家在 Krita 的文档中使用照片和传统画作，除非必须通过它们来解释某种"
961 "绘画概念。这背后的理由也很简单：使用 Krita 绘制的数字绘画作品多不胜数，又何必"
962 "非得在 Krita 的界面里祭出伦勃朗的名作进行演示？这搞不好还会被人认为我们在虚假"
963 "宣传。Pepper & Carrot 漫画是用 Krita 创作的，它们的源文件也是自由、公开的，你"
964 "可以把它们用作素材。另一方面，Krita 的定位是绘画软件，要是在文档中使用过多照"
965 "片，会给人一种 Krita 是修图软件的错觉，这并不是我们的目标。"
966
967 #: ../../contributors_manual/krita_manual_readme.rst:318
968 msgid ""
969 "Of course, we still want to show certain concepts in play in photos and "
970 "master paintings, such as glossing or indirect light. In this case, add a "
971 "caption that mentions the name of the painting or the painter, or mentions "
972 "it's a photograph."
973 msgstr ""
974 "当然，我们在介绍某些基础概念时可以用到世界名画或者照片，例如在解释厚涂法和环"
975 "境光时。在使用世界名画和照片时请为图像配上说明文字。如果是名画，请介绍作品名"
976 "称和作者。如果是照片，请注明它是一张照片。"
977
978 #: ../../contributors_manual/krita_manual_readme.rst:319
979 msgid ""
980 "Photos can still be used for photobashing and the like, but only if it's "
981 "obviously used in the context of photobashing."
982 msgstr "在照片拼接画法中我们无可避免地要用到照片，在这种情况下允许例外。"
983
984 #: ../../contributors_manual/krita_manual_readme.rst:322
985 msgid "Regarding images in general"
986 msgstr "图像使用规范"
987
988 #: ../../contributors_manual/krita_manual_readme.rst:324
989 msgid ""
990 "Avoid text in the images and use the caption instead. You can do this with "
991 "the figure directive."
992 msgstr ""
993 "避免在图像中直接嵌入文本，尽量使用配图文字。你可以用 figure 标记生成带说明文"
994 "字的图像。"
995
996 #: ../../contributors_manual/krita_manual_readme.rst:325
997 msgid ""
998 "If you do need to use text, make either an SVG, so the text inside can be "
999 "manipulated easier, or try to minimize the amount of text."
1000 msgstr ""
1001 "如果必须使用文字，请将图像制作成 SVG 格式以便于日后修改，或者将字数控制在最小"
1002 "限度。"
1003
1004 #: ../../contributors_manual/krita_manual_readme.rst:326
1005 msgid ""
1006 "Try to make your images high quality/cute. Let's give people the idea that "
1007 "they are using a program for drawing!"
1008 msgstr "文档的配图应该尽可能画得好看，毕竟 Krita 是一款绘画软件。"
1009
1010 #: ../../contributors_manual/krita_manual_readme.rst:327
1011 msgid ""
1012 "Remember that the manual is licensed under GDPL 1.3, so images submitted "
1013 "will be licensed under that. In the case of CC-By-Sa/CC-By ensure that the "
1014 "file gets attributed appropriately through a figure caption. Needless to "
1015 "say, don't submit images that cannot be licensed under either license."
1016 msgstr ""
1017 "请切记：Krita 的全套文档是在 GFDL 1.3 许可证下发布的，它包含的图像也是如此。"
1018 "如果使用的图像是在 CC-BY-SA/CC-BY 许可证下进行授权的，必须用 figure 标记为它"
1019 "们的作者进行署名。切勿使用那些无法通过上述许可证发布的图像。"
1020
1021 #: ../../contributors_manual/krita_manual_readme.rst:330
1022 msgid "Protocol"
1023 msgstr "写作流程"
1024
1025 #: ../../contributors_manual/krita_manual_readme.rst:332
1026 msgid "So here we line out all the boring workflows."
1027 msgstr "下面我们会介绍 Krita 文档的写作流程。"
1028
1029 #: ../../contributors_manual/krita_manual_readme.rst:335
1030 msgid "Tagging and Branches"
1031 msgstr "标记和分支"
1032
1033 #: ../../contributors_manual/krita_manual_readme.rst:337
1034 msgid "Adding and removing text will be done in the ``draft`` branch."
1035 msgstr "Krita 文档的增删作业在 ``draft`` branch 中进行。"
1036
1037 #: ../../contributors_manual/krita_manual_readme.rst:339
1038 msgid ""
1039 "Proofreading results for old pages will be considered as bugfixes and thus "
1040 "will go into the ``master`` branch and merged into the ``draft`` branch as "
1041 "necessary."
1042 msgstr ""
1043 "对已有页面进行的审校将被视作一次缺陷修复，因此它会被 push 到 ``master`` "
1044 "branch ，然后再按需 merge 到 ``draft`` 分支。"
1045
1046 #: ../../contributors_manual/krita_manual_readme.rst:341
1047 msgid "Before the ``draft`` branch is merged for a given release:"
1048 msgstr "每次 ``draft`` branch 被 merge 到一个新正式版文档之前："
1049
1050 #: ../../contributors_manual/krita_manual_readme.rst:343
1051 msgid "The master branch will be tagged with the old version."
1052 msgstr "当前 master branch 会被标记为旧版文档。"
1053
1054 #: ../../contributors_manual/krita_manual_readme.rst:344
1055 msgid ""
1056 "The draft branch is first double checked that it has updated version number "
1057 "and updated epub cover."
1058 msgstr "检查当前 draft branch 是否更新了版本号和新版 epub 封面图。"
1059
1060 #: ../../contributors_manual/krita_manual_readme.rst:346
1061 msgid ""
1062 "The ``draft`` branch will not be merged until the day before a release to "
1063 "keep the pages intact for long enough."
1064 msgstr ""
1065 "当前 ``draft`` branch 直到新正式版文档发布的前一天才会被 merge ，这是为了尽可"
1066 "能保持全套文档的一致性。"
1067
1068 #: ../../contributors_manual/krita_manual_readme.rst:348
1069 msgid ""
1070 "Each release will have a version of the epub uploaded as part of the release "
1071 "process. .. Where do we get the POT files from? Even the translated versions?"
1072 msgstr "新版的 epub 文件也要随新版文档一起上传。"
1073
1074 #: ../../contributors_manual/krita_manual_readme.rst:352
1075 msgid "Removing Pages"
1076 msgstr "移除页面"
1077
1078 #: ../../contributors_manual/krita_manual_readme.rst:354
1079 msgid "If a feature is removed in a certain version, the corresponding pages:"
1080 msgstr "如果 Krita 软件的某项特性在新版中被移除了，它的文档页面要如下处理："
1081
1082 #: ../../contributors_manual/krita_manual_readme.rst:356
1083 msgid "Will first be marked deprecated."
1084 msgstr "标记相关页面为“已废弃”。"
1085
1086 #: ../../contributors_manual/krita_manual_readme.rst:358
1087 msgid "This can be done as so::"
1088 msgstr "在文档的源文件中加入以下 Sphinx 标记::"
1089
1090 #: ../../contributors_manual/krita_manual_readme.rst:360
1091 msgid ""
1092 ".. deprecated:: version number\n"
1093 "\n"
1094 " Text to indicate what the user should do without this feature."
1095 msgstr ""
1096 ".. deprecated:: 版本号\n"
1097 "\n"
1098 " 文字说明，告诉用户在失去此特性后该怎么办。"
1099
1100 #: ../../contributors_manual/krita_manual_readme.rst:364
1101 msgid "Will be linked on a page called 'deprecated'"
1102 msgstr "该页面的链接将在“已废弃”页面中列出。"
1103
1104 #: ../../contributors_manual/krita_manual_readme.rst:365
1105 msgid ""
1106 "If the next version rolls around, all the pages linked in the deprecated "
1107 "section will be removed."
1108 msgstr ""
1109 "如果 Krita 软件在下一大版本中维持此废弃决定，已废弃章节所链接的页面将会被移"
1110 "除。"
1111
1112 #: ../../contributors_manual/krita_manual_readme.rst:368
1113 msgid "Adding Pages"
1114 msgstr "新增页面"
1115
1116 #: ../../contributors_manual/krita_manual_readme.rst:370
1117 msgid "Ensure that it is located in the right place."
1118 msgstr "确保把新页面添加到正确的位置。"
1119
1120 #: ../../contributors_manual/krita_manual_readme.rst:371
1121 msgid ""
1122 "Follow the :ref:`krita_markup_conventions` to ensure the page is formatted "
1123 "correctly."
1124 msgstr ""
1125 "按照 :ref:`krita_markup_conventions` 的规范撰写页面，确保标记格式无误。"
1126
1127 #: ../../contributors_manual/krita_manual_readme.rst:372
1128 msgid "Add the page to the TOC."
1129 msgstr "将新页面添加到目录。"
1130
1131 #: ../../contributors_manual/krita_manual_readme.rst:373
1132 msgid "If the feature is new, add in versionadded::"
1133 msgstr ""
1134 "如果新页面介绍了某项新特性，请将它首次出现的 Krita 版本用 versionadded 进行标"
1135 "记::"
1136
1137 #: ../../contributors_manual/krita_manual_readme.rst:375
1138 msgid ""
1139 ".. versionadded:: version number\n"
1140 "\n"
1141 " optional something or the other."
1142 msgstr ""
1143 ".. versionadded:: 版本号\n"
1144 " 可选的文字描述。"
1145
1146 #: ../../contributors_manual/krita_manual_readme.rst:379
1147 msgid ""
1148 "As with images, don't add text that you do not have permission to add. This "
1149 "means that text is either written by you, or you have permission to port it "
1150 "from the original author. The manual is GDPL 1.3+ so the text will be "
1151 "relicensed under that."
1152 msgstr ""
1153 "与图像的使用规范一样，页面中的文字也必须有合适的授权。文字要么是你的原创作"
1154 "品，要么得到了原作者的许可。Krita 的全套文档在 GFDL 1.3+ 许可证下发布，它所含"
1155 "的所有文字也必须能够在该许可证下重新发布。"
1156
1157 #: ../../contributors_manual/krita_manual_readme.rst:383
1158 msgid "Changing Pages"
1159 msgstr "修改页面"
1160
1161 #: ../../contributors_manual/krita_manual_readme.rst:385
1162 msgid ""
1163 "If you fully rewrite a page, as opposed to proofreading it, the resulting "
1164 "page should be reviewed."
1165 msgstr ""
1166 "如果你完全重写了某个页面，而不是单纯地进行审校，你应该将重写后的页面提交审"
1167 "核。"
1168
1169 #: ../../contributors_manual/krita_manual_readme.rst:387
1170 msgid ""
1171 "If you change a page because a feature has changed, and you have commit "
1172 "access, the change can be pushed without review (unless you feel more "
1173 "comfortable with a review), but you should add::"
1174 msgstr ""
1175 "如果你根据软件特性的变化修改了页面内容，而且你拥有 commit 权限，那么你可以直"
1176 "接 push 修改后的页面，无需提交审核 (除非你认为有这个必要)。不过你要在页面中加"
1177 "入以下标记::"
1178
1179 #: ../../contributors_manual/krita_manual_readme.rst:389
1180 msgid ""
1181 ".. versionchanged:: version number\n"
1182 "\n"
1183 " This and that changed."
1184 msgstr ""
1185 ".. versionchanged:: 版本号\n"
1186 " 说明被改动的内容。"
1187
1188 #: ../../contributors_manual/krita_manual_readme.rst:393
1189 msgid ""
1190 "In all cases, check if you want to add yourself to the author field in the "
1191 "metadata section on top."
1192 msgstr ""
1193 "页面顶部的元数据区含有用于记录作者的 author 标签，请自由选择是否加入你的名"
1194 "字。"
1195
1196 #: ../../contributors_manual/krita_manual_readme.rst:395
1197 msgid ""
1198 "Using deprecated, versionadded and versionchanged with the version number "
1199 "allows us to easily search the manual for these terms with grep:"
1200 msgstr ""
1201 "带有 deprecated、versionadded 或者 versionchanged 等标记和版本号的页面可以通"
1202 "过 grep 命令来进行查找："
1203
1204 #: ../../contributors_manual/krita_manual_readme.rst:400
1205 msgid "grep -d recurse versionadded * --exclude-dir={_build,locale}"
1206 msgstr "grep -d recurse versionadded * --exclude-dir={_build,locale}"
1207
1208 #: ../../contributors_manual/krita_manual_readme.rst:402
1209 msgid "Faulty pages"
1210 msgstr "报告文档页面缺陷"
1211
1212 #: ../../contributors_manual/krita_manual_readme.rst:404
1213 msgid "If a page slips through the cracks, either..."
1214 msgstr "如果你发现某个页面的内容存在问题，请通过下述方式来进行报告："
1215
1216 #: ../../contributors_manual/krita_manual_readme.rst:406
1217 msgid "Make a merge request per the :ref:`making_changes_sphinx` section."
1218 msgstr "按照 :ref:`making_changes_sphinx` 一节的指引创建一个 merge request 。"
1219
1220 #: ../../contributors_manual/krita_manual_readme.rst:407
1221 msgid "Make a task at the `Manual Project Workboard`_."
1222 msgstr "在 Phabricator 网站的 `Manual Project Workboard`_ 中创建一个 task 。"
1223
1224 #: ../../contributors_manual/krita_manual_readme.rst:408
1225 msgid ""
1226 "Make a bug at `bugzilla`_ under the project Krita in the section "
1227 "'documentation'."
1228 msgstr ""
1229 "在 `bugzilla`_ 的 Krita 项目的“documentation (文档)”组件处提交程序缺陷报告。"
1230
1231 #: ../../contributors_manual/krita_manual_readme.rst:411
1232 msgid "Proofreading"
1233 msgstr "审校工作"
1234
1235 #: ../../contributors_manual/krita_manual_readme.rst:413
1236 msgid "There are two types of proofreading that needs to be done."
1237 msgstr ""
1238 "我们需要做两种审校工作：一、审核其他人的某次改动；二、审核某个文档页面的整体"
1239 "状况。"
1240
1241 #: ../../contributors_manual/krita_manual_readme.rst:415
1242 msgid ""
1243 "The most important one is **reviewing changes people make**. You can do this "
1244 "on `KDE_gitlab`_ in two ways:"
1245 msgstr ""
1246 "第一种，也是平时最主要的审核工作就是 **审核其他人的单次改动**。你可以在 "
1247 "`KDE_gitlab`_ 网站通过下述两种方式对改动进行审核："
1248
1249 #: ../../contributors_manual/krita_manual_readme.rst:417
1250 msgid "Reviewing merge requests"
1251 msgstr "审核其他人提交的 merge request"
1252
1253 #: ../../contributors_manual/krita_manual_readme.rst:419
1254 msgid ""
1255 "You can help review merge requests. Request reviewing is usually done by "
1256 "programmers to find mistakes in each other's code, but because programming "
1257 "code is text based just like regular text, we can use this to check against "
1258 "typos as well!"
1259 msgstr ""
1260 "你可以协助审核人们提交的 merge request。merge request 审核的初衷是让程序员可"
1261 "以互相发现代码中的错误。Krita 文档的源文件和程序的源代码一样是纯文本，所以我"
1262 "们可以像程序员那样来检查 Krita 文档中存在的问题。"
1263
1264 #: ../../contributors_manual/krita_manual_readme.rst:421
1265 msgid ""
1266 "A merge request, is an amount of changes done in a document (added, removed) "
1267 "put into a machine readable file. When someone submits a review request (on "
1268 "system like gitlab or github this is a merge or pull request), people who "
1269 "maintain the original files will have to look them over and can make "
1270 "comments about things needing to change. This allows them to comment on "
1271 "things like typos, over-complicated writing but also things that are "
1272 "incorrect. After a patch has been accepted it can be pushed into the version "
1273 "control system."
1274 msgstr ""
1275 "一个 merge request 记录了某个文件发生的全部变化 (包括内容的增删)，它被保存为"
1276 "计算机能够读取的格式。 当有人提交了一个 merge request (在 gitlab 和 github 系"
1277 "统里叫做 merge 或者 pull request) 时，负责维护原始文件的人员要检查发生的改"
1278 "动。如果这些改动需要进一步修改，他们还要为此撰写评语，如拼写错误、文风不端，"
1279 "信息错误等。一个 merge request 的 patch 只有在被审核人员接受后，才可以被 "
1280 "push 到 Krita 文档源代码库对应的 branch 中。"
1281
1282 #: ../../contributors_manual/krita_manual_readme.rst:423
1283 msgid "Commenting on changes in the manual."
1284 msgstr "给 Krita 文档的改动撰写评语"
1285
1286 #: ../../contributors_manual/krita_manual_readme.rst:425
1287 msgid ""
1288 "Commenting changes happens after the fact. You can comment on a change by "
1289 "going to the commit message (from the repository page, go to history and "
1290 "then click on an entry), where you will be able to make comments on the "
1291 "changes made."
1292 msgstr ""
1293 "这里指的是在文档改动被提交后撰写的评语。请前往某次文档改动的 commit message "
1294 "(在 repository 页面，前往 history 然后点击其中一项)，在那里你可以针对此次改动"
1295 "撰写评语。"
1296
1297 #: ../../contributors_manual/krita_manual_readme.rst:427
1298 msgid ""
1299 "In both cases, the interface consists of the difference being shown, with on "
1300 "the left the old version, and on the right the new version. Lines that have "
1301 "been added will be marked in green while lines that have been removed will "
1302 "be marked with red. You can click a speech bubble icon to add an 'inline' "
1303 "comment."
1304 msgstr ""
1305 "在上述两种情况中，网站的界面都会显示修改前后版本的区别。左栏显示旧版内容，右"
1306 "栏显示新版内容。新增的行标记为绿色，被删除的行显示成红色。你可以点击对话泡泡"
1307 "图标，添加一条内联评语。"
1308
1309 #: ../../contributors_manual/krita_manual_readme.rst:429
1310 msgid ""
1311 "The second major way the manual needs to be proofread is **over the whole "
1312 "file**. Many of the pages have only been checked for correctness but not for "
1313 "style and grammar."
1314 msgstr ""
1315 "第二种审校工作是 **针对整个页面** 进行的。一个页面没有检查出拼写和语法错误，"
1316 "不代表它的文字就一定流畅，文风就一定合适。整体审校可以改进这些问题。"
1317
1318 #: ../../contributors_manual/krita_manual_readme.rst:431
1319 msgid ""
1320 "For this you will need to follow the :ref:`making_changes_sphinx` section, "
1321 "so that you can have full access to the pages and edit them."
1322 msgstr ""
1323 "要进行整页审校，请参考 :ref:`making_changes_sphinx` 一节的说明，获取页面的完"
1324 "整访问权限以进行编辑。"
1325
1326 #: ../../contributors_manual/krita_manual_readme.rst:434
1327 msgid "Translating"
1328 msgstr "翻译工作"
1329
1330 #: ../../contributors_manual/krita_manual_readme.rst:436
1331 msgid ""
1332 "Translation of the manual is handled by the `KDE localization community "
1333 "<https://l10n.kde.org/>`_. To join the translation effort, go to the "
1334 "localization site, select the list of `translation teams <https://l10n.kde."
1335 "org/teams-list.php>`_, select the language you wish to translate for, and "
1336 "follow the instructions on the team page to get in contact with fellow "
1337 "translators."
1338 msgstr ""
1339 "Krita 是 KDE 社区 的一个子项目，它的翻译是各种语言的 `KDE 本地化小组 "
1340 "<https://l10n.kde.org/>`_ 组织进行的。要参加 Krita 的中文翻译工作，请访问 "
1341 "`Krita 中文翻译参与指南 <https://krita.org/zh/get-involved-zh/krita-chinese-"
1342 "translation/>`_ 页面。你也可以加入 Krita 的开发团队，指出或者改正那些妨碍翻译"
1343 "工作的代码，让 Krita 项目的文字在任何一种语言下面都能保持自然流畅。"
1344
1345 #: ../../contributors_manual/krita_manual_readme.rst:438
1346 msgid ""
1347 "Please refer to https://community.kde.org/Get_Involved/translation for more "
1348 "general instructions on getting involved in KDE localization."
1349 msgstr ""
1350 "请访问 https://community.kde.org/Get_Involved/translation 网站获取如何加入 "
1351 "KDE 本地化 (翻译) 工作的信息。"
1352
1353 #: ../../contributors_manual/krita_manual_readme.rst:440
1354 msgid ""
1355 "The localization team has access to the PO files for this manual, which is a "
1356 "file type used by translation programs like POEdit and Lokalize. A "
1357 "translation team is able to work together on translating these files and "
1358 "uploading them to the translations SVN. A special script will then take the "
1359 "translations from the SVN and bring them to the manual section to be "
1360 "incorporated on a daily basis."
1361 msgstr ""
1362 "KDE 本地化小组成员有权限访问 Krita 文档的 PO 文件。PO 文件是一种专门用于翻译"
1363 "的文件格式，可用 POEdit 和 Lokalize 等程序打开。各个本地化小组的任务是翻译这"
1364 "些 PO 文件，然后上传至 KDE Translation 项目的 SVN 系统。SVN 配有专门的脚本，"
1365 "它每天都会将最新的 PO 文件同步到 Krita 的文档网站。"
1366
1367 #: ../../contributors_manual/krita_manual_readme.rst:442
1368 msgid ""
1369 "Images can be translated if a translation team wants to provide their own "
1370 "images. All images in the image folder are by default for 'en'. When you "
1371 "want to translate a specific image, go into that folder and add another "
1372 "folder with your language code to add in the translated versions of images. "
1373 "So Sphinx will search for a dutch version of :file:`/images/Pixels-"
1374 "brushstroke.png` at :file:`/images/nl/Pixels-brushstroke.png` and for a "
1375 "dutch version of :file:`/images/dockers/Krita-tutorial2-I.1-2.png` in :file:"
1376 "`/images/dockers/nl/Krita-tutorial2-I.1-2.png`."
1377 msgstr ""
1378 "图像也是可以被翻译的，但翻译人员必须自行制作翻译后的图像版本。在 Krita 文档源"
1379 "文件的 image 文件夹中，所有图像的语言都默认为“en”(英语)。如果你要翻译某张图"
1380 "像，请在 image 文件夹中添加一个以你的语言代码命名的文件夹 (简体中文为 "
1381 "zh_CN)，然后把翻译后的图像文件放到里面。例如：Sphinx 会把 :file:`/images/"
1382 "Pixels-brushstroke.png` 的荷语版本定位到 :file:`/images/nl/Pixels-"
1383 "brushstroke.png` ；把 :file:`/images/dockers/Krita-tutorial2-I.1-2.png` 的荷"
1384 "语版本定位到 :file:`/images/dockers/nl/Krita-tutorial2-I.1-2.png` 。"
1385
1386 #: ../../contributors_manual/krita_manual_readme.rst:444
1387 msgid ""
1388 "Finished translations also need to be added to the build script to show up "
1389 "online. Translator teams which are confident in the state of their "
1390 "translation should contact the main Krita team via the kimageshop "
1391 "mailinglist(kimages[email protected]), or [email protected], to accomplish this."
1392 msgstr ""
1393 "翻译的成果还需要被添加到编译脚本，完成编译后才能在网上显示。如果某个本地化小"
1394 "组需要编译他们的最新翻译，请通过 kimageshop 邮件列表 ([email protected]) 或"
1395 "者电邮地址 [email protected] 联系 Krita 核心团队协助处理。"
1396
1397 #: ../../contributors_manual/krita_manual_readme.rst:447
1398 msgid "Other"
1399 msgstr "更多信息"
1400
1401 #: ../../contributors_manual/krita_manual_readme.rst:449
1402 msgid ""
1403 "For restructured text conventions, check :ref:`krita_markup_conventions`."
1404 msgstr ""
1405 "如需了解 restructured 标记的使用范例，请查阅 :ref:"
1406 "`krita_markup_conventions` 。"