On Thu, 2011-02-24 at 12:09 +0900, NIIBE Yutaka wrote: > 2011-02-24 10:57, Harshula wrote:
> > anthy description: > > "Japanese input method with Anthy as a kana-kanji converter. > > Typed roma-ji is at first converted to Hiragana, > > and Space key converts the Hiragana sequences > > to Kanji-Hiragana mixed sequence." > > IMHO, this description would be better to include: > > This is a demonstration purpose (not for real use). > > Since I'd understand some reason why m17n-lib has to claim "This > library support Japanese too", I don't say more. Have you communicated this with upstream? > > Upstream may move the libmimx-*.so out of m17n-lib into m17n-db. > > Discussions are still ongoing. > > Good. Partly, I'd agree. > > It makes sence to move m17n-lib modules/plugins out of m17n-lib and > put them, say, independent package, m17n-modules or something. It > would be decision by upstream, but this could be also done by package > maintainer independently. > > It sounds somewhat odd to me to include modules into m17n-db, since > it is not data, but program. The more complex m17n input methods are *programs*. The ja-anthy.mim file, in m17n-db, is the sole user of the libmimx-anthy.so. The .so is used by ja-anthy.mim to interface to libanthy. > If you will request upstream change for moving modules/plugins out of > m17n-lib, it would also make sence to suggest rename of modules. Name > starts by 'lib' would be better to be changed, as it is plugin module > dynamically loaded, not linked to executable at compile time. Good point. cya, # -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
