[openi18n-im:01090] Re: name space cleanup
Hideki Hiura <[email protected]>
| Newsgroups | gmane.comp.internationalization.input-methods |
|---|---|
| Message-ID | <[email protected]> |
> From: AShiZaWa KaZuNoRi <[email protected]> > I'd like to propose more extensive name space changes. It's a big change but if it is affordable for everyone, I am basically in favor of this proposal, at least in mid term if it is too radical for short term. > /etc/init.d/IIim -> /etc/init.d/iiim-server I guess in this case it would be iiimd, as iiimd is the one it is kicked from it.(A miner thing) Only one big concern of me is the M$ term "IME" which stands for Input Method Editor at M$ realm(actually this is also miner, conpared to the problem I mention later in this mail) > /usr/lib/im/leif -> /usr/lib/iiim/ime > /usr/lib/im/locale/LOC/LE -> /usr/lib/iiim/ime/IME > (no locale path component) > IME static data -> /usr/share/iiim/IME/* > IME site specific files -> /etc/iiim/ime/* > IME volatile data -> /var/lib/iiim/ime/IME/* While the "LE" is the purely UNIX term, "Language Engine", and I have also been adovocating the overriding acronym "Input Method Engine" for IME intentionally for over 10+ years, but I am still not sure it was successful. For some(most of?) people, I guess the got-feeling from IME is M$ acronym which is different from what LE means. The BIGGEST concern, which is even worse, is that huge number of people use nowadays IME as an alias for MSIME. This is catastrophic. Despite my long years of efforts to override the M$ acronym on IME, I guess I have to admit that I failed on it and I now feel it is rather appropriate to change the gear toward killing the M$ acronym "IME" which misrepresent what it actually is even for M$. Best Regards, Hideki