User "TheDJ" posted a comment on MediaWiki.r87296.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87296#c16507
Commit summary:
* Impove localization.
* Add Dutch localization
Comment:
UTF-16 text files actually, but apparently SVN isn't smart enough for that.
__
User "Siebrand" posted a comment on MediaWiki.r87317.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87317#c16506
Commit summary:
Removed unused messages:
'extremelycomplextest'
'internallinktest'
'linktest'
'magictest'
'mwe-copyright-custom'
'mwe-copyright-macro'
'mwe-loading-up
User "Nikerabbit" posted a comment on MediaWiki.r87296.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87296#c16505
Commit summary:
* Impove localization.
* Add Dutch localization
Comment:
Localisation in binary files??
___
MediaWiki-
Bounces? That is, some return codes from a program delivery can be interpreted
as a failed delivery. Or perhaps the program is segfaulting or running out of
memory? Or replies sent to the envelope sender, which can be interpreted as
bounces, but which lack the empty sender of a real bounce.
R
User "Xqt" changed the status of pywikipedia.r9196.
Old Status: new
New Status: resolved
Full URL: http://www.mediawiki.org/wiki/Special:Code/pywikipedia/9196#c0
Commit summary:
Allow lists of Page and User objects to be interogated
___
MediaWiki-Code
sorry for the re-post ( having trouble with the wikitech-l list post
email migration :(
I would also be interested in discussing this in Berlin or otherwise ;)
I can offer some notes about video embedding inline:
On 04/29/2011 03:30 PM, Brion Vibber wrote:
>> > > Enhanced media player goodies li
User "MaxSem" posted a comment on MediaWiki.r87308.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87308#c16504
Commit summary:
better language handling - abandon magic language switch in favor of using
int:lang as parameter, use parser->getFunctionLang() instead of wgContLanguag
User "Aaron Schulz" posted a comment on MediaWiki.r87292.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87292#c16503
Commit summary:
* (bug 20468) User::invalidateCache throws 1205: Lock wait timeout exceeded
Severly limit the number of calls that actually update the database (f
I'd also love to know how it keeps getting unsubscribed. This is the
third time...
On Mon, May 2, 2011 at 7:03 PM, K. Peachey wrote:
> On Tue, May 3, 2011 at 10:05 AM, Happy-melon wrote:
>> Wow, now here's a blast from the past... :-D A lot of these stats are now
>> in the BZ4 report page, but
I would also be interested in discussing this in Berlin or otherwise ;)
I can offer some notes about video embedding inline:
On 04/29/2011 03:30 PM, Brion Vibber wrote:
> > Enhanced media player goodies like embedding have been slowly coming
along,
> > with a handy embedding option now available
User "Reedy" posted a comment on MediaWiki.r87232.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87232#c16502
Commit summary:
Make a method static per the comment, update the only non static usage (in
Parser) itself
Comment:
That's slightly amusing. It had one doing it one way
On Tue, May 3, 2011 at 10:05 AM, Happy-melon wrote:
> Wow, now here's a blast from the past... :-D A lot of these stats are now
> in the BZ4 report page, but it's still very nice to have the weekly
> reminder. Cookie for whoever dug it out and got it going again!
>
> --HM
Ryan resubscribed the e
"reporter" wrote in message
news:e1pprj3-bs...@kaulen.wikimedia.org...
> MediaWiki Bugzilla Report for November 29, 2010 - December 06, 2010
...
"reporter" wrote in message
news:e1qgwls-000389...@kaulen.wikimedia.org...
> MediaWiki Bugzilla Report for April 25, 2011 - May 02, 2011
>
Wow
On Mon, May 2, 2011 at 5:55 PM, Brion Vibber wrote:
> On Mon, May 2, 2011 at 5:28 PM, Tim Starling wrote:
>
>> I don't think that's a fundamental problem, I think it's a quick hack
>> added to reduce the development time devoted to rare wikitext
>> constructs, while maintaining round-trip safety.
On Mon, May 2, 2011 at 5:28 PM, Tim Starling wrote:
> On 03/05/11 04:25, Brion Vibber wrote:
> > The most fundamental problem with Wikia's editor remains its fallback
> > behavior when some structure is unsupported:
> >
> > "Source mode required
> >
> > Rich text editing has been disabled beca
On Mon, May 2, 2011 at 7:52 PM, Happy-melon wrote:
> If a feature freeze is to work, it has to either a) be for a very short
> period so that developers neither get disenchanted and wander off nor start
> stockpiling working-copy changes to empty onto trunk once it's thawed, or b)
> be part of a f
On Mon, May 2, 2011 at 8:38 PM, Chad wrote:
> People want to write their own parsers because they don't want to use PHP.
> They want to parse in C, Java, Ruby, Python, Perl, Assembly and every
> other language other than the one that it wasn't written in.
s/wasn't/was/
-Chad
___
On Mon, May 2, 2011 at 8:28 PM, Tim Starling wrote:
> I know that there is a camp of data reusers who like to write their
> own parsers. I think there are more people who have written a wikitext
> parser from scratch than have contributed even a small change to the
> MediaWiki core parser. They ha
Indeed .. i remember writing this report for brion years ago. brings back
memories.
--tomasz
On Mon, May 2, 2011 at 5:05 PM, Happy-melon wrote:
>
> "reporter" wrote in message
> news:e1pprj3-bs...@kaulen.wikimedia.org...
> > MediaWiki Bugzilla Report for November 29, 2010 - December 06, 2
On 03/05/11 04:25, Brion Vibber wrote:
> The most fundamental problem with Wikia's editor remains its fallback
> behavior when some structure is unsupported:
>
> "Source mode required
>
> Rich text editing has been disabled because the page contains complex
> code."
I don't think that's a fu
On 05/02/2011 06:40 PM, Owen Davis wrote:
> I think the current plan is to see what transpires with the
> upcoming Parser redesign and keep our code in sync. The
> primary authors of this RTE reskin will be at the Berlin
> hackathon as well.
Who are those authors? I'd like to know so I can find
"Chad" wrote in message
news:BANLkTikd4Eb-V8W-kA1qe+=bnjxmj+o...@mail.gmail.com...
>
> I understand, respect, and value the contributions of people who want to
> add new features. Features are what moves the product forward, and at
> no point do we want to be hostile to people willing to put in
Brion Vibber pobox.com> writes:
> Note that for Wikipedia that's not just going to affect experienced editors
Very true! I think we have more inexperienced editors, and that's been a
product design focus for us for a while so I tend to make assumptions
based on that.
> Do you mean that it d
Am using vim, which knows about ctags. Exuberant ctags (which is the name of a
piece of software) knows about languages other than C. It seems not to know
about class structure, and which function is being overridden where. I want to
be able to read through the code that my Swift interface will
I totally <3 that you wrote it in python.
On Mon, May 2, 2011 at 4:21 PM, Russell N. Nelson - rnnelson
wrote:
> Maybe there's a better tool to tell you what function is defined in what
> class in PHP, but I couldn't find one in the time it would take me to write
> it, so I wrote it. It's not ev
On 03/05/11 04:54, Alex wrote:
> Question: why does it have to normalise at all?
>
> I do think that the editing environment at Wikipedia means that consistent
> non-normalised editing by wikitext users and subsequent normalisation by
> anyone using WYSIWYG would be messy and disruptive, but would
User "Kaldari" posted a comment on MediaWiki.r86927.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/86927#c16501
Commit summary:
adding language support to #time parser function, per bug 28655
Comment:
After talking with Platonides, I've redone the language handling. See r87308.
On Mon, May 2, 2011 at 4:21 PM, Russell N. Nelson - rnnelson <
rnnel...@clarkson.edu> wrote:
> Maybe there's a better tool to tell you what function is defined in what
> class in PHP, but I couldn't find one in the time it would take me to write
> it, so I wrote it.
Depending on what you're tryi
Maybe there's a better tool to tell you what function is defined in what class
in PHP, but I couldn't find one in the time it would take me to write it, so I
wrote it. It's not even a screenful. Give it the class definitions, in class
hierarchy order, on the command line. It will pull out the cl
On Mon, May 2, 2011 at 4:01 PM, Platonides wrote:
> > But it's not an intractable problem. Essentially, anything in the format:
> >
> > {{start}}
> > content1
> > content2
> > {{end}}
> >
> > can be rewritten something like:
> >
> > {{container|
> > content1
> > content2
> > }
On Mon, May 2, 2011 at 3:40 PM, Owen Davis wrote:
> Hi, I work at Wikia (although I am relatively new and I have only
> made small modifications to the editor).
Hi!
> This basic criticism of
> the design is true and is still the source of issues, but it's been
> improving. I think another p
Brion Vibber wrote:
>> {{Open template}} text {{Close template}} structures are IMHO a big
>> problem for any WYSIWYG editor.
>> But there's no way they are going away.
>
>
> If we determine they have to go, then we can devise ways to find and migrate
> them -- it'll be a process that takes time a
On Mon, May 2, 2011 at 3:32 PM, Platonides wrote:
> > If we can devise a way to consistently treat expansions that *aren't* a
> > hierarchical match fro the HTML node tree, then we might not have to
> change
> > templates much. If we can't, then we might have to start enforcing
> > hierarchical t
Roan Kattouw gmail.com> writes:
> While I'm sure this particular bug has been fixed, it sounds like the
> underlying problem remains. FCKeditor seems to be converting wikitext
> to HTML, let users edit the HTML, then convert the HTML back to
> wikitext. The bugs would then result from the fact th
On Mon, May 2, 2011 at 3:29 PM, Platonides wrote:
> Magnus Manske wrote:
>>
>> So, why not use my WYSIFTW approach? It will only "parse" the parts of
>> the wikitext that it can turn back, edited or unedited, into wikitext,
>> unaltered (including whitespace) if not manually changed. Some parts
>>
On 05/02/11 15:30, wikitech-l-requ...@lists.wikimedia.org wrote:
> Date: Tue, 03 May 2011 00:29:51 +0200
> From: Platonides
> Subject: Re: [Wikitech-l] WYSIWYG and parser plans (was What is wrong
> withWikia's WYSIWYG?)
> To:wikitech-l@lists.wikimedia.org
> Message-ID:
> Content-Type: tex
User "^demon" changed the status of MediaWiki.r87306.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87306#c0
Commit summary:
Remove empty files left by r16526, r29128 and r83029
___
MediaWiki-CodeReview
On 11-05-02 03:32 PM, Platonides wrote:
> Brion Vibber wrote:
>> A bigger deal will probably be actually changing structures that don't
>> render consistently, and that'll depend on how brave we are changing nested
>> template & table structures to fit a hierarchical document model.
>>
>> We've bas
Brion Vibber wrote:
> Looks like just bad patch reverts that removed the file contents but didn't
> actually delete.
>
> -- brion
Gone in r87306.
___
Wikitech-l mailing list
Wikitech-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/
Brion Vibber wrote:
> A bigger deal will probably be actually changing structures that don't
> render consistently, and that'll depend on how brave we are changing nested
> template & table structures to fit a hierarchical document model.
>
> We've basically got two levels of stuff:
>
> * parsing
best idea so far ...
On 03. 05. 2011 00:29, Platonides wrote:
> Magnus Manske wrote:
>> So, why not use my WYSIFTW approach? It will only "parse" the parts of
>> the wikitext that it can turn back, edited or unedited, into wikitext,
>> unaltered (including whitespace) if not manually changed. Some
User "Kaldari" posted a comment on MediaWiki.r86927.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/86927#c16500
Commit summary:
adding language support to #time parser function, per bug 28655
Comment:
Fixed in r87305 (only for #time, not for Language in
User "Kaldari" posted a comment on MediaWiki.r86927.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/86927#c16499
Commit summary:
adding language support to #time parser function, per bug 28655
Comment:
Hopefully this is fixed in r87305. I don't know much
Magnus Manske wrote:
>
> So, why not use my WYSIFTW approach? It will only "parse" the parts of
> the wikitext that it can turn back, edited or unedited, into wikitext,
> unaltered (including whitespace) if not manually changed. Some parts
> may therefore stay as wikitext, but it's very rare (exce
User "Platonides" posted a comment on MediaWiki.r87232.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87232#c16498
Commit summary:
Make a method static per the comment, update the only non static usage (in
Parser) itself
Comment:
extensions/News/NewsRenderer.php:
User "Krinkle" changed the status of MediaWiki.r87265.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87265#c0
Commit summary:
Fix r87203: don't use a for..in loop on an array
___
MediaWiki-CodeReview mai
User "Krinkle" changed the status of MediaWiki.r87303.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87303#c0
Commit summary:
Localisation updates for ToolserverI18N messages from translatewiki.net
(2011-05-02 21:35:00 UTC)
__
User "Krinkle" changed the status of MediaWiki.r87304.
Old Status: new
New Status: deferred
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87304#c0
Commit summary:
Localisation updates for core and extension messages from translatewiki.net
(2011-05-02 21:42:00 UTC)
User "Reedy" changed the status of MediaWiki.r87290.
Old Status: fixme
New Status: new
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87290#c0
Commit summary:
Add makeInsertOptions
Allow Sqlite to OR IGNORE on UPDATE or INSERT
___
Med
User "Raymond" changed the status of MediaWiki.r87290.
Old Status: new
New Status: fixme
User "Raymond" also posted a comment on MediaWiki.r87290.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87290#c16497
Commit summary:
Add makeInsertOptions
Allow Sqlite to OR IGNORE on UPDA
User "Krinkle" posted a comment on MediaWiki.r86409.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/86409#c16496
Commit summary:
(bug 28352) "blocked admins actually can't unblock themselves because it checks
the wrong parameter". This doesn't need to be forward-ported as the en
On Mon, May 2, 2011 at 12:55 PM, Magnus Manske
wrote:
> On Mon, May 2, 2011 at 7:33 PM, Fred Bauder
> wrote:
> >>> Beyond that let's flip the question the other way -- what do we *want*
> >> out
> >> of WYSIWYG editing, and can that tool provide it or what else do we
> need?
> >
> > We want somet
User "Jack Phoenix" changed the status of MediaWiki.r87277.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87277#c0
Commit summary:
Fix and add some comments.
___
MediaWiki-CodeReview mailing list
mediawi
User "Jack Phoenix" changed the status of MediaWiki.r87291.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87291#c0
Commit summary:
Renamed methods as per our coding standards...
___
MediaWiki-CodeReview
On Mon, May 2, 2011 at 7:33 PM, Fred Bauder wrote:
>
>> Beyond that let's flip the question the other way -- what do we *want*
>> out
>> of WYSIWYG editing, and can that tool provide it or what else do we need?
>
> We want something simpler and easier to use. That is not what Wikia has.
> I could
User "Thenub314" posted a comment on MediaWiki.r86962.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/86962#c16495
Commit summary:
The following changes enhance the way texvc handles space around
mathematical function names when translating to HTML; adds support for
the sen, the S
On Mon, May 2, 2011 at 11:54 AM, Alex wrote:
> Question: why does it have to normalise at all?
>
> I do think that the editing environment at Wikipedia means that consistent
> non-normalised editing by wikitext users and subsequent normalisation by
> anyone using WYSIWYG would be messy and disrup
Question: why does it have to normalise at all?
I do think that the editing environment at Wikipedia means that consistent
non-normalised editing by wikitext users and subsequent normalisation by
anyone using WYSIWYG would be messy and disruptive, but would a change
whereby it more precisely recor
On 04/29/2011 05:40 PM, Bryan Tong Minh wrote:
> On Fri, Apr 29, 2011 at 10:30 PM, Brion Vibber wrote:
>> currently there's no exposed
>> license metadata (highly desired for Wikimedia's usage, obviously)
>>
> Krinkle and me have been working on that a while ago, but after
> discussion on this lis
On Mon, May 2, 2011 at 9:17 AM, Daniel Friesen wrote:
> On 11-05-02 08:12 AM, Thomas Dalton wrote:
> > No. I clearly said there would be small amounts of normalisation to
> > deal with new wikitext edits, but that the whole article would only
> > need to be normalised once. I was not assuming we w
Thomas Dalton writes:
> On 2 May 2011 13:09, Roan Kattouw wrote:
>> On Mon, May 2, 2011 at 1:41 PM, Maury Markowitz
>> wrote:
>>> Editors do this all the time anyway. Typically using automated tools
>>> so they don't have to do any actual work.
>>>
>> Sure, but those aren't typically mixed with
> Beyond that let's flip the question the other way -- what do we *want*
> out
> of WYSIWYG editing, and can that tool provide it or what else do we need?
We want something simpler and easier to use. That is not what Wikia has.
I could hardly stand trying it out for a few minutes.
Fred
___
User "Happy-melon" changed the status of MediaWiki.r83795.
Old Status: fixme
New Status: new
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/83795#c0
Commit summary:
Follow-up r83794, r83792: restore new SpecialBlock.php code from r83786. This
revision should *not* be broken :D
User "^demon" changed the status of MediaWiki.r87270.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87270#c0
Commit summary:
Update PHP minimum version checks to 5.2.3
___
MediaWiki-CodeReview mailing li
On Mon, May 2, 2011 at 12:04 AM, Tim Starling wrote:
> Can someone please tell me, in precise technical terms, what is wrong
> with Wikia's WYSIWYG editor and why we can't use it?
>
> I have heard that it has bugs in it, but I have not been told exactly
> what these bugs are, why they are more rel
User "Kaldari" posted a comment on MediaWiki.r87258.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87258#c16494
Commit summary:
FlickrChecker fixes, follow-up to r87002 and r87031
Comment:
Oops! Should be fixed in r87269.
__
On 02/05/11 09:06, Max Semenik wrote:
> I started that athttp://www.mediawiki.org/wiki/MediaWiki_1.17 some
> time ago, needs more collaboration.
And I started the 1.18 one with illustrative (and free) pictures :p
http://www.mediawiki.org/wiki/MediaWiki_1.18
--
Ashar Voultoiz
__
User "Catrope" changed the status of MediaWiki.r87259.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87259#c0
Commit summary:
revert accidental inclusion of mw.FlickrChecker.js, not ready yet
__
User "Catrope" changed the status of MediaWiki.r87031.
Old Status: fixme
New Status: resolved
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87031#c0
Commit summary:
further work on FlickrChecker module
___
Med
User "Catrope" changed the status of MediaWiki.r87002.
Old Status: fixme
New Status: resolved
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87002#c0
Commit summary:
initial partially functioning version of FlickrChecker
_
User "Catrope" changed the status of MediaWiki.r87258.
Old Status: new
New Status: fixme
User "Catrope" also posted a comment on MediaWiki.r87258.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87258#c16493
Commit summary:
FlickrChecker fixes, follow-up
Daniel Mietchen googlemail.com> writes:
>
> Thank you, Siebrand!
>
> Daniel
>
Hello, I work at Wikia and I am familiar with that extension.
If you have any specific questions feel free to get in touch
with me. Also, there's a less raw view of the code available
via trac:
http://trac.wikia
User "Catrope" posted a comment on MediaWiki.r87203.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87203#c16492
Commit summary:
(bug 28738) Implement request splitting in mw.loader so ResourceLoader requests
with query strings longer than a certain value
User "✓" posted a comment on MediaWiki.r87203.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87203#c16491
Commit summary:
(bug 28738) Implement request splitting in mw.loader so ResourceLoader requests
with query strings longer than a certain value are split up. The maximum quer
User "Reedy" posted a comment on MediaWiki.r87262.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87262#c16490
Commit summary:
Closures are a PHP 5.3 feature. MediaWiki currently requires PHP 5.2.3 or
higher. Replacing anonymous function, aka closure with traditional method.
Com
On Sat, Apr 30, 2011 at 4:15 PM, Platonides wrote:
> Johannes Weberhofer wrote:
> > Dear all,
> >
> > there are two empty files in the distribution. Are they of any usage?
> >
> > /maintenance/archives/patch-page_no_title_convert.sql
> > /maintenance/archives/patch-image_reditects.sql
>
> They ar
User "Nikerabbit" posted a comment on MediaWiki.r87260.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87260#c16489
Commit summary:
* Removed Skin::reallyGenerateUserStylesheet() nothing uses it and nothing
overrides it
* Corrected Skin::generateUserJs() and Skin::generateUserSty
User "Kaldari" posted a comment on MediaWiki.r87002.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87002#c16488
Commit summary:
initial partially functioning version of FlickrChecker
Comment:
Fixed in r87258.
___
User "Kaldari" posted a comment on MediaWiki.r87031.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87031#c16487
Commit summary:
further work on FlickrChecker module
Comment:
Fixed in r87258.
___
MediaWiki-Cod
User "Kaldari" posted a comment on MediaWiki.r87031.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87031#c16486
Commit summary:
further work on FlickrChecker module
Comment:
I wanted to get feedback from neil on the interface implementation before I
ac
User "Catrope" changed the status of MediaWiki.r87257.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87257#c0
Commit summary:
consistant use of jQuery object
___
MediaWiki-CodeRe
MediaWiki Bugzilla Report for April 25, 2011 - May 02, 2011
Status changes this week
Bugs NEW : 411
Bugs ASSIGNED : 39
Bugs REOPENED : 72
Bugs RESOLVED
User "^demon" changed the status of MediaWiki.r84169.
Old Status: new
New Status: ok
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/84169#c0
Commit summary:
Also remove message as followup to r84133
___
MediaWiki-CodeReview mailing lis
On Mon, May 2, 2011 at 3:06 AM, Max Semenik wrote:
> On 02.05.2011, 10:41 Tim wrote:
>
>> It would be nice if someone could write a user-oriented summary of the
>> major changes in the branch, like I did for 1.16. The 1.16 one was
>> used for the RELEASE-NOTES file, the mediawiki-announce email an
On Mon, May 2, 2011 at 2:41 AM, Tim Starling wrote:
>> Looking ahead to 1.19, I'd like to do the same and branch soon after 1.18 has
>> been dropped. Since 1.19's a little further out and hasn't started taking
>> shape
>> yet, I'd like to go ahead and propose what sort of release we should aim fo
On 11-05-02 08:12 AM, Thomas Dalton wrote:
> On 2 May 2011 15:31, David Gerard wrote:
>> On 2 May 2011 15:27, Thomas Dalton wrote:
>>
>>> The normalisation only really needs to happen once, though. There may
>>> be a few little bits where people have made wikitext edits since the
>>> last WYSIWYG
On 2 May 2011 15:31, David Gerard wrote:
> On 2 May 2011 15:27, Thomas Dalton wrote:
>
>> The normalisation only really needs to happen once, though. There may
>> be a few little bits where people have made wikitext edits since the
>> last WYSIWYG edit, but the whole article will only need to be
User "Catrope" changed the status of MediaWiki.r87226.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87226#c0
Commit summary:
* (bug 28265) allow outputting of comments for action=expandtemplates
__
User "Catrope" changed the status of MediaWiki.r87242.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87242#c0
Commit summary:
Followup r87225
Best to rename everything when you rename something
___
User "Catrope" changed the status of MediaWiki.r87225.
Old Status: new
New Status: ok
User "Catrope" also posted a comment on MediaWiki.r87225.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87225#c16485
Commit summary:
* (bug 27185) API: Add Special:Com
User "Catrope" changed the status of MediaWiki.r87206.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87206#c0
Commit summary:
* (bug 26664) Add 'url' to meta=globaluserinfo and/or 'database' to
action=sitematrix
Added URL
User "Catrope" changed the status of MediaWiki.r87216.
Old Status: new
New Status: ok
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87216#c0
Commit summary:
Use HTML5 for formatted API output
___
MediaWiki-Cod
User "Reedy" changed the status of MediaWiki.r83795.
Old Status: new
New Status: fixme
User "Reedy" also posted a comment on MediaWiki.r83795.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/83795#c16484
Commit summary:
Follow-up r83794, r83792: restore new SpecialBlock.php code
On 2 May 2011 15:27, Thomas Dalton wrote:
> The normalisation only really needs to happen once, though. There may
> be a few little bits where people have made wikitext edits since the
> last WYSIWYG edit, but the whole article will only need to be
> normalised the first time there is a WYSIWYG e
On 2 May 2011 13:09, Roan Kattouw wrote:
> On Mon, May 2, 2011 at 1:41 PM, Maury Markowitz
> wrote:
>> Editors do this all the time anyway. Typically using automated tools
>> so they don't have to do any actual work. Surely someone here has had
>> to wade through someone changing every REF to tha
User "Catrope" changed the status of MediaWiki.r87031.
Old Status: ok
New Status: fixme
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87031#c0
Commit summary:
further work on FlickrChecker module
___
MediaWiki
User "Catrope" posted a comment on MediaWiki.r87031.
Full URL:
https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Special:Code/MediaWiki/87031#c16483
Commit summary:
further work on FlickrChecker module
Comment:
+* Retrieve the list of all current Flickr licenses and store it in an
User "Reedy" posted a comment on MediaWiki.r87245.
Full URL: http://www.mediawiki.org/wiki/Special:Code/MediaWiki/87245#c16482
Commit summary:
bug id : 28094 + bug related to the red link closed
Comment:
You do realise core MW has jquery 1.4.4 included?
On Mon, May 2, 2011 at 1:41 PM, Maury Markowitz
wrote:
> Editors do this all the time anyway. Typically using automated tools
> so they don't have to do any actual work. Surely someone here has had
> to wade through someone changing every REF to that bag of hammers CITE
> tag.
>
Sure, but those ar
On Mon, May 2, 2011 at 1:29 PM, Tim Starling wrote:
> What about using a kind of document tree representation of wikitext?
> You could have an intermediate representation which precisely
> represents all of the source wikitext, but was easy to convert to
> displayable HTML. Kind of like HTML, but
1 - 100 of 114 matches
Mail list logo
