>>I see that more and more people are use Wiki-makeup
>>and removing HTML tags. But I like to use HTML-tags.
>>Is there, from a technical point of view any difference
>>between the folowing notations;
>>== Foobar ==
>Wiki markup is preferred because a good Wikipedia article
>is not only useful to read, but easy to edit. We want non-
>compter nerds to be able to easily edit and add to topics
>in which they are interested. Also, I still have a long-
>term plan of eliminating most HTML for security reasons.
The security issue should be a separate concern.
We can allow "<h2>...</h2>" as wiki markup
without allowing "<span onmouseover="...">...</span>".
I do agree that "==" is better, however,
and we should make wiki markup look like HTML markup
only for rarely used but supported features (like <strike>)
and as a deprecated alternative for newbies' sakes.
>I also treat Wiki markup specially in the software in a
>few places; for example == Foobar == will cause a page
>to be ranked higher in a search for "Foobar", but the
>equivalent HTML tag will not.
I've also suggested treating the rendering of "=" markup in HTML
analogously to how we treat its rendering for numbered headers:
the shortest string of '='s will always be <h2>,
even if it happens to be the currently deprecated "===".
But then "<h3>" could still be used to force an <h3> tag in the HTML.
Although this proposal got little response and is unlikely to happen,
the point is that some variation is possible, and might be desirable,
for certain purposes.
> I see that more and more people are use Wiki-makeup
> and removing HTML tags. But I like to use HTML-tags.
> Is there, from a technical point of view any difference
> between the folowing notations;
> == Foobar ==
Wiki markup is preferred because a good Wikipedia article
is not only useful to read, but easy to edit. We want non-
compter nerds to be able to easily edit and add to topics
in which they are interested. Also, I still have a long-
term plan of eliminating most HTML for security reasons.
I also treat Wiki markup specially in the software in a
few places; for example == Foobar == will cause a page
to be ranked higher in a search for "Foobar", but the
equivalent HTML tag will not.
HTML versus Wiki-makeup
I see that more and more people are use Wiki-makeup and removing HTML tags.
But i like to use HTML-tags.
Is there, from a technical point of view any difference between the folowing notations;
= Foobar = (-> This does not seems to work)
== Foobar ==
=== Foobar ===
<h3> Foobar </h3>
==== Foobar ====
Magnus and LDC wrote respectively
>> SVG graphics support was suggested on wikipedia-l. I like the
>> idea; that's why I tried it for Nupedia once, but... :-(
>> Proposal: [[svg:foobar]] is just plain-text editable, but
>> displays as an image; A link to [[svg:foobar]] is displayed as
>> an image as well. Optional, after saving an edit to
>> [[svg:foobar]], an image (foobar.png) could be created via
>> svg2png (never tried that, though). The image would then be
>> displayed instead of the SVG, and "real" SVG display could be
>> turned on in the user options (until most browsers support
>> native SVG).
>That's pretty much what I had in mind as well, but SVG isn't
>mature enough yet to think about. For now, people can upload
>the "source file" for a drawing in SVG, as well as uploading a
>PNG version, and just link to the PNG in the article.
I was just at:
It sounds like Magnus proposal might be implementable but:
1. Integration may be tough or not yet reliably feasible
2. The required java/apache batik module may load the server
>From my perspective it would be ideal if upon clicking the
associated png/jpeg image (or nearby link) one got either:
1. Directly editable SVG source text in the standard wiki
edit box .... not terribly useful or user friendly
2. SVG source file (if available) loaded into SVG capable editor
Then upon save, an acknowledgement that the source had been
modified and will be regenerated in the background at the
server's earliest opportunity .... estimated to be x hours/days
until standard usage patterns permit.
In the view of the current developers, would this type of
initial capability be worth prototyping by a new developer
attempting to get up to speed on the current software ...
Incidentally, this approach may turn out to be applicable
to other advanced formats such as:
3DS Max (an animation package)
Clearly some of these other formats would be useful
to specialists with access to high end tools when
free source convertor utilities become available to
appropriate display formats.
Issue 1. above might be best fixed by getting involved
with the development and helping fix the remaining bugs
that affect us specifically.
Issue 2. above might be addressable by using a separate
low end internet accessible server as a "compile farm" via
batch routines .... unless Bomis, the owner, the community
or the impending board of the non profit are uncomfortable
with relying on external resources for an operational
capability. In this case, I can probably arrange for the
donation and shipment/transport of an obsolete pentium
system adequate for batch compilation to the central
Obviously this would only be necessary if this approach
is found to be feasible after prototyping and we decide
to field an implementation.
Lee, regarding the immaturity of SVG. Do you think
insufficient momentum has been achieved to assure that
SVG will become widely fielded and reliaby?
Are there competing graphics standards that you feel
might be more appropriate for immediate development effort
if we do not wish to wait for wiki style collaboration
on graphics source files?
----- Forwarded message from Imran William Smith <iwsmith(a)mimos.my> -----
From: "Imran William Smith" <iwsmith(a)mimos.my>
Date: Wed, 23 Oct 2002 13:22:01 +0800
Subject: Fw: Wikipedia in Malay
Can we get the Malay language Wikipedia started? I notice
there is content on http://ms.wikipedia.com , but
http://ms.wikipedia.org just links through to Wikipedia-EN.
What else is needed? Does each language need an
Ambassador (mentioned in
http://www.wikipedia.org/wiki/Wikipedia_Embassy ) .
If so, I would not be an ideal Ambassador, maybe Sujita
(cc'd) would be.
Imran William Smith
Project Manager, Open Source Development
Mimos Bhd, Malaysia
----- Original Message -----
From: "Sujita Purushothaman" <sujita(a)mimos.my>
Sent: Wednesday, October 23, 2002 12:14 PM
Subject: Wikipedia in Malay
| Perhaps you should start off, since it's your idea :-)
| Please notice that all contributions to Wikipedia
| are considered to be released under the GNU Free
| Documentation License. If you don't want your
| writing to be edited mercilessly and redistributed at will,
| then don't hit submit. You are also promising us
| that you wrote this yourself, or copied it from a public
| domain resource. DO NOT USE COPYRIGHTED WORK
| WITHOUT PERMISSION!
| Translation :
| Sila ambil perhatian bahawa semua sumbangan kepada Wikipedia adalah
| dianggap diterbitkan dibawah GNU
| Free Documention License (Lesen GNU untuk Dokumentasi Terbuka). Jika
| anda tidak mahu hasil tulisan anda
| diubahsuai tanpa belas kasihan dan diedar sesuka hati, jangan sumbang.
| Anda juga berjanji yang sumbangan anda
| adalah hasil kerja anda sendiri atau diambil dari sumber yang terbuka.
| JANGAN GUNA BAHAN HAKCIPTA TERPELIHARA
| TANPA KEBENARAN.
----- End forwarded message -----
"Jason C. Richey" <jasonr(a)bomis.com>
the auto-bot on WP is really messing up the RC file. I think it
shouldn't be too hard to put a filter interface for admins in there,
making it easy to filter changes by specific users. (This probably will
come up again.) I'm ready to write this if there's interest from the
maintainers. I'm aware of the potential problems (filtered users could
abuse the system), but this would only be done for trustworthy users,
and there are remedies (check user contributions etc.).
So far I haven't heard back regarding my first patch (edit on
doubleclick), so I am reluctant to do more work.
FOKUS - Fraunhofer Insitute for Open Communication Systems
Project BerliOS - http://www.berlios.de
>Brion VIBBER wrote:
>> The error message comes up on the mysql_select_db, and is the
>> first thing we do after opening a connection; but since we're
>> using persistent connections, it could be left in an odd state
>> after the last process...?
> I've tweaked it so if it can't select the database, it will try
> again with a spankin' new connection (via mysql_connect()) and
> make a note in the logfile. So, with any luck, this should at
> least work around the problem.
I doubt such a band-aid will help; this looks like a symptom of
a more fundamental problem, though I don't know what it might be.
I'm afraid I'm not much of a MySQL/PHP guru either (I'd never
seen or used the language before I wrote this software), so I'm
not familiar with its capacity problems. I'm pretty confident
that they can be fixed, or else there's no way a site like
Slashdot could use them, but I'm not sure where to tweak first.
I'll have to investigate.