dotnet/roslyn

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

Open

#410 opened on Feb 11, 2015

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C# (4,257 forks)batch import
Area-CompilersConcept-PortabilityDocumentationFeature RequestTenet-LocalizationTesthelp wanted

Repository metrics

Stars
 (20,414 stars)
PR merge metrics
 (Avg merge 6d 17h) (256 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Investigate the Roslyn source code to identify which file encodings are supported (e.g., UTF 8 with/without BOM, UTF 16 LE/BE, etc.) and how they are detected. Then create documentation listing these encodings and add unit tests for each.
Tech stack
csharp
Domain
backend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
C#Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70