>>>>> "EM" == Erik Moeller <erik_moeller(a)gmx.de> writes:
EM> Instead of doing this, I'd try to get rid of the /article/,
EM> put everything in the rootdir and try to use mod_rewrite for
EM> all requests which do not contain ^/images/ or ^/cache/. Then
EM> you'd have a relatively clean access structrue. The "/" as
EM> namespace identifier has the additional problem of being
EM> easily confused with the "/" as subpage handler.
When you say "easily confused", do you mean for humans or for the
MediaWiki software?
But, yes, this is a low priority for me right now.
~ESP
--
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel - http://www.wikitravel.org/
The free, complete, up-to-date and reliable world-wide travel guide
> Any counter-opinions out there?
Seems sensible to me. But I am more optimistic about the possibility of
using hardware to improve our performance.
I think we should aim for a dedicated database server with this
configuration:
A dual CPU box maxed out with memory, whatever drive we have for the OS,
logs, and everything but the database, and the fastest drive we can
afford housing just the DB files.
We should then have a PHP front end server with all language wiki's
installed:
This should have enough memory to keep us from paging all the time, and
some CPU horsepower would be nice.
If we can get a new machine, I would say get another server to use as a
second database server. We could then make one server the home of the
English wiki's DB, and the other the home of all the international
wiki's DBs -- this would put about 150,000 articles on each database
server.
I think further performance enhancements could be found by getting a
third database server handle read-only copies of all the DB's server, to
use for full text searches, user generated sql queries and the like.
--Mark Christensen
Tomasz Wegrzanowski saith:
> Any idea to do it [indenting] in a saner way ?
Just use paragraphs within list items without bullets. It really
doesn't matter if the bullets display in non-CSS browsers.
<style type="text/css">
ul.comment {list-style-type: none;}
</style>
<ul class="comment">
<li><p>Comment</p>
<ul class="comment">
<li><p>Reply<p></li>
<li><p>Another reply</p></li>
</ul>
</li>
<li><p>Another comment</p></li>
</ul>
This same structure, with style= instead of <style> (because of HTML
restrictions) and with more text in the paragraphs, is at
[[en:User:Geoffrey/unmarked lists]]. Works great in Mozilla 1.4, IE 6,
and Opera 6. Lynx 2.8 displays them as normal lists, with bullet items,
and ignores the paragraph spacing - which should be fine.
Explicitly giving <blockquote> instead of : works, for mathematics
and stuff - but the unnumbered lists may be fine for this.
Is there anywhere in Wikipedia where definition lists (;term :def) are
actually used as such?
=====
-Geoffrey Thomas
geoffreyerffoeg(a)yahoo.com
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
So, is there a good reason that the default CSS for stub links is to
take out the underlines? I don't get it, and after some complaints I
reenabled underlines for wikitravel.org. I'm wondering if there
is some user-interface principle I'm missing here.
~ESP
--
Evan Prodromou <evan(a)wikitravel.org>
Wikitravel - http://www.wikitravel.org/
The free, complete, up-to-date and reliable world-wide travel guide
On talk
http://meta.wikipedia.org/wiki/Talk%3ALanguageRu.php
someone wrote the below text.
Is it proper to stick Javascript in the langa.php
file? Im sure the anon user here is just trying to be
helpful, but it doesnt seem like a good idea.
-S-
===
The following link leads to LanguageRu.php variant,
working at Russkaja wikipedia! project
(http://www.wikipedia.ru). This could be of use to the
translation team...
The text should be used as is, because
* only ~80% is translated, sometime orignal
meaning changed drastically
* it conatains special javasxcript code for
russian rating catalogues
* some string translations are ugly
---
http://www.wikipedia.ru/wiki/wiki.phtml?title=%D0%92%D0%B8%D0%BA%D0%B8%D0%B…
(vovkav yahoo com - put punctuation, where applicable)
====
-S-
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com
Here's one that uses lex + single pass over tokens, and can generate
valid XHTML. It's proof-of-concept program, not a drop-in replacement
for current parser.
=== How it works ===
Wiki syntax is line based and uses state-transition model -
a token chances state from anything to X. HTML is free-form
and states can nest.
This parser maintains stack of "inline" elements. Every time it
finds </X>, it checks if <X> is on stack, and if it is, it pops and closes
every element till it gets to <X>, otherwise it prints raw </X>.
If it finds <X>, it checks if it conflicts with something on stack,
and acts accordingly.
When "paragraph state" has to change, it closes all open inline tags.
It doesn't preserve whitespace unless necessary (<pre> and wiki pre,
for now also <nowiki>).
Example: <<END
Ala <b>ma kota
Ala <b>ma <b>kota
Ala </b>ma kota
Ala <strong> <b>ma kota
Ala <i> <b>ma kota
END
Output (with \ns inserted): <<END
<p>Ala <b>ma kota </b></p>
<p>Ala <b>ma <b>kota </b></p>
<p>Ala </b>ma kota </p>
<p>Ala <strong> <b>ma kota </strong></p>
<p>Ala <i> <b>ma kota </b></i></p>
END
Because it has to support both HTML and wiki paragraph control,
it's quite ugly code.
Example: <<END
<ul>
<li>
Ala
</li>
<li>
Ma
<li>
Kota
<ul>
i
<li> Psa
</ul>
END
Output: <<END
<ul> <li> Ala </li> <li> Ma </li><li> Kota </li><ul> <li>i </li><li> Psa </li></ul> </ul>
END
As you can see above, <li> was automatically opened in nested list.
=== More examples of magic ===
Example: <<END
=== Foo ===
Bar
END
Output: <<END
<h3> Foo </h3><p>Bar </p>
END
But also:
Example: <<END
=== Foo
Bar
END
Output: <<END
<h3> Foo </h3><p>Bar </p>
END
=== '''-magic ===
It reopens quote if necessary.
Example (Quotes.txt from test suite) <<END
Wikipedia quoting tests:
(1) normal '''bold''' normal
(2) normal ''italic'' normal
(3) normal '''''bold italic''''' normal
(4) normal '''bold ''bold italic'' bold''' normal
(5) normal ''italic '''bold italic''' italic'' normal
(6) normal '''''bold italic'' bold''' normal
(7) normal '''''bold italic''' italic'' normal
(8) normal ''italic '''bold italic''''' normal
(9) normal '''bold ''bold italic''''' normal
(10) normal '''bold's''' normal
(11) normal ''italic's'' normal
(12) normal ''italic's '''bold's italic''' italic's'' normal
(13) normal '''''bold's italic'' bold's''' normal
(14) normal ''italic''' normal
(15) normal ''''bold''' normal
(16) normal ''italic'' normal ''italic'' normal
(17) normal ''italic'' normal '''bold''' normal
(18) normal '''bold''' normal '''bold''' normal
(19) normal '''bold''' normal ''italic'' normal
END
Output (with \ns inserted): <<END
<p>Wikipedia quoting tests: </p>
<p>(1) normal <b>bold</b> normal </p>
<p>(2) normal <i>italic</i> normal </p>
<p>(3) normal <b><i>bold italic</i></b> normal </p>
<p>(4) normal <b>bold <i>bold italic</i> bold</b> normal </p>
<p>(5) normal <i>italic <b>bold italic</b> italic</i> normal </p>
<p>(6) normal <b><i>bold italic</i> bold</b> normal </p>
<p>(7) normal <b><i>bold italic</i></b><i> italic</i> normal </p>
<p>(8) normal <i>italic <b>bold italic</b></i> normal </p>
<p>(9) normal <b>bold <i>bold italic</i></b> normal </p>
<p>(10) normal <b>bold's</b> normal </p>
<p>(11) normal <i>italic's</i> normal </p>
<p>(12) normal <i>italic's <b>bold's italic</b> italic's</i> normal </p>
<p>(13) normal <b><i>bold's italic</i> bold's</b> normal </p>
<p>(14) normal <i>italic<b> normal </b></i></p>
<p>(15) normal <b>'bold</b> normal </p>
<p>(16) normal <i>italic</i> normal <i>italic</i> normal </p>
<p>(17) normal <i>italic</i> normal <b>bold</b> normal </p>
<p>(18) normal <b>bold</b> normal <b>bold</b> normal </p>
<p>(19) normal <b>bold</b> normal <i>italic</i> normal </p>
END
7 is not optimal but still 100% correct.
14 has different interpretation.
Might it be a good idea to conceal (make hash/
otherwise encrypt) the username in a cookie?
-S-
__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com