source: branches/alilink/UNIT_TESTER/run/help/unittest.hlp

Last change on this file was 13998, checked in by westram, 9 years ago
File size: 5.6 KB
Line 
1# Generated from XML with Sablotron -- Stylesheet by Ralf Westram (ralf@arb-home.de)
2#
3#  ****  DO NOT EDIT (edit in $(ARBHOME)/HELP_SOURCE/oldhelp instead)  ****
4#
5# This page was converted by arb_help2xml and may look strange.
6# If you think it's really bad, please send a
7# mail [mailto: helpfeedback@arb-home.de  subject: 'Helppage unittest.xml looks weird']
8# to our help keeper.
9
10# UP references:
11UP                  arb.hlp
12UP                  glossary.hlp
13
14# SUB references:
15SUB                 aci.hlp
16SUB                 srt.hlp
17
18# ------------------------------------------------------------
19# Start of real helpfile:
20TITLE   Unittest example helpfile
21
22OCCURRENCE
23
24    nowhere
25
26
27
28DESCRIPTION
29
30    This is the first paragraph of the description. It may be continued on
31    the next line.
32
33    Another paragraph also belonging to description. It is followed by an
34    enumeration on the same indentation level:
35
36    1. first enum
37
38    2. second enum which is continued on the next line. Now this is no
39       longer misinterpreted as monospaced paragraph.
40
41    3. third enum
42
43    Again a paragraph - a one liner followed by an item list. It is no
44    longer misplaced now!
45
46    * item 1
47
48    * item 2
49
50    * item 3 contains 2 lines
51
52
53
54CUSTOM    A custom section.
55
56    Acts like DESCRIPTION, despite the SECTION line will be part of the
57    headline. In DESCRIPTION it would be part of the first paragraph.
58
59    First i need to check proper support for different indentation levels.
60
61        This paragraph has to be indented one level deeper than the
62        previous paragraph.
63
64        That paragraph should be on the same level.
65
66            Here is another one, even deeper.
67
68            Same, same.
69
70        Back one step.
71
72            One step down - ignoring deeper indentation in source.
73
74            Consecutive paragraphs are only placed on the same level if
75            their indentation matches.
76
77            Using the indentation level used 4 paragraphs above, wont help
78            here.
79
80                But the "wrong" indentation of the previous paragraph
81                forces this paragraph to get indented one level deeper than
82                the paragraphs before.
83
84                This does not step back.
85
86                same same.
87
88    Back to top (end of indentation tests).
89
90
91
92Wanted fixes
93
94    Paragraphs containing multiple spaces will be treated as monospaced.
95    This is done to support tabular information like the following:
96
97                            other
98                column      column
99        row     1           2
100        row2    -           3
101
102    Problems occur if there are empty lines inside such a table, like here:
103
104                    other
105        column      column
106
107        row     1           2
108        row2    -           3
109
110        (should better be combined)
111
112    Here is an itemlist whose items are triggered by '*':
113
114        * item1 continued on next line
115
116        * item2
117
118        * item3
119
120    Itemlist containing paragraphs under some items
121
122        * item 1
123
124        * item 2
125
126            This is a short description of item 2. This description gets
127            indented below the corresponding item.
128
129        * item 3
130
131            This is a shorter description of item 3.
132
133        This is a paragraph which should be placed outside the itemlist.
134        Currently this is misinterpreted as part of the itemlist.
135
136    And this paragraph should be back where we were before the itemlist
137    began.
138
139    Enumeration also work if using letters instead of digits. You can use
140    capital letters as in the following enum
141
142    A. first enum
143
144    B. 2nd enum
145
146    C. third enum
147
148    D. last enum
149
150    or small letters like here:
151
152        a. first enum
153
154        b. 2nd enum
155
156        c. third enum
157
158        d. last enum
159
160    Check some "illegal" itemlists:
161
162        ----------------------
163
164        -noitem
165
166        -  eithernoitem
167
168        **********************
169
170        *noitem
171
172        *  eithernoitem
173
174
175
176FEATURE TESTS
177
178    Here all existing helpfile features should be tested:
179
180        * first testing an inlined link to another help file: 'Search and
181          Replace Tool (SRT)'
182
183        * and a link to the arb homepage http://www.arb-home.de/ followed
184          by text.
185
186        * arb help also supports mail-links (like devel@arb-home.de
187          [mailto: devel@arb-home.de subject: 'Concerning helppage
188          unittest.xml']). All 3 sorts of links should be clickable in the
189          html version.
190
191
192
193NESTED LISTS
194
195    text before enum
196
197    1. first enum
198
199        text below first enum
200
201        * first item below first enum
202
203        * second item below first enum
204
205            1. first subenum below second item
206
207                * first item below first subenum
208
209                * second item below first subenum
210
211            2. second subenum below second item
212
213                text before subsubenum
214
215                1. first subsubenum below second subenum
216
217                2. second subsubenum below second subenum
218
219                text behind subsubenum
220
221            3. third subenum below second item
222
223        * third item below first enum
224
225    2. second enum
226
227        This text is not indented more than the second enum, but is
228        nevertheless interpreted as sub-elements which belongs to the enum.
229
230    3. third enum
231
232        behind the last enum, text only becomes a son of the enum-entry if
233        it is indented.
234
235    text behind enum
236
237
238
239NOTES
240
241    Note that this test may help me.
242
243
244
245EXAMPLES
246
247    The whole file is just an example.
248
249
250
251WARNINGS
252
253    This text wont help you.
254
255    Even if i add more paragraphs here, it will not get more useful.
256
257
258
259BUGS
260
261    will be detected by the unit test checking the files into which this
262    file gets converted.
263
Note: See TracBrowser for help on using the repository browser.