Code Samples - Maintaining Spaces WITHIN code
Posted: Wed May 21, 2008 2:05 pm
I have a project in Flare where code samples need to be placed in various locations. There are hundreds of these rather small samples to place.
Currently, the samples themselves live in one big Word document. The code samples must be moved into their relevant context within the larger project being written in Flare. The samples in Word contain many instances of non-breaking spaces. It is imperative that all of the non-breaking spaces be preserved when the code samples moved into Flare, as they represent specific amounts of field padding relating to databases.
Cutting and pasting from Word into Flare results in all of the non-breaking spaces (in Word) being compressed to one space (in Flare). I understand that Flare, being an XML editor, is going to compress multiple spaces into one space. Is there a way (either using cut and paste or by some other method) to get Flare to recognize when non-breaking spaces are being moved into the editor?
I'm using Flare 3.1. The target output is Word, though I've not even gotten to working with this in the output.
Currently, the samples themselves live in one big Word document. The code samples must be moved into their relevant context within the larger project being written in Flare. The samples in Word contain many instances of non-breaking spaces. It is imperative that all of the non-breaking spaces be preserved when the code samples moved into Flare, as they represent specific amounts of field padding relating to databases.
Cutting and pasting from Word into Flare results in all of the non-breaking spaces (in Word) being compressed to one space (in Flare). I understand that Flare, being an XML editor, is going to compress multiple spaces into one space. Is there a way (either using cut and paste or by some other method) to get Flare to recognize when non-breaking spaces are being moved into the editor?
I'm using Flare 3.1. The target output is Word, though I've not even gotten to working with this in the output.