On Mon, Mar 23, 2009 at 11:06 AM, Brion Vibber wrote:
> On 3/20/09 11:42 PM, Gerard Meijssen wrote:
>> This is confusing. So there are two parts to Cite to make it work
>> completely.
>
> There are actually two *entirely separate extensions* in the Cite directory:
>
>
> Cite/Cite.php : the , tags
Hi,
I hate to be resurrecting an old thread, but I think for the purpose of
completion I would like to post my experience with the Import of XML
Dumps of Wikipedia into Mediawiki, so that it would help someone else
looking for this information. I started this thread after all.
I
And I thought this was wikitech-l... :)
Welcome, Fred.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l
Everybody please join me in welcoming Frédéric Vassard as the latest
addition to the Wikimedia Foundation's tech team.
Fred's been doing Linux and Unix system administration around the SF bay
area for the last few years, and has enough notches on his belt to dare
to step up and tame the beasts
Chad schrieb:
> On Mon, Mar 23, 2009 at 4:39 PM, Brion Vibber wrote:
>> On 3/22/09 6:08 PM, Chad wrote:
>>> Unfortunately, this comes back to the limitation of the
>>> Http class to return helpful error messages. There's an
>>> open bug about similarly vague messages in Interwiki
>>> imports. Sadl
On Mon, Mar 23, 2009 at 4:39 PM, Brion Vibber wrote:
> On 3/22/09 6:08 PM, Chad wrote:
>> Unfortunately, this comes back to the limitation of the
>> Http class to return helpful error messages. There's an
>> open bug about similarly vague messages in Interwiki
>> imports. Sadly, the methods in Htt
Brion Vibber wrote:
> On 3/20/09 11:42 PM, Gerard Meijssen wrote:
>> This is confusing. So there are two parts to Cite to make it work
>> completely.
>
> There are actually two *entirely separate extensions* in the Cite directory:
>
>
> Cite/Cite.php : the , tags.
>
> This adds a system for ad
On 3/23/09 12:57 PM, MinuteElectron wrote:
> The first main solution to the problems outlined here would be to have
> an option in preferences to completely enable or disable the edit
> tools dialog.
There's really no need for that; an initial load with a sensible
architecture would be trivial in
On 3/23/09 9:17 AM, Roan Kattouw wrote:
> Aryeh Gregor schreef:
>> with JavaScript parsing it to make the characters clickable?
>>
> Since all of this requires JavaScript to work anyway, a quick and dirty
> first step to un-bloating stuff would be to move all of the charinsert
> stuff to a separate
On 3/22/09 6:08 PM, Chad wrote:
> Unfortunately, this comes back to the limitation of the
> Http class to return helpful error messages. There's an
> open bug about similarly vague messages in Interwiki
> imports. Sadly, the methods in Http only return content
> or failure, not a helpful message wh
Hello,
We have been looking in to making a few modifications to edit tools to
make it more useful, and spent some time discussing various solutions.
At the moment we have a specification for some basic additional
features [1] (waiting for auditing) but as it stands this does not
solve all of the p
On Mon, Mar 23, 2009 at 12:29 PM, Roan Kattouw wrote:
> Chad schreef:
>> For the ForeignApiRepo to support it, we need native upload
>> support in the API to begin with.
>>
> Right, didn't think about that :)
>
> Roan Kattouw (Catrope)
>
> ___
> Wikitech
Chad schreef:
> For the ForeignApiRepo to support it, we need native upload
> support in the API to begin with.
>
Right, didn't think about that :)
Roan Kattouw (Catrope)
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia
On Mon, Mar 23, 2009 at 12:20 PM, Roan Kattouw wrote:
> Michael Dale schreef:
>> Great that we are moving forward with Upload-by-URL uploads :)
>>
>> I have been simultaneously testing / developing things with the
>> new-upload branch. So the injection script check if upload over
>> javascript api
Michael Dale schreef:
> Great that we are moving forward with Upload-by-URL uploads :)
>
> I have been simultaneously testing / developing things with the
> new-upload branch. So the injection script check if upload over
> javascript api is supported then uses that (over parsing the form html
>
Aryeh Gregor schreef:
> with JavaScript parsing it to make the characters clickable?
>
Since all of this requires JavaScript to work anyway, a quick and dirty
first step to un-bloating stuff would be to move all of the charinsert
stuff to a separate .js file whose sole purpose is to add the
cha
Great that we are moving forward with Upload-by-URL uploads :)
I have been simultaneously testing / developing things with the
new-upload branch. So the injection script check if upload over
javascript api is supported then uses that (over parsing the form html
output).
We also have to think a
Seems reasonable for logged in users to opt in for languages they are
going to actually use, but what about anonnomous users? Perhaps it
could be a hidden field with an Ajax(/some fallback) control that only
loads the other languages when the user asks for them, which would
probably be seld
On Mon, Mar 23, 2009 at 8:10 AM, wrote:
> Nice to have all the world's alphabets at one's fingertips right there
> on the (www.mediawiki.org) edit page. Wow, IPA, Pīnyīn, they're all
> there. I'm saving it for even when I'm not editing MediaWiki.
>
> (However, as it bloats the edit page up to 700
Nice to have all the world's alphabets at one's fingertips right there
on the (www.mediawiki.org) edit page. Wow, IPA, Pīnyīn, they're all
there. I'm saving it for even when I'm not editing MediaWiki.
(However, as it bloats the edit page up to 700%
$ wget -O x.html
http://www.mediawiki.org/w/inde
20 matches
Mail list logo
