Skip to content
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

UTF16 BE support #322

Closed
martinlindhe opened this issue Jan 15, 2017 · 2 comments
Closed

UTF16 BE support #322

martinlindhe opened this issue Jan 15, 2017 · 2 comments

Comments

@martinlindhe
Copy link
Contributor

martinlindhe commented Jan 15, 2017

Hello. Am currently on Windows, and there for some reason (...) unicode files are often created as UTF16BE.
I realized I have a project with mixed file encodings, most is UTF8 and some are UTF16BE, and ripgrep currently don't find anything in those files.

In the attached archive is a project I was working on, and the file src\GUIGroup.ts happens to be in UTF16BE,
so try searching the folder for "GUIGroup" causes no hits in that file.

Tested with ripgrep 0.4.0 on Windows. Same result with ripgrep 0.4.0 on macOS

Github dont want to attach zip files today, so I put it here:
http://wikisend.com/download/290136/utf16issue_ripgrep.zip

@BurntSushi
Copy link
Owner

This is a dupe of #1.

As the README says, ripgrep doesn't seamlessly support any encoding that isn't ASCII compatible. (That includes UTF-8 and latin1, but not UTF-16.)

This is a desirable feature, especially at least UTF-16 since it is used a lot on Windows.

@martinlindhe
Copy link
Contributor Author

Ah, thanks. I glanced through the open issues looking for "UTF16", thats why I didn't notice #1.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants