View Single Post
Old 09-10-2009, 10:59 AM   #286
DaleDe
Grand Sorcerer
DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.DaleDe ought to be getting tired of karma fortunes by now.
 
DaleDe's Avatar
 
Posts: 11,470
Karma: 13095790
Join Date: Aug 2007
Location: Grass Valley, CA
Device: EB 1150, EZ Reader, Literati, iPad 2 & Air 2, iPhone 7
Quote:
Originally Posted by Jad View Post
Hi DaleDe,

I've had a play in the code and tried building the batch file using unicode. The text appears correctly in the command prompt now if you do a 'type' command on the file, but when you execute the batch file it outputs corrupted symbols. I've done quite a bit of googling and can't seem to find a definative answer to supporting special characters in the CMD process. I may need to nest a seperate command call as you can flag unicode output. Any ideas anyone.
I do not believe there is any support for unicode in the CMD process. Certain commands may support it but the shell processing it very likely to fail. The symbols are not exactly corrupted but rather are being reported on byte at a time as would be expected by a process that does not understand unicode. I suspect this is not a solvable problem with the current shell.

Dale
DaleDe is offline   Reply With Quote