Re: Luit and screen [was: anti-luit]

2001-07-06 Thread Michael Schroeder
> It's UTF-8..UTF-8 support is good as far as it goes but there's no support > for double width characters. The next version of screen will support double width UTF-8 chars. Cheers, Michael. -- Michael Schroeder [EMAIL PROTECTED] main(_){while(_=~getchar())p

Re: Luit and screen [was: anti-luit]

2001-07-05 Thread Bruno Haible
Tomohiro KUBOTA writes: > However, softwares of GNU Project will have to be assigned to FSF. > (Note the difference between merely GPL-ed softwares and GNU Project > softwares.) This FSF's way is to guard itself legally. This is not true in this generality. There are packages in the GNU project

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread David Starner
> X11 license is compatible with the GPL. This means X11-licensed softwares > can be used as a basis of GPL-ed softwares. However, softwares of GNU > Project will have to be assigned to FSF. (Note the difference between > merely GPL-ed softwares and GNU Project softwares.) This FSF's way is >

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Tomohiro KUBOTA
Hi, At Wed, 4 Jul 2001 20:39:30 +0100 (BST), Robert de Bath wrote: > Oops, I just went back to the GNU site; wrong licence. > The _X11_ licence is compatible with the GPL ... > so what's the problem Juliusz? You won't be using GPL code from outside > in luit so there's no 'infection'. X11 lice

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Robert de Bath
On Wed, 4 Jul 2001, Markus Kuhn wrote: > On Wed, 4 Jul 2001, Robert de Bath wrote: > > On 1 Jul 2001, Juliusz Chroboczek wrote: > > > RB> Tho I do agree that luit should be integrated into screen eventually. > > > Impossible for licensing reasons. I should hope that luit will get > > > into the

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Pablo Saratxaga
Kaixo! On Wed, Jul 04, 2001 at 09:28:28AM +0100, Markus Kuhn wrote: > You can even add LGPLed code to MIT-licences code without anything > bad happening to either. Not exactly, you can *link* code under LGPL with MIT-licences code. But you cannot put LGPL code in a same file with other non (L)G

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Edmund GRIMLEY EVANS
Markus Kuhn <[EMAIL PROTECTED]>: > The GPL is an absolutely fabulous idea, but since there is so much > unjustified phobia around it, I'd recommed to donate anything that you > produce related to support the use of UTF-8 under POSIX to the public > domain (as I did with all my font and other UCS

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Markus Kuhn
On Wed, 4 Jul 2001, Robert de Bath wrote: > On 1 Jul 2001, Juliusz Chroboczek wrote: > > RB> Tho I do agree that luit should be integrated into screen eventually. > > Impossible for licensing reasons. I should hope that luit will get > > into the XFree86 tree. > Shame, I assume you're using code

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Edmund GRIMLEY EVANS
Juliusz Chroboczek <[EMAIL PROTECTED]>: > RB> Tho I do agree that luit should be integrated into screen eventually. > > Impossible for licensing reasons. I should hope that luit will get > into the XFree86 tree. What are those reasons? Why can't it be dual-licensed? Edmund - Linux-UTF8: i18

Re: Luit and screen [was: anti-luit]

2001-07-04 Thread Robert de Bath
On 1 Jul 2001, Juliusz Chroboczek wrote: > RB> Tho I do agree that luit should be integrated into screen eventually. > > Impossible for licensing reasons. I should hope that luit will get > into the XFree86 tree. Shame, I assume you're using code that has to stay under the MIT licence. I've ju