Re: About japanese character error

Jamma Tino Schwarze <[email protected]>
Newsgroups gmane.comp.version-control.subversion.cvs2svn.user
Message-ID <[email protected]>
Hi David,

are you sure that the file names in question are in shift_jis encoding? 
Maybe there are some filenames in different encodings - I'd try
--encoding=shift_jis --encoding=gb2312 --encoding=euc_jp
--encoding=utf-8
and see what happens.

Tino.

On Fri, Nov 26, 2010 at 03:03:19PM +0800, David Wang wrote:
> Hello 
> everyone~
>  
> Has anyone succeed import 
> files with Japanese file name or comment? I got stuck here for almost two 
> weeks.
>  
> I update cvs2svn to the 
> latest version 2.3.0, and python to v2.7, 
> but when I tried to excute following operation, the error has reported in step 
> 16
>  
> Python2.7 cvs2svn 
> --encoding=shift_jis --encoding=gb2312 --fallback-encoding=sjis 
> --existing-svnrepos -s /home/svnroot/test_wangwei 
> /home/cvsroot/smplus/cvs2svn_test
>  
> The error 
> is:
>  
> ERROR: Unable to convert 
> a path 'trunk/¥¿¥¤¥ß¥ó¥°¥Á¥ã©`¥È1.txt' to internal 
> encoding.
> Consider rerunning with 
> one or more '--encoding' parameters or
> with 
> '--fallback-encoding'.
>  
> There are several file 
> with Japanese or Chinese filename. The Chinese filename can be pass but Japanese 
> failed.
>  
> Need 
> help
>  
> Thanks a 
> lot
>  
> p.s. The code server OS 
> is unix
>  
> Best 
> Regards,
> David 
> Wang
> 
> ------------------------------------------------------
> http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2685804
> 
> To unsubscribe from this discussion, e-mail: [[email protected]].
-- 
"What we nourish flourishes." - "Was wir nähren erblüht."

www.tisc.de

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=2685881

To unsubscribe from this discussion, e-mail: [[email protected]].
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.