Re: RFS: scim-python: python bindings and input methods for scim
Hi and thanks for pointing out. On Thu, Jul 24, 2008 at 01:15:06AM +0200, Bas Wijnen wrote: ... > > This should have been "In copyright" file describing license term in the > > package, you (Mr. Li) have:" > > > > > > LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public > > > > License. On Debian systems, the complete text may be found in > > > > /usr/share/common-licenses/LGPL-2.1. > > > > > > > > LGPL-2+ can also be treated as version 3 of GNU Lesser General Public > > > > License. On Debian systems, the complete text may be found in > > > > /usr/share/common-licenses/LGPL-3. ... > I did read it now, but I still don't understand it. The copyright file > doesn't talk about the GPL anywhere (except in the python part about > compatibility, but that's not about versions), it only talks about LGPL > versions. Yes. > You quoted this part of the copyright file (it's still quoted above). Yes. > Do I understand correctly that your problem is "Mr. Li talks about > GPL, but the files are licensed LGPL"? My problem was there was no need to make this statement in this copyright file. Especially out of blue reference to LGPL2.1 and LGPL3 since it is standard acronym. Hmmm... I see LGPL. Sorry... I should have said differently. > I would agree that he should not do this; I'm just saying that you seem > to have misread the file, because de doesn't talk about the GPL. > ;-) Aha, that is right. It was LGPL2.1 and 3. I should have been tired. I still think removing such excess will cut doen in confusion. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
On Wed, Jul 23, 2008 at 10:05:25PM +0900, Osamu Aoki wrote: > Hi Bas, Hi, > I may have made confusing statement for casual observer... > > On Mon, Jul 21, 2008 at 01:09:02PM +0200, Bas Wijnen wrote: > > On Mon, Jul 21, 2008 at 10:06:27AM +0900, Osamu Aoki wrote: > > > In License, you have: > > This should have been "In copyright" file describing license term in the > package, you (Mr. Li) have:" > > > > LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public > > > License. On Debian systems, the complete text may be found in > > > /usr/share/common-licenses/LGPL-2.1. > > > > > > LGPL-2+ can also be treated as version 3 of GNU Lesser General Public > > > License. On Debian systems, the complete text may be found in > > > /usr/share/common-licenses/LGPL-3. > > > --- > > > > > > These are missleading. > > > > > I do not think you need these additional (and very misleading when > > > mentioning > > > GPL3) text here. They are properly addressed in respective license or in > > > source code as "or (at your option) any later version." > > > > You seem to have misread the license file (I didn't check, but only read > > what you quoted). It talks about LGPL-3, not about GPL-3. It's not > > misleading, just complete. > > I clearly made you confused. If you read packager's copyright file, you > should have understood my comment. I did read it now, but I still don't understand it. The copyright file doesn't talk about the GPL anywhere (except in the python part about compatibility, but that's not about versions), it only talks about LGPL versions. You quoted this part of the copyright file (it's still quoted above). Do I understand correctly that your problem is "Mr. Li talks about GPL, but the files are licensed LGPL"? I would agree that he should not do this; I'm just saying that you seem to have misread the file, because de doesn't talk about the GPL. ;-) Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.html signature.asc Description: Digital signature
Re: RFS: scim-python: python bindings and input methods for scim
On Wed, Jul 23, 2008 at 09:59:41PM +0800, Zhengpeng Hou wrote: > Hi all, > > > > > What I know as a part of SCIM package team: > > * The KDE libraries were behind Gnome ones to support immodule. > > * Some SCIM package seems to disable skim support by the maintainer patch. > this is not what I'm talking about, I know what you are talking is > something like skim-scim-pinyin. scim-tables has 90_disable-skim.dpatch So I assume it disables skim > > If you think skim support is important and these are unjustly removing > > support, please povide patch+test result report to us. > AFAIK: every SCIM engine module can work well with skim, even they > haven't provide > a kde set up fronted for skim, like scim-pinyin, scim-chewing, etc can > work just out-of-the-box > with skim. I don't know why scim-python can not work with skim. I do not know either. > > This is volunteer work. Please do not tell people "you should be able > > to do this if you learn how...". If you know better, tell us the > > answer. Quite honestly, I feel the same way for skim support but I do > > not have time to test unfamiliar programs. > As I've said above, every modules of scim can work with skim, but not > scim-python. I raised up this issue > just wanna feedback, but not complann here. Just like a bug report, > the difference is scim-python is not > in archive, I happened know it, wanna have a try, and then feedback. Please also give us feed back on good old scim-tables. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
2008/7/23 Osamu Aoki <[EMAIL PROTECTED]>: > On Wed, Jul 23, 2008 at 09:59:41PM +0800, Zhengpeng Hou wrote: >> Hi all, >> >> >> >> > What I know as a part of SCIM package team: >> > * The KDE libraries were behind Gnome ones to support immodule. >> > * Some SCIM package seems to disable skim support by the maintainer patch. >> this is not what I'm talking about, I know what you are talking is >> something like skim-scim-pinyin. > > scim-tables has 90_disable-skim.dpatch > So I assume it disables skim come on, please look at the source in scim-tables-0.5.7/skim and try to figure out what on earth those code for. these just for set up UI, but not others. and the following patch: @DPATCH@ diff -urNad scim-tables-0.5.7~/Makefile.am scim-tables-0.5.7/Makefile.am --- scim-tables-0.5.7~/Makefile.am 2005-12-05 01:13:12.0 -0600 +++ scim-tables-0.5.7/Makefile.am 2007-04-28 01:50:35.0 -0500 @@ -30,7 +30,7 @@ SKIM_SUBDIR=skim endif -SUBDIRS= docs intl icons m4 po src tables $(SKIM_SUBDIR) +SUBDIRS= docs intl icons m4 po src tables MAINTAINERCLEANFILES = Makefile.in aclocal.m4 configure $(AUX_DIST) diff -urNad scim-tables-0.5.7~/Makefile.in scim-tables-0.5.7/Makefile.in --- scim-tables-0.5.7~/Makefile.in 2006-10-08 10:57:57.0 -0500 +++ scim-tables-0.5.7/Makefile.in 2007-04-28 01:50:35.0 -0500 @@ -75,7 +75,7 @@ uninstall-recursive ETAGS = etags CTAGS = ctags -DIST_SUBDIRS = docs intl icons m4 po src tables skim +DIST_SUBDIRS = docs intl icons m4 po src tables DISTFILES = $(DIST_COMMON) $(DIST_SOURCES) $(TEXINFOS) $(EXTRA_DIST) distdir = $(PACKAGE)-$(VERSION) top_distdir = $(distdir) is just to disable build the set up UI for skim, without this, scim-table can also work with skim, but without the set up in skim. >> > If you think skim support is important and these are unjustly removing >> > support, please povide patch+test result report to us. >> AFAIK: every SCIM engine module can work well with skim, even they >> haven't provide >> a kde set up fronted for skim, like scim-pinyin, scim-chewing, etc can >> work just out-of-the-box >> with skim. I don't know why scim-python can not work with skim. > > I do not know either. > >> > This is volunteer work. Please do not tell people "you should be able >> > to do this if you learn how...". If you know better, tell us the >> > answer. Quite honestly, I feel the same way for skim support but I do >> > not have time to test unfamiliar programs. >> As I've said above, every modules of scim can work with skim, but not >> scim-python. I raised up this issue >> just wanna feedback, but not complann here. Just like a bug report, >> the difference is scim-python is not >> in archive, I happened know it, wanna have a try, and then feedback. > > Please also give us feed back on good old scim-tables. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > > Osamu > > -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: http://getfiregpg.org iEYEARECAAYFAkiHPcEACgkQJrhDLBNiZtx/eQCeNF+3xmzMzHkNidsY9VJze81A o2MAn0Qv/UTlsd4OqpVAS6h3d87bxGUT =XcgY -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi all, -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: http://getfiregpg.org iEYEARECAAYFAkiHOYcACgkQJrhDLBNiZtw5+QCfVeiHOqWYnSkMZYj3xkjD2mqk FhEAn2qZ5vs+wJMgXD10oJrXBi73ciQg =YT0o -END PGP SIGNATURE- > What I know as a part of SCIM package team: > * The KDE libraries were behind Gnome ones to support immodule. > * Some SCIM package seems to disable skim support by the maintainer patch. this is not what I'm talking about, I know what you are talking is something like skim-scim-pinyin. > > If you think skim support is important and these are unjustly removing > support, please povide patch+test result report to us. AFAIK: every SCIM engine module can work well with skim, even they haven't provide a kde set up fronted for skim, like scim-pinyin, scim-chewing, etc can work just out-of-the-box with skim. I don't know why scim-python can not work with skim. > This is volunteer work. Please do not tell people "you should be able > to do this if you learn how...". If you know better, tell us the > answer. Quite honestly, I feel the same way for skim support but I do > not have time to test unfamiliar programs. As I've said above, every modules of scim can work with skim, but not scim-python. I raised up this issue just wanna feedback, but not complann here. Just like a bug report, the difference is scim-python is not in archive, I happened know it, wanna have a try, and then feedback. Cheers Zhengpeng Hou -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
Hi, On Fri, Jun 27, 2008 at 08:27:32AM +0800, Zhengpeng Hou wrote: > 2008/6/22 LI Daobing (李道兵) <[EMAIL PROTECTED]>: > > Hello, > > > > 2008/6/22 ZhengPeng Hou <[EMAIL PROTECTED]>: > >> On Sun, Jun 22, 2008 at 10:43:18AM +0800, LI Daobing (李道兵) wrote: > >> Hi, > >> Would u mind tell me how to use it? after I built the packge with your > >> source tarball(built with updated sid sbuild), and installed those > >> binary packages, except the dbg one, re-login, I could not have it in > >> skim. so is there anything wrong? or it can not work with skim? > > > > I does not test with skim, and it should does NOT work, please test with > > scim. > > > skim is just a kde fronted of scim, I don't think there is anything > specific to skim. if scim-python > can not work with skim, then we'd firstly check what's wrong with scim-python. > Cheers > Zhengpeng Hou What I know as a part of SCIM package team: * The KDE libraries were behind Gnome ones to support immodule. * Some SCIM package seems to disable skim support by the maintainer patch. If you think skim support is important and these are unjustly removing support, please povide patch+test result report to us. This is volunteer work. Please do not tell people "you should be able to do this if you learn how...". If you know better, tell us the answer. Quite honestly, I feel the same way for skim support but I do not have time to test unfamiliar programs. Thanks, Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
Hi Bas, I may have made confusing statement for casual observer... On Mon, Jul 21, 2008 at 01:09:02PM +0200, Bas Wijnen wrote: > On Mon, Jul 21, 2008 at 10:06:27AM +0900, Osamu Aoki wrote: > > In License, you have: This should have been "In copyright" file describing license term in the package, you (Mr. Li) have:" > > LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public > > License. On Debian systems, the complete text may be found in > > /usr/share/common-licenses/LGPL-2.1. > > > > LGPL-2+ can also be treated as version 3 of GNU Lesser General Public > > License. On Debian systems, the complete text may be found in > > /usr/share/common-licenses/LGPL-3. > > --- > > > > These are missleading. > > > I do not think you need these additional (and very misleading when > > mentioning > > GPL3) text here. They are properly addressed in respective license or in > > source code as "or (at your option) any later version." > > You seem to have misread the license file (I didn't check, but only read > what you quoted). It talks about LGPL-3, not about GPL-3. It's not > misleading, just complete. I clearly made you confused. If you read packager's copyright file, you should have understood my comment. > The files are distributed with multiple licenses, namely LGPL-2, > LGPL-2.1, and LGPL-3. Later versions are automatically added to that > list as they are released. Yep. > As always when receiving multiple licensed files, debian/copyright > should list them all. Listing licenses which aren't released yet isn't > possible of course, but listing all currently available options is a > good idea IMO. That's what the part you quoted does. Yep. The issue I complained is authogonal to what you are telling us. > Thanks, Thanks, Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
On Mon, Jul 21, 2008 at 10:06:27AM +0900, Osamu Aoki wrote: > In License, you have: > LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public > License. On Debian systems, the complete text may be found in > /usr/share/common-licenses/LGPL-2.1. > > LGPL-2+ can also be treated as version 3 of GNU Lesser General Public > License. On Debian systems, the complete text may be found in > /usr/share/common-licenses/LGPL-3. > --- > > These are missleading. > I do not think you need these additional (and very misleading when mentioning > GPL3) text here. They are properly addressed in respective license or in > source code as "or (at your option) any later version." You seem to have misread the license file (I didn't check, but only read what you quoted). It talks about LGPL-3, not about GPL-3. It's not misleading, just complete. The files are distributed with multiple licenses, namely LGPL-2, LGPL-2.1, and LGPL-3. Later versions are automatically added to that list as they are released. As always when receiving multiple licensed files, debian/copyright should list them all. Listing licenses which aren't released yet isn't possible of course, but listing all currently available options is a good idea IMO. That's what the part you quoted does. Thanks, Bas -- I encourage people to send encrypted e-mail (see http://www.gnupg.org). If you have problems reading my e-mail, use a better reader. Please send the central message of e-mails as plain text in the message body, not as HTML and definitely not as MS Word. Please do not use the MS Word format for attachments either. For more information, see http://pcbcn10.phys.rug.nl/e-mail.html signature.asc Description: Digital signature
Re: RFS: scim-python: python bindings and input methods for scim
Hi, I have changed svn content. Explanation below. Please ack these changes are OK then we can do upload. > >> The package can be found on mentors.debian.net: > >> - URL: http://mentors.debian.net/debian/pool/main/s/scim-python > >> - Source repository: deb-src http://mentors.debian.net/debian unstable > >> main contrib non-free > >> - dget > >> http://mentors.debian.net/debian/pool/main/s/scim-python/scim-python_0.1.12-1.dsc > > > > Add this to SVN too, please. > > > Done, and new version have uploaded to debian-mentors. In License, you have: LGPL-2+ can also be treated as version 2.1 of GNU Lesser General Public License. On Debian systems, the complete text may be found in /usr/share/common-licenses/LGPL-2.1. LGPL-2+ can also be treated as version 3 of GNU Lesser General Public License. On Debian systems, the complete text may be found in /usr/share/common-licenses/LGPL-3. --- These are missleading. LGPL2 states: 3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices. LGPL2.1 states: [This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.] I do not think you need these additional (and very misleading when mentioning GPL3) text here. They are properly addressed in respective license or in source code as "or (at your option) any later version." If you had reason to change from LGPL to GPL, you need to make changes as specified but I see no reason to do so. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
Hello, On Sun, Jul 20, 2008 at 5:02 PM, Osamu Aoki <[EMAIL PROTECTED]> wrote: > On Sat, Jun 21, 2008 at 11:39:09PM +0800, LI Daobing (李道兵) wrote: >> Dear mentors, >> >> I am looking for a sponsor for my package "scim-python". >> * Package name: scim-python >> Version : 0.1.12 >> Upstream Authors: Huang Peng >> Ming Hua >> Yu Fan >> 余钰炜 >> * URL : http://code.google.com/p/scim-python/ >> * License : LGPL >> Programming Lang: Python, C++ >> Description : python language binding and input methods for SCIM >> > > Looks interesting... > >> The package can be found on mentors.debian.net: >> - URL: http://mentors.debian.net/debian/pool/main/s/scim-python >> - Source repository: deb-src http://mentors.debian.net/debian unstable >> main contrib non-free >> - dget >> http://mentors.debian.net/debian/pool/main/s/scim-python/scim-python_0.1.12-1.dsc > > Add this to SVN too, please. > Done, and new version have uploaded to debian-mentors. -- Best Regards, LI Daobing
Re: RFS: scim-python: python bindings and input methods for scim
On Sat, Jun 21, 2008 at 11:39:09PM +0800, LI Daobing (李道兵) wrote: > Dear mentors, > > I am looking for a sponsor for my package "scim-python". > * Package name: scim-python > Version : 0.1.12 > Upstream Authors: Huang Peng > Ming Hua > Yu Fan > 余钰炜 > * URL : http://code.google.com/p/scim-python/ > * License : LGPL > Programming Lang: Python, C++ > Description : python language binding and input methods for SCIM > Looks interesting... > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/s/scim-python > - Source repository: deb-src http://mentors.debian.net/debian unstable > main contrib non-free > - dget > http://mentors.debian.net/debian/pool/main/s/scim-python/scim-python_0.1.12-1.dsc Add this to SVN too, please. Osamu -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
2008/6/22 LI Daobing (李道兵) <[EMAIL PROTECTED]>: > Hello, > > 2008/6/22 ZhengPeng Hou <[EMAIL PROTECTED]>: >> On Sun, Jun 22, 2008 at 10:43:18AM +0800, LI Daobing (李道兵) wrote: >> Hi, >> Would u mind tell me how to use it? after I built the packge with your >> source tarball(built with updated sid sbuild), and installed those >> binary packages, except the dbg one, re-login, I could not have it in >> skim. so is there anything wrong? or it can not work with skim? > > I does not test with skim, and it should does NOT work, please test with scim. > skim is just a kde fronted of scim, I don't think there is anything specific to skim. if scim-python can not work with skim, then we'd firstly check what's wrong with scim-python. Cheers Zhengpeng Hou
Re: RFS: scim-python: python bindings and input methods for scim
Hello, 2008/6/22 ZhengPeng Hou <[EMAIL PROTECTED]>: > On Sun, Jun 22, 2008 at 10:43:18AM +0800, LI Daobing (李道兵) wrote: > Hi, > Would u mind tell me how to use it? after I built the packge with your > source tarball(built with updated sid sbuild), and installed those > binary packages, except the dbg one, re-login, I could not have it in > skim. so is there anything wrong? or it can not work with skim? I does not test with skim, and it should does NOT work, please test with scim. thanks. -- Best Regards, LI Daobing -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
On Sun, Jun 22, 2008 at 10:43:18AM +0800, LI Daobing (李道兵) wrote: Hi, Would u mind tell me how to use it? after I built the packge with your source tarball(built with updated sid sbuild), and installed those binary packages, except the dbg one, re-login, I could not have it in skim. so is there anything wrong? or it can not work with skim? > Hello, > > On Sun, Jun 22, 2008 at 9:05 AM, Ming Hua <[EMAIL PROTECTED]> wrote: > > On Sun, Jun 22, 2008 at 12:00:04AM +0800, LI Daobing (李道兵) wrote: > >> On Sat, Jun 21, 2008 at 11:48 PM, Zhengpeng Hou <[EMAIL PROTECTED]> wrote: > >> > what's the license of the pinyin table data in scim-pinyin? > >> > >> not declared, I will ask the upstream authors. > >> > >> and this file is not required. we can prepare a dfsg version. > > > > The Pinyin data in scim-python are not DFSG-free as far as I know. > > > there are two pinyin table: > 1. > http://code.google.com/p/scim-python/source/browse/trunk/data/pinyin_table.txt > 2. > http://code.google.com/p/scim-python/downloads/detail?name=pinyin-database-0.1.10.5.tar.bz2&can=2&q= > > you mean which one is non-free, or both? > > -- > Best Regards, > LI Daobing > > > -- > To UNSUBSCRIBE, email to [EMAIL PROTECTED] > with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] signature.asc Description: Digital signature
Re: RFS: scim-python: python bindings and input methods for scim
On Sat, Jun 21, 2008 at 11:48 PM, Zhengpeng Hou <[EMAIL PROTECTED]> wrote: > what's the license of the pinyin table data in scim-pinyin? not declared, I will ask the upstream authors. and this file is not required. we can prepare a dfsg version. -- Best Regards, LI Daobing -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: RFS: scim-python: python bindings and input methods for scim
what's the license of the pinyin table data in scim-pinyin? 2008/6/21 LI Daobing (李道兵) <[EMAIL PROTECTED]>: > Dear mentors, > > I am looking for a sponsor for my package "scim-python". > * Package name: scim-python > Version : 0.1.12 > Upstream Authors: Huang Peng >Ming Hua >Yu Fan >余钰炜 > * URL : http://code.google.com/p/scim-python/ > * License : LGPL > Programming Lang: Python, C++ > Description : python language binding and input methods for SCIM > > It builds these binary packages: > python-scim - Python language binding for SCIM > python-scim-dbg - Python language binding for SCIM (debug extension) > scim-python - Python input method framework for SCIM > scim-python-common - Python language binding for SCIM - Common files > scim-python-englishwriter - English writer input method for scim-python > scim-python-xingma - XingMa input method for scim-python > > I split it into 6 package. first it provide a public module "scim", so > I think there should be a package named "python-scim" and another > package "python-scim-dbg". and the input method framework is put in > "scim-python", two input methods in two separated packages. and all > the 5 packages share a i18n domain "scim-python", so I put the mo > files and the shared icons in the "scim-python-common" package > > The package appears to be lintian clean. > > The upload would fix these bugs: 487360 > > The package can be found on mentors.debian.net: > - URL: http://mentors.debian.net/debian/pool/main/s/scim-python > - Source repository: deb-src http://mentors.debian.net/debian unstable > main contrib non-free > - dget > http://mentors.debian.net/debian/pool/main/s/scim-python/scim-python_0.1.12-1.dsc > > I would be glad if someone uploaded this package for me. > > Kind regards > LI Daobing > > -- > Best Regards, > LI Daobing >
