-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Add setting charset #3862
Comments
@jayvdb please assign me this. |
@jack17529 please read our newcomer guide |
@Makman2 already did it sir , no newcomer issues are present |
There are 7. They are not in this repo. The newcomer guide explains how to find them. |
Setting for which Bear? |
This problem is not about a specific bear; the file open code is in coala. This is a fix for problems like #488 |
when i run we just need to add options like i'm not getting , can you please explain more 😅 |
Ya, those are binary files. Binary files do not have a charset. Test on a text file which uses a different character encoding, i.e. not utf8. |
I will work on this issue |
Reassigning due to inactivity. |
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
coala currently only supports utf-8 encodings. Before merging this we need to add support for non utf-8 encodings to coala-utils. Some bears like SpellCheckBear have external linters which only support utf-8 encodings. To solve this the bears should describe the encoding it can handle followed by coala creating a temporary file in the linter's accepted encoding (Converting utf-16 to utf-8) Some encodings have glyphs which are not in unicode and can't be transcoded to utf16/32. We should write test to catch such exceptions. Closes coala#3862
#3529 show the problem with non -utf8 content.
We need a setting so users can control the charset used, which will reduce the severity of above bug.
The text was updated successfully, but these errors were encountered: