You can follow along with my presentation right here
UTF-8 for OS X
OS X by default supports UTF-8 in the command line. But… sometimes it doesn’t? So we’ll add a few commands that will run every time you start the shell that forces UTF-8.
If you’re typing instead of cutting and pasting, make sure you use
>> — two greater-than symbols — not
». Also, be sure to hit enter after pasting in the second line.
echo 'export LC_ALL=en_US.UTF-8' >> ~/.bash_profile echo 'export LANG=en_US.UTF-8' >> ~/.bash_profile
If you do it right, it won’t say anything (but I promise it worked!).
Adding UTF-8 support to Command Prompt in Windows
chcp 65001 and suddenly it will work. But if you close your window you’re going to have to do it again!
Also, open up Default Settings by clicking the top left-hand corner and change the font to Lucida Console (or the other one with a name).
Adding automatic UTF-8 support to Command Prompt in Windows
Create a new shortcut for
cmd.exe. Right-click the icon, then change the “Target” and “Start in” to match this image:
Then select Advanced and set it to run as an Administrator.
Also, open up Default Settings from the Command Prompt by clicking the top left-hand corner and change the font to Lucida Console (or the other one with a name).