Gerard.Meijssen wrote:
> When I try to reach en:wiktionary.org or nl:, de:, I get an error message: redirection limit exceeded or cookie problems. So I tried Internet Explorer which does not load the page either, no error message though.
>
> Can someone please find out what the problem is ??
>
> Thanks,
> GerardM
Fixed
-- Tim Starling
On Sat, Jul 24, 2004 at 01:40:17PM +0000, wikitech-l-request(a)wikimedia.org wrote:
>
> > Seeing we want the ability to make printed material out of Wikipedia
> > content, uploading full-resolution images is IMO the way to do it.
> > However, such images currently break the image description page.
>
> Suggestion: Have a magic word, __SCREENSIZE__ or something like that,
> which you can put on an image description page, and it will set
> style="width: 100%" on the image (thus telling the browser to size the
> image in such a way that its width fits the bounding rectangle). Of
> course, __SCREENSIZE__ should be omitted when the image is very small,
> because then "width: 100%" would tell the browser to enlarge it.
>
> Of course, this isn't without problems. If someone's bounding rectangle
> is about 800 pixels wide (it's 826 for me at 1024x768 with Monobook) for
> someone, but 1000 pixels for someone else (possibly using 1280x1024),
> then one of them will want __SCREENSIZE__ to be inserted, while the
> other will complain that it enlarges the image unnecessarily. :/
This approach is fine for broadband users, but it doesn't help for modem
users, who apparently can still be found in massive numbers (modems?
haven't used one of those in years...) If we're going to shrink the
image, we should shrink it on the server, rather than on the client.
--
---------------------------------------------------------------------------
Robert Merkel
robert.merkel(a)benambra.org
http://benambra.org
If ignorance ever reaches a barrel, I want the drilling rights
to his head.
-- a political opponent on President George W. Bush
--------------------------------------------------------------------------
> And recognise that, however much we may like it, Windows 95 may not
have support for Ogg.
Neither does it for MP3. As far as I remember, Windows 95, 98,
Millenium, 2000 all need third-paty software, such as Winamp, installed,
in order to play MP3's.
Interestingly, the full install of Winamp plays OGG's.
> Libraries, schools, offices and many other places prohibit software
installation without permission and we probably don't want to bar those
users from our content,
Libraries, offices etc.. also often prohibit users from playing sound
and/or do not provide sound cards.
Granted, some of those libraries may have installed some older audio
player (an old version of Winamp), or a reduced version, and may not be
willing to upgrade it.
> nor third world or poor users who may have older equipment.
Which probably cannot play MP3 either. Again, if this is a question of
equipment, I think that a 486 cannot play MP3 or OGG, and most Pentiums
should do fine. This is more a question of software than a question of
hardware.
When I try to reach en:wiktionary.org or nl:, de:, I get an error message: redirection limit exceeded or cookie problems. So I tried Internet Explorer which does not load the page either, no error message though.
Can someone please find out what the problem is ??
Thanks,
GerardM
Hi
I tried to change the sysop rights for Triebtäter (notice the a with
umlaut), and it did not work. Could someone check what is going on with
special caracters ?
ps : I tried by replacing with Triebt%E4ter, and it did not work either
ant
The French donation is a 4U 6CPU Pentium III-750 system with 2GB of RAM and three or four 9GB SCSI drives in a RAID setup; and three 1U Celerons. 2GB for the 4U because it comes with one but the donor is upgrading it to two for us. The other equipment mentioned was for us to consider and the donor would then allocate it among all of the projects which were competing for it. We didn't get it all.
On the technical side, it was decided that the Celerons just aren't suitable for the US site because the US Squids require roughly comparable specifications and the Celerons aren't really fast enough to be page builders, given the shipping costs to get them to the US. So, European Squid caches is the role they best fit. They will need a fairly cheap RAM upgrade to be Squids. These squids will speed things up for those in France and possibly more of Europe who are not logged in, by avoiding the sometimes slow or broken transatlantic links, and for everyone by taking some of the load from the US-based Squids.
The 4U 6CPU is best for the US side. That's the main page building site and putting it there will help everyone who's logged in or getting a non-cached page. Because peak load times are different in different parts of the world, the same amount of resources for the central site delivers more benefit than dedicating them to any one place. Also, the lag from locking and unlocking the database records across a slow link (the internet instead of a LAN) would hurt performance for everyone, by keeping locks for longer than necessary.
The donor requested that the celerons be named chloe, bleuenn and ennael. That seems like a reasonable request to accept, since we don't yet have a naming convention for remote or donated equipment. I doubt that a corporate donor would want their name associated with problem reports, so I expect that we could discourage corporate names if we wanted to.
> I see it regurlarly that german people are carrying IP's from other
> countries depending on their service provider in my shop.
> AOL for instance assigns US registered IP's to whoever they feel fit.
In my experiments with per-country IP classification, the main issue,
apart from ARIN's reluctance to give their list, was AOL. They have
enormous blocks of addresses registered in the US. I don't know how to
tell apart European and American AOL users.
(This goes back to some years ago, so my information may not be current.)
* Guttorm Flataboe <dittaeva(a)yahoo.com> wrote:
Hi,
> Hi Enrico, its nice to see that some refreshing new developer effort
> for the MediaWiki software!
>
> I also would like to use Mediawiki for something non-wikipedian, but
> there are some bugs that have been holding me back.
>
> Currently the Mediawiki software will not detect and show all changes
> to a text, and it does not do mark changes consistently. This is very
> unfortunate since users will be under the impression that when they do
> a diff they will be shown all changes, while infact some will not be
> shown and therefore overlooked.
hmm, I'm currently fighting on other frontiers.
My wiki setups are normally sitting behind a masquerading firewall.
This sometimes makes trouble on redirections (redirect goes to the
local host named instead the virtual host name). I've fixed most of
them, but some are still unfixed.
I've also splitted off the common wiki code from individual instance
stuff in a way, that the wiki code is imported by the actual instance
just like a library. Here's a little example:
Directory listing:
drwxr-xr-x 2 subsys/p root 4096 Jul 12 15:33 .
drwxr-xr-x 10 subsys/p wwwrun 4096 Jul 12 22:38 ..
-rw-rw-rw- 1 subsys/p nobody 2382 Jul 12 22:05 LocalSettings.php
lrwxrwxrwx 1 subsys/p root 40 Jul 12 15:22 _mediawiki_current_ -> /home/subsys/borg/lib/packages/mediawiki
lrwxrwxrwx 1 subsys/p root 26 Jul 12 15:22 images -> _mediawiki_current_/images
lrwxrwxrwx 1 subsys/p root 28 Jul 12 15:22 includes -> _mediawiki_current_/includes
-rw-r--r-- 1 subsys/p root 228 Jul 12 22:06 index.php
lrwxrwxrwx 1 subsys/p root 29 Jul 12 15:22 languages -> _mediawiki_current_/languages
lrwxrwxrwx 1 subsys/p root 31 Jul 12 15:22 maintenance -> _mediawiki_current_/maintenance
lrwxrwxrwx 1 subsys/p root 24 Jul 12 15:22 math -> _mediawiki_current_/math
lrwxrwxrwx 1 subsys/p root 31 Jul 12 15:22 stylesheets -> _mediawiki_current_/stylesheets
lrwxrwxrwx 1 subsys/p root 29 Jul 12 15:22 templates -> _mediawiki_current_/templates
index.php:
<?php
error_reporting ( E_ALL );
define ( 'MEDIAWIKI_ROOT', '_mediawiki_current_/' );
define ( 'MEDIAWIKI_INSTANCE', './' );
define ( 'MEDIAWIKI_BREAKPOINT', 1 );
require_once ( MEDIAWIKI_ROOT.'includes/common-page.php' );
-------
The changes are not too huge, so I'd suggest we try to get this in
the current wiki branch before forking off.
cu
--
---------------------------------------------------------------------
Enrico Weigelt == metux IT service
phone: +49 36207 519931 www: http://www.metux.de/
fax: +49 36207 519932 email: contact(a)metux.de
cellphone: +49 174 7066481
---------------------------------------------------------------------
-- DSL ab 0 Euro. -- statische IP -- UUCP -- Hosting -- Webshops --
---------------------------------------------------------------------
Hello,
I have a question about categories: when a category has a sub-category,
should a page belonging to this sub-category be displayed in the main
category listing?
I have this main category:
http://it.wikipedia.org/wiki/Categoria:Astronomia_e_Astrofisica
With, among others, two sub-categories:
http://it.wikipedia.org/wiki/Categoria:Stellehttp://it.wikipedia.org/wiki/Categoria:Costellazioni
All articles in the second sub-category are also displayed in the main
one, but not the ones inside the first sub-category.
All those articles were recently changes from the main category to one or
the other sub-category. Are there any server-side caching issue?
Thanks,
Alfio