Fair enough. I can't remember when I've had that not work, though. I've seen a lot of software that deliberately treats ALT-160, ALT-32 and ALT-255 the same way.
Cross platform support should be tested, definitely. -ASB: http://XeeSM.com/AndrewBaker On Thu, Jun 10, 2010 at 2:03 PM, Ben Scott <[email protected]> wrote: > On Thu, Jun 10, 2010 at 1:41 PM, Andrew S. Baker <[email protected]> > wrote: > > Easiest Approach > > ECHO <ALT-255> >C:\Temp\FileName.TXT > > {where <ALT-255> is the actual character, not that whole text} > > That's fine for human consumption on a Windows box, but be aware that: > > (1) If the character is going to be consumed by software, character > 255 is not the same as ASCII space, and will likely be interpreted > differently. > > (2) If this will end up in an email, web page, or other network thing, > the non-ASCII character is likely to make things very interesting. > > Myself, if I had to do this, I would prolly use GECHO.EXE (the GNU > "echo" utility from http://unxutils.sf.net/), but only because I > already have that close to hand. There are prolly other ways that > don't require a third-party utility. > > gecho " " > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
