-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
For MediaWiki (not necessarily Wikipedia), sometimes you want to upload
really big files. An HTTP upload isn't necessarily the best way to do
this, especially if it's lots of really big files (tar gzip them and
uplaod via ftp then telnet in and unpackage).
If you do that, then you've got a bunch of files sitting on the
webserver. Now we've got to link them into the wiki.
How would I do that?
If that's not a feature, any pointers on where to start hacking to get
this to work?
- --
Edward Z. Yang Personal: edwardzyang(a)thewritingpot.com
SN:Ambush Commander Website: http://www.thewritingpot.com/
GPGKey:0x869C48DA http://www.thewritingpot.com/gpgpubkey.asc
3FA8 E9A9 7385 B691 A6FC B3CB A933 BE7D 869C 48DA
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (MingW32)
iD8DBQFDpNygqTO+fYacSNoRAr/6AJ9sdRmls4DyBKyYrZo3C4rv7VuYxwCfZakt
edv3vDz0VydjN0rpyNi1e9c=
=UVJn
-----END PGP SIGNATURE-----
Ævar wrote:
>That still doesn't avoid the problem of
>1. Us allocating a site under a SIL code or some draft ISO spec
>2. ISO allocating a code that equals the SIL code for a different
>language or the ISO changing its mind in the final revision of its
>standard
>3. Us having to deal with the mess
>Which is why I think it would be a good idea to put languages that
>don't have *official* ISO codes or only have SIL codes under some name
>that defenetly won't conflict with future ISO allocations.
Me too, I believe those codes will be taken over as they are now when ISO 639-3 will become official. But then again, believing is not knowing, of course.
I'm not sure if using caps for subdomain names will prevent more confusion than it will possibly cause to many users.
A while ago, when this issue was discussed at Wikipedia-l somebody (could've been me, not sure...) suggested to use locally defined four-lettered codes for languages that don't have ISO codes yet. Thus, any potential interference with future ISO codes (in other words: "mess") could definitely be avoided. Plus it's probably more user-friendly than those somewhat clumsy three-plus-three letter codes.
Arbeo
---------------------------------
Sarah Connor, Moshammer oder Papst Benedikt die Top-Suchen 2005.
The dumps for ja seem a bit old. The latest pages_current is from
beginning of november.
(http://download.wikipedia.org/wikipedia/ja/)
Am I looking in the wrong place?
Thanks
David Harvey
By mistake, I seem to have logged in as another user. I was typing my
username, when my finger slipped and I logged in before I had either
finished typing my complete username, or any password whatsoever.
It seems that the user I accidently logged in as has an empty password.
* is this really possible, or have I made a mistake?
* if this really is so, this is a moderate-sized security hole, because
this has the same dangers as accounts with publicly accessible
passwords, which are generally held to be a case for block-on-sight.
It would probably make sense to check for zero-length passwords at
account creation time,
and to scan for zero length and other trivial passwords on existing
accounts, if possible, and issue a warning that they will be locked if
the user does not change their password after (say) a month.
It would also make sense to try to enforce a simple password-checking
routine, to make sure that users from now on can only set passwords that
are at least slightly stronger than a single dictionary word (two short
words are a surprisingly effective measure in terms of bang-per-character).
-- Neil
Do articles get allocated a unique, stable identity number (UID) along
with their name when they are created in the database?
Paul
--
Yellowikis is to Yellow Pages, as Wikipedia is to The Encyclopedia Britannica
Hello,
I tried installing MediaWiki using Chinese (zh) as the language during
the install process. But when i try to load the site after the install,
i only get a "The page cannot be displayed" error page. I was wondering
if i need to somehow enable support in apache or mysql or download some
other language support package for chinese characters in order for it to
work? I'm using Fedora Core 4 as an operating system.
Andrew.
Anthony DiPierro wrote:
>
>
> As an aside, would the user who clicks the "publish" button find
> herself legally liable for the content of that article? I certainly
> could see an argument for that being the case. Whether or not that'd
> be a good thing or a bad thing is another unanswered question.
>
> Anthony
>
>
This problem could probably be avoided by _not_ providing a "publish"
button at all, but instead only a "deprecate/delete" voting button, and
automatically moving articles from the new-article queue to the main
article space after, say, an hour after creation if they are not shot
down first. An hour is probably plenty of time, given a queue system to
ensure that articles do not fall through the cracks, and the current
number of people doing RC patrol.
I like the idea that new articles could be made visible to logged-on
users only, until they are moved to the main article space -- the
introduction of logged-on-user-only article creation now removes any
need to make the article visible to IP-only users creating their own
articles. Not making queued articles visible to IP-only readers would
also have the effect of making them invisible to web crawlers and
real-time proxy-leeching sites, and hence less likely to appear in
Wikipedia mirrors.
Similarly, it would be a good idea to avoid backing up new articles on
the queue to article database dumps, which would further reduce the
possibility of their being picked up by syndicators.
An RSS feed of the new article queue would be useful, too.
-- Neil