[Mono-bugs] [Bug 80838][Nor] Changed - Process.StandardOutput not always using the correct encoding

[bugzilla-daemon at bugzilla.ximian.com]

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by kornelpal at gmail.com.

http://bugzilla.ximian.com/show_bug.cgi?id=80838

--- shadow/80838	2007-02-13 15:38:30.000000000 -0500
+++ shadow/80838.tmp.28602	2007-02-13 16:06:02.000000000 -0500
@@ -1,14 +1,14 @@
 Bug#: 80838
 Product: Mono: Class Libraries
 Version: 1.2
-OS: 
+OS: unknown
 OS Details: 
 Status: NEW   
 Resolution: 
-Severity: 
+Severity: Unknown
 Priority: Normal
 Component: CORLIB
 AssignedTo: mono-bugs at ximian.com                            
 ReportedBy: lluis at ximian.com               
 QAContact: mono-bugs at ximian.com
 TargetMilestone: ---
@@ -80,6 +80,18 @@
 output, which is actually latin2.
 
 ------- Additional Comments From lluis at ximian.com  2007-02-13 15:32 -------
 Created an attachment (id=18693)
 Proposed fix.
 
+
+------- Additional Comments From kornelpal at gmail.com  2007-02-13 16:06 -------
+To be user friendly (that is the expected behavior) 
+Process.StandardInput should use Console.InputEncoding, 
+Process.StandardOutput and Process.StandardError should use 
+Console.OutputEncoding instead of UTF-8 or Encoding.Default or other 
+things not directly related to console.
+
+Alternatively the same detection method found in Console could be 
+used. (Windows console encodings usually differ from 
+Encoding.Default and there is some UTF-8 supporting code for Unix 
+console as well.)