Merge lp:~littlergirl/kubuntu-docs/bugs into lp:kubuntu-docs/precise

Proposed by Little Girl
Status: Merged
Merged at revision: 266
Proposed branch: lp:~littlergirl/kubuntu-docs/bugs
Merge into: lp:kubuntu-docs/precise
Diff against target: 1052 lines (+262/-214)
2 files modified
docs/audio/C/audio.xml (+47/-45)
docs/bugs/C/bugs.xml (+215/-169)
To merge this branch: bzr merge lp:~littlergirl/kubuntu-docs/bugs
Reviewer Review Type Date Requested Status
Ubuntu Documentation Committers Pending
Review via email: mp+98783@code.launchpad.net

Description of the change

* Added a couple of entities.
* Fixed some grammar.
* Fixed some punctuation.
* Fixed some tags.
* Rewrapped some lines.

To post a comment you must log in.

Preview Diff

[H/L] Next/Prev Comment, [J/K] Next/Prev File, [N/P] Next/Prev Hunk
1=== modified file 'docs/audio/C/audio.xml'
2--- docs/audio/C/audio.xml 2011-12-30 16:40:04 +0000
3+++ docs/audio/C/audio.xml 2012-03-22 06:10:23 +0000
4@@ -22,20 +22,20 @@
5 <title>Playing CDs</title>
6 <para>
7 <application>Amarok</application> is the default application for playing audio
8-<acronym>CDs</acronym> in &kubuntu;. When a <acronym>CD</acronym> is inserted,
9+<acronym>CD</acronym>s in &kubuntu;. When a <acronym>CD</acronym> is inserted,
10 &kubuntu; will recognize it and display default options. To hear the content
11 with <application>Amarok</application>, select <guilabel>Play Audio CD with
12 Amarok</guilabel> and then press the <guibutton>OK</guibutton> button.
13 &kubuntu; can be configured to remember this choice every time
14 a <acronym>CD</acronym> is inserted by selecting <guilabel>Always do
15 this for this type of media</guilabel>, and pressing <guibutton>OK</guibutton>.
16-<application>Amarok</application> also offers other useful features. If connected to
17-the Internet, <application>Amarok</application> will retrieve
18+<application>Amarok</application> also offers other useful features. If
19+connected to the Internet, <application>Amarok</application> will retrieve
20 <acronym>CD</acronym> artist, title, and track data from <ulink
21 url="http://freedb.org">freedb.org</ulink>. It will also download the lyrics
22-for the current selection if they are available by choosing the
23-<guilabel>Lyrics</guilabel> tab. Other Artist information can be found on <ulink
24-url="http://www.wikipedia.org">Wikipedia</ulink> by selecting the
25+for the current selection &mdash; if they are available &mdash; by choosing the
26+<guilabel>Lyrics</guilabel> tab. Other artist information can be found on
27+<ulink url="http://www.wikipedia.org">Wikipedia</ulink> by selecting the
28 <guilabel>Artist</guilabel> tab.
29 </para>
30 </sect1>
31@@ -44,19 +44,21 @@
32 <title>Editing Audio </title>
33
34 <para>
35-For editing audio files, &kubuntu; provides <application>Sound Editor (Audacity)</application>,
36-a full-featured, free and open source software application. To use
37-<application>Sound Editor (Audacity)</application>:
38+For editing audio files, &kubuntu; provides <application>Sound Editor
39+(Audacity)</application>, a full-featured, free, and open source software
40+application. To use <application>Sound Editor (Audacity)</application>:
41 </para>
42 <procedure>
43 <step>
44 <para>
45-Install <application>Sound Editor (Audacity)</application> from the package manager (Muon)
46+Install <application>Sound Editor (Audacity)</application> from the package
47+manager (Muon).
48 </para>
49 </step>
50 <step>
51 <para>
52-Run <application>Sound Editor (Audacity)</application> by going to &menuaudacity;.
53+Run <application>Sound Editor (Audacity)</application> by going to
54+&menuaudacity;.
55 </para>
56 </step>
57 <step>
58@@ -64,8 +66,7 @@
59 Detailed instructions (including tutorials and weblinks) on using
60 <application>Sound Editor (Audacity)</application> can be found by going to
61 <menuchoice>
62-<guimenu>Help</guimenu>
63-<guisubmenu>Contents</guisubmenu>
64+<guimenu>Help</guimenu> <guisubmenu>Contents</guisubmenu>
65 </menuchoice> from within <application>Sound Editor (Audacity)</application>.
66 </para>
67 </step>
68@@ -78,7 +79,7 @@
69 <para>
70 In addition to being the default music player in &kubuntu;,
71 <application>Amarok</application> is also helpful for managing music
72-collections. Start <application>Amarok</application> by going to &menuamarok;.
73+collections. Start <application>Amarok</application> by going to &menuamarok;.
74 </para>
75 <para>
76 Another useful <application>Amarok</application> feature is the built-in ID3
77@@ -93,10 +94,11 @@
78
79 <para>
80 Another exciting <application>Amarok</application> feature is the ability to
81-play music directly from an iPod or other portable device. <application>Amarok</application> can also be
82-used to transfer music files to and from an iPod. Please refer to the <ulink
83-type="help" url="help:/amarok">Amarok Handbook</ulink> for more information on
84-transferring and managing iPod media files.
85+play music directly from an iPod or other portable device.
86+<application>Amarok</application> can also be used to transfer music files to
87+and from an iPod. Please refer to the <ulink type="help"
88+url="help:/amarok">Amarok Handbook</ulink> for more information on transferring
89+and managing iPod media files.
90 </para>
91 </sect1>
92
93@@ -105,30 +107,29 @@
94 <procedure>
95 <step>
96 <para>
97-When a blank <acronym>CD</acronym> is inserted, &kubuntu; will
98-recognize it, mount it, and then ask what to do with the <acronym>CD</acronym>.
99-Choose <guilabel>Create an audio CD with K3B</guilabel> and press
100-<guibutton>OK</guibutton>. This will open
101-<application>K3b</application>, the <acronym>CD</acronym> and
102-<acronym>DVD</acronym> Kreator, and provide various options.
103+When a blank <acronym>CD</acronym> is inserted, &kubuntu; will recognize it,
104+mount it, and then ask what to do with the <acronym>CD</acronym>. Choose
105+<guilabel>Create an audio CD with K3B</guilabel> and press
106+<guibutton>OK</guibutton>. This will open the <application>K3b</application>
107+<acronym>CD</acronym> and <acronym>DVD</acronym> creator, and provide various
108+options.
109 </para>
110 </step>
111 <step>
112 <para>
113-To start <application>K3b</application> manually, go to <guilabel>Kickoff Application
114-> Applications > Multimedia > </guilabel><application>Disk Burning (K3b)</application>.
115+To start <application>K3b</application> manually, go to &menuk3b;.
116 </para>
117 </step>
118 <step>
119 <para>
120 Select <guilabel>New Audio CD Project</guilabel> in the <guilabel>New
121-Project</guilabel> dropdown menu.
122+Project</guilabel> drop-down menu.
123 </para>
124 </step>
125 <step>
126 <para>
127 Inside <application>K3b</application>, browse and select the tracks to be
128-ripped. Then drag and drop the tracks in the white area at the bottom of the
129+ripped. Then drag and drop the tracks into the white area at the bottom of the
130 <application>K3b</application> window.
131 <mediaobject>
132 <imageobject>
133@@ -154,9 +155,10 @@
134 <itemizedlist>
135 <listitem>
136 <para>
137-<guilabel>Writing</guilabel> - provides choices related to burning an image from
138-the files selected in the previous step.
139-<note><title>No MP3 Support by Default</title>
140+<guilabel>Writing</guilabel> - provides choices related to burning an image
141+from the files selected in the previous step.
142+<note>
143+<title>No MP3 Support by Default</title>
144 <para>
145 <acronym>MP3</acronym> is a protocol restricted by patents. In order to use it
146 with <application>K3b</application>, please refer to the information at the end
147@@ -194,36 +196,36 @@
148 </step>
149 </procedure>
150 <para>
151-<application>K3b</application> can extract audio files to the following formats:
152+<application>K3b</application> can extract audio files to the following
153+formats:
154 <itemizedlist>
155 <listitem>
156 <para>
157-<emphasis role="strong">Ogg Vorbis</emphasis> - Ogg
158-Vorbis is a patent-free lossy audio compression format which usually produces
159-higher quality and greater compression than MP3. See the <ulink
160-url="http://www.vorbis.com/faq/">Vorbis website</ulink> for more information.
161+<emphasis role="strong">Ogg Vorbis</emphasis> - Ogg Vorbis is a patent-free
162+lossy audio compression format which usually produces higher quality and
163+greater compression than MP3. See the <ulink url="http://www.vorbis.com/faq/">
164+Vorbis website</ulink> for more information.
165 </para>
166 </listitem>
167 <listitem>
168 <para><emphasis role="strong">FLAC</emphasis> - The Free Lossless Audio
169-Codec, <acronym>FLAC</acronym>, can compress audio files up to 50% without removing
170-any information from the audio stream. For more information on this format, see
171-the <ulink url="http://flac.sourceforge.net/">FLAC homepage</ulink> on
172-sourceforge.net.
173+Codec, <acronym>FLAC</acronym>, can compress audio files up to 50% without
174+removing any information from the audio stream. For more information on this
175+format, see the <ulink url="http://flac.sourceforge.net/">FLAC
176+homepage</ulink> on <trademark>Sourceforge</trademark>.
177 </para>
178 </listitem>
179 <listitem>
180-<para><emphasis role="strong">WAV</emphasis> - Wav is an
181-uncompressed audio format that can be compressed into OGG Vorbis or a codec of
182-your choice. It is often edited in applications such as Audacity before being
183-compressed.
184+<para><emphasis role="strong">WAV</emphasis> - Wav is an uncompressed audio
185+format that can be compressed into OGG Vorbis or a codec of your choice. It is
186+often edited in applications such as Audacity before being compressed.
187 </para>
188 </listitem>
189 </itemizedlist>
190 </para>
191 <para>
192 CD audio files can be extracted to the proprietary, non-free
193-<emphasis role="strong">MP3</emphasis> lossy format by using the
194+<emphasis role="strong">MP3</emphasis> lossy format by using the
195 <application>lame</application> encoder. Please refer to the <ulink type="help"
196 url="help:/kubuntu/add-applications/">Adding Applications</ulink> documentation
197 for help with installing applications such as <application>lame</application>.
198
199=== modified file 'docs/bugs/C/bugs.xml'
200--- docs/bugs/C/bugs.xml 2011-09-15 05:13:39 +0000
201+++ docs/bugs/C/bugs.xml 2012-03-22 06:10:23 +0000
202@@ -28,8 +28,8 @@
203 <varlistentry><term>Crash</term>
204 <listitem>
205 <para>
206-An application or system crash or failure. Most of the time, a crash dialog will
207-be presented that can be turned into a bug report.
208+An application or system crash or failure. Most of the time a crash dialog will
209+be presented. This can be turned into a bug report.
210 </para>
211 </listitem>
212 </varlistentry>
213@@ -59,19 +59,25 @@
214 <title>KDE's Bug Tracking System</title>
215 <para><ulink url="https://bugs.kde.org/"/></para>
216 <para>
217-KDE uses Bugzilla, a &quot;Defect Tracking System&quot;. Bugzilla is one of the
218-most popular tools used in the open source development community.
219+<trademark>KDE</trademark> uses <trademark>Bugzilla</trademark>, a
220+<quote>Defect Tracking System</quote>. <trademark>Bugzilla</trademark> is one
221+of the most popular tools used in the open source development community.
222 </para>
223 <note><title>Register first</title>
224 <para>
225-To report a bug, one must register for an account on KDE's Bugzilla
226-at <ulink url="https://bugs.kde.org/createaccount.cgi"/>. A valid email address
227-is required for registration.
228+To report a bug, one must register for an account on
229+<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark> at <ulink
230+url="https://bugs.kde.org/createaccount.cgi"/>. A valid email address is
231+required for registration.
232 </para>
233 </note>
234 <note><title>Only for KDE bugs</title>
235 <para>
236-Bugzilla is only for KDE bugs. If the application is not part of KDE, for instance Firefox, LibreOffice, or VLC, then the report should be filed in Launchpad instead. Please see the next section, which covers filing reports concerning Launchpad.
237+<trademark>Bugzilla</trademark> is only for <trademark>KDE</trademark> bugs. If
238+the application is not part of <trademark>KDE</trademark> &mdash; Firefox,
239+LibreOffice, or VLC, for instance &mdash; then the report should be filed in
240+Launchpad instead. Please see the next section, which covers filing reports
241+concerning Launchpad.
242 </para>
243 </note>
244 </sect2>
245@@ -79,22 +85,24 @@
246 <title>Launchpad</title>
247 <para><ulink url="https://launchpad.net/"/></para>
248 <para>
249-Launchpad is an open source suite of tools that help people and teams to work
250-together on software projects. Launchpad is used by the Ubuntu and &kubuntu;
251-Projects, as well as various other open source projects.
252+<trademark>Launchpad</trademark> is an open source suite of tools that help
253+people and teams to work together on software projects. Launchpad is used by
254+the &ubuntu; and &kubuntu; projects, as well as various other open source
255+projects.
256 </para>
257 <note><title>Register first</title>
258 <para>
259-To report a bug, one must register for a Launchpad account at
260-<ulink url="https://launchpad.net/+login"/>. A valid email address is required
261-for registration.
262+To report a bug, one must register for a <trademark>Launchpad</trademark>
263+account at <ulink url="https://launchpad.net/+login"/>. A valid email address
264+is required for registration.
265 </para>
266 </note>
267 <note><title>For any bug in &kubuntu;</title>
268 <para>
269-Launchpad can be used to file a bug report for any application available in the
270-Ubuntu or &kubuntu; repositories. For KDE applications, the
271-KDE Bug Tracking system (above) is preferred.
272+<trademark>Launchpad</trademark> can be used to file a bug report for any
273+application available in the &ubuntu; or &kubuntu; repositories. For
274+<trademark>KDE</trademark> applications, the <trademark>KDE Bug
275+Tracking</trademark> system (above) is preferred.
276 </para>
277 </note>
278 </sect2>
279@@ -104,18 +112,19 @@
280 <title>Filing a Crash Report</title>
281 <para>
282 When an application crashes in &kubuntu;, the appropriate crash dialog will
283-appear. It is usually easy to file a bug report from the dialog. With a KDE
284-application, the KDE crash dialog will appear along with instructions
285-for reporting the bug. Otherwise, the Ubuntu crash dialog will appear with
286-instructions for filing a bug on Launchpad.
287+appear. It is usually easy to file a bug report from the dialog. With a
288+<trademark>KDE</trademark> application, the <trademark>KDE</trademark> crash
289+dialog will appear along with instructions for reporting the bug. Otherwise,
290+the &ubuntu; crash dialog will appear with instructions for filing a bug on
291+<trademark>Launchpad</trademark>.
292 </para>
293 <sect2 id="filing-crash-kde">
294 <title>KDE</title>
295 <para>
296-When an application crashes in KDE, a crash dialog will be presented that is
297-similar to the following images. The first image shows the
298-<guilabel>General</guilabel> tab which provides an overview of the crash. The
299-second image shows the <guilabel>Developer Information</guilabel> tab which
300+When an application crashes in <trademark>KDE</trademark>, a crash dialog will
301+be presented that is similar to the following images. The first image shows the
302+<guilabel>General</guilabel> tab, which provides an overview of the crash. The
303+second image shows the <guilabel>Developer Information</guilabel> tab, which
304 provides trace information that is useful to developers.
305 </para>
306 <para>
307@@ -139,10 +148,10 @@
308 </example>
309 </para>
310 <para>
311-If the trace information is deemed valuable, filing a bug report is
312-easy with the crash dialog wizard. If the trace is not deemed valuable, then it
313-is not possible to file a bug report with the wizard. The bug report can still
314-be filed manually at <ulink url="https://bugs.kde.org/"/>.
315+If the trace information is deemed valuable, filing a bug report is easy with
316+the crash dialog wizard. If the trace is not deemed valuable, then it is not
317+possible to file a bug report with the wizard. The bug report can still be
318+filed manually at <ulink url="https://bugs.kde.org/"/>.
319 </para>
320 <para>
321 To complete the bug reporting process, follow the procedure below.
322@@ -151,14 +160,15 @@
323 <step>
324 <para>
325 <mousebutton>Click</mousebutton> the <guibutton>Report Bug</guibutton> button.
326-The following dialog will appear.
327+The following dialog will appear:
328 </para>
329 <para>
330 <example>
331 <title>Welcome to the Reporting Assistant</title>
332 <mediaobject>
333 <imageobject>
334-<imagedata fileref="help:/images/C/crash_report_assistant_welcome.png" format="PNG"/>
335+<imagedata
336+fileref="help:/images/C/crash_report_assistant_welcome.png" format="PNG"/>
337 </imageobject>
338 </mediaobject>
339 </example>
340@@ -167,14 +177,15 @@
341 <step>
342 <para>
343 <mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The
344-following dialog will appear.
345+following dialog will appear:
346 </para>
347 <para>
348 <example>
349 <title>What do you know about the crash?</title>
350 <mediaobject>
351 <imageobject>
352-<imagedata fileref="help:/images/C/crash_report_assistant_about_crash.png" format="PNG"/>
353+<imagedata
354+fileref="help:/images/C/crash_report_assistant_about_crash.png" format="PNG"/>
355 </imageobject>
356 </mediaobject>
357 </example>
358@@ -183,15 +194,17 @@
359 <step>
360 <para>
361 Select the applicable options. The drop-down box under the question,
362-&quot;<guilabel>Does the application crash again if you repeat the
363-same situation?</guilabel>&quot; has several options.
364+<quote><guilabel>Does the application crash again if you repeat the
365+same situation?</guilabel></quote> has several options.
366 </para>
367 <para>
368 <example>
369 <title>Does the application crash again if you repeat the same situation?</title>
370 <mediaobject>
371 <imageobject>
372-<imagedata fileref="help:/images/C/crash_report_assistant_about_crash_dropdown.png" format="PNG"/>
373+<imagedata
374+fileref="help:/images/C/crash_report_assistant_about_crash_dropdown.png"
375+format="PNG"/>
376 </imageobject>
377 </mediaobject>
378 </example>
379@@ -205,18 +218,21 @@
380 </step>
381 <step>
382 <para>
383-Depending on the information available in the crash report, either of two
384+Depending on the information available in the crash report, either of two
385 dialogs will appear. One is a dialog that indicates that there is not enough
386 information to file a good report. The other is a dialog indicating that the
387-information is useful, and that it would be helpful to continue with filing the
388+information is useful and that it would be helpful to continue with filing the
389 report.
390 </para>
391 <para>
392 <example>
393-<title>Not enough information for developers to continue the reporting process</title>
394+<title>Not enough information for developers to continue the reporting
395+process</title>
396 <mediaobject>
397 <imageobject>
398-<imagedata fileref="help:/images/C/crash_report_assistant_not_enough_info.png" format="PNG"/>
399+<imagedata
400+fileref="help:/images/C/crash_report_assistant_not_enough_info.png"
401+format="PNG"/>
402 </imageobject>
403 </mediaobject>
404 </example>
405@@ -226,7 +242,9 @@
406 <title>This crash information is useful</title>
407 <mediaobject>
408 <imageobject>
409-<imagedata fileref="help:/images/C/crash_report_assistant_useful_information.png" format="PNG"/>
410+<imagedata
411+fileref="help:/images/C/crash_report_assistant_useful_information.png"
412+format="PNG"/>
413 </imageobject>
414 </mediaobject>
415 </example>
416@@ -235,7 +253,7 @@
417 <para>
418 It may be necessary to install the proper debug packages in order to get a good
419 trace. Such packages include <filename>kdebase-dbg</filename>,
420-<filename>kdebase-workspace-dbg</filename>,
421+<filename>kdebase-workspace-dbg</filename>, and
422 <filename>kdebase-runtime-dbg</filename>.
423 </para>
424 </note>
425@@ -243,36 +261,42 @@
426 <step>
427 <para>
428 If enough information was provided to continue filing a bug report using
429-the assistant, a dialog will appear to allow logging in to KDE's Bugzilla.
430+the assistant, a dialog will appear to allow logging in to
431+<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark>.
432 </para>
433 <para>
434 <example>
435 <title>KDE Bug Tracking System Login</title>
436 <mediaobject>
437 <imageobject>
438-<imagedata fileref="help:/images/C/crash_report_assistant_bugtracker_login.png" format="PNG"/>
439+<imagedata
440+fileref="help:/images/C/crash_report_assistant_bugtracker_login.png"
441+format="PNG"/>
442 </imageobject>
443 </mediaobject>
444 </example>
445 </para>
446 <note><title>Use e-mail address as username</title>
447 <para>
448-Use the e-mail address that was used to register with KDE's Bugzilla.
449+Use the email address that was used to register with
450+<trademark>KDE</trademark>'s <trademark>Bugzilla</trademark>.
451 </para>
452 </note>
453 </step>
454 <step>
455 <para>
456-After logging in with username (e-mail address) and password,
457+After logging in with your username (email address) and password,
458 <mousebutton>click</mousebutton> the <guibutton>Login</guibutton> button. The
459-assistant will check for duplicates and display the following dialog.
460+assistant will check for duplicates and display the following dialog:
461 </para>
462 <para>
463 <example>
464 <title>Bug Report Possible Duplicates List</title>
465 <mediaobject>
466 <imageobject>
467-<imagedata fileref="help:/images/C/crash_report_assistant_possible_duplicates.png" format="PNG"/>
468+<imagedata
469+fileref="help:/images/C/crash_report_assistant_possible_duplicates.png"
470+format="PNG"/>
471 </imageobject>
472 </mediaobject>
473 </example>
474@@ -283,14 +307,17 @@
475 If there is a possible duplicate report, <mousebutton>click</mousebutton> the
476 report in the list and then <mousebutton>click</mousebutton> the <guibutton>Open
477 selected report</guibutton> button. Either of the following dialogs will be
478-presented.
479+presented:
480 </para>
481 <para>
482 <example>
483-<title>The report you selected is already marked as a duplicate of bug...</title>
484+<title>The report you selected is already marked as a duplicate of
485+bug...</title>
486 <mediaobject>
487 <imageobject>
488-<imagedata fileref="help:/images/C/crash_report_assistant_nested_duplicate_detected.png" format="PNG"/>
489+<imagedata
490+fileref="help:/images/C/crash_report_assistant_nested_duplicate_detected.png"
491+format="PNG"/>
492 </imageobject>
493 </mediaobject>
494 </example>
495@@ -300,7 +327,9 @@
496 <title>Showing the duplicate bug report you selected</title>
497 <mediaobject>
498 <imageobject>
499-<imagedata fileref="help:/images/C/crash_report_assistant_duplicate_report.png" format="PNG"/>
500+<imagedata
501+fileref="help:/images/C/crash_report_assistant_duplicate_report.png"
502+format="PNG"/>
503 </imageobject>
504 </mediaobject>
505 </example>
506@@ -313,23 +342,26 @@
507 bug report and inform the developers that it may be a duplicate. This is
508 recommended, except in cases with experienced users where it is clearly not a
509 duplicate. <mousebutton>Clicking</mousebutton> the <guibutton>Attach to this
510-report (Advanced)</guibutton> will attach the crash information to the report.
511+report (Advanced)</guibutton> button will attach the crash information to the
512+report.
513 </para>
514 <para>
515 If the bug is not a duplicate, simply <mousebutton>click</mousebutton>
516-the <guibutton>Next</guibutton> in the dialog showing the possible duplicates.
517-A dialog will appear with <guibutton>Let me check more reports</guibutton>. To
518-prevent checking for more reports and continue to file the report,
519-<mousebutton>click</mousebutton> the <guibutton>There
520-are no real duplicates</guibutton> button. A dialog will appear to enter
521-additional information concerning the report.
522+the <guibutton>Next</guibutton> button in the dialog showing the possible
523+duplicates. A dialog will appear with <guibutton>Let me check more
524+reports</guibutton>. To prevent checking for more reports and continue filing
525+the report, <mousebutton>click</mousebutton> the <guibutton>There
526+are no real duplicates</guibutton> button. A dialog will appear asking you to
527+enter additional information concerning the report.
528 </para>
529 <para>
530 <example>
531 <title>Details of the Bug Report</title>
532 <mediaobject>
533 <imageobject>
534-<imagedata fileref="help:/images/C/crash_report_assistant_report_details.png" format="PNG"/>
535+<imagedata
536+fileref="help:/images/C/crash_report_assistant_report_details.png"
537+format="PNG"/>
538 </imageobject>
539 </mediaobject>
540 </example>
541@@ -337,16 +369,18 @@
542 </step>
543 <step>
544 <para>
545-Once the details of the bug report are complete,
546-<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. The
547-following dialog will be presented.
548+Once the details of the bug report are complete,
549+<mousebutton>click</mousebutton> the <guibutton>Next</guibutton> button. The
550+following dialog will be presented:
551 </para>
552 <para>
553 <example>
554 <title>Preview Report</title>
555 <mediaobject>
556 <imageobject>
557-<imagedata fileref="help:/images/C/crash_report_assistant_report_details_preview.png" format="PNG"/>
558+<imagedata
559+fileref="help:/images/C/crash_report_assistant_report_details_preview.png"
560+format="PNG"/>
561 </imageobject>
562 </mediaobject>
563 </example>
564@@ -355,14 +389,16 @@
565 <step>
566 <para>
567 If the information looks correct, <mousebutton>click</mousebutton> the
568-<guibutton>Next</guibutton> button. The following dialog will be presented.
569+<guibutton>Next</guibutton> button. The following dialog will be presented:
570 </para>
571 <para>
572 <example>
573 <title>Send Crash Report</title>
574 <mediaobject>
575 <imageobject>
576-<imagedata fileref="help:/images/C/crash_report_assistant_report_filed.png" format="PNG"/>
577+<imagedata
578+fileref="help:/images/C/crash_report_assistant_report_filed.png"
579+format="PNG"/>
580 </imageobject>
581 </mediaobject>
582 </example>
583@@ -370,18 +406,19 @@
584 </step>
585 </procedure>
586 <para>
587-<emphasis role="bold">Congratulations on a successful bug report!</emphasis>
588-Identifying and reporting bugs are essential to improving &kubuntu; and KDE.
589-Some emails may be sent to the registered address to update progress or to
590-allow developers to get additional information about the bug.
591+<emphasis>Congratulations on a successful bug report!</emphasis> Identifying
592+and reporting bugs are essential to improving &kubuntu; and
593+<trademark>KDE</trademark>. Some emails may be sent to the registered address
594+to update progress or to allow developers to get additional information about
595+the bug.
596 </para>
597 </sect2>
598 <sect2 id="filing-crash-lp">
599 <title>Launchpad</title>
600 <para>
601-When an application that is not KDE crashes in &kubuntu;, a pop-up notification
602-will appear from <application>Apport</application> that is similar to the
603-following image.
604+When an application that is not <trademark>KDE</trademark> crashes in
605+&kubuntu;, a pop-up notification will appear from
606+<application>Apport</application> that is similar to the following image:
607 </para>
608 <para>
609 <example><title>Apport Crash Pop-pup Notification</title>
610@@ -394,11 +431,11 @@
611 </para>
612 <note><title>Crash information may be different</title>
613 <para>
614-The following screen shots were created by crashing the application
615-<application>VLC</application> deliberately. Crash dialogs associated with other
616-applications will be different. In an actual bug situation, the application
617-name, <application>VLC</application>, will be replaced by the name of the
618-application that actually crashed.
619+The screen shots below were created by crashing the application
620+<application>VLC</application> deliberately. Crash dialogs associated with
621+other applications will be different. In an actual bug situation, the
622+application name, <application>VLC</application>, will be replaced by the name
623+of the application that actually crashed.
624 </para>
625 </note>
626 <para>
627@@ -409,7 +446,7 @@
628 <para>
629 <mousebutton>Click</mousebutton> the <guibutton>Details</guibutton> buttons on
630 the <application>System Notification Helper</application>. The following dialog
631-will be presented.
632+will be presented:
633 </para>
634 <para>
635 <example>
636@@ -441,11 +478,11 @@
637 </step>
638 <step>
639 <para>
640-After all of the information concerning the crash is collected, a dialog will
641-be presented that displays the details of the report, and the report is sent to
642-the developers. <mousebutton>Click</mousebutton> the
643+After all information concerning the crash is collected, a dialog will be
644+presented that displays the details of the report, and the report is sent to
645+the developers. <mousebutton>Click</mousebutton> the
646 <guibutton>Details...</guibutton> button to view details of the report. The
647-following dialog will be presented.
648+following dialog will be presented:
649 </para>
650 <para>
651 <example><title>Send problem report to the developers? (Details)</title>
652@@ -460,8 +497,8 @@
653 <step>
654 <para>
655 <mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send
656-the report to the developers. In this case, it will send the report to
657-Launchpad. The following progress dialog will be presented.
658+the report to the developers. In this case, it will send the report to
659+<trademark>Launchpad</trademark>. The following progress dialog will be presented:
660 </para>
661 <para>
662 <example><title>Uploading problem information</title>
663@@ -476,15 +513,16 @@
664 <step>
665 <para>
666 After the progress dialog completes, the default web browser will open to
667-Launchpad presenting either the login page or the beginning of the online
668-version of the bug reporting process. After logging in (if necessary) the
669-following page will be presented.
670+<trademark>Launchpad</trademark>, presenting either the log-in page or the
671+beginning of the online version of the bug reporting process. After logging in
672+(if necessary), the following page will be presented:
673 </para>
674 <para>
675 <example><title>Please wait while bug data is processed...</title>
676 <mediaobject>
677 <imageobject>
678-<imagedata fileref="help:/images/C/apport-browser-processing.png" format="PNG"/>
679+<imagedata fileref="help:/images/C/apport-browser-processing.png"
680+format="PNG"/>
681 </imageobject>
682 </mediaobject>
683 </example>
684@@ -492,8 +530,8 @@
685 </step>
686 <step>
687 <para>
688-When Launchpad is finished processing the bug data, the following page will be
689-presented.
690+When <trademark>Launchpad</trademark> is finished processing the bug data, the
691+following page will be presented:
692 </para>
693 <para>
694 <example><title>Extra debug information will be added...</title>
695@@ -508,7 +546,7 @@
696 <step>
697 <para>
698 <mousebutton>Click</mousebutton> the <guibutton>Next</guibutton> button. The
699-following page will be presented.
700+following page will be presented:
701 </para>
702 <para>
703 <example><title>Further information</title>
704@@ -522,10 +560,10 @@
705 </step>
706 <step>
707 <para>
708-Any extra information can be filled in about the bug report such as what was
709-being done when it crashed or the online file locations that may have caused the
710-crash. The following is a brief description filed with the report in
711-this procedure.
712+Any extra information about the bug report can be filled in to describe, for
713+example, what was being done when the application crashed or the online file
714+locations that may have caused the crash. The following is a brief description
715+filed with the report in this procedure:
716 </para>
717 <para>
718 <example><title>Further information (Completed)</title>
719@@ -540,7 +578,7 @@
720 <step>
721 <para>
722 <mousebutton>Click</mousebutton> the <guibutton>Submit Bug Report</guibutton>
723-button on the bottom of the page. The following page will be presented.
724+button on the bottom of the page. The following page will be presented:
725 </para>
726 <para>
727 <example><title>Thank you for your bug report</title>
728@@ -554,10 +592,10 @@
729 </step>
730 </procedure>
731 <para>
732-<emphasis role="bold">Congratulations on making a successful crash
733-report!</emphasis>Identifying and reporting bugs are essential to improving
734-&kubuntu;. Some emails may be sent to the registered address to update progress
735-or to allow developers to get additional information about the bug.
736+<emphasis>Congratulations on making a successful crash report!</emphasis>
737+Identifying and reporting bugs are essential to improving &kubuntu;. Some
738+emails may be sent to the registered address to update progress or to allow
739+developers to get additional information about the bug.
740 </para>
741 </sect2>
742 </sect1>
743@@ -565,32 +603,33 @@
744 <sect1 id="filing-non-crash">
745 <title>Filing a Non-Crash or Regression Report</title>
746 <para>
747-If an application has regressed in functionality, a bug report should be
748-filed on that application. A regress occurs when a function worked in a previous
749-release but in the latest release, it is not working. In most cases, this type
750-of report will be filed by those who have more experience and may be testing
751-beta quality software. However there are situations where a user needs to report
752-an issue with an application that isn't working right, but isn't crashing. The
753-following procedures will help.
754+If an application has regressed in functionality, a bug report should be filed
755+on that application. A regression occurs when a function worked in a previous
756+release, but is not working in the latest release. In most cases, this type of
757+report will be filed by those who have previous experience and may be testing
758+beta quality software. There are, however, situations where a user needs to
759+report an issue with an application that isn't working right, but isn't
760+crashing. The following procedures will help:
761 </para>
762 <sect2 id="filing-non-crash-kde">
763 <title>KDE</title>
764 <para>
765-Filing non-crash related bug reports for KDE applications are done with a web
766-browser using <ulink url="https://bugs.kde.org/"/>.
767+Filing non-crash related bug reports for <trademark>KDE</trademark>
768+applications is done with a web browser using
769+<ulink url="https://bugs.kde.org/"/>.
770 </para>
771 <note><title>Register first</title>
772 <para>
773 To report a bug, one must register for an account on the bug tracker.
774-KDE's bug tracker is located at <ulink url="https://bugs.kde.org/"/>.
775+<trademark>KDE</trademark>'s bug tracker is located at <ulink
776+url="https://bugs.kde.org/"/>.
777 </para>
778 </note>
779 <procedure><title>Filing a bug report without a crash</title>
780 <step>
781 <para>
782-In a web browser, go to <ulink url="https://bugs.kde.org/"/> and either
783-create a new account or login. Once logged in, the following page will be
784-presented.
785+In a web browser, go to <ulink url="https://bugs.kde.org/"/> and either create
786+a new account or log in. Once logged in, the following page will be presented:
787 </para>
788 <para>
789 <example><title>Welcome to the KDE Bug Tracking System</title>
790@@ -605,8 +644,8 @@
791 <step>
792 <para>
793 <mousebutton>Click</mousebutton> the <guilabel>Report New Wish or Bug</guilabel>
794-link in the top-right-hand corner of the page to start the process of filing the
795-bug report. The following page will be presented.
796+link in the top right-hand corner of the page to start the process of filing
797+the bug report. The following page will be presented:
798 </para>
799 <para>
800 <example><title>Welcome to the KDE Bug Report Wizard!</title>
801@@ -620,8 +659,8 @@
802 </step>
803 <step>
804 <para>
805-<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The
806-following page will be presented.
807+<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button.
808+The following page will be presented:
809 </para>
810 <para>
811 <example><title>Software Configuration</title>
812@@ -639,7 +678,7 @@
813 <guilabel>Distribution Method</guilabel> (Should be <guilabel>Ubuntu
814 Packages</guilabel>) from the drop-down menus. <mousebutton>Click</mousebutton>
815 the <guibutton>Continue</guibutton> button when finished with the selections.
816-The following page will be presented.
817+The following page will be presented:
818 </para>
819 <para>
820 <example><title>Application Selection</title>
821@@ -660,10 +699,10 @@
822 </step>
823 <step>
824 <para>
825-Under the <guilabel>Find</guilabel> section under the
826-<guilabel>Application</guilabel> list, fill in the <guilabel>Keyword
827+Under the <guilabel>Find</guilabel> section in the
828+<guilabel>Application</guilabel> list, fill in the <guilabel>Keyword
829 Search</guilabel> text box with the application being reported. It should look
830-similar to the following image.
831+similar to the following image:
832 </para>
833 <para>
834 <example><title>Application Selection (Search for application)</title>
835@@ -681,8 +720,8 @@
836 </step>
837 <step>
838 <para>
839-<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button. The
840-following page will be presented.
841+<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button.
842+The following page will be presented:
843 </para>
844 <para>
845 <example><title>General Information</title>
846@@ -700,7 +739,7 @@
847 information similar to the example under the text box. Select
848 <guilabel>Linux</guilabel> in the <guilabel>Operating System</guilabel>
849 drop-down menu. When completed, <mousebutton>Click</mousebutton> the
850-<guibutton>Continue</guibutton> button. The following page will be presented.
851+<guibutton>Continue</guibutton> button. The following page will be presented:
852 </para>
853 <para>
854 <example><title>Check for Duplicate Bug Reports</title>
855@@ -714,12 +753,12 @@
856 </step>
857 <step>
858 <para>
859-If a duplicate report is found, click on that report ID to view the report. If
860-it is a duplicate and more information is needed, then simply enter text in the
861-large text box confirming it. If more information is not needed, nothing need
862-be entered. If no duplicate reports are found, <mousebutton>Click</mousebutton>
863-the <guibutton>Continue</guibutton> button. The following page will be
864-presented.
865+If a duplicate report is found, click on that report <acronym>ID</acronym> to
866+view the report. If it is a duplicate and more information is needed, then
867+enter text into the large text box confirming it. If more information is not
868+needed, nothing needs to be entered. If no duplicate reports are found,
869+<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button.
870+The following page will be presented:
871 </para>
872 <para>
873 <example><title>Bug Entry Form</title>
874@@ -734,11 +773,11 @@
875 <step>
876 <para>
877 The <guilabel>Severity</guilabel> (required) drop-down menu should display the
878-<guilabel>Bug - Bug report (no crashes)</guilabel> option. In the <guilabel>Long
879-Description in English</guilabel> (required) text box, enter all information
880-pertaining to the bug report. When completed, <mousebutton>Click</mousebutton>
881-the <guibutton>Continue</guibutton> button. The following page will be
882-presented.
883+<guilabel>Bug - Bug report (no crashes)</guilabel> option. In the
884+<guilabel>Long Description in English</guilabel> (required) text box, enter all
885+information pertaining to the bug report. When completed,
886+<mousebutton>Click</mousebutton> the <guibutton>Continue</guibutton> button.
887+The following page will be presented:
888 </para>
889 <para>
890 <example><title>Bug Submitted</title>
891@@ -752,27 +791,30 @@
892 </step>
893 </procedure>
894 <para>
895-<emphasis role="bold">Congratulations on making a successful non-crash related
896-bug report!</emphasis> Identifying and reporting bugs are essential to improving
897-&kubuntu; and KDE. Some emails may be sent to the registered address to update
898-progress or to allow developers to get additional information about the bug.
899+<emphasis>Congratulations on making a successful non-crash-related bug
900+report!</emphasis> Identifying and reporting bugs are essential to improving
901+&kubuntu; and <trademark>KDE</trademark>. Some emails may be sent to the
902+registered address to update progress or to allow developers to get additional
903+information about the bug.
904 </para>
905 </sect2>
906 <sect2 id="filing-non-crash-lp">
907 <title>Launchpad</title>
908 <para>
909-Filing non-crash related bug reports in non-KDE applications can be done either
910-by going to <ulink url="https://bugs.launchpad.net/ubuntu/+filebug"/> in a web
911-browser or by using the <application>Apport</application> bug reporting
912-application. The following procedure will demonstrate the use of
913-<application>Apport</application> as this is the recommended way of filing
914-Ubuntu or non-KDE related bug reports.
915+Filing non-crash-related bug reports in non-<trademark>KDE</trademark>
916+applications can be done either by going to <ulink
917+url="https://bugs.launchpad.net/ubuntu/+filebug"/> in a web browser or by using
918+the <application>Apport</application> bug reporting application. The following
919+procedure will demonstrate the use of <application>Apport</application> as this
920+is the recommended way of filing &ubuntu; or
921+non-<trademark>KDE</trademark>-related bug reports:
922 </para>
923 <procedure><title>Filing a bug report without a crash</title>
924 <step>
925 <para>
926-Open <application>KRunner</application>, the KDE run command interface, by
927-pressing <keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo>.
928+Open <application>KRunner</application>, the <trademark>KDE</trademark> run
929+command interface, by pressing
930+<keycombo><keycap>Alt</keycap><keycap>F2</keycap></keycombo>.
931 </para>
932 <para>
933 <example><title>KRunner</title>
934@@ -786,10 +828,11 @@
935 </step>
936 <step>
937 <para>
938-In the <application>KRunner</application> dialog, enter <userinput>apport-bug -p
939-PROGRAM_NAME</userinput>. Replace <emphasis>PROGRAM_NAME</emphasis> with the
940-name of the program the bug report is for. Press <keycap>Enter</keycap> when
941-complete. The following dialog will be presented.
942+In the <application>KRunner</application> dialog, enter
943+<userinput>apport-bug -p PROGRAM_NAME</userinput>. Replace
944+<emphasis>PROGRAM_NAME</emphasis> with the name of the program the bug report
945+is for. Press <keycap>Enter</keycap> when complete. The following dialog will
946+be presented:
947 </para>
948 <para>
949 <example><title>Collecting Problem Information</title>
950@@ -818,9 +861,9 @@
951 </step>
952 <step>
953 <para>
954-<mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button to
955-see details of the report to be followed. The following dialog will be
956-presented.
957+<mousebutton>Click</mousebutton> the <guibutton>Details...</guibutton> button
958+to see details of the report to be followed. The following dialog will be
959+presented:
960 </para>
961 <para>
962 <example><title>Report Details</title>
963@@ -835,7 +878,7 @@
964 <step>
965 <para>
966 <mousebutton>Click</mousebutton> the <guibutton>Send</guibutton> button to send
967-the report to the developers. The following progress dialog will be presented.
968+the report to the developers. The following progress dialog will be presented:
969 </para>
970 <para>
971 <example><title>Uploading Problem Information</title>
972@@ -850,7 +893,7 @@
973 <step>
974 <para>
975 After the information has been uploaded, the web browser will open and display
976-a page similar to the following.
977+a page similar to the following:
978 </para>
979 <para>
980 <example><title>Please wait while bug data is processed.</title>
981@@ -862,7 +905,7 @@
982 </example>
983 </para>
984 <para>
985-After the bug data is processed, the following page will be presented.
986+After the bug data is processed, the following page will be presented:
987 </para>
988 <para>
989 <example><title>Report a bug... (Summary)</title>
990@@ -876,9 +919,9 @@
991 </step>
992 <step>
993 <para>
994-Enter text in the <guilabel>Summary</guilabel> text box that describes the bug
995-with a few words. When finished, <mousebutton>Click</mousebutton> the
996-<guibutton>Next</guibutton> button. The following page will be presented.
997+Enter text that describes the bug into the <guilabel>Summary</guilabel> text
998+box. When finished, <mousebutton>Click</mousebutton> the
999+<guibutton>Next</guibutton> button. The following page will be presented:
1000 </para>
1001 <para>
1002 <example><title>Report a bug... (Further information)</title>
1003@@ -895,7 +938,7 @@
1004 Enter text in the <guilabel>Further information</guilabel> text box describing
1005 the bug in detail. When complete, <mousebutton>Click</mousebutton> the
1006 <guibutton>Submit Bug Report</guibutton> button. The following page will be
1007-presented.
1008+presented:
1009 </para>
1010 <para>
1011 <example><title>Thank you for your bug report</title>
1012@@ -909,8 +952,8 @@
1013 </step>
1014 </procedure>
1015 <para>
1016-<emphasis role="bold">Congratulations on making a successful non-crash related
1017-bug report!</emphasis> Identifying and reporting bugs are essential to improving
1018+<emphasis>Congratulations on making a successful non-crash related bug
1019+report!</emphasis> Identifying and reporting bugs are essential to improving
1020 &kubuntu;. Some emails may be sent to the registered address to update progress
1021 or to allow developers to get additional information about the bug.
1022 </para>
1023@@ -920,21 +963,24 @@
1024 <sect1 id="filing-wishlist">
1025 <title>Filing a Feature Request or Wishlist Report</title>
1026 <para>
1027-The easiest way to request a new feature in either an application or the
1028-operating system is to file a bug, otherwise known as a wishlist report.
1029+The easiest way to request a new feature, in either an application or the
1030+operating system, is to file a bug &mdash; otherwise known as a wishlist
1031+report.
1032 </para>
1033 <sect2 id="filing-wishlist-kde">
1034 <title>KDE</title>
1035 <para>
1036-Filing a feature request report in KDE is exactly the same as filing a <link
1037-linkend="filing-non-crash-kde">non-crash KDE bug report</link>.
1038+Filing a feature request report in <trademark>KDE</trademark> is exactly the
1039+same as filing a <link linkend="filing-non-crash-kde">non-crash
1040+<trademark>KDE</trademark> bug report</link>.
1041 </para>
1042 </sect2>
1043 <sect2 id="filing-wishlist-lp">
1044 <title>Launchpad</title>
1045 <para>
1046 Filing a wishlist report for &kubuntu; is exactly the same as filing a <link
1047-linkend="filing-non-crash-lp">non-crash Launchpad bug report</link>.
1048+linkend="filing-non-crash-lp">non-crash <trademark>Launchpad</trademark> bug
1049+report</link>.
1050 </para>
1051 </sect2>
1052 </sect1>

Subscribers

People subscribed via source and target branches

to all changes: