Comment 1:

It would be nice if we got the English text all the time on Windows,
to match the behavior on other systems.  Is it possible to ask for
non-localized error text?  Or else we could just hard-code a table
of error strings like we do for Unix?

Owner changed to @alexbrainman.

Status changed to Accepted.

Comment 2:

<peterGo-hat-on> <g>
From http://golang.org/doc/go_tutorial.html:
Now we can compile and run the program. On Unix, this would be the result:
    $ 6g file.go                       # compile file package
    $ 6g helloworld3.go                # compile main package
    $ 6l -o helloworld3 helloworld3.6  # link - no need to mention "file"
    $ helloworld3
    hello, world
    can't open file; err=No such file or directory
    $
Please, note the "Unix" bit. There is no promise the message will be the same everywhere.
<peterGo-hat-off>
In fact, building on my English Windows OS displays similar error message:
$ ./run
helloworld3 failed: "hello, world can't open file; err=The system cannot find the path
specified." is not "hello, world can't open file; err=no such file or directory"
$ 
The error doesn't stop the build, the build completes successfully.
I've never tried, but it looks to me, we can ask for error message to be always English
- see dwLanguageId parameter of FormatMessage. I believe, we use "default" language at
this moment, it is something that "user" wants. It is hard for me to make a judgement
(my default language is English), but I think it works the way it is intended.
Alex

Comment 3:

I am pretty sure your problem is a dup of 1899. Please, let me know if you think
different. Thank you.
Alex

Status changed to Duplicate.

Merged into issue #1899.

Comment 4:

This is not a duplicate of issue #1899. It should still be an open issue. For example,
go printout messy code
http://groups.google.com/group/golang-nuts/browse_thread/thread/cf9727737e5b4a00

Comment 5:

How about we will change the summary ...

Labels changed: added priority-someday, os-windows, removed priority-medium.

Status changed to HelpWanted.

Comment 7:

This issue was closed by revision b17a233.

Status changed to Fixed.