[ http://issues.apache.org/jira/browse/STDCXX-285?page=comments#action_12432708 ] Martin Sebor commented on STDCXX-285: -------------------------------------
This is an issue for the ISO-IR-90 character set which contains such sequences (e.g., <UE002> encoded as \xc1 and <U00C0> encoded as \xc1\x41) -- see http://svn.apache.org/repos/asf/incubator/stdcxx/branches/4.1.3/etc/nls/charmaps/ISO-IR-90. The single-byte characters in the charmap are marked as "(not a real character)" in a comment but the utility generates entries only for them and not for the multibyte characters with that prefix. This is actually by design (dictated by the layout of the codecvt tables), but it appears to be a problem nonetheless. > localedef fails to generate multibyte characters with the same prefix > --------------------------------------------------------------------- > > Key: STDCXX-285 > URL: http://issues.apache.org/jira/browse/STDCXX-285 > Project: C++ Standard Library > Issue Type: Bug > Components: Utilities > Affects Versions: 4.1.2, 4.1.3 > Environment: all > Reporter: Martin Sebor > Assigned To: Martin Sebor > > The localedef utility fails to generate multibyte characters whose initial > prefix (leading byte) is the same as some single-byte character. The test > case below demonstrates the problem: > $ cat charmap && cat ctype && ./localedef -c -w -f charmap -i ctype > /tmp/dummy && LC_ALL=/tmp/dummy ./locale --charmap > CHARMAP > <U0041> \x41 > <U0141> \x41\x42 > <U0241> \x41\x43 > END CHARMAP > LC_CTYPE > END LC_CTYPE > <escape_char> \ > <comment_char> # > <code_set_name> charmap > <mb_cur_max> 1 > # charmap data: > # charmap name = charmap > # n_to_w_tab_off = 0 > # w_to_n_tab_off = 1024 > # utf8_to_ext_tab_off = 4096 > # xliteration_off = 7168 > # wchar_off = 8192 > # codeset_off = 8216 > # charmap_off = 8224 > # codecvt_ext_off = 0 > CHARMAP > <U0041> \x41 # L'\x41' > END CHARMAP > # charmap stats: > # number of tables = 1 > # number of characters = 1 > # number of unused slots = 255 (100% waste) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
