Skip to content

Specify what encodings of source files are recognized by Roslyn and add corresponding tests #410

New issue
New issue
Open
Open
Specify what encodings of source files are recognized by Roslyn and add corresponding tests#410
Labels
Area-CompilersConcept-PortabilityThe issue deals with portable code (portable libraries, etc.).DocumentationFeature RequestTenet-LocalizationSome piece of UI isn’t localized, often due to hard-coding of strings or other visible elements.TestTest failures in roslyn-CIhelp wantedThe issue is "up for grabs" - add a comment if you are interested in working on it
Milestone
 
Backlog
@VladimirReshetnikov

Description

@VladimirReshetnikov
VladimirReshetnikov
opened on Feb 11, 2015

Documentation for Roslyn should specify what encodings of source files are recognized by Roslyn (and what heuritics/defaults are used, if any, when there are no BOM), e.g. UTF8 w/o BOM, UTF8, UTF16 little-endian, UTF16 big-endian, UTF32 little-endian, UTF32 big-endian, etc...

There should be tests for all supported encodings.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Area-CompilersConcept-PortabilityThe issue deals with portable code (portable libraries, etc.).DocumentationFeature RequestTenet-LocalizationSome piece of UI isn’t localized, often due to hard-coding of strings or other visible elements.TestTest failures in roslyn-CIhelp wantedThe issue is "up for grabs" - add a comment if you are interested in working on it

    Type

    No type

    Projects

    No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions