Issue #16233 has been updated by duerst (Martin D=FCrst).


Will do, but probably not very soon, because it's now the most busy time of=
 the year at work, sorry.

Some notes: For the encoding (onigX), windows-1256 is a replica of iso-8859=
-6. But windows-1256 is much more complete, while iso-8859-6 has many unass=
igned codepoints, so it may be a good idea to fix this if we get around to =
it.

Just adding an alias 'CP720' for windows-1256 is much easier. =


----------------------------------------
Feature #16233: winruby UTF8 Fallback for no CodePage
https://bugs.ruby-lang.org/issues/16233#change-83851

* Author: gabuscus (Gabriel Nagy)
* Status: Open
* Priority: Normal
* Assignee: duerst (Martin D=FCrst)
* Target version: 2.8
----------------------------------------
This is to deal specifically with setting the Region to Arabic which
sets the codepage to 720. This codepage isn't recognised by Ruby which
causes it to fail during initialisation when setting up LOCALE.

This patch to Ruby is necessary to handle languages/regions on windows
where the codepage is not supported by Ruby such as Arabic which uses =

codepage 720.
If the codepage is not found, the Locale falls back to UTF8.

This is a well known Ruby/Ruby on Rails issue which is described at
https://stackoverflow.com/questions/22815542/rails4-unknown-encoding-name-c=
p720

Opened PR: https://github.com/ruby/ruby/pull/2518

---Files--------------------------------
windows_nocodepage_utf8_fallback_r2.5.patch (946 Bytes)


-- =

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

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