Not too long ago, I had to fix the command line output for tf.exe, the Team Foundation Version Control command line app, so that output would be formatted properly for console windows (cmd.exe) using double-byte code pages.<\/p>\n
The code originally computed the output display width as the length of the string. However, that’s not correct when the code is running on a Japanese Windows system, for example. Whereas English letters all take up one position in the console window, double-byte characters are twice as wide and take two positions. The original code produced really bad looking output.<\/p>\n
To make sure that I got the right solution, I asked Aldo<\/a>, an internalization PM. The solution was to use the number of bytes that would result from converting the string to a byte array using the console window’s code page. Each English letter results in a byte, and each Japanese character results in two bytes.<\/p>\n For single-byte code pages, the double-byte characters only take up one position, because they get munged due to the console not being able to display them. The .NET System.Text.Encoding<\/a> class handles properly converting strings to and from byte arrays. Of course, I didn’t need an actual byte array. Fortunately, the Encoding class has a method called GetByteCount()<\/a> that gives the information I need.<\/p>\n The end result is the following simple method that calculates the display width of a string in the console’s encoding.<\/p>\n static int CalculateConsoleWidth(String text) if (encoding.IsSingleByte) Not too long ago, I had to fix the command line output for tf.exe, the Team Foundation Version Control command line app, so that output would be formatted properly for console windows (cmd.exe) using double-byte code pages. The code originally computed the output display width as the length of the string. However, that’s not correct when […]<\/p>\n","protected":false},"author":94,"featured_media":10268,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":""},"categories":[1],"tags":[2],"class_list":["post-4853","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-c"],"acf":[],"blog_post_summary":" Not too long ago, I had to fix the command line output for tf.exe, the Team Foundation Version Control command line app, so that output would be formatted properly for console windows (cmd.exe) using double-byte code pages. The code originally computed the output display width as the length of the string. However, that’s not correct when […]<\/p>\n","_links":{"self":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/4853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/users\/94"}],"replies":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/comments?post=4853"}],"version-history":[{"count":0,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/posts\/4853\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media\/10268"}],"wp:attachment":[{"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/media?parent=4853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/categories?post=4853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/devblogs.microsoft.com\/buckh\/wp-json\/wp\/v2\/tags?post=4853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}
{
Encoding encoding = Console.Out.Encoding;<\/p>\n
{
return text.Length;
}
else
{
return encoding.GetByteCount(text);
}
}<\/font><\/p><\/p>\n","protected":false},"excerpt":{"rendered":"