[Pkg-ime-devel] Bug#690911: Chinese full stop: U+3002 or U+FF0E?
Package: hime
Version: 0.9.9+git20120619+dfsg-1
Severity: normal
Tags: patch
Dear Maintainers,
In full width mode, the full stop key "." turns to be U+FF0E "?", which is
used rarely in either Chinese or English text.
I think it's more useful to have U+3002 "?" instead for this key, and I
attached a patch.
Regards,
Guo Yixuan
-- System Information:
Debian Release: wheezy/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Versions of packages hime depends on:
ii hime-data 0.9.9+git20120619+dfsg-1
ii hime-tables 0.9.9+git20120619+dfsg-1
ii libc6 2.13-35
ii libcairo2 1.12.2-2
ii libgdk-pixbuf2.0-0 2.26.1-1
ii libglib2.0-0 2.33.12+really2.32.4-2
ii libgtk2.0-0 2.24.10-2
ii libpango1.0-0 1.30.0-1
ii libx11-6 2:1.5.0-1
ii libxtst6 2:1.2.1-1
Versions of packages hime recommends:
ii hime-gtk3-immodule 0.9.9+git20120619+dfsg-1
ii im-config [im-switch] 0.18
Versions of packages hime suggests:
ii hime-anthy 0.9.9+git20120619+dfsg-1
ii hime-chewing 0.9.9+git20120619+dfsg-1
ii hime-qt4-immodule 0.9.9+git20120619+dfsg-1
-- no debconf information
*** /home/gyx/pkg/next/hime/debian/patches/fullstop.patch
Index: hime/src/fullchar.c
===================================================================
--- hime.orig/src/fullchar.c
+++ hime/src/fullchar.c
@@ -2,7 +2,7 @@
unich_t *fullchar[]=
{
"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
-"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
+"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
"?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?", "?",
Reply to: