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

Last change on this file was 19575, checked in by westram, 4 weeks ago
  • reintegrates 'help' into 'trunk'
    • preformatted text gets checked for width now (to enforce it fits into the arb help window).
    • fixed help following these checks, using the following steps:
      • ignore problems in foreign documentation.
      • increase default help window width.
      • introduce control comments to
        • accept oversized preformatted sections.
        • enforce preformatted style for whole sections.
        • simply define single-line preformatted sections
          Used intensive for definition of internal script languages.
    • fixed several non-related problems found in documentation.
    • minor layout changes for HTML version of arb help (more compacted; highlight anchored/all sections).
    • refactor system interface (GUI version) and use it from help module.
  • adds: log:branches/help@19532:19574
File size: 5.6 KB
Line 
1# Generated from XML with xsltproc -- Stylesheet by Ralf Westram (ralf@arb-home.de)
2#
3#  ****  DO NOT EDIT (edit in $(ARBHOME)/HELP_SOURCE/source 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 the next
31    line.
32
33    Another paragraph also belonging to description. It is followed by an enumeration on
34    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 longer
39       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 longer misplaced
44    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 headline. In
57    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 previous paragraph.
62
63        That paragraph should be on the same level.
64
65            Here is another one, even deeper.
66
67            Same, same.
68
69        Back one step.
70
71            One step down - ignoring deeper indentation in source.
72
73            Consecutive paragraphs are only placed on the same level if their
74            indentation matches.
75
76            Using the indentation level used 4 paragraphs above, wont help here.
77
78                But the "wrong" indentation of the previous paragraph forces this
79                paragraph to get indented one level deeper than the paragraphs before.
80
81                This does not step back.
82
83                same same.
84
85    Back to top (end of indentation tests).
86
87
88
89Wanted fixes
90
91    Paragraphs containing multiple spaces will be treated as monospaced. This is done to
92    support tabular information like the following:
93
94                            other
95                column      column
96        row     1           2
97        row2    -           3
98
99    Problems occur if there are empty lines inside such a table, like here:
100
101                    other
102        column      column
103
104        row     1           2
105        row2    -           3
106
107        (should better be combined)
108
109    Here is an itemlist whose items are triggered by '*':
110
111        * item1 continued on next line
112
113        * item2
114
115        * item3
116
117    Itemlist containing paragraphs under some items
118
119        * item 1
120
121        * item 2
122
123            This is a short description of item 2. This description gets indented below
124            the corresponding item.
125
126        * item 3
127
128            This is a shorter description of item 3.
129
130        This is a paragraph which should be placed outside the itemlist. Currently this
131        is misinterpreted as part of the itemlist.
132
133    And this paragraph should be back where we were before the itemlist began.
134
135    Enumeration also work if using letters instead of digits. You can use capital
136    letters as in the following enum
137
138    A. first enum
139
140    B. 2nd enum
141
142    C. third enum
143
144    D. last enum
145
146    or small letters like here:
147
148        a. first enum
149
150        b. 2nd enum
151
152        c. third enum
153
154        d. last enum
155
156    Check some "illegal" itemlists:
157
158        ----------------------
159
160        -noitem
161
162        -  eithernoitem
163
164        **********************
165
166        *noitem
167
168        *  eithernoitem
169
170
171
172FEATURE TESTS
173
174    Here all existing helpfile features should be tested:
175
176        * first testing an inlined link to another help file: 'Search and Replace Tool
177          (SRT)'
178
179        * and a link to the arb homepage http://www.arb-home.de/ followed by text.
180
181        * arb help also supports mail-links (like devel@arb-home.de [mailto:
182          devel@arb-home.de subject: 'Concerning helppage unittest.xml']). All 3 sorts
183          of links should be clickable in the html version.
184
185
186
187NESTED LISTS
188
189    text before enum
190
191    1. first enum
192
193        text below first enum
194
195        * first item below first enum
196
197        * second item below first enum
198
199            1. first subenum below second item
200
201                * first item below first subenum
202
203                * second item below first subenum
204
205            2. second subenum below second item
206
207                text before subsubenum
208
209                1. first subsubenum below second subenum
210
211                2. second subsubenum below second subenum
212
213                text behind subsubenum
214
215            3. third subenum below second item
216
217        * third item below first enum
218
219    2. second enum
220
221        This text is not indented more than the second enum, but is nevertheless
222        interpreted as sub-elements which belongs to the enum.
223
224    3. third enum
225
226        behind the last enum, text only becomes a son of the enum-entry if it is
227        indented.
228
229    text behind enum
230
231
232
233NOTES
234
235    Note that this test may help me.
236
237
238
239EXAMPLES
240
241    The whole file is just an example.
242
243
244
245WARNINGS
246
247    This text wont help you.
248
249    Even if i add more paragraphs here, it will not get more useful.
250
251
252
253BUGS
254
255    will be detected by the unit test checking the files into which this file gets
256    converted.
257
Note: See TracBrowser for help on using the repository browser.