Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Windows executable does not handle non-ascii file names correctly #6587

Closed
sgjesse opened this issue Nov 7, 2012 · 3 comments
Closed

Windows executable does not handle non-ascii file names correctly #6587

sgjesse opened this issue Nov 7, 2012 · 3 comments
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-cannot-reproduce Closed as we were unable to reproduce the reported issue closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)

Comments

@sgjesse
Copy link
Contributor

sgjesse commented Nov 7, 2012

Running

> dart.exe æøå.dart

fails with:

Dart_NewStringFromUTF8 expects argument 'str' to be valid UTF-8.
@sgjesse
Copy link
Contributor Author

sgjesse commented Nov 7, 2012

The same issue exists with dart:io files, running

main() {
  new File("æøå.dart").openInputStream();
}

also fails with:

Dart_NewStringFromUTF8 expects argument 'str' to be valid UTF-8.

@iposva-google
Copy link
Contributor

Removed Priority-Medium label.
Added Priority-Unassigned label.

@sgjesse sgjesse added Type-Defect area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. labels Jun 5, 2013
@iposva-google iposva-google changed the title Windows executable does not hanle non-ascii file names corectly Windows executable does not handle non-ascii file names corectly Dec 8, 2015
@iposva-google iposva-google mentioned this issue Dec 8, 2015
Closed
@iposva-google iposva-google changed the title Windows executable does not handle non-ascii file names corectly Windows executable does not handle non-ascii file names correctly Dec 8, 2015
@kevmoo kevmoo added type-bug Incorrect behavior (everything from a crash to more subtle misbehavior) and removed priority-unassigned labels Feb 29, 2016
@zanderso zanderso added closed-obsolete Closed as the reported issue is no longer relevant closed-cannot-reproduce Closed as we were unable to reproduce the reported issue labels Jun 15, 2016
@zanderso
Copy link
Member

I tried these examples on Windows, and saw no errors.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area-vm Use area-vm for VM related issues, including code coverage, FFI, and the AOT and JIT backends. closed-cannot-reproduce Closed as we were unable to reproduce the reported issue closed-obsolete Closed as the reported issue is no longer relevant type-bug Incorrect behavior (everything from a crash to more subtle misbehavior)
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@kevmoo @sgjesse @iposva-google @zanderso