On Wed, Jul 13, 2011 at 10:58 AM, Yehuda Sadeh Weinraub <yehudasa@xxxxxxxxx> wrote: > On Wed, Jul 13, 2011 at 10:45 AM, Colin McCabe <cmccabe@xxxxxxxxxxxxxx> wrote: >> On Wed, Jul 13, 2011 at 9:59 AM, Yehuda Sadeh Weinraub >> <yehudasa@xxxxxxxxx> wrote: >>> On Wed, Jul 13, 2011 at 12:48 AM, Sylar Shen <kimulaaa@xxxxxxxxx> wrote: >>>> Hi developers, >>>> I installed ceph and radosgw v0.3 and got 1 server with MON and >>>> radosgw , 2 OSDs server. (without MDS) >>>> The environment started successfully and I wanted to test >>>> upload/download file via radosgw. >>>> It all went well if I uploaded/downloaded English file names. >>>> But It went wrong when I tried Chinese file names. >>>> Radowgw can receive files normally, but Chinese file names were turned >>>> into unrecognized codes. >>>> Therefore, radosgw cannot show the file list in a bucket normally. >>>> It turned out to show nothing when I wanted to list files in a bucket. >>>> But the Chinese file did exist in the bucket. >>>> >>>> I am curious that if I did something wrong to result in such kind of problems >>>> Does anyone who has the same problem as I did? >>> >>> That's a bug. It appears that the xml escaping doesn't work correctly >>> with unicode characters. I just opened issue #1301 for that, we'll >>> look at it. >> >> I guess this means that XML escaping needs to be utf-8-aware, which it >> isn't now. Probably it's just a matter of recognizing when we are >> inside a utf-8 character and skipping the bytes comprising that >> character. JSON escaping probably also needs that change. >> > Might be, though our specific issue here was just a bad test (actually > using char instead of unsigned char) in which we clobbered all utf8 > characters. Whether we need to translate utf8 into UCS is a different > question. Actually, I just realized that every UTF-8 character that is not ASCII has the high-bit set. So you can never have the problem I described. Colin -- To unsubscribe from this list: send the line "unsubscribe ceph-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
