GNU gettext - Bugs: bug #57714, libintl: Unicode paths passed to...
You are not allowed to post comments on this tracker with your current authentication level.
bug #57714: libintl: Unicode paths passed to bindtextdomain fail on Windows (when linked to the MSVCRT)
Submitter: | pastdue | ||
Submitted: | Fri 31 Jan 2020 07:51:03 PM UTC | ||
Category: | End-user / runtime | Severity: | 3 - Normal |
Item Group: | None | Status: | Fix Released |
Privacy: | Public | Assigned to: | haible |
Open/Closed: | Closed |
Mon 27 Jul 2020 05:44:59 PM UTC, comment #2: |
Bruno Haible <haible> |
Mon 20 Apr 2020 02:04:02 AM UTC, comment #1: Thanks for the report.
|
Bruno Haible <haible> |
Fri 31 Jan 2020 07:51:03 PM UTC, original submission:
Description:libintl fails to load message catalogs from dirnames containing non-ASCII UTF-8 characters
To Reproduce:With a Windows build linked to the MSVCRT:
Expected Behavior:libintl succeeds at finding message catalogs in the valid UTF-8 dirname
Actual Behavior:libintl fails to load message catalogs
Cause:gettext-runtime/intl/loadmsgcat.c uses open() internally, which does not support / expect UTF-8 filenames on the MSVCRT
Solution:gettext-runtime/intl/loadmsgcat.c: Provide a wrapper for open() that converts the input char* to a UTF-16 wchar_t* and then calls _wopen(), which properly handles a Unicode path
|
pastdue |
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Follow 5 latest changes.
Date | Changed by | Updated Field | Previous Value | => | Replaced by |
---|---|---|---|---|---|
2023-01-04 | haible | Status | Fixed | Fix Released | |
2020-04-20 | haible | Status | None | Fixed | |
Assigned to | None | haible | |||
Open/Closed | Open | Closed | |||
2020-01-31 | pastdue | Attached File | - | Added example_patch.txt, #48317 |
Powered by Savane 3.13-d3ae.
Corresponding source code
The fix is contained in gettext 0.21.