Hello,

Did you set proper encoding in config file? For me it works ok with
Russian (windows-1251 codepage).

On 8/2/05, Oscar Hellstr?m <[EMAIL PROTECTED]> wrote:
> Installed the latest CVS tarball and look, i can recieve ???? and such
> from ICQ folks. However, the Vcards and status messages are messed up
> still. If someone doesn't know a quick fix, i'll tell you more about
> what happends, when and what encoding, icq client etc...


-- 
Regards,
Oleg
From [EMAIL PROTECTED]  Tue Aug  2 07:45:25 2005
From: [EMAIL PROTECTED] (Etienne LAVANANT)
Date: Tue Aug  2 07:45:34 2005
Subject: [py-transports] Advices for GNU/GPL license use
Message-ID: <[EMAIL PROTECTED]>

Hi,
I made a component from the source code of PyMSN-t 0.9.3. The component is not
related to MSN, it was just to have an example of how to use Twisted for Jabber
and use some generic jabber fonctionnalities (connection to the server,
discovery, etc.).
When my component is finished, I would like to release it so that it may be
useful to other people. I am not a developper and I am not familiar with
license use in practice. I am not sure how to do it to respect the GNU/GPL
license :

- for non-modified files, I let the original copyright;
- for files I created, I had my own copyright.
OK

The problem is for modified files:
Should I just add my copyright to the file or should I put a comment for every
single line modified to show what parts were modified? What about slightly
modified files (a couple lines removed, maybe a couple lines added)?

You may be more familiar with it than I am so if you could give me advices on
how to fully respect the GNU/GPL license, it would be great.

Thanks.

--
Etienne

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.
From [EMAIL PROTECTED]  Tue Aug  2 12:48:00 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Tue Aug  2 12:48:09 2005
Subject: [py-transports] Advices for GNU/GPL license use
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

You don't have to worry about what lines were changed or anything like 
that.
The way it's generally done is to just tack your name on the end of the 
copyright header of files that you have modified.

The only really crucial bit is that everything is GPL, including what 
you wrote from scratch. Everything else is mostly courtesy (eg, it 
isn't nice to delete the original author's name).

---

James



On 02/08/2005, at 5:45 PM, Etienne LAVANANT wrote:

> Hi,
> I made a component from the source code of PyMSN-t 0.9.3. The 
> component is not
> related to MSN, it was just to have an example of how to use Twisted 
> for Jabber
> and use some generic jabber fonctionnalities (connection to the server,
> discovery, etc.).
> When my component is finished, I would like to release it so that it 
> may be
> useful to other people. I am not a developper and I am not familiar 
> with
> license use in practice. I am not sure how to do it to respect the 
> GNU/GPL
> license :
>
> - for non-modified files, I let the original copyright;
> - for files I created, I had my own copyright.
> OK
>
> The problem is for modified files:
> Should I just add my copyright to the file or should I put a comment 
> for every
> single line modified to show what parts were modified? What about 
> slightly
> modified files (a couple lines removed, maybe a couple lines added)?
>
> You may be more familiar with it than I am so if you could give me 
> advices on
> how to fully respect the GNU/GPL license, it would be great.
>
> Thanks.
>
> --
> Etienne
>
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>

Reply via email to