Re: [Pkg-ime-devel] RFS: scim-kmfl-imengine
Ming Hua wrote: I thought scim-kmfl-engine would know exactly which languages it wants to set im-switch for, instead of the system default language as Doug proposed. Just to clarify, kmfl is often used in a multilingual situation where documents are written in multiple languages and for languages which often do not have a locale associated with them. For example as a Linguistics organization we often write papers with IPA symbols in them and have developed an kmfl keyboard to easily enter the IPA characters. There is no locale for IPA. We also work in minority languages which most likely do not have a locale defined for them. Many of our Linguists have an en_XX locales as their main locale but want to use SCIM to type IPA, Chinese, Thai, Greek, Hebrew, perhaps all in the same document. If SCIM is not set up as the default IM for their working locales (ie. en_XX), then it is very cumbersome to switch to SCIM when they want to type in another language. Do I understand correctly that if SCIM is set up to handle all_ALL, then the above situation would be addressed? On all the systems I have used all_ALL is set to default not SCIM. I am very willing to not do anything with setting up SCIM startup provided SCIM will be the default for locales such as en_US, en_CA, etc, if not other IM is defined for these locales. Doug, -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: [Pkg-ime-devel] RFS: scim-kmfl-imengine
On Fri, Dec 07, 2007 at 03:52:38PM -0800, Doug Rintoul wrote: > Ming Hua wrote: > > I am curious about how you are going to set im-switch though. Are you > > going to set them just for several specific languages? Or are you going > > to set the all_ALL (pseudo-)locale setting? Or is there another way to > > set it for all languages that I don't know? > > My initial thought was to set it for the default language, i.e. the > language specified at installation time. The code I have written to do > this is as follows: > > # use im-switch to set up the scim environment > tmplang=${LC_ALL:-${LC_CTYPE:-${LANG}}} > > tl=${tmplang%%.*} > update-alternatives --install /etc/X11/xinit/xinput.d/$tl xinput-$tl \ > /etc/X11/xinit/xinput.d/scim-immodule 50 > im-switch -s scim-immodule -l $tmplang Hmm. On Sat, Dec 08, 2007 at 02:36:18PM +0900, Osamu Aoki wrote: > On Fri, Dec 07, 2007 at 05:31:20PM -0600, Ming Hua wrote: > > > And I will use the debconf question to offer to set im-switch to > > > scim-immodule if you think that would be acceptable. > > > > I have absolutely no problem with that. Im-switch setting, being a part > > of the alternative system, is always for system admin to change. And > > debconf question is a good way to do that. > > Are you sure. If 2 packages play on one configuration file, then > depending on upgrade sequence, it may conflict. You are right, the way Doug proposes (recreate the /etc/X11/xinit/xinput.d/ alternative links with different priority) indeed will cause conflicts. When I said "I have absolutely no problem", I was not thinking about things like this. What I had in mind was more like: If ll_CC locale is not handled by scim (currently scim handles all_ALL, ja_JP, ko_KR, zh_{CN,TW,HK,SG}): run "update-alternatives --install" to register im-switch for this new language If ll_CC locale is not handled by scim: run "update-alternatives --set xinput- /etc/X11/xinit/xinput.d/scim-immodule", to set the alternative to manual status as scim-immodule. This approach is still a bit fragile though, as it needs to be synchronized with scim's im-switch locale list. I thought scim-kmfl-engine would know exactly which languages it wants to set im-switch for, instead of the system default language as Doug proposed. I need to think a bit more about this. Regards, Ming 2007.12.08 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
RFS: blam 1.8.4-3
Hi all, My usual sponsor (Amaya) is away for a while and so I've been orphaned :( Package: blam Version: 1.8.4-3 Upstream Author: me URL: http://cmartin.tk/blam.html License: GPL Section: gnome This package is lintian clean. This upload fixes bug #442510, fixes a lintian warning and moves to the new menu structure. Blam is a news feed reader written in C# which supports Atom and RSS. It is already in Debian but I need a new sponsor. You can find it at http://www.cmartin.tk/blam/blam_1.8.4-3.dsc Thanks for reading, cmn -- Carlos Martín Nieto| http://www.cmartin.tk Hobbyist programmer| signature.asc Description: This is a digitally signed message part
RFS: dblatex (updated package)
Dear mentors, as my default sponsor seems to be overloaded at the moment, I am looking for an one time sponsor for the new version 0.2.8-1 of my package "dblatex". It builds these binary packages: dblatex- Produces DVI, PostScript, PDF documents from DocBook sources The package appears to be lintian clean. The upload would fix these bugs: 446871, 447607, 447616, 451267 The package can be found on mentors.debian.net: - URL: http://mentors.debian.net/debian/pool/main/d/dblatex - Source repository: deb-src http://mentors.debian.net/debian unstable main contrib non-free - dget http://mentors.debian.net/debian/pool/main/d/dblatex/dblatex_0.2.8-1.dsc I would be glad if someone uploaded this package for me. Kind regards, Andreas Hoenen -- Andreas Hoenen <[EMAIL PROTECTED]> GPG: 1024D/B888D2CE A4A6 E8B5 593A E89B 496B 82F0 728D 8B7E B888 D2CE pgpWEhFjhjOGE.pgp Description: PGP signature
Re: Ubuntu-to-Debian packaging
On Wed, Dec 05, 2007 at 01:42:56PM +0100, Cesare Tirabassi wrote: > On Wednesday 05 December 2007 04:27:28 C.J. Adams-Collier wrote: > > Do you feel that it is appropriate to copy someone else's changelog > > entry verbatim without giving credit to the original author? > > I guess you refer to mono-addins, for which I prepared an SRU in Ubuntu, > using > the patches provided by Mirco? > Yes, I partly used his changelog because, quite frankly, what was the point > of > changing it? Its the author's changelog and for him it reflected best the > content of the change, beside it ties with the history of the package. For > those not familiar with our SRU, we apply the changes in the development > version (in this case from the new Debian version) to solve a problem in our > stable release. If you look at the bug report this should be clearer to you: > > https://bugs.launchpad.net/ubuntu/+source/mono-addins/+bug/149485 > > In summary, I made the (evidently wrong) assumption that it was clear that > this was a backport of an issue already fixed in Debian. > So, in retrospect, yes, it would have been clearer to quote the source in the > changelog, something that I won't forget in the future. I've now adjusted the Ubuntu stable release updates documentation to explicitly say: As with any upload, the changelog entry must properly credit the author of the change, if it was not originally made by you. I hope this will avoid such mistakes in the future. Cheers, -- Colin Watson [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Ubuntu-to-Debian packaging
Hi, On Fri, Dec 07, 2007 at 12:16:12PM -0800, C.J. Adams-Collier wrote: > I'm sorry, what is an "SRU"? with Google the first hit I found by earching for "SRU+Ubuntu" was [1], so I think this are updates to a "stable" Ubuntu release. Best Regards, Patrick [1] https://wiki.ubuntu.com/StableReleaseUpdates -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]