http://test.wikipedia.com/ Please visit the website, and report bugs and request any *really* essential features.
Well, my extensive use of subpages in Poker get translated pretty badly, so I'll have to do a lot of manual fixing there. But I'm probably the worst case on that score, and I don't think the problem is that bad, and I'd much rather do it now than after 20,000 more pages are added.
Likewise, I'd like to tweak the code for dictionary lists a bit before I add 20 more pages of poker jargon, but that too can be done post-live, and I can do the code myself as soon as it's in some reasonable source control system like Sourceforge CVS.
So I'm certainly in favor of going live. 0
lcrocker@nupedia.com wrote:
Likewise, I'd like to tweak the code for dictionary lists a bit before I add 20 more pages of poker jargon, but that too can be done post-live, and I can do the code myself as soon as it's in some reasonable source control system like Sourceforge CVS.
Well, Magnus's development version is in Sourceforge CVS:
http://cvs.sourceforge.net/cgi-bin/viewcvs.cgi/wikipedia/
Is that helpful?
On Thu, 17 Jan 2002 lcrocker@nupedia.com wrote:
http://test.wikipedia.com/ Please visit the website, and report bugs and request any *really* essential features.
Well, my extensive use of subpages in Poker get translated pretty badly, so I'll have to do a lot of manual fixing there. But I'm probably the worst case on that score, and I don't think the problem is that bad, and I'd much rather do it now than after 20,000 more pages are added.
I think what would help a lot is if there were added, to the conversion script, something that made [[Poker/Bluff]] (for instance) into [[Poker/Bluff|Bluff]]. It appears that what the script does right now is to convert instances of [[/Bar]] on a [[Foo]] subpage into [[Foo/Bar]]. I'd say it would be better in 95% of the cases to convert it instead into [[Foo/Bar|Bar]].
Likewise, I'd like to tweak the code for dictionary lists a bit before I add 20 more pages of poker jargon, but that too can be done post-live, and I can do the code myself as soon as it's in some reasonable source control system like Sourceforge CVS.
So I'm certainly in favor of going live.
Woo-hoo!
Larry
Is it a good idea to change to the new software after a press release? Imagine something goes wrong and some newspaper features wikipedia in the same day thing go wrong...
Joao http://www.nonio.com
Larry Sanger wrote:
On Thu, 17 Jan 2002 lcrocker@nupedia.com wrote:
http://test.wikipedia.com/ Please visit the website, and report bugs and request any *really* essential features.
Well, my extensive use of subpages in Poker get translated pretty badly, so I'll have to do a lot of manual fixing there. But I'm probably the worst case on that score, and I don't think the problem is that bad, and I'd much rather do it now than after 20,000 more pages are added.
I think what would help a lot is if there were added, to the conversion script, something that made [[Poker/Bluff]] (for instance) into [[Poker/Bluff|Bluff]]. It appears that what the script does right now is to convert instances of [[/Bar]] on a [[Foo]] subpage into [[Foo/Bar]]. I'd say it would be better in 95% of the cases to convert it instead into [[Foo/Bar|Bar]].
Likewise, I'd like to tweak the code for dictionary lists a bit before I add 20 more pages of poker jargon, but that too can be done post-live, and I can do the code myself as soon as it's in some reasonable source control system like Sourceforge CVS.
So I'm certainly in favor of going live.
Woo-hoo!
Larry
[Wikipedia-l] To manage your subscription to this list, please go here: http://www.nupedia.com/mailman/listinfo/wikipedia-l
João Mário Miranda wrote:
Is it a good idea to change to the new software after a press release? Imagine something goes wrong and some newspaper features wikipedia in the same day thing go wrong...
We should certainly proceed with caution. But press releases, in my personal experience, don't usually lead to much traffic directly.
Keep in mind that a slashdot story can generate significantly more times traffic than even the New York Times article did. The AP article hardly produced even a blip.
On Fri, 18 Jan 2002, Jimmy Wales wrote:
João Mário Miranda wrote:
Is it a good idea to change to the new software after a press release? Imagine something goes wrong and some newspaper features wikipedia in the same day thing go wrong...
We should certainly proceed with caution. But press releases, in my personal experience, don't usually lead to much traffic directly.
Keep in mind that a slashdot story can generate significantly more times traffic than even the New York Times article did. The AP article hardly produced even a blip.
Two comments are in order: (1) I'll be absent Sunday through Wednesday and possibly later. This doesn't mean you can't do it, of course (why need I be on hand?); I'll leave it up to the higher powers. (2) test.wikipedia.com is not working at this very moment :-( --
Warning: MySQL Connection Failed: Can't connect to local MySQL server through socket '/tmp/mysql.sock' (111) in ./databaseFunctions.php on line 6
Warning: Supplied argument is not a valid MySQL-Link resource in ./wikiPage.php on line 45
Warning: Supplied argument is not a valid MySQL-Link resource in ./wikiPage.php on line 63
Warning: Supplied argument is not a valid MySQL result resource in ./wikiPage.php on line 64
Warning: Supplied argument is not a valid MySQL result resource in ./wikiPage.php on line 76
Warning: Supplied argument is not a valid MySQL-Link resource in ./wikiPage.php on line 83
etc.
--Larry
I think what would help a lot is if there were added, to the conversion script, something that made [[Poker/Bluff]] (for instance) into [[Poker/Bluff|Bluff]]. It appears that what the script does right now is to convert instances of [[/Bar]] on a [[Foo]] subpage into [[Foo/Bar]]. I'd say it would be better in 95% of the cases to convert it instead into [[Foo/Bar|Bar]].
I fixed the conversion script so it does that now, although it might become confusing for the reader if (in your example) there's a "real" [[Bar]] article too, because it would look exactly like [[Foo/Bar|Bar]]. Well, I guess we can't have the cake and eat it...
Magnus
wikipedia-l@lists.wikimedia.org