gryf/pentadactyl-pm
1
0
Fork 0
mirror of https://github.com/gryf/pentadactyl-pm.git synced 2026-03-16 03:43:34 +01:00
Code Issues Projects Releases Wiki Activity

Update help source files for Asciidoc 8.4.x.

Browse Source
This commit is contained in:
Doug Kearns
2009-08-06 23:17:08 +10:00
parent 817cbd1e75
commit 9ede619160
52 changed files with 323 additions and 321 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
vimperator/locale/en-US/developer.txt
View File

@@ -1,6 +1,6 @@
heading:Developer{nbsp}information[developer-information]
heading::Developer{nbsp}information[developer-information]
section:Writing{nbsp}documentation[writing-docs,documentation]
section::Writing{nbsp}documentation[writing-docs,documentation]
For every new feature, writing documentation is _mandatory_ for the patch to
be accepted. The docs are written in
@@ -62,7 +62,7 @@ Some notes about the code above:
There are also some additional asciidoc commands specifically for writing
Vimperator documentation:
- *$$section:Writing{nbsp}documentation[writing-docs,documentation]$$* Creates
- *$$section::Writing{nbsp}documentation[writing-docs,documentation]$$* Creates
a new section like _Writing Documentation_ in this help file with 2 tags.
- *$$help:developer{nbsp}information[developer.html,documentation]$$* creates
a link with text _developer information_ to the tag _documentation_ in
@@ -74,7 +74,7 @@ on the mailing list or on #vimperator. Usually help should be grouped together
in logically connected subject areas like
help:opening{nbsp}web{nbsp}pages[browsing.html,opening].
section:Generating{nbsp}documentation[generating-docs]
section::Generating{nbsp}documentation[generating-docs]
You can also autogenerate most of the asciidoc help after you have written a
new command, mapping or option. For this, use: