Search results
Page title matches
- ...some other way of showing keyboard shortcuts. What's important is that the DocBook source has the "information" necessary to work out what is being referred t ...735 bytes (119 words) - 10:35, 11 March 2016
- ...we're very happy to receive documentation written in plain text). Although DocBook can look somewhat intimidating to beginners, the markup is extremely self-d ...358 bytes (56 words) - 10:30, 11 March 2016
- ...E applications. Therefore, when referring to, for example, '''Konqueror in documentation, you should use: ...328 bytes (49 words) - 10:29, 11 March 2016
- ...in KDE documentation. See [[Special:myLanguage/Documentation Primer/Manual/DocBook#KDE Specialities|KDE Specialities]] for more information about entities. Ta ...840 bytes (128 words) - 10:27, 11 March 2016
- 18 bytes (1 word) - 10:30, 11 March 2016
- 449 bytes (66 words) - 10:29, 11 March 2016
- | prevpage=Special:myLanguage/Documentation_Primer/Manual/Writing | prevtext=Writing Documentation: Procedures and Tools ...340 bytes (40 words) - 10:34, 11 March 2016
- 377 bytes (62 words) - 10:30, 11 March 2016
- 24 bytes (2 words) - 10:30, 11 March 2016
- 79 bytes (11 words) - 10:32, 11 March 2016
- 32 bytes (3 words) - 10:31, 11 March 2016
- 56 bytes (9 words) - 10:26, 11 March 2016
- * All KDE documentation has a similar look, so once readers are familiar with conventions in one do ...144 bytes (23 words) - 10:32, 11 March 2016
- ...iately after the FPI. See [[Special:myLanguage/Documentation Primer/Manual/DocBook Reference/Prologue|The Prologue]] for more details about this section. ...320 bytes (40 words) - 10:31, 11 March 2016
- 16 bytes (1 word) - 10:29, 11 March 2016
- ...of DocBook in KDE is that content and presentation are strictly separated. DocBook files contain the content, and XSL files contain the information about pres ...262 bytes (43 words) - 10:30, 11 March 2016
- ...that appear in all KDE DocBook files, even though they are not required by DocBook itself: ...117 bytes (20 words) - 10:32, 11 March 2016
- 289 bytes (50 words) - 10:31, 11 March 2016
- 110 bytes (13 words) - 10:37, 11 March 2016
- ...o tell you (or a computer) what that text represents. So, a snippet from a DocBook file might look like: ...429 bytes (75 words) - 10:31, 11 March 2016
Page text matches
- ...item to the [[Documentation Primer/Manual/DocBook Reference/Index|index of DocBook commands]]. Usage: {{Input|1=<nowiki>{{DBIndexItem|General markup|acronym}} </noinclude>* [[Special:myLanguage/Documentation Primer/Manual/DocBook Reference/{{{1}}}#{{{2}}}{{!}}{{Tag|{{{2}}}}}]] ...393 bytes (43 words) - 15:12, 25 May 2013
- Documentation Primer/Manual/DocBook ...35 bytes (4 words) - 10:28, 11 March 2016
- ...ecial:myLanguage/Documentation Primer/Manual/DocBook Reference|Appendix A. DocBook Reference]]. ...247 bytes (36 words) - 10:31, 11 March 2016
- ...iately after the FPI. See [[Special:myLanguage/Documentation Primer/Manual/DocBook Reference/Prologue|The Prologue]] for more details about this section. ...320 bytes (40 words) - 10:31, 11 March 2016
- ...in KDE documentation. See [[Special:myLanguage/Documentation Primer/Manual/DocBook#KDE Specialities|KDE Specialities]] for more information about entities. Ta ...840 bytes (128 words) - 10:27, 11 March 2016
- = KDE Documentation Tasks = ...ssible. It is recommended that you [https://community.kde.org/Get_Involved/documentation get in touch with the team] and coordinate with the other members so ...2 KB (300 words) - 10:54, 8 November 2023