okay before i explain anything i just want to say that this is not what im talking about.

@echo off
echo ÉÍËÍ» ÚÄÂÄ¿ ÖÄÒÄ· ÕÍÑ͸
echo º º º ³ ³ ³ º º º ³ ³ ³
echo ÌÍÎ͹ ÃÄÅÄ´ ÇÄ×Ķ ÆÍØ͵
echo º º º ³ ³ ³ º º º ³ ³ ³
echo ÈÍÊͼ ÀÄÁÄÙ ÓÄÐĽ ÔÍÏ;

it is unicode but the batch file is saved in ANSI format.
im trying to find out how to make it execute properly in unicode format.

i found a program online that CONVERTS regular batch code into complete Unicode, while at the same time can be saved as unicode format as well as execute properly as an batch file.

here is an example

਍汣൳䀊捥潨漠晦਍楴汴⁥湵捩摯൥挊汯牯〠ൡ琊浩潥瑵⼠⁴″港扯敲歡਍捥潨吠楨⁳獩愠甠楮潣敤戠瑡档映汩൥瀊畡敳ഠ攊档湡⁹潣浭湡⁤慣敢洠摡⁥湵敲摡汢⁥湩琠硥⁴摥瑩牯⹳਍慰獵൥

copy and paste the above code in notepad (or WHATEVER) and right before you save a name and EXTENSION to the file look below to find and enable the Unicode option or else it will not work.

okay if you have done everything right, it should have posted some green text stating "This is a unicode batch file", "any command can be made unreadable in text editors." any my question is does anyone know how to do this or any information on where i can find out how this works because ive looked everywhere on the internet and no hope has yet to come.thanksThere ya go talkin to yourself again...1. Prepend normal text/batch file with "ÿþ"

2. Close and re-OPEN the file.

It's not ACTUALLY unicode, the only difference is that the byte characters FF FE are a "BOM" or Byte Order Mark. At the start of text file it means the file is unicode and what order the bytes should be expected in. If you open a file starting with a BOM, the editor will figure it's Unicode- so Notepad, and most other text editors, will open your file as if it was.

Command prompt doesn't care about unicode and treats the BOM as whitespace when it interprets it.

Quote from: BC_Programmer on February 24, 2016, 05:06:29 PM

1. Prepend normal text/batch file with "ÿþ"

2. Close and re-open the file.

It's not actually unicode, the only difference is that the byte characters FF FE are a "BOM" or Byte Order Mark. At the start of text file it means the file is unicode and what order the bytes should be expected in. If you open a file starting with a BOM, the editor will figure it's Unicode- so Notepad, and most other text editors, will open your file as if it was.

Command prompt doesn't care about unicode and treats the BOM as whitespace when it interprets it.