You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+59-5Lines changed: 59 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -348,14 +348,17 @@ Input files can be in one of six formats:
348
348
349
349
* A CSV file that is already in a format supported by iThoughts' Import function.
350
350
* A flat file where each line is a new node. Spaces and tabs can be used to indent the text. Here the level of indentation is used to control what level the line is added at.
351
-
* A Markdown nested list where each line is a new node. Spaces and tabs can be used to indent the text. Here the level of indentation is used to control what level the line is added at. Only an asterisk (`*`) followed by a space is supported as a list item marker.
351
+
* A Markdown nested list where each line is a new node. Spaces and tabs can be used to indent the text. Here the level of indentation is used to control what level the line is added at. Either an asterisk (`*`) or a minus sign followed by a space are supported as a list item marker. \
352
+
Further, Markdown headings of one type, described below, can be used.
352
353
* An OPML XML file - with or without `head` or `body` elements.
353
354
* An XML file, including one with namespaces (both default and named).
354
355
* A CSV file where the hierarchy is described by how many empty cells are to the left of the first cell with text in.
355
356
356
357
#### Nesting Level Detection
357
358
358
-
When parsing a Markdown or tab/space-indented non-CSV file the first line with leading white space (spaces and/or tabs) is used to detect the indentation scheme: Any white space on this line is used as a single indentation level marker. It is expected that all lines are indented in the same way.
359
+
When parsing a Markdown or tab/space-indented non-CSV file the first line with leading white space (spaces and/or tabs) is used to detect the indentation scheme: \
360
+
Any white space on this line is used as a single indentation level marker. \
361
+
It is expected that all lines are indented in the same way.
359
362
360
363
For example, if the second line starts with two spaces this is taken to indicate that every line will have zero, two, four, etc spaces:
361
364
@@ -364,13 +367,52 @@ For example, if the second line starts with two spaces this is taken to indicate
364
367
* Four spaces denotes a level 2 node
365
368
* And so on
366
369
367
-
If the file is detected to contain Markdown, leading dashes and asterisks followed by a single space are removed. (These are bulleted list markers in Markdown.) For example:
370
+
If the file is detected to contain Markdown, leading dashes and asterisks followed by a single space are removed. \
371
+
(These are bulleted list markers in Markdown.) \
372
+
For example:
368
373
369
374
* A
370
375
* A1
371
376
372
377
leads to the input file being interpreted as a level 0 node with text "A" and its child node with text "A1".
373
378
379
+
You can also specify nesting levels using one of the two forms of heading that Markdown supports. \
380
+
Consider the following example:
381
+
382
+
# Fruit
383
+
384
+
## Citrus
385
+
386
+
* Lemon
387
+
* Orange
388
+
* Vaguely orange-like
389
+
* Mandarin
390
+
* Satsuma
391
+
392
+
In this example:
393
+
394
+
* "Fruit" is a Heading Level 0 node.
395
+
* "Citrus" is a Heading Level 1 node.
396
+
* "Lemon", "Orange" and "Vaguely orange-like" are Heading Level 2 nodes.
397
+
* "Mandarin" and "Satsuma" are Heading Level 3 nodes.
398
+
* The blank lines in between are ignored.
399
+
* The leading `#` and `*` characters are removed, as are the first space after each occurrence.
0 commit comments