QBasic / QB64 Discussion Forum      Other Subforums, Links and Downloads
 Return to Index  

Post without losing leading and embedded spaces

October 26 2003 at 2:25 PM
  (Login Mac36)

FAQ001 = How do I post on the QBasic Forum
FAQ002 = How can I post without losing leading and embedded spaces?

Method 1
========

1. Get your program into the Clipboard
2. Click on CallURL* and select option Double-Spaces
3. Paste on forum

* It's that simple. To download CallURL, see the Links&Downloads section of the forum

Method 2
========

1. Save your program as an ASCII file.
   For example, in QBasic 1.0, Click on File, Save.
2. Edit your program with NOTEPAD
   or it's equivalent on other platforms.
3. Do a global replace
   Find What:    <space><space>   (double space)
   Replace With: ASC(???)ASC(???) (double non-breaking space)
4. Also do a replace on any single spaces that start a line.
4. Take the result and post in QBasic Forum.
5. Exit from the editor without changing your original program.

To enter ASC(???),
  Hold down the ALT key
  Using the Numeric Keypad, enter 0160 (leading zero required).
    (Do not use the row of numbers at the top of the keyboard)
  Release the ALT key.
Something that looks like a space will appear.  

Why replace two blanks? Because only pairs of blanks are a problem on the Forum. There is no need to replace every single blank in your program. However, if you have any lines that start with a single blank, then you should replace all blanks, or specially fix the single blank.

Note: At one point, I recommended ALT-255. Based on input from Note based on input from stylez, JT, and PhyloGenesis, I found that this only worked on WindowsNT. Then someone recommended ALT+0126, but this also seems to work only on some systems. So now the FAQ has been updated to recomment ALT+0160 which seems to work universally.


    
This message has been edited by Mac36 on Jul 22, 2004 5:22 AM
This message has been edited by iorr5t on Apr 5, 2004 10:53 AM
This message has been edited by iorr5t on Oct 30, 2003 5:35 PM


 
 Respond to this message   
Responses