I was using p11 ... so i did a config::setKey protocol 12 and seems to work (getKey returns 12 at least :P). Dunno if i'm wrong...
BTW, PMs have problems with every unicode char as it was expectable :P Rafa El Sábado, 14 de Enero de 2006 10:54, Lz escribió: > how can i activate that P12 or how it's called so i can use personal > messages? i mean, someone activated it for "everyone", but i did checkout > and i can't see them (ctrl+d shows still old protocol), nor i can find an > option for activating that :P i'd like to do my best casuality-bug-finding > there :P > > thanks > > On 1/14/06, Rafael Rodríguez <[EMAIL PROTECTED]> wrote: > > 'ñ' chars don't work :P > > > > Rafa > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > > files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > > http://ads.osdn.com/?ad_idv37&alloc_id865&opclick > > _______________________________________________ > > Amsn-devel mailing list > > Amsn-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/amsn-devel > > -- > Lz ([EMAIL PROTECTED]). > http://elezeta.bounceme.net ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Amsn-devel mailing list Amsn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/amsn-devel
