I've seen a few instances where text lists - such as response codes and 10 codes - that read like one long string when you view them in the database are being unloaded into the wiki, and end up reading the same way. This makes such lists very hard to read and should be avoided.
However the fix is pretty simple. Put a '*' (shift of 8) in front of each item to be listed. This is somewhat like the <ul> (unordered list) command in HTML. It's coded like this;
* Item 1
* Item 2
* Item 3
and so on. The nice thing about this feature is that each item ends with a soft break, so you don't need to code a <br> after each one; however depending on how you are organizing your lists, you may need a <br> at the very end of the list to be able to terminate it. Here's an example;
http://wiki.radioreference.com/index.php/Scanning_101
You can also put it into a table (wiki markup or HTML if you're more comfortable with it), since it's rather unlikely that things like 10 codes or response codes change very much (which is generally the best kind of data to put into a table, since tables tend to be a bit harder to maintain).
If your list represents a logical progression of steps, then creating a numbered list is the way to go. You do that with a '#' (shift of 3) in the first column. Here's an example of a numbered list;
http://wiki.radioreference.com/index...al_to_Software
The choice of how you go about it is yours - but please, consider readability when you post straight text lists. 73 Mike
unloading text files from the database
Linear Mode
