You don't tell the purpose of getting those characters in a batch file to begin with. If that's for making or checking pathnames on disk, then all you need is to get the codepage matching between the editor used to save the batch file, and the cmd prompt used to execute it. If it's for echo and console display purposes, you additionally need a font which carries those characters.
MrKnowItAllxx wrote:I just want to get extended ascii characters like ▓ ▒ ░ into batch, but I am unable to save files with such characters
Use a better editor, then
one which allows you to choose the target codepage.
Barring that, paste your characters into Notepad, Save-As with encoding set to Unicode, choose a name say "etc.txt". Then open a cmd prompt, "chcp 437" (replace "437" by the codepage you want), then "type etc.txt >etc-437.txt". At this point, "etc-437.txt" would be an 8-bit extended-ASCII text file saved in codepage 437.
However, I don't think that's the question you really meant to ask.
MrKnowItAllxx wrote:I don't know what chart online would tell me other characters like that which are interpreted as extended ascii characters in batch.
Batch files are 8-bit text, and all characters are interpreted. However, the _interpretation_ of character codes above 127 depends on the active codepage, because there is no single "extended ASCII" standard.
You can find the mappings for different codepages at http://msdn.microsoft.com/en-us/goglobal/bb964653, for example
- http://msdn.microsoft.com/en-us/goglobal/cc305156 (OEM 437);
- http://msdn.microsoft.com/en-us/goglobal/cc305145 (ANSI 1252).
MrKnowItAllxx wrote:Found what I need here: http://www.jimprice.com/jim-asc.shtml ... "Microsoft Windows ® has a different notion about what the high-order (upper 128) characters are"
That's not a bad summary, but it works better if one is already familiar with the 7-bit-ASCII vs 8-bit-extended matters, and the mechanics of Unicode mappings.
Liviu