Comments (4)
Thanks for the report.
Hmm.. this looks like a code clean-up task rather than a bug since I don't
think ibus engine ids are visible to users...
Can you let me know if there are any problems that are user-visible regarding
the engine id. I'd keep the code as it is for now if there aren't any,
> though the keyboard layout other than Japanese can't be selected in this
revision
It's not exactly true. If the --enable_us_engine command line option is
specified, an alternative engine for US keyboards, "Mozc (US keyboard layout)",
should appear in the ibus-setup dialog. And your patch seems not to work fine
with the command line option since ibus-daemon is not able to handle two or
more engines that have the same engine id (i.e. "mozc"). For example, if your
patch is used with the option, Shift+2 generates @ (full-width at sign)
character even with the "mozc-jp" engine.
Kana input mode in ibus-mozc also requires a dedicated engine id for each
keyboard layout in order to select a correct ASCII-to-Kana mapping table:
http://code.google.com/p/mozc/source/browse/trunk/src/unix/ibus/mozc_engine.cc#4
28
Original comment by [email protected]
on 30 May 2010 at 12:38
from mozc.
> I don't think ibus engine ids are visible to users...
ibus.el, client for Emacs I wrote, shows engine name in the mode line as
"IBus[mozc-
jp]". I think "mozc-jp" occupies unnecessarily large width.
> If the --enable_us_engine command line option is specified, an alternative
engine
for US keyboards, "Mozc (US keyboard layout)", should appear in the ibus-setup
dialog.
Oops, sorry, I've not known it.
> And your patch seems not to work fine with the command line option since ibus-
daemon is not able to handle two or more engines that have the same engine id
(i.e.
"mozc").
I see. But currently the relations between engine names and longnames are
inconsistent:
mozc-jp => Mozc
mozc => Mozc (US keyboard layout)
I think engine names for JP and US keyboard should be changed to "mozc" and
"mozc-
us", respectively:
mozc => Mozc
mozc-us => Mozc (US keyboard layout)
Original comment by [email protected]
on 30 May 2010 at 4:33
from mozc.
I see your point, but I'm still wondering how severe the string width problem
is, and also wondering why you don't take an approach which is compatible with
ibus-setup and the language panel. They always use <longname> (and <language>
for some places) rather than the <name>. Contrary to the implications of its
name,
longnames in major ibus engines are not that long :)
FWIW, in the meanwhile, it is a bit difficult to change the engine name in
ibus-mozc for some reasons, especially on Chrome OS which has a "Sync user
preferences with Cloud" feature.
> But currently the relations between engine names and longnames are
inconsistent:
From the perspective of Chrome OS whose primary keyboard layout is US, I
believe it's consistent.
mozc => Mozc (US keyboard layout)
mozc-jp => Mozc (Japanese keyboard layout)
Closing this as WontFix for now. Thanks.
Original comment by [email protected]
on 31 May 2010 at 1:35
- Changed state: WontFix
from mozc.
> ... why you don't take an approach which is compatible with ibus-setup and
the
language panel.
ibus.el needs to show users the unique names of engines because the function
'ibus-
enable' requires the users give an unique name to specify which engine is
activated
(See http://d.hatena.ne.jp/iRiE/20100530/1275212234). The longname, however, is
not
unique. ibus-m17n uses the same longname for multiple languages.
> Contrary to the implications of its name, longnames in major ibus engines are
not
that long :)
Mozc engine's longname "Mozc (US keyboard layout)" is too long! Displaying this
longname in mode line is really annoying... (See screenshot)
> ... especially on Chrome OS which has a "Sync user preferences with Cloud"
feature.
I see, but I can't still understand why mozc provides two different engines for
the
same input method. I think keyboard layout should be selected in mozc
properties
tool.
Thanks.
Original comment by [email protected]
on 31 May 2010 at 5:29
Attachments:
- [Screenshot-scratch - emacs.png](https://storage.googleapis.com/google-code-attachments/mozc/issue-8/comment-4/Screenshot-*scratch* - emacs.png)
from mozc.
Related Issues (20)
- Mozc does not seem to work under VanillaOS HOT 2
- Typing issue: コロンビア HOT 1
- Migration of Bazel dependency system to Bzlmod.
- Typing issue: 旧制高校
- Typing issue: 文学士
- Typing issue: 接續
- Typing issue: 巻次
- Typing issue: 搬器
- Typing issue: 原始共産主義
- Typing issue: 孔版印刷 HOT 1
- Typing issue: 写真植字
- Typing issue: 鶏卵紙 HOT 2
- Typing issue: 魹ヶ崎
- Typing issue: 桾(単漢字変換)
- Typing issue: 掖谷/棭谷
- Typing issue: 掖/棭(単漢字変換)
- Typing issue: 敏馬, 敏馬神社
- Typing issue: 結了
- Typing issue: 二簡字
- Mozc incorrectly treats right-click combined with certain keys as a dead-key modifier under Wine HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from mozc.