Issue 313: Source code output in Windows command prompt http://bitbucket.org/tortoisehg/stable/issue/313/source-code-output-in-windows-command
Joongi Kim / daybreaker on Sun, 21 Jun 2009 09:38:10 +0200: Changes: content: When I use command-line interface, I often use `hg diff`. But because Windows command prompt uses local encoding only (for example, cp949 for Korean), unicode (utf-8) source files are crashed. Typing non-ASCII commit logs in command-line (like `hg commit -m "blah blah") are OK and well-translated to utf-8 encoding correctly. I hope there be a kind of fallback processing for Windows command prompt output that converts utf-8 encoded source code to local encodings. If there are not convertible characters, just marking them as '?' would be ok. -> When I use command-line interface, I often use `hg diff`. But because Windows command prompt uses local encoding only (for example, cp949 for Korean), unicode (utf-8) source files are crashed. Typing non-ASCII commit logs in command-line (like `hg commit -m "blah blah") are OK and well-translated to utf-8 encoding correctly. I hope there be a kind of fallback processing for Windows command prompt output that converts utf-8 encoded source code to local encodings. If there are not convertible characters, just marking them as '?' would be ok. -- This is an issue notification from bitbucket.org. You are receiving this either because you are the owner of the issue, or you are following the issue. ------------------------------------------------------------------------------ Are you an open source citizen? Join us for the Open Source Bridge conference! Portland, OR, June 17-19. Two days of sessions, one day of unconference: $250. Need another reason to go? 24-hour hacker lounge. Register today! http://ad.doubleclick.net/clk;215844324;13503038;v?http://opensourcebridge.org _______________________________________________ Tortoisehg-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
