cgiirc-general Mailing List for CGI:IRC (Page 12)
Brought to you by:
dgl
You can subscribe to this list here.
| 2002 |
Jan
|
Feb
(2) |
Mar
(21) |
Apr
(9) |
May
(21) |
Jun
(18) |
Jul
(20) |
Aug
(16) |
Sep
(26) |
Oct
(25) |
Nov
(17) |
Dec
(10) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2003 |
Jan
(16) |
Feb
(25) |
Mar
(16) |
Apr
(13) |
May
(9) |
Jun
(20) |
Jul
(7) |
Aug
(17) |
Sep
(20) |
Oct
(19) |
Nov
(30) |
Dec
(20) |
| 2004 |
Jan
(15) |
Feb
(42) |
Mar
(18) |
Apr
(15) |
May
(24) |
Jun
(10) |
Jul
(8) |
Aug
(19) |
Sep
(6) |
Oct
(1) |
Nov
(3) |
Dec
(2) |
| 2005 |
Jan
(1) |
Feb
(8) |
Mar
(8) |
Apr
(3) |
May
(4) |
Jun
(3) |
Jul
(5) |
Aug
(3) |
Sep
(2) |
Oct
(29) |
Nov
(1) |
Dec
(3) |
| 2006 |
Jan
(1) |
Feb
(8) |
Mar
(1) |
Apr
(6) |
May
(6) |
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
| 2007 |
Jan
(1) |
Feb
(3) |
Mar
(4) |
Apr
(2) |
May
(2) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
(1) |
| 2008 |
Jan
|
Feb
|
Mar
(1) |
Apr
(6) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2009 |
Jan
(1) |
Feb
|
Mar
(2) |
Apr
|
May
|
Jun
(1) |
Jul
(3) |
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
| 2010 |
Jan
|
Feb
(1) |
Mar
(2) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2011 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
(3) |
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(1) |
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2024 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(4) |
Oct
|
Nov
|
Dec
|
|
From: David L. <dg...@dg...> - 2004-02-05 21:07:15
|
Dunkin wrote: > images directory, is inside the cgi-bin folder.... > > using default setting > > image_path = images > > or > > image_path = /cgi-bin/images > Put them somewhere that they can be served as static files (the apache error_log would have told you this..). |
|
From: Dunkin <du...@hi...> - 2004-02-05 20:58:15
|
images directory, is inside the cgi-bin folder.... using default setting image_path = images or image_path = /cgi-bin/images and the graphics don't load... any suggestions? |
|
From: stephen f. <stu...@ya...> - 2004-02-05 18:55:55
|
nm --------------------------------- Do you Yahoo!? Yahoo! Finance: Get your refund fast by filing online |
|
From: David L. <dg...@dg...> - 2004-02-05 11:10:16
|
sil wrote: > Hi, > > Firstly I am very happy with powerdns, I found it easy to setup and > use :) [..] I'm glad to hear that, but this is the CGI:IRC list not powerdns ;). |
|
From: Onslo <on...@ni...> - 2004-02-04 20:24:14
|
Not sure if this made it last time, so i'll send it again.... Guys, I have played around with UTF-8 and CGI:IRC before, but have only just got to a point whereby my findings are understandable to myself ! Enabling UTF-8 (Unicode Charset) in CGI:IRC is relatively easy, but you have to define the charset in numerous places for it to be accepted on both input and output. I'll use the ie.pm file as an example, but the same should apply to all interfaces really. Add this line inside every HEAD tag within the ie.pm file .. <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> that way you are defining the browser encoding that should be used by IE. Then you have to tell the CGI::IRC form to accept UTF-8 as an input charset within it's form structure. I managed this by adding... ACCEPT-CHARSET="UTF-8" within the form tag for hsubmit and myform. eg. <form ACCEPT-CHARSET="UTF-8" name="myform" onSubmit="return cmd();" class="form-form"> Hope that helps -- Best regards, Onslo mailto:on...@ni... |
|
From: Onslo <on...@ni...> - 2004-02-04 18:13:54
|
Guys, I have played around with UTF-8 and CGI:IRC before, but have only just got to a point whereby my findings are understandable to myself ! Enabling UTF-8 (Unicode Charset) in CGI:IRC is relatively easy, but you have to define the charset in numerous places for it to be accepted on both input and output. I'll use the ie.pm file as an example, but the same should apply to all interfaces really. Add this line inside every HEAD tag within the ie.pm file .. <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> that way you are defining the browser encoding that should be used by IE. Then you have to tell the CGI::IRC form to accept UTF-8 as an input charset within it's form structure. I managed this by adding... ACCEPT-CHARSET="UTF-8" within the form tag for hsubmit and myform. eg. <form ACCEPT-CHARSET="UTF-8" name="myform" onSubmit="return cmd();" class="form-form"> Hope that helps -- Best regards, Onslo mailto:on...@ni... |
|
From: Onslo <on...@ni...> - 2004-02-04 17:27:55
|
seems i am having a problem posting to this list, so i'll try again...hope it's not annoying anyone. This was what i previoulsy tried to send to the list, but failed....think it got to David however. . Guys, I have played around with UTF-8 and CGI:IRC before, but have only just got to a point whereby my findings are understandable to myself ! Enabling UTF-8 (Unicode Charset) in CGI:IRC is relatively easy, but you have to define the charset in numerous places for it to be accepted on both input and output. I'll use the ie.pm file as an example, but the same should apply to all interfaces really. Add this line inside every HEAD tag within the ie.pm file .. <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> that way you are defining the browser encoding that should be used by IE. Then you have to tell the CGI::IRC form to accept UTF-8 as an input charset within it's form structure. I managed this by adding... ACCEPT-CHARSET="UTF-8" within the form tag for hsubmit and myform. eg. <form ACCEPT-CHARSET="UTF-8" name="myform" onSubmit="return cmd();" class="form-form"> Hope that helps, it certainly works for me! Onslo |
|
From: Onslo <on...@ni...> - 2004-02-04 17:17:25
|
Oops, it appears I mailed this directly to David without cc'ing the list - sorry ! Here's what I sent for the benefit of everyone else (perhaps?) Guys, I have played around with UTF-8 and CGI:IRC before, but have only just got to a point whereby my findings are understandable to myself ! Enabling UTF-8 (Unicode Charset) in CGI:IRC is relatively easy, but you have to define the charset in numerous places for it to be accepted on both input and output. I'll use the ie.pm file as an example, but the same should apply to all interfaces really. Add this line inside every HEAD tag within the ie.pm file .. <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> that way you are defining the browser encoding that should be used by IE. Then you have to tell the CGI::IRC form to accept UTF-8 as an input charset within it's form structure. I managed this by adding... ACCEPT-CHARSET="UTF-8" within the form tag for hsubmit and myform. eg. <form ACCEPT-CHARSET="UTF-8" name="myform" onSubmit="return cmd();" class="form-form"> Hope that helps Onslo Wednesday, February 4, 2004, 1:04:59 AM, you wrote: JW> On Tue, 3 Feb 2004, David Leadbeater wrote: >> # The charset to send to IRC, to send anything other than UTF-8 you will >> # need the Text::Iconv perl module installed. Any character set supported >> # by your system iconv should work here. JW> I just remembered the module Encode (perldoc Encode)... it is standard but JW> I think it only comes with perl 5.8, so Text::Iconv should be more JW> portable. -- Best regards, Onslo mailto:on...@ni... |
|
From: David L. <dg...@dg...> - 2004-02-04 10:53:35
|
Onslo wrote: > Guys, > > I have played around with UTF-8 and CGI:IRC before, but have only just > got to a point whereby my findings are understandable to myself ! [..] I've basically done this, except it uses a different method as we send via XMLHTTP now (this requires UTF-8 which is the main reason for the change). And obviously there is also code to allow changing of encoding so it doesn't totally break if people need a different character set on IRC. |
|
From: David L. <dg...@dg...> - 2004-02-04 10:14:33
|
Julien WAJSBERG wrote: > On Tue, 3 Feb 2004, David Leadbeater wrote: > > > # The charset to send to IRC, to send anything other than UTF-8 you will > > # need the Text::Iconv perl module installed. Any character set supported > > # by your system iconv should work here. > > I just remembered the module Encode (perldoc Encode)... it is standard but > I think it only comes with perl 5.8, so Text::Iconv should be more > portable. It seems to require perl 5.8 (well 5.7), so for now I'll leave it with Text::Iconv I think. I probably ought to test this on 5.8 to see that my utf8 stuff doesn't interfere with any of perl's.. |
|
From: Julien W. <fl...@mi...> - 2004-02-04 01:05:26
|
On Tue, 3 Feb 2004, David Leadbeater wrote: > # The charset to send to IRC, to send anything other than UTF-8 you will > # need the Text::Iconv perl module installed. Any character set supported > # by your system iconv should work here. I just remembered the module Encode (perldoc Encode)... it is standard but I think it only comes with perl 5.8, so Text::Iconv should be more portable. -- Julien |
|
From: Reinis R. <re...@ap...> - 2004-02-03 22:22:47
|
And what about the daemon / standalone version of CGI:IRC (which was in future plans quite a time ago)? Roze is still waiting for some less resource consuming solution for large mases.. ----- Original Message ----- From: "David Leadbeater" <dg...@dg...> To: <cgi...@li...> Sent: Tuesday, February 03, 2004 7:57 PM Subject: [cgiirc-general] CGI:IRC 0.5.5pre1 > The main change is that the main interface uses only UTF-8, by default > UTF-8 will be sent to IRC. There is a new configuration option "irc charset" > from the config file: > # The charset to send to IRC, to send anything other than UTF-8 you will > # need the Text::Iconv perl module installed. Any character set supported > # by your system iconv should work here. > # If you see the wrong characters in CGI:IRC or with a normal IRC client > # you probably need to change this. > # Extended ASCII: > #irc charset = iso-8859-1 > > Unfortantely this isn't going to just work like the old CGI:IRC did when > there are normal IRC clients involved, between CGI:IRC clients the default > should work fine however.. > > I also fixed the www. url bug. > > You can get it from http://babylon.otherwize.co.uk/releases/ or cvs > tag rel_0_5_5pre1. > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > cgiirc-general mailing list > cgi...@li... > https://lists.sourceforge.net/lists/listinfo/cgiirc-general > |
|
From: David L. <dg...@dg...> - 2004-02-03 21:57:48
|
The main change is that the main interface uses only UTF-8, by default UTF-8 will be sent to IRC. There is a new configuration option "irc charset" from the config file: # The charset to send to IRC, to send anything other than UTF-8 you will # need the Text::Iconv perl module installed. Any character set supported # by your system iconv should work here. # If you see the wrong characters in CGI:IRC or with a normal IRC client # you probably need to change this. # Extended ASCII: #irc charset = iso-8859-1 Unfortantely this isn't going to just work like the old CGI:IRC did when there are normal IRC clients involved, between CGI:IRC clients the default should work fine however.. I also fixed the www. url bug. You can get it from http://babylon.otherwize.co.uk/releases/ or cvs tag rel_0_5_5pre1. |
|
From: sil <pd...@on...> - 2004-02-03 11:25:39
|
Hi, Firstly I am very happy with powerdns, I found it easy to setup and use :) I guess this is a type of feature request, the current situation (POWERDNS 2.9.13) a lookup of host -t txt version.bind 127.0.0.1 gives version.bind text "Served by POWERDNS 2.9.13 $Id: packethandler.cc,v 1.19 2003/11/23 15:14:57 ahu Exp $" I think this is too much information leak, the version number (2.9.13) does not need to be there at least. I am proposing something similar to apache with it's ServerTokens directive http://httpd.apache.org/docs/mod/core.html#servertokens So giving the ability to hide version number if preferred (w/o editing code / re-compiling). Perhaps another way would be to allow the user to have an entry in the DB for a TXT lookup on version.bind and specify whatever they liked there (I tried this but it didn't seem to work). Thanks for a neat dns server :) Sil |
|
From: Julien W. <fl...@mi...> - 2004-02-02 20:54:24
|
On Mon, 2 Feb 2004, David Leadbeater wrote: > [sending to the mailing list too..] > peter green wrote: > [snip how utf8 works] > > mirc treats all text recived as extended ascii > > afaict x-chat trys to parse as utf-8 first and if it's not valid utf-8 > > treats it as extended ascii > > Currently the Unicode::Map8 module looks like the best thing to use (and > if it isn't installed we'll only work with iso-8859-1)... > > Anyone else have thoughts? Maybe Text::Iconv ? It seems to be somewhat standard these days. -- Julien |
|
From: David L. <dg...@dg...> - 2004-02-02 16:35:56
|
[sending to the mailing list too..] peter green wrote: [snip how utf8 works] > mirc treats all text recived as extended ascii > afaict x-chat trys to parse as utf-8 first and if it's not valid utf-8 > treats it as extended ascii Yes, this is all pretty simple, it becomes complex because we do not know what charset people will be using on IRC, at the moment it just "works" because people generally have their browser set to correctly read their local character set (and presumably their IRC client too). Now for most (US/Western Europe) people extended ascii is what they expect and this works ok with XMLHTTP (the first 0xFF chars of unicode are the same as iso-8859-1). But anything else is encoded as a unicode character with the format %uXXXX where XXXX is the hexadecimal representation of the unicode character much like other HTTP params are encoded. (btw, the thing I've been testing with on this system is the euro character). So basically all my patch does is change this %uXXXX into utf-8 and provided CGI:IRC is set to use utf-8 all should appear fine to the CGI:IRC user, however the problem now is CGI:IRC will be sending utf-8 over IRC and some people expect it to be something different (e.g. cyrillic users are probably using windows CP1251). To solve this there is going to have to be something to convert in CGI:IRC (and probably a config setting as to what to send to IRC - I think we should try to keep the HTTP side of things running in utf-8). Currently the Unicode::Map8 module looks like the best thing to use (and if it isn't installed we'll only work with iso-8859-1)... Anyone else have thoughts? |
|
From: David L. <dg...@dg...> - 2004-02-02 13:57:13
|
Maxim Shpakov wrote: > b) translate from utf8-to-plain in client.cgi I have only got as far as converting %uXXXX to real utf-8, see the attached patch (you will also need to add the line charset = utf-8 into the format (formats/default)).. Obviously if clients can't read utf-8 then they won't understand the text still. |
|
From: David L. <dg...@dg...> - 2004-02-01 17:55:05
|
Maxim Shpakov wrote: > The problem is that xmlhttp.send method it translate chars into utf8 > from msdn: > >> > >>If the input type is a BSTR, the response is always encoded as UTF-8. > >>The caller must set a Content-Type header with the appropriate content type and include a charset parameter. > > as I see the solution is: > a) use SAFEARRAY parameter type for xmlhttp.send > MSDN: > >>>If the input type is a SAFEARRAY of UI1, the response is sent as is without additional encoding. > >>>The caller must set a Content-Type header with the appropriate content type. > but jscript doesn't support safearrays... > > b) translate from utf8-to-plain in client.cgi > > what do you think? > > This bug is critical for me.. because..it doesn't allow to chat in > cyrillic language.. 0.5.3 is fine. b) is difficult, CGI:IRC currently knows nothing about encodings, also sending %uHHHH doesn't look like UTF-8 to me, it looks like some other sort of unicode encoding.. To translate unicode characters into another format (I'm assuming you use something like windows-1251?) would be difficult.. |
|
From: David L. <dg...@dg...> - 2004-02-01 16:53:51
|
Maxim wrote:
> Hello.
>
> There are encoding problems with xmlhttp_send in IE
> Mozilla is fine.
> Then browser [IE] send post request to client.cgi the encoding is
> utf-8 .. english letters are fine.. but cyrillic appears in irc as
> %u0430%u0431%u0432 unicode encoded string.. some experiments with
>
> xmlhttp.setRequestHeader("Content-type",
> "application/x-www-form-urlencoded");
>
> failed.... adding charset in header in no sense.
>
> client.cgi must convert this string from utf to some charset or..
> somehow ie must send post data in needed charset.
I don't think you can specify the charset sent (it's always utf-8),
I think maybe it's time to do utf-8 support for CGI:IRC..
(Although some IRC clients might not be able to display utf-8 still)
|
|
From: David L. <dg...@dg...> - 2004-02-01 15:18:08
|
Julien WAJSBERG wrote: > On Thu, 29 Jan 2004, David Leadbeater wrote: > > > Not that much new, main things are XMLHTTP support (so IE no longer does > > the annoying clicking), a bug with trusted-proxies was fixed (didn't work) > > some new images and various other bug fixes I've probably forgotten to > > mention. > > To make upgrades easier, could you possibly provide a diff ? > Thanks, cvs -d:pserver:cv...@cv...:/cvs co -r rel_0_5_4 cgiirc cd cgiirc cvs diff -u -r rel_0_5_3 note the images won't diff.. |
|
From: Maxim <ma...@os...> - 2004-02-01 15:17:13
|
Hello.
There are encoding problems with xmlhttp_send in IE
Mozilla is fine.
Then browser [IE] send post request to client.cgi the encoding is
utf-8 .. english letters are fine.. but cyrillic appears in irc as
%u0430%u0431%u0432 unicode encoded string.. some experiments with
xmlhttp.setRequestHeader("Content-type",
"application/x-www-form-urlencoded");
failed.... adding charset in header in no sense.
client.cgi must convert this string from utf to some charset or..
somehow ie must send post data in needed charset.
--
Best regards,
Maxim mailto:ma...@os...
|
|
From: Julien W. <fl...@mi...> - 2004-01-31 17:28:44
|
On Thu, 29 Jan 2004, David Leadbeater wrote: > Not that much new, main things are XMLHTTP support (so IE no longer does > the annoying clicking), a bug with trusted-proxies was fixed (didn't work) > some new images and various other bug fixes I've probably forgotten to > mention. To make upgrades easier, could you possibly provide a diff ? Thanks, -- Julien |
|
From: Fateyev G. <he...@an...> - 2004-01-31 05:56:39
|
Hello to all! I use cgiirc 5.3 , but after some times without writing in browser (Mozilla 1.4) cgiirc does not refresh any frames. In that time see in xchat that client in a channel. How to fix that? I use client.cgi Thanks! |
|
From: David L. <dg...@dg...> - 2004-01-31 02:21:50
|
Not that much new, main things are XMLHTTP support (so IE no longer does the annoying clicking), a bug with trusted-proxies was fixed (didn't work) some new images and various other bug fixes I've probably forgotten to mention. |
|
From: mark <ma...@ya...> - 2004-01-30 21:06:35
|
Hello, I am assuming CGI-IRC uses a fair amount of bandwidth if there is a steady amount of users at any given time. I am curious as to how much bandwidth it can consme. Examples would be great. Thnks! Mark __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/ |