Issue #14456 has been updated by Gondolin (Damien Robert).


shevegen (Robert A. Heiler) wrote:
> Not sure if it can be removed, but I think you can change the status
> to "closed" (or someone from the ruby core team probably could).

Someone did, thanks!

> To the bug report, just out of curiosity, can you avoid the UTF
> problem if you change to use another encoding before calling
> Dir.glob?

Yes: `Dir.glob('*a'.encode!('ISO-8859-1'), File::FNM_CASEFOLD)` works.



----------------------------------------
Bug #14456: Dir.glob with FNM_CASEFOLD gives ArgumentError: invalid byte sequence in UTF-8
https://bugs.ruby-lang.org/issues/14456#change-70258

* Author: Gondolin (Damien Robert)
* Status: Open
* Priority: Normal
* Assignee: 
* Target version: 
* ruby -v: 2.5.0p0
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN, 2.5: UNKNOWN
----------------------------------------
With ruby 2.5.0p0, in a folder that contains a file encoded in latin-1, I get the following error:

~~~ ruby
Dir.glob('*a', File::FNM_CASEFOLD)
ArgumentError: invalid byte sequence in UTF-8
~~~

Note that `Dir.glob('*', File::FNM_CASEFOLD)`, `Dir.glob('a*', File::FNM_CASEFOLD)` and `Dir.glob('*')` work.



-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:ruby-core-request / ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>