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

Encoding class does not support UTF- encodings #11744

Open
munificent opened this Issue Jul 8, 2013 · 6 comments

Comments

Projects
None yet
7 participants
@munificent
Member

munificent commented Jul 8, 2013

File.writeAsString() accepts an encoding. However, there are no instances of the Encoding class that map to any of the UTF- types except for UTF-8: no UTF-16, UTF-32, etc.

@iposva-google

This comment has been minimized.

Show comment
Hide comment
@iposva-google

iposva-google Jul 10, 2013

Contributor

Added Area-IO, Triaged labels.

Contributor

iposva-google commented Jul 10, 2013

Added Area-IO, Triaged labels.

@nordlien

This comment has been minimized.

Show comment
Hide comment
@nordlien

nordlien Jul 11, 2013

Yes, adding other UTF encoding is on the library roadmap.


Removed Area-IO label.
Added Area-Library label.

nordlien commented Jul 11, 2013

Yes, adding other UTF encoding is on the library roadmap.


Removed Area-IO label.
Added Area-Library label.

@floitschG

This comment has been minimized.

Show comment
Hide comment
@floitschG

floitschG Jul 11, 2013

Contributor

Set owner to @floitschG.
Added Accepted label.

Contributor

floitschG commented Jul 11, 2013

Set owner to @floitschG.
Added Accepted label.

@lrhn

This comment has been minimized.

Show comment
Hide comment
@lrhn

lrhn May 5, 2014

Member

Added Library-Convert label.

Member

lrhn commented May 5, 2014

Added Library-Convert label.

@lrhn

This comment has been minimized.

Show comment
Hide comment
@lrhn

lrhn May 5, 2014

Member

Removed Type-Defect label.
Added Type-Enhancement label.

Member

lrhn commented May 5, 2014

Removed Type-Defect label.
Added Type-Enhancement label.

@nex3

This comment has been minimized.

Show comment
Hide comment
@nex3

nex3 Jan 27, 2017

Member

Dart Sass needs UTF-16 (both big- and little-endian) support to match other implementations' encoding support.

Member

nex3 commented Jan 27, 2017

Dart Sass needs UTF-16 (both big- and little-endian) support to match other implementations' encoding support.

nex3 added a commit to sass/sass-spec that referenced this issue May 29, 2017

Enable one last spec for Dart Sass.
This brings Dart Sass up to full sass-spec compliance, with the
exception of two UTF-16 specs that can't be supported until
dart-lang/sdk#11744 is fixed.

nex3 added a commit to sass/sass-spec that referenced this issue May 30, 2017

Enable one last spec for Dart Sass. (#1130)
This brings Dart Sass up to full sass-spec compliance, with the
exception of two UTF-16 specs that can't be supported until
dart-lang/sdk#11744 is fixed.

@floitschG floitschG added the core-m label Aug 11, 2017

@floitschG floitschG removed their assignment Aug 11, 2017

@lrhn lrhn added core-m and removed core-m labels Aug 11, 2017

@floitschG floitschG added core-l and removed core-m labels Aug 28, 2017

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment