Menu
▾
▴
vimcdoc-translate
|
From: Yi-an H. <yia...@gm...> - 2006-03-08 06:52:58
|
Hi lang2, For your list of problematic files, there are a few different cases. Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign alphabets utf-8 are designed to incorporate characters from different languages, enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some characters cannot be converted correctly and there are unfortunately no eas= y fix. In my opinion, utf-8 is the better form for translations for at least those documents that discuss digraphs and a few foreign languages. Likely, people who only read gb encodings will not care about these documents anyway, but we never know for sure... Add "-c" parameter to iconv can work around the problem and iconv would succeed by not translating these characters. But it is better for us to leave unfixable characters with question marks. So for gb translations some manual work is needed, but i would still argue that the utf-8 versions should be the primary ones. Case 2, pi_netrw, pattern: small nuisance pi_netrw.txt: the name of a French author near the end of the file pattern.txt: "a" with a hat on top of it (actually reverting to the previous version fixes the problem. but I wonder whether people reading utf-8 may feel the current way is cleaner) Case 3, various, index: incorrect characters in use and they should be fixed. netbean used to have this problem too with two unusual dashes (-), a recent update fixed it, thanks. I can upload the fixes of case 2 and 3. Willlis |
|
From: hai x. <xx...@ms...> - 2006-03-09 18:31:12
|
Is it OK I commited two files ? >From: "Yi-an Huang" <yia...@gm...> >Reply-To: vim...@li... >To: vim...@li... >Subject: Re: [Vimcdoc-translate] help with iconv >Date: Wed, 8 Mar 2006 01:52:56 -0500 > >Hi lang2, > >For your list of problematic files, there are a few different cases. > >Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign alphabets > >utf-8 are designed to incorporate characters from different languages, >enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some >characters cannot be converted correctly and there are unfortunately no >easy >fix. In my opinion, utf-8 is the better form for translations for at least >those documents that discuss digraphs and a few foreign languages. Likely, >people who only read gb encodings will not care about these documents >anyway, but we never know for sure... > >Add "-c" parameter to iconv can work around the problem and iconv would >succeed by not translating these characters. But it is better for us to >leave unfixable characters with question marks. So for gb translations some >manual work is needed, but i would still argue that the utf-8 versions >should be the primary ones. > >Case 2, pi_netrw, pattern: small nuisance > >pi_netrw.txt: the name of a French author near the end of the file >pattern.txt: "a" with a hat on top of it (actually reverting to the >previous version fixes the problem. but I wonder whether people reading >utf-8 may feel the current way is cleaner) > >Case 3, various, index: incorrect characters in use and they should be >fixed. > >netbean used to have this problem too with two unusual dashes (-), a recent >update fixed it, thanks. > >I can upload the fixes of case 2 and 3. > >Willlis |
|
From: Yi-an H. <yia...@gm...> - 2006-03-09 19:58:28
|
Sure, thanks. On 3/9/06, hai xie <xx...@ms...> wrote: > > Is it OK I commited two files ? > > > >From: "Yi-an Huang" <yia...@gm...> > >Reply-To: vim...@li... > >To: vim...@li... > >Subject: Re: [Vimcdoc-translate] help with iconv > >Date: Wed, 8 Mar 2006 01:52:56 -0500 > > > >Hi lang2, > > > >For your list of problematic files, there are a few different cases. > > > >Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign alphabets > > > >utf-8 are designed to incorporate characters from different languages, > >enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some > >characters cannot be converted correctly and there are unfortunately no > >easy > >fix. In my opinion, utf-8 is the better form for translations for at > least > >those documents that discuss digraphs and a few foreign languages. > Likely, > >people who only read gb encodings will not care about these documents > >anyway, but we never know for sure... > > > >Add "-c" parameter to iconv can work around the problem and iconv would > >succeed by not translating these characters. But it is better for us to > >leave unfixable characters with question marks. So for gb translations > some > >manual work is needed, but i would still argue that the utf-8 versions > >should be the primary ones. > > > >Case 2, pi_netrw, pattern: small nuisance > > > >pi_netrw.txt: the name of a French author near the end of the file > >pattern.txt: "a" with a hat on top of it (actually reverting to the > >previous version fixes the problem. but I wonder whether people reading > >utf-8 may feel the current way is cleaner) > > > >Case 3, various, index: incorrect characters in use and they should be > >fixed. > > > >netbean used to have this problem too with two unusual dashes (-), a > recent > >update fixed it, thanks. > > > >I can upload the fixes of case 2 and 3. > > > >Willlis > > > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting > language > that extends applications into web and mobile media. Attend the live > webcast > and join the prime developer group breaking into this new coding > territory! > http://sel.as-us.falkag.net/sel?cmd=3Dlnk&kid=3D110944&bid=3D241720&dat= =3D121642 > _______________________________________________ > Vimcdoc-translate mailing list > Vim...@li... > https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate > |
|
From: å¤©é¢ æ¨ <cn_...@ho...> - 2006-03-10 04:24:09
|
<html><div style='background-color:'><DIV class=RTE> <P>Ôõô·¢µ½ÎÒÕâÀïÀ´ÁË$&*%(^()<BR><BR></P></DIV> <DIV></DIV> <BLOCKQUOTE style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #a0c6e5 2px solid; MARGIN-RIGHT: 0px"><FONT style="FONT-SIZE: 11px; FONT-FAMILY: tahoma,sans-serif"> <HR color=#a0c6e5 SIZE=1> <DIV></DIV>From: <I>"hai xie" <xx...@ms...></I><BR>Reply-To: <I>vim...@li...</I><BR>To: <I>vim...@li...</I><BR>Subject: <I>Re: [Vimcdoc-translate] help with iconv</I><BR>Date: <I>Thu, 09 Mar 2006 18:31:01 +0000</I><BR>>Is it OK I commited two files ?<BR>><BR>><BR>>>From: "Yi-an Huang" <yia...@gm...><BR>>>Reply-To: vim...@li...<BR>>>To: vim...@li...<BR>>>Subject: Re: [Vimcdoc-translate] help with iconv<BR>>>Date: Wed, 8 Mar 2006 01:52:56 -0500<BR>>><BR>>>Hi lang2,<BR>>><BR>>>For your list of problematic files, there are a few different <BR>>>cases.<BR>>><BR>>>Case 1, digraph, arabic, hebrew, mbyte, farsi, usr_24: foreign <BR>>>alphabets<BR>>><BR>>>utf-8 are designed to incorporate characters from different <BR>>>languages,<BR>>>enc-cn/cp936/gb2312/gb18030 is not, so in a few special cases some<BR>>>characters cannot be converted correctly and there are <BR>>>unfortunately no easy<BR>>>fix. In my opinion, utf-8 is the better form for translations for <BR>>>at least<BR>>>those documents that discuss digraphs and a few foreign languages. <BR>>>Likely,<BR>>>people who only read gb encodings will not care about these <BR>>>documents<BR>>>anyway, but we never know for sure...<BR>>><BR>>>Add "-c" parameter to iconv can work around the problem and iconv <BR>>>would<BR>>>succeed by not translating these characters. But it is better for <BR>>>us to<BR>>>leave unfixable characters with question marks. So for gb <BR>>>translations some<BR>>>manual work is needed, but i would still argue that the utf-8 <BR>>>versions<BR>>>should be the primary ones.<BR>>><BR>>>Case 2, pi_netrw, pattern: small nuisance<BR>>><BR>>>pi_netrw.txt: the name of a French author near the end of the file<BR>>>pattern.txt: "a" with a hat on top of it (actually reverting to <BR>>>the<BR>>>previous version fixes the problem. but I wonder whether people <BR>>>reading<BR>>>utf-8 may feel the current way is cleaner)<BR>>><BR>>>Case 3, various, index: incorrect characters in use and they should <BR>>>be<BR>>>fixed.<BR>>><BR>>>netbean used to have this problem too with two unusual dashes (-), <BR>>>a recent<BR>>>update fixed it, thanks.<BR>>><BR>>>I can upload the fixes of case 2 and 3.<BR>>><BR>>>Willlis<BR>><BR>><BR>><BR>><BR>>-------------------------------------------------------<BR>>This SF.Net email is sponsored by xPML, a groundbreaking scripting <BR>>language<BR>>that extends applications into web and mobile media. Attend the live <BR>>webcast<BR>>and join the prime developer group breaking into this new coding <BR>>territory!<BR>>http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642<BR>>_______________________________________________<BR>>Vimcdoc-translate mailing list<BR>>Vim...@li...<BR>>https://lists.sourceforge.net/lists/listinfo/vimcdoc-translate<BR></FONT></BLOCKQUOTE></div><br clear=all><hr> <a href="http://g.msn.com/8HMAENUS/2749??PS=47575" target="_top">Make FREE PC-to-PC calls with MSN Messenger. Get it now! </a> </html> |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X