Could please a kind soul take a look at the el wikipedia.
Since about 3-4 days ago every article (including the main page)
come out with a strange notice at the bottom effective saying that
the article was recovered from the same article that is being viewed.
For example the main page comes out saying:
Ανακτήθηκε από
"http://el.wikipedia.org/wiki/%CE%9A%CF%8D%CF%81%CE%B9%CE%B1_%CE%A3%CE%B5%CE…"
Thanks for all the help.
Andreas
--
Andreas Kasenides
e-mail: Andreas.Kasenides_at_cs.ucy.ac.cy
<mailto:Andreas.Kasenides%20at%20cs.ucy.ac.cy>
(replace the _at_ above with @)
hi,
Thanks ivan/jimmy for responding...
Jimmy wrote:
> all, for
> many many topics, en.wikipedia.org is the most convenient and best
> reference,
> and the content is available for free. But it is more generally the
> case in
> fr, de, ja, it, etc. that the articles are independent constructions
> from
> scratch.
I think, there will be 2 types of articles, ones translated from EN
wikipedia, and the regional language secific stuff that's contributed.
Until there is certain point, most of the content will only be
translations.
> At the same time, I absolutely think that if you can find a way to
> get
> access (is there some way that I can help, for example by writing a
> letter to some authorities, or giving you a signature on an
> application, or even paying money, if it is not too much?) for
> wikipedia contributors to this state-funded agency's tool, then if it
> helps a small number of contributors to work faster, then I am all
> for
> it.
Thanks, I believe, as the tool was developed under state funding, it
should be available for citizens, at least for non-commercial causes. I
have initiated communication with the concerned professor. It's great
to know, that the project can back efforts to get the resources. I will
definately come back to you ppl if I need to convince the authorities
for the software access.
>
> What I would envision is that you would have to do a machine
> translation and then immediately edit it to correct grammar and
> meaning mistakes. Whether that would be faster or slower than either
> writing the article from scratch or doing a human-translation
> yourself, I do not know.
>
Yeh, sort of the auto translated docs checked by human editors before
publishing.
Thanks & regards,
Prasad gadgil.
___________________________________________________________ALL-NEW Yahoo! Messenger - all new features - even more fun! http://uk.messenger.yahoo.com
Apologies if this has been brought up before, but I am
curious about the status of automatic replacement of
dashes in the wikitext (in particular -- and ---) with
HTML-entity versions that many users seem to like so
much (ndash and mdash). I noticed that a while back
(February 2004) such a conversion was implemented, but
apparently reverted due to undesirable breakage. Any
way it could be reinstated? I may look into it once I
get familiar with the code.
Also, there's some ongoing disagreement about
"correct" quote usage: several users like to replace
standard ASCII apostrophes with their lsquo/rsquo HTML
counterparts, which seriously uglifies the wikitext.
The same is true of normal double-quotes
(ldquo/rdquo). I realize it may be quite difficult to
implement some form of quote-matching that could
automatically convert these from ASCII, especially
given our other uses for single-quotes; would it be
feasible to use multiple ASCII double-quotes to clue
in the parser about desired behavior? e.g., "foo" for
normal ASCII double-quotes, ""foo"" for an HTML
lsquo/rsquo, and """foo""" for ldquo/rdquo. I can see
where this might run into some problems in situations
involving nested quotation, but seems adequate for the
majority of quoting.
Given the regularity of conflict over this issue (not
to mention some users, who shall remain nameless, on a
mission to replace all occurrences of what they
perceive as bad quoting, wikitext readability be
damned), it seems like something worth implementing. I
like correct and nicely-readable HTML-entity-style
quotes as much as the next guy, as long as it doesn't
hamper editing. It's frustrating to see so much heated
debate over a matter that could, at least in theory,
be solved by such an improvement.
Eric
=====
Do you know stuff? Contribute to Wikipedia! http://www.wikipedia.org/
Help preserve the public domain by becoming a Distributed Proofreader. http://www.pgdp.net/
__________________________________
Do you Yahoo!?
New and Improved Yahoo! Mail - 100MB free storage!
http://promotions.yahoo.com/new_mail
Hi.
I've committed a new feature I just wrote. Recent Changes Patrol. The
commit message explains everything:
New feature: Recent Changes Patrol. All edits and new pages are
now highlighted on Special:Recentchanges and Special:Newpages
until someone "marks" them as "patrolled" using a special link.
For new pages, this link appears at the bottom of the article if
the link in Recent Changes or New Pages is followed. For all
other edits, this link appears only in the diff and only if the
diff link is followed from Recent Changes. (Might need to add
this functionality to Watchlist too; haven't done that yet.)
Since the patch you see in the CVS commit messages is useless because of
all the pointless whitespace removal, I am providing here a patch in
diff -u format which ignores the whitespace changes:
http://lionking.org/~timwi/t/wikipedia/recent-changes-patrol-patch.txt
Please test this feature thoroughly. Thanks!
Timwi
You can disregard my comment about changing the PHPTAL.php as I've done a
clean installation. The only action I have taken is to create a directory
(writable by everyone) called /tmp in the media wiki folder.
The error I get when installing is this:
Checking environment...
Warning: set_time_limit(): Cannot set time limit in safe mode in
/home/virtual/site22/fst/var/www/html/wiki/install-utils.inc on line
26
* PHP 4.3.3 ok
* PHP server API is apache; ok, using pretty URLs (index.php/Page_Title)
* Have XML / Latin1-UTF-8 conversion support.
* PHP's memory_limit is 8M. If this is too low, installation may fail!
Attempting to raise limit to 20M... failed.
* Have zlib support; enabling output compression.
* Found GD graphics library built-in, image thumbnailing will be
enabled if you enable uploads.
* Installation directory: /home/virtual/site22/fst/var/www/html/wiki
* Script URI path: /wiki
Warning: $wgProxyKey is insecure Can't find a writable temp
directory for the XHTML template. Check that the TMP environment
variable points to a writable directory, or that the default temp
dir (/tmp) exists and is writable.
Thanks for any help,
Karl
> <karl(a)karllong.com>:
>> I have acttually created a /tmp directory in my mediawiki directory and
>> made it writable, I've also gone into the PHPTAL.php and changed the TMP
>> variable to a foll path ie.
>> /home/virtual/site22/fst/var/www/html/wiki/tmp, but that still results in
>> the install seeming to hang at "Warning: $wgProxyKey is insecure"
>
> What dit you change exactly in PHPTAL.php?
Hello,
In the new default skin, the Alt-B key combination seems to bound to the
"what links here" function. Alt-B is normally the shortcut to the
bookmarks, at least in my browser (Mozilla Firefox). I find the binding to
"what links here" rather annoying, because it blocks me from a keyboard
shortcut. I doubt that I'm the only one annoyed by this.
I suggest that the Alt-B key mapping be dropped or changed to something
else.
--
Greetings from Troels Arvin, Copenhagen, Denmark
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
This should be the final beta release of MediaWiki 1.3.0; the final
final version will be released in a few days after some more bug fixing
and polishing up of documentation and installation.
Beta 6 includes a security fix: earlier 1.3.0 beta releases may be
vulnerable to a PHP inclusion attack if you have allow_url_fopen and
register_globals on (this is the default configuration in PHP 4.1.x, but
register_globals is off by default in 4.2.x and later).
Note that while MediaWiki through 1.1 required register_globals to be
on, 1.2 and 1.3 *do not*. If you have register_globals on, you should
turn it off unless you are absolutely sure you require it for some other
package. See http://php.net/register_globals for general information.
Release notes:
https://sourceforge.net/project/shownotes.php?release_id=258701
Download:
http://prdownloads.sourceforge.net/wikipedia/mediawiki-1.3.0beta6.tar.gz?do…
Wiki admin help mailing list:
http://mail.wikipedia.org/mailman/listinfo/mediawiki-l
Bug report system:
https://sourceforge.net/tracker/?group_id=34373&atid=411192
Play "stump the developers" live on IRC:
#mediawiki on irc.freenode.net
- -- brion vibber (brion @ pobox.com)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (Darwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBFA81wRnhpk1wk44RAjtcAJ45L8KSHvZEv6strva58iChHvYliQCgj85E
UyHl6D/y/mm4nPhnS6zWjpE=
=lNM6
-----END PGP SIGNATURE-----
I've actually found several tmp directories (writable by everyone):
/home/virtual/site22/fst/tmp
/home/virtual/site22/fst/var/tmp
I'm not permissioned to write to /var/www/
I wonder if there is somewhere I can tell the mediawiki installer to use
on of those tmp directories.
> If I'm not mistaken you need the tmp-directory in your virtual host
> setting to be writeable by your apache user.
> Maybe you got a tmp directory like so /home/virtual/site22/fst/var/www/tmp
> in the virtual_host config of your account (So it's outside docroot). That
> virtual host directory may have permissions like drwxr_xr_x or just
> drwx______ with you as owner and ftpuser as group.
> That's something the apache user won't have any write permissions to. If
> so, you can give that tmp directory write permissions like 777 or ask your
> provider to do a chown apache-user.apache-user (www-data in my case) to
> that tmp directory and it should work.
>
> But that would mean your VirtualHost setup is being a poor, sad story.
> I.e. not real useful.
>
> --tictric
Hi all,
I'm trying to install mediawiki on a shared host and am getting an error
regarding the /tmp directory:
Checking environment...
Warning: set_time_limit(): Cannot set time limit in safe mode in
/home/virtual/site22/fst/var/www/html/wiki/install-utils.inc on line
26
* PHP 4.3.3 ok
* PHP server API is apache; ok, using pretty URLs (index.php/Page_Title)
* Have XML / Latin1-UTF-8 conversion support.
* PHP's memory_limit is 8M. If this is too low, installation may fail!
Attempting to raise limit to 20M... failed.
* Have zlib support; enabling output compression.
* Found GD graphics library built-in, image thumbnailing will be
enabled if you enable uploads.
* Installation directory: /home/virtual/site22/fst/var/www/html/wiki
* Script URI path: /wiki
Warning: $wgProxyKey is insecure Can't find a writable temp
directory for the XHTML template. Check that the TMP environment
variable points to a writable directory, or that the default temp
dir (/tmp) exists and is writable.
I have acttually created a /tmp directory in my mediawiki directory and
made it writable, I've also gone into the PHPTAL.php and changed the TMP
variable to a foll path ie.
/home/virtual/site22/fst/var/www/html/wiki/tmp, but that still results in
the install seeming to hang at "Warning: $wgProxyKey is insecure"
Any help is appreciated,
Karl
You can disregard my comment about changing the PHPTAL.php as I've done a
clean installation. The only action I have taken is to create a directory
(writable by everyone) called /tmp in the media wiki folder.
The error I get when installing is this:
Checking environment...
Warning: set_time_limit(): Cannot set time limit in safe mode in
/home/virtual/site22/fst/var/www/html/wiki/install-utils.inc on line
26
* PHP 4.3.3 ok
* PHP server API is apache; ok, using pretty URLs (index.php/Page_Title)
* Have XML / Latin1-UTF-8 conversion support.
* PHP's memory_limit is 8M. If this is too low, installation may fail!
Attempting to raise limit to 20M... failed.
* Have zlib support; enabling output compression.
* Found GD graphics library built-in, image thumbnailing will be
enabled if you enable uploads.
* Installation directory: /home/virtual/site22/fst/var/www/html/wiki
* Script URI path: /wiki
Warning: $wgProxyKey is insecure Can't find a writable temp
directory for the XHTML template. Check that the TMP environment
variable points to a writable directory, or that the default temp
dir (/tmp) exists and is writable.
Thanks for any help,
Karl
> <karl(a)karllong.com>:
>> I have acttually created a /tmp directory in my mediawiki directory and
>> made it writable, I've also gone into the PHPTAL.php and changed the TMP
>> variable to a foll path ie.
>> /home/virtual/site22/fst/var/www/html/wiki/tmp, but that still results in
>> the install seeming to hang at "Warning: $wgProxyKey is insecure"
>
> What dit you change exactly in PHPTAL.php?