[ 
https://issues.apache.org/jira/browse/STDCXX-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12523408
 ] 

Martin Sebor commented on STDCXX-373:
-------------------------------------

I'm having trouble reproducing this problem with the latest trunk. What I get 
instead is:

$ (export RWSTD_SRC_ROOT=/nfs/devco/sebor/stdcxx/etc/nls; mkdir -p /tmp/$$ && 
./localedef -w -c -f $RWSTD_SRC_ROOT/charmaps/CP1255 -i 
$RWSTD_SRC_ROOT/src/yi_US /tmp/$$/yi_US.CP1255)
Error 308: illegal multibyte prefix '\x90' in character map file

Looks like the localedef utility cannot process the CP1255 character set 
description file.

Same behavior in 4.1.3.

Oddly, though, there is no x90 in the charmap.

$ grep "x90" /nfs/devco/sebor/stdcxx/etc/nls/charmaps/CP1255 || echo not found
not found


> [locale] error: incomplete multibyte character on yi_US.CP1255
> --------------------------------------------------------------
>
>                 Key: STDCXX-373
>                 URL: https://issues.apache.org/jira/browse/STDCXX-373
>             Project: C++ Standard Library
>          Issue Type: Bug
>          Components: Locales
>    Affects Versions: 4.2
>         Environment: gcc 3.4.6, Linux x86_64
>            Reporter: Martin Sebor
>
> $ ./yi_US.CP1255 -d -n
> -bash: ./yi_US.CP1255: No such file or directory
> bin$ ./yi_US.CP1255.sh -d -n
> RWSTD_SRC_ROOT=/amd/devco/sebor/stdcxx/etc/nls
> export RWSTD_SRC_ROOT
> mkdir -p /tmp/locale.12106/stage.1/charmaps
> ./localedef -w -c -f /amd/devco/sebor/stdcxx/etc/nls/charmaps/CP1255 -i 
> /amd/devco/sebor/stdcxx/etc/nls/src/yi_US 
> /tmp/locale.12106/stage.1/yi_US.CP1255 >/dev/tty 2>&1
> LC_ALL=/tmp/locale.12106/stage.1/yi_US.CP1255 ./locale --charmap -l 
> >/tmp/locale.12106/stage.1/charmaps/CP1255 2>/dev/tty
> LC_ALL=/tmp/locale.12106/stage.1/yi_US.CP1255 ./locale -ck -h -l LC_ALL 
> >/tmp/locale.12106/stage.1/yi_US.src 2>/dev/tty
> Error 308: incomplete multibyte character in character map file: expecting 3 
> bytes, found 0

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to