diff options
author | Avi Halachmi (:avih) <avihpit@yahoo.com> | 2023-08-03 18:23:23 +0300 |
---|---|---|
committer | Avi Halachmi (:avih) <avihpit@yahoo.com> | 2023-08-03 20:57:53 +0300 |
commit | bf70275f786716546ec474caade0f16ec28da541 (patch) | |
tree | c92cc94e1fd5508b6a0cc7745f40cd7750b3e160 /TODO | |
parent | a42cc92778545d21429f9267540330991185f1f1 (diff) | |
download | busybox-w32-bf70275f786716546ec474caade0f16ec28da541.tar.gz busybox-w32-bf70275f786716546ec474caade0f16ec28da541.tar.bz2 busybox-w32-bf70275f786716546ec474caade0f16ec28da541.zip |
win32: add FEATURE_UTF8_OUTPUT (enabled with unicode)
Previously, the unicode build required console (out) codepage of UTF8
in order for unicode output to be printed correctly - e.g. at the
shell command prompt or the output of `ls` for unicode file names.
This is inconvenient, because by default it's not UTF8, and so unless
the user invoked 'chcp 65001' - by default unicode output didn't work.
This feature (which is now enabled for the unicode build) makes it
print unicode output correctly regardless of the console CP, by
using a new stream-conversion funcion from UTF8 chars to wchar_t,
and writing those using WriteConsoleW.
If the console CP happens to be UTF8 - this conversion is disabled.
We could have instead changed the console CP to UTF8, but that's
a slippery slope, and some old program which expect the default CP
might get broken, so achieving the same result without touching
the console CP is hopefully better.
Diffstat (limited to 'TODO')
0 files changed, 0 insertions, 0 deletions