mizuho 0.9.6 → 0.9.8
Sign up to get free protection for your applications and to get access to all the features.
- data/README.markdown +4 -2
- data/Rakefile +0 -37
- data/asciidoc/BUGS +9 -18
- data/asciidoc/BUGS.txt +5 -14
- data/asciidoc/CHANGELOG +1433 -266
- data/asciidoc/CHANGELOG.txt +2821 -1810
- data/asciidoc/COPYING +339 -339
- data/asciidoc/COPYRIGHT +18 -18
- data/asciidoc/INSTALL +189 -30
- data/asciidoc/INSTALL.txt +175 -19
- data/asciidoc/MANIFEST +88 -0
- data/asciidoc/Makefile.in +29 -13
- data/asciidoc/README +16 -17
- data/asciidoc/README.txt +35 -36
- data/asciidoc/a2x.py +902 -0
- data/asciidoc/asciidoc.conf +610 -455
- data/asciidoc/asciidoc.py +1965 -1061
- data/asciidoc/asciidocapi.py +257 -0
- data/asciidoc/common.aap +2 -2
- data/asciidoc/configure +1170 -1023
- data/asciidoc/configure.ac +1 -1
- data/asciidoc/dblatex/asciidoc-dblatex.xsl +42 -0
- data/asciidoc/doc/a2x.1 +559 -102
- data/asciidoc/doc/a2x.1.txt +233 -91
- data/asciidoc/doc/article-docinfo.xml +87 -0
- data/asciidoc/doc/article.pdf +0 -0
- data/asciidoc/doc/article.txt +139 -122
- data/asciidoc/doc/asciidoc.1 +157 -46
- data/asciidoc/doc/asciidoc.1.txt +171 -118
- data/asciidoc/doc/asciidoc.conf +7 -8
- data/asciidoc/doc/asciidoc.dict +960 -635
- data/asciidoc/doc/asciidoc.txt +2335 -1464
- data/asciidoc/doc/asciidocapi.txt +189 -0
- data/asciidoc/doc/asciimathml.txt +14 -17
- data/asciidoc/doc/book-multi.txt +181 -155
- data/asciidoc/doc/book.epub +0 -0
- data/asciidoc/doc/book.txt +156 -131
- data/asciidoc/doc/customers.csv +18 -18
- data/asciidoc/doc/epub-notes.txt +210 -0
- data/asciidoc/doc/faq.txt +1122 -547
- data/asciidoc/doc/latex-backend.txt +192 -191
- data/asciidoc/doc/latex-bugs.txt +134 -0
- data/asciidoc/doc/latex-filter.pdf +0 -0
- data/asciidoc/doc/latex-filter.txt +196 -0
- data/asciidoc/doc/latexmath.txt +13 -136
- data/asciidoc/doc/latexmathml.txt +2 -2
- data/asciidoc/doc/main.aap +233 -297
- data/asciidoc/doc/music-filter.pdf +0 -0
- data/asciidoc/doc/music-filter.txt +55 -65
- data/asciidoc/doc/publishing-ebooks-with-asciidoc.txt +398 -0
- data/asciidoc/doc/slidy-example.txt +167 -0
- data/asciidoc/doc/slidy.txt +113 -0
- data/asciidoc/doc/source-highlight-filter.pdf +0 -0
- data/asciidoc/doc/source-highlight-filter.txt +45 -20
- data/asciidoc/doc/testasciidoc.txt +231 -0
- data/asciidoc/docbook-xsl/asciidoc-docbook-xsl.txt +30 -8
- data/asciidoc/docbook-xsl/chunked.xsl +17 -19
- data/asciidoc/docbook-xsl/common.xsl +106 -67
- data/asciidoc/docbook-xsl/epub.xsl +35 -0
- data/asciidoc/docbook-xsl/fo.xsl +3 -0
- data/asciidoc/docbook-xsl/htmlhelp.xsl +16 -17
- data/asciidoc/docbook-xsl/manpage.xsl +31 -31
- data/asciidoc/docbook-xsl/text.xsl +6 -1
- data/asciidoc/docbook-xsl/xhtml.xsl +14 -14
- data/asciidoc/docbook45.conf +759 -0
- data/asciidoc/filters/code/code-filter-readme.txt +37 -37
- data/asciidoc/filters/code/code-filter-test.txt +15 -15
- data/asciidoc/filters/code/code-filter.conf +8 -8
- data/asciidoc/filters/graphviz/asciidoc-graphviz-sample.txt +104 -64
- data/asciidoc/filters/graphviz/graphviz-filter.conf +20 -16
- data/asciidoc/filters/graphviz/graphviz2png.py +54 -39
- data/asciidoc/filters/latex/latex-filter.conf +18 -0
- data/asciidoc/filters/latex/latex2png.py +216 -0
- data/asciidoc/filters/music/music-filter.conf +8 -17
- data/asciidoc/filters/music/music2png.py +40 -32
- data/asciidoc/filters/source/source-highlight-filter.conf +40 -34
- data/asciidoc/help.conf +261 -96
- data/asciidoc/html4.conf +505 -460
- data/asciidoc/html5.conf +686 -0
- data/asciidoc/images/highlighter.png +0 -0
- data/asciidoc/images/icons/caution.png +0 -0
- data/asciidoc/images/icons/example.png +0 -0
- data/asciidoc/images/icons/important.png +0 -0
- data/asciidoc/images/icons/note.png +0 -0
- data/asciidoc/images/icons/tip.png +0 -0
- data/asciidoc/images/icons/warning.png +0 -0
- data/asciidoc/images/smallnew.png +0 -0
- data/asciidoc/javascripts/asciidoc.js +189 -0
- data/asciidoc/javascripts/slidy.js +2845 -0
- data/asciidoc/javascripts/toc.js +8 -0
- data/asciidoc/lang-de.conf +57 -0
- data/asciidoc/lang-en.conf +54 -0
- data/asciidoc/lang-es.conf +49 -9
- data/asciidoc/lang-fr.conf +59 -0
- data/asciidoc/lang-hu.conf +55 -0
- data/asciidoc/lang-it.conf +55 -0
- data/asciidoc/lang-nl.conf +57 -0
- data/asciidoc/lang-pt-BR.conf +56 -0
- data/asciidoc/lang-ru.conf +60 -0
- data/asciidoc/lang-uk.conf +60 -0
- data/asciidoc/latex.conf +700 -663
- data/asciidoc/main.aap +77 -0
- data/asciidoc/slidy.conf +136 -0
- data/asciidoc/{examples/website/xhtml11-manpage.css → stylesheets/asciidoc-manpage.css} +1 -1
- data/asciidoc/stylesheets/asciidoc.css +508 -0
- data/asciidoc/stylesheets/docbook-xsl.css +322 -272
- data/asciidoc/stylesheets/flask-manpage.css +1 -0
- data/asciidoc/stylesheets/flask.css +584 -0
- data/asciidoc/stylesheets/pygments.css +66 -0
- data/asciidoc/stylesheets/slidy.css +445 -0
- data/asciidoc/stylesheets/toc2.css +33 -0
- data/asciidoc/stylesheets/volnitsky-manpage.css +1 -0
- data/asciidoc/stylesheets/volnitsky.css +435 -0
- data/asciidoc/stylesheets/xhtml11-quirks.css +5 -3
- data/asciidoc/tests/asciidocapi.py +257 -0
- data/asciidoc/tests/data/deprecated-quotes.txt +12 -0
- data/asciidoc/tests/data/filters-test.txt +90 -0
- data/asciidoc/tests/data/lang-de-test.txt +106 -0
- data/asciidoc/tests/data/lang-en-test.txt +114 -0
- data/asciidoc/tests/data/lang-es-test.txt +106 -0
- data/asciidoc/tests/data/lang-fr-test.txt +106 -0
- data/asciidoc/tests/data/lang-hu-test.txt +106 -0
- data/asciidoc/tests/data/lang-nl-test.txt +94 -0
- data/asciidoc/tests/data/lang-pt-BR-test.txt +106 -0
- data/asciidoc/tests/data/lang-ru-test.txt +106 -0
- data/asciidoc/tests/data/lang-uk-test.txt +106 -0
- data/asciidoc/tests/data/oldtables.txt +64 -0
- data/asciidoc/tests/data/rcs-id-marker-test.txt +6 -0
- data/asciidoc/tests/data/testcases.conf +2 -0
- data/asciidoc/tests/data/testcases.txt +740 -0
- data/asciidoc/tests/data/utf8-bom-test.txt +9 -0
- data/asciidoc/tests/data/utf8-examples.txt +217 -0
- data/asciidoc/tests/testasciidoc.conf +520 -0
- data/asciidoc/tests/testasciidoc.py +411 -0
- data/asciidoc/text.conf +16 -16
- data/asciidoc/vim/syntax/asciidoc.vim +99 -91
- data/asciidoc/wordpress.conf +43 -3
- data/asciidoc/xhtml11-quirks.conf +61 -57
- data/asciidoc/xhtml11.conf +684 -645
- data/lib/mizuho.rb +2 -0
- data/lib/mizuho/generator.rb +2 -2
- data/test/generator_spec.rb +1 -1
- data/test/parser_spec.rb +1 -1
- data/test/spec_helper.rb +3 -4
- metadata +87 -88
- data/asciidoc/a2x +0 -674
- data/asciidoc/doc/article.css-embedded.html +0 -602
- data/asciidoc/doc/article.html +0 -46
- data/asciidoc/doc/asciidoc-revhistory.xml +0 -27
- data/asciidoc/doc/asciidoc.1.css-embedded.html +0 -598
- data/asciidoc/doc/asciidoc.1.css.html +0 -212
- data/asciidoc/doc/asciidoc.1.html +0 -190
- data/asciidoc/doc/asciidoc.css-embedded.html +0 -7853
- data/asciidoc/doc/asciidoc.css.html +0 -7416
- data/asciidoc/doc/asciidoc.html +0 -3339
- data/asciidoc/doc/book-multi.css-embedded.html +0 -575
- data/asciidoc/doc/book-multi.html +0 -55
- data/asciidoc/doc/book.css-embedded.html +0 -607
- data/asciidoc/doc/book.html +0 -43
- data/asciidoc/doc/docbook-xsl.css +0 -272
- data/asciidoc/doc/latex-backend.html +0 -117
- data/asciidoc/doc/music-filter.html +0 -566
- data/asciidoc/doc/source-highlight-filter.html +0 -214
- data/asciidoc/docbook.conf +0 -721
- data/asciidoc/examples/website/ASCIIMathML.js +0 -938
- data/asciidoc/examples/website/CHANGELOG.html +0 -4389
- data/asciidoc/examples/website/CHANGELOG.txt +0 -1810
- data/asciidoc/examples/website/INSTALL.html +0 -161
- data/asciidoc/examples/website/INSTALL.txt +0 -71
- data/asciidoc/examples/website/LaTeXMathML.js +0 -1223
- data/asciidoc/examples/website/README-website.html +0 -118
- data/asciidoc/examples/website/README-website.txt +0 -29
- data/asciidoc/examples/website/README.html +0 -125
- data/asciidoc/examples/website/README.txt +0 -36
- data/asciidoc/examples/website/a2x.1.html +0 -419
- data/asciidoc/examples/website/a2x.1.txt +0 -204
- data/asciidoc/examples/website/asciidoc-docbook-xsl.html +0 -130
- data/asciidoc/examples/website/asciidoc-docbook-xsl.txt +0 -43
- data/asciidoc/examples/website/asciidoc-graphviz-sample.txt +0 -130
- data/asciidoc/examples/website/asciimathml.txt +0 -64
- data/asciidoc/examples/website/build-website.sh +0 -25
- data/asciidoc/examples/website/customers.csv +0 -18
- data/asciidoc/examples/website/downloads.html +0 -257
- data/asciidoc/examples/website/downloads.txt +0 -121
- data/asciidoc/examples/website/faq.html +0 -673
- data/asciidoc/examples/website/faq.txt +0 -547
- data/asciidoc/examples/website/index.html +0 -419
- data/asciidoc/examples/website/index.txt +0 -245
- data/asciidoc/examples/website/latex-backend.html +0 -535
- data/asciidoc/examples/website/latex-backend.txt +0 -191
- data/asciidoc/examples/website/latexmathml.txt +0 -41
- data/asciidoc/examples/website/layout1.conf +0 -161
- data/asciidoc/examples/website/layout1.css +0 -65
- data/asciidoc/examples/website/layout2.conf +0 -158
- data/asciidoc/examples/website/layout2.css +0 -93
- data/asciidoc/examples/website/manpage.html +0 -266
- data/asciidoc/examples/website/manpage.txt +0 -118
- data/asciidoc/examples/website/music-filter.html +0 -242
- data/asciidoc/examples/website/music-filter.txt +0 -158
- data/asciidoc/examples/website/music1.abc +0 -12
- data/asciidoc/examples/website/music1.png +0 -0
- data/asciidoc/examples/website/music2.ly +0 -9
- data/asciidoc/examples/website/music2.png +0 -0
- data/asciidoc/examples/website/newlists.txt +0 -40
- data/asciidoc/examples/website/newtables.txt +0 -397
- data/asciidoc/examples/website/sample1.png +0 -0
- data/asciidoc/examples/website/sample3.png +0 -0
- data/asciidoc/examples/website/sample4.png +0 -0
- data/asciidoc/examples/website/source-highlight-filter.html +0 -286
- data/asciidoc/examples/website/source-highlight-filter.txt +0 -203
- data/asciidoc/examples/website/support.html +0 -78
- data/asciidoc/examples/website/support.txt +0 -5
- data/asciidoc/examples/website/toc.js +0 -69
- data/asciidoc/examples/website/userguide.html +0 -7460
- data/asciidoc/examples/website/userguide.txt +0 -4979
- data/asciidoc/examples/website/version83.txt +0 -37
- data/asciidoc/examples/website/version9.html +0 -143
- data/asciidoc/examples/website/version9.txt +0 -48
- data/asciidoc/examples/website/xhtml11-quirks.css +0 -41
- data/asciidoc/examples/website/xhtml11.css +0 -328
- data/asciidoc/stylesheets/xhtml11-manpage.css +0 -18
- data/asciidoc/stylesheets/xhtml11.css +0 -328
@@ -1,547 +0,0 @@
|
|
1
|
-
AsciiDoc Frequently Asked Questions
|
2
|
-
===================================
|
3
|
-
|
4
|
-
An embryonic AsciiDoc FAQ.
|
5
|
-
|
6
|
-
|
7
|
-
== Is it possible to include charts in AsciiDoc documents?
|
8
|
-
|
9
|
-
There are a number of programs available that generate presentation
|
10
|
-
charts from textual specification, for example
|
11
|
-
http://home.gna.org/pychart/[Pychart] is a library for writing chart
|
12
|
-
scripts in Python. Here's an example from the 'Pychart' documentation:
|
13
|
-
|
14
|
-
.barchart.py
|
15
|
-
---------------------------------------------------------------------
|
16
|
-
#
|
17
|
-
# Example bar chart (from Pychart documentation http://home.gna.org/pychart/).
|
18
|
-
#
|
19
|
-
from pychart import *
|
20
|
-
theme.get_options()
|
21
|
-
|
22
|
-
data = [(10, 20, 30, 5), (20, 65, 33, 5), (30, 55, 30, 5), (40, 45, 51, 7),
|
23
|
-
(50, 25, 27, 3), (60, 75, 30, 5), (70, 80, 42, 5), (80, 62, 32, 5),
|
24
|
-
(90, 42, 39, 5), (100, 32, 39, 4)]
|
25
|
-
|
26
|
-
# The attribute y_coord=... tells that the Y axis values
|
27
|
-
# should be taken from samples.
|
28
|
-
# In this example, Y values will be [40,50,60,70,80].
|
29
|
-
ar = area.T(y_coord = category_coord.T(data[3:8], 0),
|
30
|
-
x_grid_style=line_style.gray50_dash1,
|
31
|
-
x_grid_interval=20, x_range = (0,100),
|
32
|
-
x_axis=axis.X(label="X label"),
|
33
|
-
y_axis=axis.Y(label="Y label"),
|
34
|
-
bg_style = fill_style.gray90,
|
35
|
-
border_line_style = line_style.default,
|
36
|
-
legend = legend.T(loc=(80,10)))
|
37
|
-
|
38
|
-
# Below call sets the default attributes for all bar plots.
|
39
|
-
chart_object.set_defaults(bar_plot.T, direction="horizontal", data=data)
|
40
|
-
|
41
|
-
# Attribute cluster=(0,3) tells that you are going to draw three bar
|
42
|
-
# plots side by side. The plot labeled "foo" will the leftmost (i.e.,
|
43
|
-
# 0th out of 3). Attribute hcol tells the column from which to
|
44
|
-
# retrive sample values from. It defaults to one.
|
45
|
-
ar.add_plot(bar_plot.T(label="foo", cluster=(0,3)))
|
46
|
-
ar.add_plot(bar_plot.T(label="bar", hcol=2, cluster=(1,3)))
|
47
|
-
ar.add_plot(bar_plot.T(label="baz", hcol=3, cluster=(2,3)))
|
48
|
-
ar.draw()
|
49
|
-
---------------------------------------------------------------------
|
50
|
-
|
51
|
-
To execute the script and include the generated chart image in your
|
52
|
-
document add the following lines to the AsciiDoc source:
|
53
|
-
|
54
|
-
---------------------------------------------------------------------
|
55
|
-
// Generate chart image file.
|
56
|
-
\sys2::[python barchart.py --format=png --output=barchart.png --scale=2]
|
57
|
-
|
58
|
-
// Display chart image file.
|
59
|
-
image::barchart.png[]
|
60
|
-
---------------------------------------------------------------------
|
61
|
-
|
62
|
-
NOTE: You need to run asciidoc(1) with the `--unsafe` command-line
|
63
|
-
option to execute the `sys2` system macro.
|
64
|
-
|
65
|
-
|
66
|
-
== How can I render indented paragraphs?
|
67
|
-
|
68
|
-
To unconditionally indent all paragraphs add the following line to the
|
69
|
-
`xhtml11.css` stylesheet (or a custom stylesheet).
|
70
|
-
|
71
|
-
---------------------------------------------------------------------
|
72
|
-
div.paragraph p {text-indent: 3em;}
|
73
|
-
---------------------------------------------------------------------
|
74
|
-
|
75
|
-
This will restyle the entire document by indenting all paragraphs
|
76
|
-
which is normally what you want to do (mixed paragraph styles produce
|
77
|
-
ugly documents).
|
78
|
-
|
79
|
-
To selectively indent paragraphs with the 'indented' style add the
|
80
|
-
following line to the `xhtml11.css` stylesheet (or a custom
|
81
|
-
stylesheet).
|
82
|
-
|
83
|
-
---------------------------------------------------------------------
|
84
|
-
div.paragraph.indented p {text-indent: 3em;}
|
85
|
-
---------------------------------------------------------------------
|
86
|
-
|
87
|
-
Then apply the 'indented' style to normal paragraphs, for example:
|
88
|
-
|
89
|
-
---------------------------------------------------------------------
|
90
|
-
[indented]
|
91
|
-
Lorem ipsum dolor sit amet, consectetuer adipiscing elit. Maecenas
|
92
|
-
ultrices justo porttitor augue. Vestibulum pretium. Donec porta
|
93
|
-
vestibulum mi. Aliquam pede. Aenean lobortis lorem et lacus. Sed
|
94
|
-
lacinia. Vivamus at lectus.
|
95
|
-
---------------------------------------------------------------------
|
96
|
-
|
97
|
-
NOTE: This FAQ applies to XHTML output not DocBook. To achieve the
|
98
|
-
same results with DocBook you would need to customize the DocBook XSL
|
99
|
-
stylesheets to indent paragraphs with the `simpara` element
|
100
|
-
`role="indented"` attribute.
|
101
|
-
|
102
|
-
|
103
|
-
== Is there a way to set default image height and width attributes?
|
104
|
-
|
105
|
-
You can set the 'height' and 'width' attributes globally in your
|
106
|
-
document with Attribute Entries or from the command-line using the
|
107
|
-
`--attribute` option. In the following example images that don't
|
108
|
-
explicitly set the 'height' and 'width' values will be 350 by 250
|
109
|
-
pixels.
|
110
|
-
|
111
|
-
---------------------------------------------------------------------
|
112
|
-
:height: 250
|
113
|
-
:width: 350
|
114
|
-
|
115
|
-
image:images/tiger.png[]
|
116
|
-
---------------------------------------------------------------------
|
117
|
-
|
118
|
-
|
119
|
-
== How can I place a backslash character in front of an attribute reference without escaping the reference?
|
120
|
-
|
121
|
-
Use the predefined `\{backslash}` attribute reference instead of an
|
122
|
-
actual backslash, for example if the `\{projectname}` attribute has
|
123
|
-
the value `foobar` then:
|
124
|
-
|
125
|
-
d:\data{backslash}{projectname}
|
126
|
-
|
127
|
-
would be rendered as:
|
128
|
-
|
129
|
-
d:\data\foobar
|
130
|
-
|
131
|
-
== How can I escape AsciiDoc markup?
|
132
|
-
|
133
|
-
Most AsciiDoc inline elements can be suppressed by preceding them with
|
134
|
-
a backslash character. These elements include:
|
135
|
-
|
136
|
-
- Attribute references.
|
137
|
-
- Text formatting.
|
138
|
-
- Quoting,
|
139
|
-
- Macros.
|
140
|
-
- Replacements.
|
141
|
-
- Special words.
|
142
|
-
- Table cell separators.
|
143
|
-
|
144
|
-
But there are exceptions -- see the next question.
|
145
|
-
|
146
|
-
|
147
|
-
== Some elements can't be escaped with a single backslash
|
148
|
-
|
149
|
-
There are a number of exceptions to the usual single backslash rule
|
150
|
-
-- mostly relating to URL macros that have two syntaxes or quoting
|
151
|
-
ambiguity. Here are some non-standard escape examples:
|
152
|
-
|
153
|
-
[cols="1default,4literal",width="70%",grid="none",frame="none"]
|
154
|
-
|====================================================================
|
155
|
-
|Mailto URLs |
|
156
|
-
\srackham@methods.co.nz
|
157
|
-
<\srackham@methods.co.nz>
|
158
|
-
\mailto:[\srackham@methods.co.nz]
|
159
|
-
|
160
|
-
|Web URLs |
|
161
|
-
\http://www.foo1.co.nz
|
162
|
-
\\http://www.foobar.com[]
|
163
|
-
\\http://www.foobar.com[Foobar Limited]
|
164
|
-
|
165
|
-
|Other |
|
166
|
-
A C+\+ Library for C++
|
167
|
-
A C+\+ Library for C+\+ \+++
|
168
|
-
\\``double-quotes''
|
169
|
-
\*\*F**ile Open...
|
170
|
-
|====================================================================
|
171
|
-
|
172
|
-
The source of this problem is ambiguity across substitution types --
|
173
|
-
the first match unescapes allowing the second to substitute. A
|
174
|
-
work-around for difficult cases is to side-step the problem using the
|
175
|
-
`\pass:[]` passthrough inline macro.
|
176
|
-
|
177
|
-
|
178
|
-
== How can I set default list and tables styles?
|
179
|
-
|
180
|
-
You can set the element's 'style' entry in a global or custom
|
181
|
-
configuration file.
|
182
|
-
|
183
|
-
This example this will horizontally style all labeled lists that don't
|
184
|
-
have an explicit style attribute:
|
185
|
-
|
186
|
-
----------------------------------
|
187
|
-
[listdef-labeled]
|
188
|
-
style=horizontal
|
189
|
-
|
190
|
-
[listdef-labeled2]
|
191
|
-
style=horizontal
|
192
|
-
----------------------------------
|
193
|
-
|
194
|
-
This example will put a top and bottom border on all tables that don't
|
195
|
-
already have an explicit style attribute:
|
196
|
-
|
197
|
-
----------------------------------
|
198
|
-
[tabledef-default]
|
199
|
-
style=topbot
|
200
|
-
topbot-style=frame="topbot"
|
201
|
-
----------------------------------
|
202
|
-
|
203
|
-
Alternatively you can set the configuration entries from inside your
|
204
|
-
document, the above examples are equivalent to:
|
205
|
-
|
206
|
-
----------------------------------
|
207
|
-
:listdef-labeled.style: horizontal
|
208
|
-
:listdef-labeled2.style: horizontal
|
209
|
-
|
210
|
-
:tabledef-default.topbot-style: frame="topbot"
|
211
|
-
:tabledef-default.style: topbot
|
212
|
-
----------------------------------
|
213
|
-
|
214
|
-
|
215
|
-
== Why do I get a filter non-zero exit code error?
|
216
|
-
|
217
|
-
An error was returned when AsciiDoc tried to execute an external
|
218
|
-
filter command. The most common reason for this is that the filter
|
219
|
-
command could not be found by the command shell. To figure out what
|
220
|
-
the problem is run AsciiDoc with the `--verbose` option to determine
|
221
|
-
the command that is failing and then try to run the command manually
|
222
|
-
from the command-line.
|
223
|
-
|
224
|
-
|
225
|
-
== Are there any DocBook viewers?
|
226
|
-
|
227
|
-
http://live.gnome.org/Yelp[Yelp], the GNOME help viewer, does a
|
228
|
-
creditable job of displaying DocBook files XML files directly. Just
|
229
|
-
run it from the command-line, for example:
|
230
|
-
|
231
|
-
$ yelp file://home/srackham/tmp/book.xml
|
232
|
-
|
233
|
-
Note that you have to supply the full path name in URI format, this
|
234
|
-
shell script makes interactive use easier:
|
235
|
-
|
236
|
-
-------------------------------
|
237
|
-
#!/bin/sh
|
238
|
-
if [ -z "$1" ]; then
|
239
|
-
echo "usage: dbkview FILE"
|
240
|
-
exit 1
|
241
|
-
fi
|
242
|
-
yelp "file://$(pwd)/$1"
|
243
|
-
-------------------------------
|
244
|
-
|
245
|
-
This tip was submitted by Lionel Orry.
|
246
|
-
|
247
|
-
|
248
|
-
== Can you create ODF documents using AsciiDoc?
|
249
|
-
|
250
|
-
The easiest and highest fidelity methods I've seen is to generate
|
251
|
-
HTML from AsciiDoc then paste it from your browser (we use Firefox)
|
252
|
-
into OpenOffice Writer.
|
253
|
-
|
254
|
-
- I found that that there is better fidelity pasting HTML generated by
|
255
|
-
the 'html4' backend instead of the default 'xhtml11' backend.
|
256
|
-
- Don't paste AsciiDoc tables of contents, OpenOffice Writer (I was
|
257
|
-
using version 2.3) hangs when saving. This may be something to do
|
258
|
-
with the embedded JavaScript but I haven't looked closely at it, I
|
259
|
-
may even be wrong about this.
|
260
|
-
|
261
|
-
This tip was contributed by Bernard Amade.
|
262
|
-
|
263
|
-
|
264
|
-
== How can I supress cell separators in included table data files?
|
265
|
-
|
266
|
-
Use the `\{include:}` system attribute instead of the `\include::[]`
|
267
|
-
macro (the former is not expanded until after the table data has been
|
268
|
-
parsed into cells, whereas the latter is included before the table is
|
269
|
-
processed.
|
270
|
-
|
271
|
-
|
272
|
-
== How can I preserve paragraph line boundaries?
|
273
|
-
|
274
|
-
Apply the The 'verse' paragraph style, the rendered text preserves
|
275
|
-
line boundaries and is useful for lyrics and poems. For example:
|
276
|
-
|
277
|
-
---------------------------------------------------------------------
|
278
|
-
[verse]
|
279
|
-
Consul *necessitatibus* per id,
|
280
|
-
consetetur, eu pro everti postulant
|
281
|
-
homero verear ea mea, qui.
|
282
|
-
---------------------------------------------------------------------
|
283
|
-
|
284
|
-
If you are generating PDF files (using FOP) or HTML files then you can
|
285
|
-
use line breaks. For example:
|
286
|
-
|
287
|
-
---------------------------------------------------------------------
|
288
|
-
Consul *necessitatibus* per id, +
|
289
|
-
consetetur, eu pro everti postulant +
|
290
|
-
homero verear ea mea, qui.
|
291
|
-
---------------------------------------------------------------------
|
292
|
-
|
293
|
-
|
294
|
-
== How can I include non-breaking space characters?
|
295
|
-
|
296
|
-
The predefined `\{nbsp}` attribute reference will be replaced by a
|
297
|
-
non-breaking space character. You could also use the non-breaking
|
298
|
-
space character entity reference `\ ` (see the next question).
|
299
|
-
|
300
|
-
|
301
|
-
== Can I include HTML and XML character entity references in my document?
|
302
|
-
|
303
|
-
Yes, just enter the reference in your document. For example `\β`
|
304
|
-
will print a Greek small beta character β
|
305
|
-
|
306
|
-
|
307
|
-
[[X1]]
|
308
|
-
== How do I include spaces in URLs?
|
309
|
-
|
310
|
-
URL inline macro targets (addresses) cannot contain white space
|
311
|
-
characters. If you need spaces encode them as `%20`. For example:
|
312
|
-
|
313
|
-
image:large%20image.png[]
|
314
|
-
http://www.foo.bar.com/an%20example%20document.html
|
315
|
-
|
316
|
-
|
317
|
-
== How can I get AsciiDoc to assign the correct DocBook language attribute?
|
318
|
-
|
319
|
-
Set the AsciiDoc 'lang' attribute to the appropriate language code.
|
320
|
-
For example:
|
321
|
-
|
322
|
-
$ a2x -a lang=es doc/article.txt
|
323
|
-
|
324
|
-
This will ensure that downstream DocBook processing will generate the
|
325
|
-
correct language specific document headings (things like table of
|
326
|
-
contents, revision history, figure and table captions, admonition
|
327
|
-
captions).
|
328
|
-
|
329
|
-
|
330
|
-
== Why does AsciiDoc give me a ``malformed author'' error?
|
331
|
-
|
332
|
-
This is normally because there are more than three names (up to three
|
333
|
-
are expected: first name, middle name and last name). For example,
|
334
|
-
this author line would result in an error:
|
335
|
-
|
336
|
-
Vincent Willem van Gogh
|
337
|
-
|
338
|
-
You can enter multi-word first, middle and last names in the author
|
339
|
-
line using the underscore as a word separator. For example:
|
340
|
-
|
341
|
-
Vincent Willem van_Gogh
|
342
|
-
|
343
|
-
You could also resolve the problem by replacing the author line with
|
344
|
-
explicit attribute entries:
|
345
|
-
|
346
|
-
:First name: Vincent
|
347
|
-
:Middle name: Willem
|
348
|
-
:Last name: Van Gogh
|
349
|
-
|
350
|
-
|
351
|
-
== How can I assign multiple author names?
|
352
|
-
|
353
|
-
A quick way to do this is put both authors in a single first name, for
|
354
|
-
example:
|
355
|
-
|
356
|
-
My Document
|
357
|
-
===========
|
358
|
-
:Author: Bill_and_Ben_the_Flowerpot_Men
|
359
|
-
:Author Initials: BB & BC
|
360
|
-
|
361
|
-
asciidoc(1) replaces the underscores with spaces.
|
362
|
-
|
363
|
-
The longer, semantically correct, way is to override the
|
364
|
-
`[header]` configuration file section in a document specific `.conf`
|
365
|
-
file. For example if your document is `mydoc.txt` then a file called
|
366
|
-
`mydoc.conf` in the document directory would be picked up
|
367
|
-
automatically by asciidoc(1). Copy and paste the default
|
368
|
-
`docbook.conf` file `[header]` to `mydoc.conf` and modify the author
|
369
|
-
related markup:
|
370
|
-
|
371
|
-
[header]
|
372
|
-
:
|
373
|
-
<authorgroup>...
|
374
|
-
:
|
375
|
-
|
376
|
-
|
377
|
-
== How can I escape a labeled list entry?
|
378
|
-
|
379
|
-
Two colons or semicolons in a paragraph may be confused with a labeled
|
380
|
-
list entry. Use the predefined `\{two_colons}` and `\{two_semicolons}`
|
381
|
-
to suppress this behavior, for example:
|
382
|
-
|
383
|
-
Qui in magna commodo{two_colons} est labitur dolorum an. Est ne
|
384
|
-
magna primis adolescens.
|
385
|
-
|
386
|
-
Will be rendered as:
|
387
|
-
|
388
|
-
Qui in magna commodo{two_colons} est labitur dolorum an. Est ne
|
389
|
-
magna primis adolescens.
|
390
|
-
|
391
|
-
|
392
|
-
== How can I selectively disable a quoted text substitution?
|
393
|
-
|
394
|
-
Omitting the tag name will disable quoting. For example, if you don't
|
395
|
-
want superscripts or subscripts then put the following in a custom
|
396
|
-
configuration file or edit the global `asciidoc.conf` configuration
|
397
|
-
file:
|
398
|
-
|
399
|
-
-------------------
|
400
|
-
[quotes]
|
401
|
-
^=
|
402
|
-
~=
|
403
|
-
-------------------
|
404
|
-
|
405
|
-
Alternatively you can set the configuration entries from within your
|
406
|
-
document, the above examples are equivalent to:
|
407
|
-
|
408
|
-
-------------------
|
409
|
-
:quotes.^:
|
410
|
-
:quotes.~:
|
411
|
-
-------------------
|
412
|
-
|
413
|
-
|
414
|
-
== How can I customize the \{localdate} format?
|
415
|
-
|
416
|
-
The default format for the `\{localdate}` attribute is the ISO 8601
|
417
|
-
`yyyy-mm-dd` format. You can change this format by explicitly setting
|
418
|
-
the `\{localdate}` attribute. For example by setting it using the
|
419
|
-
asciidoc(1) `-a` command-line option:
|
420
|
-
|
421
|
-
$ asciidoc -a localdate=`date +%d-%d-%Y` mydoc.txt
|
422
|
-
|
423
|
-
You could also set it by adding an Attribute Entry to your souce
|
424
|
-
document, for example:
|
425
|
-
|
426
|
-
:localdate: {sys: date +%Y-%m-%d}
|
427
|
-
|
428
|
-
Since it's set using an executable attribute you'll also need to
|
429
|
-
include the `--unsafe` option when you run asciidoc).
|
430
|
-
|
431
|
-
|
432
|
-
== Why doesn't AsciiDoc support strike through text?
|
433
|
-
|
434
|
-
The reason it's not in the distribution is that DocBook does not have
|
435
|
-
provision for strike through text and one of the AsciiDoc design goals
|
436
|
-
is that AsciiDoc markup should be applicable to all output formats.
|
437
|
-
|
438
|
-
Strike through is normally used to mark deleted text -- a more
|
439
|
-
comprehensive way to manage document revisions is to use a version
|
440
|
-
control system such as Subversion. You can also use the AsciiDoc
|
441
|
-
'CommentLines' and 'CommentBlocks' to retain revised text in the
|
442
|
-
source document.
|
443
|
-
|
444
|
-
If you really need strike through text for (X)HTML outputs then adding
|
445
|
-
the following to a configuration file will allow you to quote strike
|
446
|
-
through text with hyphen characters:
|
447
|
-
|
448
|
-
---------------------------------------------------------------------
|
449
|
-
ifdef::basebackend-html[]
|
450
|
-
|
451
|
-
[quotes]
|
452
|
-
-=strikethrough
|
453
|
-
|
454
|
-
[tags]
|
455
|
-
strikethrough=<span style="text-decoration: line-through;">|</span>
|
456
|
-
|
457
|
-
endif::basebackend-html[]
|
458
|
-
---------------------------------------------------------------------
|
459
|
-
|
460
|
-
|
461
|
-
== Where can I find examples of commands used to build output documents?
|
462
|
-
|
463
|
-
The User Guide has some. You could also look at `./doc/main.aap` in
|
464
|
-
the AsciiDoc distribution, it has all the commands used to build the
|
465
|
-
AsciiDoc documentation (even if you don't use A-A-P you'll still find
|
466
|
-
it useful).
|
467
|
-
|
468
|
-
|
469
|
-
== Why have you used the DocBook <simpara> element instead of <para>?
|
470
|
-
|
471
|
-
`<simpara>` is really the same as `<para>` except it can't contain
|
472
|
-
block elements -- this matched, more closely, the AsciiDoc paragraph
|
473
|
-
semantics.
|
474
|
-
|
475
|
-
|
476
|
-
== How can I format text inside a listing block?
|
477
|
-
|
478
|
-
By default only 'specialcharacters' and 'callouts' are substituted in
|
479
|
-
listing blocks; you can add quotes substitutions by explicitly setting
|
480
|
-
the block 'subs' attribute, for example:
|
481
|
-
|
482
|
-
[subs="quotes"]
|
483
|
-
------------------------------------------
|
484
|
-
$ ls *-al*
|
485
|
-
------------------------------------------
|
486
|
-
|
487
|
-
The `-al` will rendered bold. Note that:
|
488
|
-
|
489
|
-
- You would need to explicitly escape text you didn't want quoted.
|
490
|
-
- Don't do this in source code listing blocks because it modifies the
|
491
|
-
source code which confuses the syntax highlighter.
|
492
|
-
- This only works if your DocBook processor recognizes DocBook
|
493
|
-
`<emphasis>` elements inside `<screen>` elements.
|
494
|
-
|
495
|
-
|
496
|
-
== Why doesn't the include1::[] macro work?
|
497
|
-
|
498
|
-
Internally the `include1` macro is translated to the `include1` system
|
499
|
-
attribute which means it must be evaluated in a region where attribute
|
500
|
-
substitution is enabled. `include1` won't work, for example, in a
|
501
|
-
ListingBlock (unless attribute substitution is enabled). `include1`
|
502
|
-
is intended for use in configuration files, use the `include` macro
|
503
|
-
and set the attribute `depth=1` instead, for example:
|
504
|
-
|
505
|
-
-----------------------------------------------
|
506
|
-
include::blogpost_media_processing.txt[depth=1]
|
507
|
-
-----------------------------------------------
|
508
|
-
|
509
|
-
== How can I customize PDF files generated by dblatex?
|
510
|
-
|
511
|
-
There are a number of dblatex XSL parameters that can be used to
|
512
|
-
customize PDF output. You can set them globally in the AsciiDoc
|
513
|
-
`./dblatex/asciidoc-dblatex.xsl` configuration file or you can also
|
514
|
-
pass them on the a2x(1) command-line, for example:
|
515
|
-
|
516
|
-
a2x -f pdf --dblatex-opts "-P latex.output.revhistory=0" doc/article.txt
|
517
|
-
|
518
|
-
See also the http://dblatex.sourceforge.net/[dblatex] documentation.
|
519
|
-
|
520
|
-
|
521
|
-
== How can I make the mailto macro work with multiple email addresses?
|
522
|
-
|
523
|
-
For the AsciiDoc 'mailto' macro to work with multiple email addresses
|
524
|
-
(as per RFC2368) you need to URL encode the '@' characters (replace
|
525
|
-
them with '%40'), if you don't the individual addresses will be
|
526
|
-
rendered as separate links. You also need to <<X1,replace spaces with
|
527
|
-
'%20'>>.
|
528
|
-
|
529
|
-
For example, the following call won't work:
|
530
|
-
|
531
|
-
mailto:jb@foobar.com,jd@acme.co.nz?subject=New foofoo release[New foofoo release]
|
532
|
-
|
533
|
-
Use this instead:
|
534
|
-
|
535
|
-
mailto:jb%40foobar.com,jd%40acme.co.nz?subject=New%20foofoo%20release[New foofoo release]
|
536
|
-
|
537
|
-
|
538
|
-
== How can a replacement have a trailing backslash?
|
539
|
-
Quote the entry name -- this nonsensical example replaces `x\` with
|
540
|
-
`y`:
|
541
|
-
|
542
|
-
"x\\"=y
|
543
|
-
|
544
|
-
If quoting were omitted the equals character (separating the
|
545
|
-
entry name `x` from the value `y`) would be escaped.
|
546
|
-
|
547
|
-
|