-
Notifications
You must be signed in to change notification settings - Fork 518
All project files are in non-UTF encoding #259
Comments
Can you give repro instructions? I'm not 100% sure what you mean when you say the files are saved in a non-UTF encoding, given that without a BOM (which the files don't have) or any special chars (which the generator doesn't itself put in the files), the UTF-8 encoding of the file is bitwise-identical with ASCII. As such, I'm not clear how it's meaningful to say the files are in one encoding or another. Only when you edit them to include some extended-range characters would a difference appear, and then it's your choice of encoding when you save the edited file. No doubt you are correct that there's something for us to fix here - I'm just not sure what, so would appreciate specific steps that show something going wrong! Thanks. |
In the absence of more info, I'll close this, but if anyone is able to provide repro information, please let us know! |
Looks like it's rather up to VS2015.
|
All project files after yeoman generator are created in non-UTF encoding (in my case - Windows 1251), which lead to national characters (in my case - Cyrillic) are corrupted.
After resaving from Visual Studio with UTF8 encoding, the issue has gone.
The text was updated successfully, but these errors were encountered: