Your message dated Wed, 23 Jul 2008 22:54:00 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#306724: vim-gnome: Input chinese uncorrectly when
encoding is set to prc
has caused the Debian Bug report #306724,
regarding [gvim] Input chinese incorrectly when 'encoding' is set to prc
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)
--
306724: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=306724
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Subject: vim-gnome: Input chinese correctly when encoding is set to prc
Package: vim-gnome
Version: 1:6.3-071+1
Severity: normal
Tags: l10n
*** Please type your report below this line ***
Hello,
I found that gvim would expand some chinese input into `??????'<chinese
word> when encoding of gvim is set to prc.
Let me take scim-chinese (a chinese pinyin input method module for scim)
as an example. I will give a short introduction for chinese input
method to make my question clearly. The very famous chinese input
method is `pinyin' input method: each chinese word has `pinyin', a
alphabet string. When a user want to input a chinese word, he would
change into chinese input method environment first, then type the
`pinyin' string on keyboard. After typing, he would select the chinese
word he needs since different chinese words may have the same `pinyin'
string.
When I type a chinese word `pinyin: fei', it will be displayed as
`??????<chinese word of fei>' in gvim. A more detailed description: I
typed `f', then scim-chinese gave a list of candidates and nothing
happened. Then I continued my input: I typed `e', then scim-chinese
gave another list of candidates. When I typed `i', the last letter of
the `pinyin' string of chinese word `fei', I would get a candiates list
for all chinese words having `pinyin' string as `fei'. The problem
occured when I type `e', that is, `fe' is not valid `pinyin' string of
normal chinese words and the candidates list would contain
unrecognizable one. The gvim would expand the input as `??????'. When
I finish the `pinyin' string input, the correct chinese word would
appear after `??????' as `??????<a chinese word>'.
It seems that gvim accepted a temporary input of chinese and expanded it
into `??????' since it is not a valid gbk chinese word when encoding is
set to prc. When encoding is set to utf-8, then this problem dispeared.
Since scim-chinese works properly in other applications, such as gedit,
the problem may be not belong to scim-chinese itself. So I report this
problem here.
Thank you.
-- System Information:
Debian Release: 3.1
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: i386 (i686)
Kernel: Linux 2.6.11-1-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages vim-gnome depends on:
ii libart-2.0-2 2.3.17-1 Library of functions for 2D
graphi
ii libatk1.0-0 1.8.0-4 The ATK accessibility
toolkit
ii libbonobo2-0 2.8.1-2 Bonobo CORBA interfaces
library
ii libbonoboui2-0 2.8.1-2 The Bonobo UI library
ii libc6 2.3.2.ds1-21 GNU C Library: Shared
libraries an
ii libgconf2-4 2.8.1-5 GNOME configuration
database syste
ii libglib2.0-0 2.6.4-1 The GLib library of C
routines
ii libgnome2-0 2.8.1-2 The GNOME 2 library -
runtime file
ii libgnomecanvas2-0 2.8.0-1 A powerful object-oriented
display
ii libgnomeui-0 2.8.1-3 The GNOME 2 libraries (User
Interf
ii libgnomevfs2-0 2.8.4-2 The GNOME virtual
file-system libr
ii libgpmg1 1.19.6-20 General Purpose Mouse -
shared lib
ii libgtk2.0-0 2.6.4-1 The GTK+ graphical user
interface
ii libice6 4.3.0.dfsg.1-12.0.1 Inter-Client Exchange
library
ii libncurses5 5.4-4 Shared libraries for
terminal hand
ii liborbit2 1:2.12.2-1 libraries for ORBit2 - a
CORBA ORB
ii libpango1.0-0 1.8.1-1 Layout and rendering of
internatio
ii libpopt0 1.7-5 lib for parsing cmdline
parameters
ii libsm6 4.3.0.dfsg.1-12.0.1 X Window System Session
Management
ii libx11-6 4.3.0.dfsg.1-12.0.1 X Window System protocol
client li
ii libxml2 2.6.16-7 GNOME XML library
ii libxt6 4.3.0.dfsg.1-12.0.1 X Toolkit Intrinsics
ii vim 1:6.3-071+1 Vi IMproved - enhanced vi
editor
ii xlibs 4.3.0.dfsg.1-12 X Keyboard Extension (XKB)
configu
ii zlib1g 1:1.2.2-4 compression library -
runtime
-- no debconf information
--
Hongzheng Wang
Department of Electronic Engineering
Tsinghua University
Beijing 100084, China
Tel: (+86 10) 6279 6973
--- End Message ---
--- Begin Message ---
Version: 1:7.1.314-3
On Thu, Apr 28, 2005 at 02:39:01PM +0800, Hongzheng Wang wrote:
> I found that gvim would expand some chinese input into `??????'<chinese
> word> when encoding of gvim is set to prc.
>
> When I type a chinese word `pinyin: fei', it will be displayed as
> `??????<chinese word of fei>' in gvim. A more detailed description: I
> typed `f', then scim-chinese gave a list of candidates and nothing
> happened. Then I continued my input: I typed `e', then scim-chinese
> gave another list of candidates. When I typed `i', the last letter of
> the `pinyin' string of chinese word `fei', I would get a candiates list
> for all chinese words having `pinyin' string as `fei'. The problem
> occured when I type `e', that is, `fe' is not valid `pinyin' string of
> normal chinese words and the candidates list would contain
> unrecognizable one. The gvim would expand the input as `??????'. When
> I finish the `pinyin' string input, the correct chinese word would
> appear after `??????' as `??????<a chinese word>'.
>
> It seems that gvim accepted a temporary input of chinese and expanded it
> into `??????' since it is not a valid gbk chinese word when encoding is
> set to prc. When encoding is set to utf-8, then this problem dispeared.
This bug looks to be fixed in the latest testing/unstable version. I
tested it as thoroughly as I know how given that I've only used scim
while testing this bug. Please reopen if I missed a scenario.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <[EMAIL PROTECTED]>
signature.asc
Description: Digital signature
--- End Message ---
