You can subscribe to this list here.
2007 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(9) |
Sep
(3) |
Oct
|
Nov
|
Dec
(1) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2008 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(5) |
Jun
(2) |
Jul
(2) |
Aug
(1) |
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2009 |
Jan
(8) |
Feb
|
Mar
|
Apr
|
May
|
Jun
(8) |
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
|
2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
(2) |
2012 |
Jan
(1) |
Feb
(1) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
2016 |
Jan
(8) |
Feb
(2) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Jérôme B. <jer...@la...> - 2017-07-14 20:23:32
|
Hello, The 1.7.1 version uses -O python : ./wicd/wicd-daemon.py: child_pid = Popen([wpath.python, "-O", Fichier binaire ./icons/192px/wicd-gtk.png correspondant ./in/scripts=wicd.in:exec %PYTHON% -O %SHARE%daemon/wicd-daemon.py $@ ./in/scripts=wicd-gtk.in:exec %PYTHON% -O %SHARE%gtk/wicd-client.py $@ ./in/scripts=wicd-cli.in:exec %PYTHON% -O %SHARE%cli/wicd-cli.py $@ ./in/scripts=wicd-curses.in:exec %PYTHON% -O %SHARE%curses/wicd-curses.py $@ On my host, I replaced -O by -OO in order make python optimize more by discarding the docstrings. It appears a few MB are saved. Why this optimization isn't enabled in the original code ? Thanks. |
From: toogley <to...@ma...> - 2016-02-26 12:56:35
|
Hey. it seems this message wasn't properly sent, or sth similar. At least i didn't found it in the archives. -------- Forwarded Message -------- Subject: how important is at_console block in other/wicd.conf Date: Sat, 20 Feb 2016 16:38:27 +0100 From: toogley <to...@ma...> To: wic...@li..., wi...@pa... Hey, my question concerns this block in other/wicd.conf: ---------------------------------------------------------------------- <!-- Comment the block below if you do not want all users logged in locally to have permission to use wicd-client. This ignores the group based permission model defined above for the "netdev" group. Note that this only applies if you are using ConsoleKit - if you do not have ConsoleKit installed and in use, then this block makes no difference either way. --> <policy at_console="true"> <allow send_destination="org.wicd.daemon"/> <allow send_interface="org.wicd.daemon"/> <allow send_destination="org.wicd.daemon.wireless"/> <allow send_interface="org.wicd.daemon.wireless"/> <allow send_destination="org.wicd.daemon.wired"/> <allow send_interface="org.wicd.daemon.wired"/> <allow send_interface="org.freedesktop.DBus.Introspectable"/> </policy> ---------------------------------------------------------------------- the current situation, as i see it: - this block is not really debug friendly, as the behavior of wicd changes in dependence whether consoleKit is installed or not. But this block is the only reference in the whole wicd docs and users won't be notified about the ignoring of the netdev UNIX group. So i think this feature would at least cause lots of confusion and is currently not very helpful. - feature is depending on the deprecated Consolekit feature (according to the comment above) and on the deprecated at_console condition. So i think, we have 2 options: 1) remove that block above completely in the upstream sources. To me this feature doesn't seem to be useful/important (but i don't know your opinion on this, therefore my question) and simplifying the code is always good, in my opinion. 2) Document this feature properly in the wicd docs/manpages and converting it to Consolekit2 or maybe polkit (?). I think this way, we are the most independent from systemd(which is important as Axel Beckert pointet out here https://lists.debian.org/debian-mentors/2016/02/msg00245.html). What are your thoughts about this? |
From: toogley <to...@ma...> - 2016-02-20 15:35:55
|
Hey, my question concerns this block in other/wicd.conf: ---------------------------------------------------------------------- <!-- Comment the block below if you do not want all users logged in locally to have permission to use wicd-client. This ignores the group based permission model defined above for the "netdev" group. Note that this only applies if you are using ConsoleKit - if you do not have ConsoleKit installed and in use, then this block makes no difference either way. --> <policy at_console="true"> <allow send_destination="org.wicd.daemon"/> <allow send_interface="org.wicd.daemon"/> <allow send_destination="org.wicd.daemon.wireless"/> <allow send_interface="org.wicd.daemon.wireless"/> <allow send_destination="org.wicd.daemon.wired"/> <allow send_interface="org.wicd.daemon.wired"/> <allow send_interface="org.freedesktop.DBus.Introspectable"/> </policy> ---------------------------------------------------------------------- the current situation, as i see it: - this block is not really debug friendly, as the behavior of wicd changes in dependence whether consoleKit is installed or not. But this block is the only reference in the whole wicd docs and users won't be notified about the ignoring of the netdev UNIX group. So i think this feature would at least cause lots of confusion and is currently not very helpful. - feature is depending on the deprecated Consolekit feature (according to the comment above) and on the deprecated at_console condition. So i think, we have 2 options: 1) remove that block above completely in the upstream sources. To me this feature doesn't seem to be useful/important (but i don't know your opinion on this, therefore my question) and simplifying the code is always good, in my opinion. 2) Document this feature properly in the wicd docs/manpages and converting it to Consolekit2 or maybe polkit (?). I think this way, we are the most independent from systemd(which is important as Axel Beckert pointet out here https://lists.debian.org/debian-mentors/2016/02/msg00245.html). What are your thoughts about this? |
From: Tom V. B. <tom...@gm...> - 2016-01-26 10:59:40
|
Got it, will do, thanks! |
From: Axel B. <ab...@de...> - 2016-01-26 10:42:29
|
Hi Tom, On Tue, Jan 26, 2016 at 06:22:33AM +0100, Tom Van Braeckel wrote: > > IIRC I read a commit somewhere which declared the changelog as > > obsolete. Why is it considered obsolete? Wasn't it only generated > > automatically anyways? > > Oh... Yes, it was generated automatically but I figured it wasn't very > useful because that information can also be found in the Bazaar > repository at Launchpad. > But okay, I understand it is convenient/necessary for you so I re-added it :-) Well, it's not a must (the "P" in the warning meant "pedantic" :-), but it's helpful for packagers (e.g. "Do I need to update any dependencies?") as well as users. At least on Debian, users are used to first lookup upstream changes in the installed package at /usr/share/doc/$package/changelog.gz (while the packaging changelog resides in /usr/share/doc/$package/changelog.Debian.gz), so it's indeed mostly convenience not having to figure out _where_ to lookup the bzr log. > I fixed the issues and updated the release .tar.gz at Launchpad: > https://launchpad.net/wicd/1.7/1.7.4/+download/wicd-1.7.4.tar.gz Appreciated, but please don't do that in the future anymore and give new tar balls a different name. It's considered bad practice to overwrite already published releases: Packagers may have already imported the old tar ball into their systems labeled "1.7.4" and now there is a different tar ball which would need the same label, e.g. a git tag. And deleting git tags to let them later point elsewhere is considered bad practice for the same reason. Additionally some tools may not even be able to cope with it. So I've imported that second tar ball now into the Debian packaging as version number "1.7.4+tb2". Another project I'm involved in had to fixup a tar ball recently, too, and they dubbed the second tar ball for the "0.9.6" release "0.9.6v2". Also a possibility. Anyways, the new tar ball looks much better and no more throws the warnings I sent you. Thanks! :-) Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | ab...@de... (Mail) X See http://www.nonhtmlmail.org/campaign.html | ab...@no... (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web) |
From: Tom V. B. <tom...@gm...> - 2016-01-26 05:24:22
|
> Some more files which definitely don't belong into an source tar ball > (and which have been removed by the clean target of the debian package): > > deleted: encryption/templates/psu.~1~ > deleted: gtk/wicd-client.py.orig > deleted: gtk/wicd-client.py.rej > deleted: wicd/configmanager.py.~1~ > deleted: wicd/networking.py.orig > deleted: wicd/networking.py.rej > deleted: wicd/networking.py.~1~ > deleted: wicd/wnettools.py.orig > deleted: wicd/wnettools.py.rej > deleted: wicd/wnettools.py.~1~ > Fixed, thanks! I added to our release instructions: find -name "*.pyc" -o -name "*.orig" -o -name "*.rej" -o -name "*.~1~" -delete |
From: Tom V. B. <tom...@gm...> - 2016-01-26 05:23:19
|
>> Thanks for the patch for the WEP connection issue >> (https://bugs.launchpad.net/wicd/+bug/1419464), it is now in wicd >> release 1.7.4 Cool! > > Lintian (the Debian package checker) found some issues with the > upstream tar ball: > > P: wicd source: source-contains-prebuilt-python-object gtk/gui.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/guiutil.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/netentry.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/prefs.pyc Ah, seems they are not removed by the "setup.py clean --all" command. I added to our release instructions: find -name "*.pyc" -o -name "*.orig" -o -name "*.rej" -o -name "*.~1~" -delete > > Also new are the following warnings: > > P: python-wicd: no-upstream-changelog > P: wicd-cli: no-upstream-changelog > P: wicd-curses: no-upstream-changelog > P: wicd-gtk: no-upstream-changelog > > IIRC I read a commit somewhere which declared the changelog as > obsolete. Why is it considered obsolete? Wasn't it only generated > automatically anyways? Oh... Yes, it was generated automatically but I figured it wasn't very useful because that information can also be found in the Bazaar repository at Launchpad. But okay, I understand it is convenient/necessary for you so I re-added it :-) Thanks a lot for the useful feedback! I fixed the issues and updated the release .tar.gz at Launchpad: https://launchpad.net/wicd/1.7/1.7.4/+download/wicd-1.7.4.tar.gz Kind regards, Tom Van Braeckel. |
From: Axel B. <ab...@de...> - 2016-01-25 20:25:11
|
Hi again, On Mon, Jan 25, 2016 at 09:22:52PM +0100, Axel Beckert wrote: > On Mon, Jan 25, 2016 at 05:48:42AM +0100, Tom Van Braeckel wrote: > > Thanks for the patch for the WEP connection issue > > (https://bugs.launchpad.net/wicd/+bug/1419464), it is now in wicd > > release 1.7.4 > > Lintian (the Debian package checker) found some issues with the > upstream tar ball: > > P: wicd source: source-contains-prebuilt-python-object gtk/gui.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/guiutil.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/netentry.pyc > P: wicd source: source-contains-prebuilt-python-object gtk/prefs.pyc Some more files which definitely don't belong into an source tar ball (and which have been removed by the clean target of the debian package): deleted: encryption/templates/psu.~1~ deleted: gtk/wicd-client.py.orig deleted: gtk/wicd-client.py.rej deleted: wicd/configmanager.py.~1~ deleted: wicd/networking.py.orig deleted: wicd/networking.py.rej deleted: wicd/networking.py.~1~ deleted: wicd/wnettools.py.orig deleted: wicd/wnettools.py.rej deleted: wicd/wnettools.py.~1~ Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | ab...@de... (Mail) X See http://www.nonhtmlmail.org/campaign.html | ab...@no... (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web) |
From: Axel B. <ab...@de...> - 2016-01-25 20:23:00
|
Hi Tom, On Mon, Jan 25, 2016 at 05:48:42AM +0100, Tom Van Braeckel wrote: > Thanks for the patch for the WEP connection issue > (https://bugs.launchpad.net/wicd/+bug/1419464), it is now in wicd > release 1.7.4 Lintian (the Debian package checker) found some issues with the upstream tar ball: P: wicd source: source-contains-prebuilt-python-object gtk/gui.pyc P: wicd source: source-contains-prebuilt-python-object gtk/guiutil.pyc P: wicd source: source-contains-prebuilt-python-object gtk/netentry.pyc P: wicd source: source-contains-prebuilt-python-object gtk/prefs.pyc Also new are the following warnings: P: python-wicd: no-upstream-changelog P: wicd-cli: no-upstream-changelog P: wicd-curses: no-upstream-changelog P: wicd-gtk: no-upstream-changelog IIRC I read a commit somewhere which declared the changelog as obsolete. Why is it considered obsolete? Wasn't it only generated automatically anyways? Kind regards, Axel -- /~\ Plain Text Ribbon Campaign | Axel Beckert \ / Say No to HTML in E-Mail and News | ab...@de... (Mail) X See http://www.nonhtmlmail.org/campaign.html | ab...@no... (Mail+Jabber) / \ I love long mails: http://email.is-not-s.ms/ | http://abe.noone.org/ (Web) |
From: Tom V. B. <tom...@gm...> - 2016-01-25 04:49:28
|
Dear Axel, Thanks for the patch for the WEP connection issue (https://bugs.launchpad.net/wicd/+bug/1419464), it is now in wicd release 1.7.4 If I understand correctly, Debian is carrying 37 (!) patches to wicd and I just applied patch #38 (so that one will go away)... I wonder what other Debian patches we could safely apply... or perhaps all 37 of them? Are there any Debian-specific patches that you know of...? :-) Kind regards and thanks again, Tom Van Braeckel. |
From: Tom V. B. <tom...@gm...> - 2016-01-25 04:46:01
|
Hi, Axel Beckert from Debian submitted a patch for the critical WEP connection error, which he traced back to an issue with variable substitution in the configuration file. I applied it. Pretty grave, so good news that it's fixed. It seems like a good time to make a new release now, so here goes! Find it in the usual spot: https://launchpad.net/wicd/1.7/1.7.4 Kind regards, Tom Van Braeckel. |
From: Tom V. B. <tom...@gm...> - 2014-12-17 13:38:29
|
Dear wicd enthousiasts, We are preparing for the release of the next version of wicd (1.7.2.5) during the course of next week. The merge window will be open until this Sunday at midnight, so if you have any pending work that needs to go in, please do it this week, ask/remind someone else to merge it, or shout if something else still needs to happen. Also, now is a good time for us developers to update our local wicd to the latest development version, try it out, and report regressions, if any are found. Happy testing! Kind regards, Tom Van Braeckel. |
From: David P. <d.p...@gm...> - 2012-03-04 15:20:25
|
On Sun, 04 Mar 2012 07:57:40 -0700, Yves Dorfsman wrote: > >> The two main ones right now are: > > > > You listed only one :) > > Yes I hit send to early. Here are the other ones: > [..] Can you please file all these as separate bugs on launchpad? Thanks! David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 |
From: Yves D. <yv...@zi...> - 2012-03-04 14:57:49
|
> Have you checked the "Use these settings for network sharing the same ESSID" > option? Ah! No I had completely missed that - thanks! >> The two main ones right now are: > > You listed only one :) Yes I hit send to early. Here are the other ones: -when disconnected, even though the icon is grey to show it is disconnected, if you hover on the icon it says "connected to blah" with blah being your last network you were connected to. -in the Ubuntu/Debian packages, there is no extension.js for gnome3 (gnome-shell). Adding two small files /usr/share/gnome-shell/extensions/wicd@xxx would make wicd show up in the apps bar automatically -on a laptop, there is no way to tell if the wireless card has been disabled or not. On Network-Manager they capture that (I suspect through dbus) and display a red x if the wireless card is disconnected. -I like what Apple does with arp. I cannot find the article right now, but apparently when they re-connect to the same ssid, the do an arp on the lasp ip address they use on that network, and if nobody answers, they use it, then only, do they talk to the dhcp server to try to re-new that lease. This way apparently they re-connect to network instantly with no side-effect. -this will sound silly, but I'd add a blinking icon while wicd is trying to connect to a network - very low priority of course. -- Yves. http://www.SollerS.ca/ http://ipv6.SollerS.ca http://blog.zioup.org/ |
From: Genghis K. <gen...@gm...> - 2012-03-04 12:19:17
|
The following transient dialogues are displayed properly. Connection Failed: Unable to Get IP Address (Unnamed dialogue) Credits (inside About) Network Information (inside Properties) List of bad dialogues (it is not pretending to be a complete list) About Create an Ad-Hoc Network Hidden Network "Network Name" - Properties Preferences I am using Wicd 1.7.0 On Sat, 7 Jan 2012 16:10:06 +0200 Genghis Khan <gen...@gm...> wrote: > The Alert dialogues, or the About WICD dialogue (and others too) are > not on top, meaning that by clicking on the main WICD PyGTK+ window > the Alert box left on the bottom and to get this box back to top, you > need to click on the task-bar (using Fluxbox or Openbox). > > Realization: > Execute $ mousepad (under Fluxbox or Openbox) > Help > About > Click on the main Mousepad window > The About dialog is still on top. |
From: David P. <d.p...@gm...> - 2012-03-04 10:10:29
|
On Fri, 24 Feb 2012 00:54:35 -0700, Yves Dorfsman wrote: > The two main ones right now are: You listed only one :) > • If there are repeaters for the same ssid, I get prompted for the key for > each repeater. NM assumes (and network system for other OSes) assumes that > the same key should be used for the same ssid even if they are on different > channels, as a matter of fact they show up as the same "network". Have you checked the "Use these settings for network sharing the same ESSID" option? -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 |
From: Yves D. <yv...@zi...> - 2012-02-24 08:09:54
|
I've switched over from nm hell to wiki. It's vastly better, but, there are a few things that bother me. The two main ones right now are: • If there are repeaters for the same ssid, I get prompted for the key for each repeater. NM assumes (and network system for other OSes) assumes that the same key should be used for the same ssid even if they are on different channels, as a matter of fact they show up as the same "network". Was this a conscious decision? Would it be difficult to change? I've done some python, can I start working on this? Thanks. -- Yves. http://www.SollerS.ca/ http://ipv6.SollerS.ca http://blog.zioup.org/ |
From: Genghis K. <gen...@gm...> - 2012-01-07 14:30:35
|
The Alert dialogues, or the About WICD dialogue (and others too) are not on top, meaning that by clicking on the main WICD PyGTK+ window the Alert box left on the bottom and to get this box back to top, you need to click on the task-bar (using Fluxbox or Openbox). Realization: Execute $ mousepad (under Fluxbox or Openbox) Help > About Click on the main Mousepad window The About dialog is still on top. |
From: David P. <d.p...@gm...> - 2011-12-06 21:36:24
|
On Tue, 29 Nov 2011 14:15:47 +0000, Jonatan Olofsson wrote: > Hi, Hello Jonatan, > It seems http://downloads.wicd.net/src/testing/1.7.x/ is a bit outdated. Well. 1.7.1b2 was the last wicd release until.. yesterday ;) Please have a look at http://launchpad.net/wicd/1.7/1.7.1/+download/wicd-1.7.1~b3.tar.gz 1.7.1 "final" is expected by 17-18 December. Kindly, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 |
From: David P. <d.p...@gm...> - 2011-12-06 21:25:09
|
Hello everybody, I just released WICD version 1.7.1~b3: this is the last beta before 1.7.1 gets released on 17-18 December. Please test it, and report bugs as soon as you get them -- we all want 1.7.1 to be as bug-free as possible :) http://launchpad.net/wicd/1.7/1.7.1/+download/wicd-1.7.1~b3.tar.gz Have a nice day, David -- . ''`. Debian developer | http://wiki.debian.org/DavidPaleino : :' : Linuxer #334216 --|-- http://www.hanskalabs.net/ `. `'` GPG: 1392B174 ----|---- http://deb.li/dapal `- 2BAB C625 4E66 E7B8 450A C3E1 E6AA 9017 1392 B174 |
From: Jonatan O. <jon...@gm...> - 2011-11-29 14:15:58
|
Hi, It seems http://downloads.wicd.net/src/testing/1.7.x/ is a bit outdated. It is used e.g. for the ebuilds in gentoo, and it would be nice to be able to update it. Is there another directory for compressed sources available or do i have to find out how to pull directly from bazaar to get the latest wicd in my installation? Best regards, Jonatan Olofsson |
From: Harlan H. B. <ha...@bl...> - 2010-06-19 22:14:42
|
Hello, First of all, please let me say that I find WICD to be very stable and one of the best networking tools available, especially for wireless. I would like to request that bridging be added. I need bridging for virtual systems to work with the outside world. I haven't seen anything updated on the internet about this for more than a year now. I would be able to do some testing for you if needed. Thank You for your time, attention and hard work! Harlan... |
From: Stefan M. <mo...@ir...> - 2009-11-12 15:15:25
|
Is there something comparable to the pre-up/post-down hooks of ifupdown in wicd? My wireless driver (rtl8187se) tends to kernel-panic the whole system when I switch from one network to another, so until someone fixes the driver, I'd like to use such hooks to rmmod/insmod the driver between disconnection and reconnection. Stefan |
From: Simon G. <sim...@gm...> - 2009-11-03 19:49:19
|
I started building a python library to query and control wicd. I plan to use this library as a basis for a replacement gtk gui. However, as I learned from my last time on the irc channel, that wicd is pending a rewrite. I'm trying to write the library to be as future proof as possible, but I'd be interested in hearing about the direction a rewrite will take wicd. For example, my library tries to make it as simple as possible to query the information the wicd daemon provides. For example, the wicd daemon seems to only notify when a scan is happening so the front ends can rebuild their network list, my library instead notifies users on the discovery of new networks and changes in existing ones, without forcing the user to rebuild the list manually as it handles that internally. I designed it this way because while wicd requires manually scanning, it probably should eventually move to the NetworkManager way of doing things of notifying the front end when it discovers a new network. My library also allows managing multiple devices (wireless/wired) but only fills wlan0/eth0 as there is no support for that in wicd. |
From: Alexandre M. <ale...@ya...> - 2009-07-23 21:21:52
|
Greetings First of all, my congrats. The WICD is very easy to use and I think its the best alternative to another confusing similar softwares. I want to colaborate fixing some bugs I found on WICD 1.6.1 and WICD-client 2.0. Well, the first bug I found is when you right-click on wicd-client tray icon, and hit "Connect", the "Wired Network" appears without icon, just an "x" (that must indicate something is missing). The others possible connections (wireless) appears with correct icons, indicating the wifi signal. The other "bug" I want to correct is about the language (both on wicd and and wicd-client). Some terms (on boxes) is in my correct idiom, but some not. I would like to change it all, if possible. Thats it... Thank you, so much and sorry about the english (I speak portuguese) ____________________________________________________________________________________ Veja quais são os assuntos do momento no Yahoo! +Buscados http://br.maisbuscados.yahoo.com |