1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
|
#Please insert up references in the next lines (line starts with keyword UP)
UP arb.hlp
UP glossary.hlp
#Please insert subtopic references (line starts with keyword SUB)
SUB aci.hlp
# Hypertext links in helptext can be added like this: LINK{ref.hlp|http://add|bla@domain}
#************* Title of helpfile !! and start of real helpfile ********
TITLE Unittest example helpfile
OCCURRENCE nowhere
DESCRIPTION This is the first paragraph of the description.
It may be continued on the next line.
Another paragraph
also
belonging to description. It is followed by
an enumeration on the same indentation level:
1. first enum
2. second enum which
is continued on the next line.
Now this is no longer misinterpreted as monospaced paragraph.
3. third enum
Again a paragraph - a one liner followed by an item list. It is no longer misplaced now!
- item 1
- item 2
- item 3
contains 2 lines
SECTION CUSTOM A custom section.
Acts like DESCRIPTION, despite the SECTION line will be part of the headline.
In DESCRIPTION it would be part of the first paragraph.
First i need to check proper support for different
indentation levels.
This paragraph has to be indented one level deeper than
the previous paragraph.
That paragraph should be on
the same level.
Here is another one, even deeper.
Same,
same.
Back one step.
One step down - ignoring deeper
indentation in source.
Consecutive paragraphs are only placed on the same
level if their indentation matches.
Using the indentation level used 4 paragraphs above, wont help here.
But the "wrong" indentation of the previous
paragraph forces this paragraph to get indented one
level deeper than the paragraphs before.
This does not step back.
same same.
Back to top (end of indentation tests).
SECTION Wanted fixes
Paragraphs containing multiple spaces will be
treated as monospaced. This is done to support
tabular information like the following:
other
column column
row 1 2
row2 - 3
Problems occur if there are empty lines inside such a table, like here:
other
column column
row 1 2
row2 - 3
(should better be combined)
Here is an itemlist whose items are triggered by '*':
* item1
continued on next line
* item2
* item3
Itemlist containing paragraphs under some items
- item 1
- item 2
This is a short
description of item 2.
This description gets indented below the corresponding item.
- item 3
This is a shorter description of item 3.
This is a paragraph which should
be placed outside the itemlist.
Currently this is misinterpreted as part of the itemlist.
And this paragraph should be back where we were before
the itemlist began.
Enumeration also work if using letters
instead of digits. You can use capital letters as in
the following enum
A. first enum
B. 2nd enum
C. third enum
D. last enum
or small letters like here:
a. first enum
b. 2nd enum
c. third enum
d. last enum
Check some "illegal" itemlists:
----------------------
-noitem
- eithernoitem
**********************
*noitem
* eithernoitem
SECTION FEATURE TESTS
Here all existing helpfile features should be tested:
- first testing an inlined
link to another help file: LINK{srt.hlp}
- and a link to the arb homepage
LINK{http://www.arb-home.de/}
followed by text.
- arb help also supports mail-links (like LINK{devel@arb-home.de}).
All 3 sorts of links should be clickable in the html version.
SECTION NESTED LISTS
text before enum
1. first enum
text below first enum
- first item below first enum
- second item below first enum
1. first subenum below second item
- first item below first subenum
- second item below first subenum
2. second subenum below second item
text before subsubenum
1. first subsubenum below second subenum
2. second subsubenum below second subenum
text behind subsubenum
3. third subenum below second item
- third item below first enum
2. second enum
This text is not indented more than the second enum,
but is nevertheless interpreted as sub-elements which
belongs to the enum.
3. third enum
behind the last enum, text only becomes a son
of the enum-entry if it is indented.
text behind enum
NOTES Note that this test may help me.
EXAMPLES The whole file is just an example.
WARNINGS This text wont help you.
Even if i add more paragraphs here,
it will not get more useful.
BUGS will be detected by the unit test
checking the files into which
this file gets converted.
|
