From: Wenzhi L. <wen...@gm...> - 2006-03-08 23:01:32
|
Hi wandys, Long time no see. :-) On 08/03/06, Alecs King <al...@pe...> wrote: > On Tue, Mar 07, 2006 at 11:31:40PM +0000, Wenzhi Liang wrote: > > wandys, I remember we had this problem before and you fixed it. If you > > are still around, can you take a look at this? > > The problem i 'fixed' falls in the case 2 & 3 as Willis stated. (welcome > aboard. huge job you did. thanks). > > There's no easy and elegant fix for case 1. It may be not very polite > to have people's names misspelled as Thunder said in another mail. I agree with thunder too. > > > There is a work around for this: add 'enc=3Dutf-8' to the status line. > > This doesnt affect utf-8 users since they already set to use utf8 in the > first place. And this does no good for a regular enc-cn user since s/he > normally cannot view utf-8 in his/her enc-cn environment (ie. in a > enc-cn locale'd terminal). Well that's not entirely true. When I said it was a work around, I tested w= ith the GUI version (don't use vim on console that often). And you are right a= bout the console side. However, if the console cannot display utf8 character at all, it is not a problem of the translation then. So the work around is sti= ll a work around. > > > So there are several options for us: > > 1) We dont care about euc-cn any more. utf-8 only, simple and clear. hmmm. How do we achieve that? I tried to set LANG=3Dzh_CN.UTF-8 and vim still can't display usr_24.txt > > 2) We care about euc-cn by sacrificing utf-8 quality (change/remove > questionable chars). Don't think that's a good idea. > > 3) With utf-8 versions being good and untouched, we start maintaining > and providing separate euc-cn versions (iconv -c). I think 'iconv -c' simply drop the character that it has problem with. Righ= t? Then is this not the same as 2? > > 4) Patch Vim to make it act like iconv -c when it's doing conversion. Don't think Vim's maintainer would be happy with this. Same reason as 3. > > Nooooone is perfect. That seems true. If I understand correctly, it is because iconv doesn't sup= port gbk? lang2 |