Comment 3 for bug 1685091

I did further tests. If I replaced libglib-2.0-0.dll in 0.92.1 with the same dll in Rev 15625, the problem occurred in 0.92.1 too.
Due to DLL dependency I couldn't test 0.92.1 DLL with 15625 exe.

And I wrote a small program which loaded Glib DLL and called g_fopen("a.txt", "wbb"). g_fopen() succeeded with 0.92.1 DLL but failed with 15625 DLL.

Maybe there was something changed in Glib. The version number of 0.92.1's DLL is 2.47.4.0, and that of 15625 is 2.52.0.0.

Is "wbb" or "rbb" a reasonable value for g_fopen()? I used g_printerr() to show the value of 'how' and it was surely "wbb".
If this is an undocumented behavior, I think it would be better to fix it.
But I am not sure which way is better. Change fopen_utf8name() itself and remove "how.append("b");", or change fopen_utf8name() callings and remove the "b" mode.