Hello,
I understand the need for cite, thats why it is still there :) But...
- We format Cite references list every 100th request to backend,
though it takes 8.15% backend response time (thanks parser cache,
without it Cite formatting would take 815% cluster time - though
developers should
Marcus Buck schreef:
I just read the last category intersection discussion from December to
see, what's the latest state of it. While doing that, I saw, that the
last message in that thread was this post from Roan Kattouw, providing
his extension. Oddly, nobody reacted on it. After 65 posts
2009/1/31 Roan Kattouw roan.katt...@home.nl:
Marcus Buck schreef:
I just read the last category intersection discussion from December to
see, what's the latest state of it. While doing that, I saw, that the
last message in that thread was this post from Roan Kattouw, providing
his extension.
David Gerard schreef:
Win!
So what's in the way of this going live on Wikimedia?
(Commons first?
As I said before, the extension was written especially for MixesDB, and
has all kinds of features WMF wikis don't need or don't want for
performance reasons. Also, the UI is pretty crude (note
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Sat, Jan 31, 2009 at 2:03 PM, Domas Mituzas wrote:
Hello,
I understand the need for cite, thats why it is still there :) But...
(...)
What about converting these to ref tags?
Unfortunately, {{cite}} is the only template I can profile/account
A long while ago I remember looking at the parser and realizing that
the recursive template expansion and argument handling led the parser
to run all branches of #if and #switch statements before deciding
which one to include.
In other words, given {{#if: something | statements_A | statements_B
Domas Mituzas wrote:
So, a checklist what can be done ( simple to complex )
[ ] - Simplification of {{cite}}
Short of significant improvements to the parser or requireing people to
ask Domas before editing the template, I can
[ ] - Separate cache for Cite, to avoid reparsing on minor
Hi,There seems to be an issue with the extension: It seems when I saved a
draft after editing a section, the draft was considered a draft of the
corresponding section number (it was mentioned as Article#Section name in
the list of drafts). If the given section was removed, clicking on this
saved
Would storing an intermediate template improve things?
I mean, keep a template but where the inner templates are substed,
depending on the original parameters.
Robert Rohde wrote:
A long while ago I remember looking at the parser and realizing that
the recursive template expansion and
On Sat, Jan 31, 2009 at 1:28 PM, Alex mrzmanw...@gmail.com wrote:
Domas Mituzas wrote:
So, a checklist what can be done ( simple to complex )
[ ] - Simplification of {{cite}}
Short of significant improvements to the parser or requireing people to
ask Domas before editing the
Gentlemen, In wikitext I want to do ol start=6101
lia
lib
/ol
but http://www.w3.org/TR/html401/struct/lists.html says that is
deprecated. In fact I really want to just use # and have that
start at 6101. OK, I'll just hard wire them into the page 6101. a
6102. b
Chad wrote:
On Sat, Jan 31, 2009 at 1:28 PM, Alex mrzmanw...@gmail.com wrote:
Domas Mituzas wrote:
So, a checklist what can be done ( simple to complex )
[ ] - Simplification of {{cite}}
Short of significant improvements to the parser or requireing people to
ask Domas before editing the
I understand the need for cite, thats why it is still there :) But...
(...)
What about converting these to ref tags?
Unfortunately most of those are designed to format the ref's to a
proper standard that we use (Harvard/MLA standard iirc) and are
designed to easily updated when we change out
On Sat, Jan 31, 2009 at 5:37 PM, Alex mrzmanw...@gmail.com wrote:
Chad wrote:
On Sat, Jan 31, 2009 at 1:28 PM, Alex mrzmanw...@gmail.com wrote:
Domas Mituzas wrote:
So, a checklist what can be done ( simple to complex )
[ ] - Simplification of {{cite}}
Short of significant
On Sat, Jan 31, 2009 at 7:12 PM, Platonides platoni...@gmail.com wrote:
{{val}} is just a presentational template. It's trivial to create an
equivalent, fixed, parserfunction.
We do not want to create a new parser function for every
presentational template people come up with.
Aryeh Gregor wrote:
On Sat, Jan 31, 2009 at 4:23 PM, jida...@jidanni.org wrote:
Gentlemen, In wikitext I want to do ol start=6101
lia
lib
/ol
but http://www.w3.org/TR/html401/struct/lists.html says that is
deprecated.
It's been un-deprecated in HTML5, for what that's worth. I don't
Aryeh Gregor wrote:
On Sat, Jan 31, 2009 at 8:03 AM, Domas Mituzas midom.li...@gmail.com wrote:
[ ] - Implement proper scripting engine like Lua for metatemplates
(http://pecl.php.net/package/lua
- another can of worms, though yet again, can be managed via trusted
set of people, on top20
Just as an FYI, wiki.freeculture.org has mis-encoded UTF-8 for the better
part of the past four years. This is because we used the old Latin 1
schemas.
Now we don't have these problems anymore. I wrote up my notes at
http://wiki.freeculture.org/Fixing_text_encoding_corruption , but here
they
This discussion is getting side tracked.
The real complaint here is that
{{#expr:(0.7 * 1000 * 1000) mod 1000}} is giving 69 when it should give 70.
This is NOT a formatting issue, but rather it is bug in the #expr
parser function, presumably caused by some kind of round-off error.
-Robert
Aryeh Gregor wrote:
On Sat, Jan 31, 2009 at 7:12 PM, Platonides wrote:
{{val}} is just a presentational template. It's trivial to create an
equivalent, fixed, parserfunction.
We do not want to create a new parser function for every
presentational template people come up with.
I know,
On Sat, Jan 31, 2009 at 8:33 PM, Robert Rohde raro...@gmail.com wrote:
This discussion is getting side tracked.
The real complaint here is that
{{#expr:(0.7 * 1000 * 1000) mod 1000}} is giving 69 when it should give
70.
This is NOT a formatting issue, but rather it is bug in the #expr
Aryeh, this reaction of “We do not want to create a new parser
function for every presentational template people come up with” is
understandable. However, I understand that a character-counting parser
function in another form has been in the works for a long time but
hasn’t proven to be
On Sat, Jan 31, 2009 at 8:53 PM, greg_l_at_wikipedia
greg_l_at_wikipe...@comcast.net wrote:
Aryeh, this reaction of We do not want to create a new parser
function for every presentational template people come up with is
understandable. However, I understand that a character-counting parser
^_^ Wikipedia is already a horrible place to copy templates from. Unlike
Wikipedia most other MW installations don't bother turning on Tidy, and
Wikipedia abuses that /feature/ way to much.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [http://nadir-seen-fire.com]
-Nadir-Point
On Sat, Jan 31, 2009 at 10:12 PM, Daniel Friesen dan_the_...@telus.net wrote:
Someone needs to read a good WP article before they start mentioning
(X)HTML version numbers:
http://en.wikipedia.org/wiki/XHTML
Both HTML5 and XHTML2 are successors to HTML4. That's all that's
really relevant here.
On Sat, Jan 31, 2009 at 5:43 PM, Aryeh Gregor
simetrical+wikil...@gmail.com wrote:
On Sat, Jan 31, 2009 at 8:33 PM, Robert Rohde raro...@gmail.com wrote:
This discussion is getting side tracked.
The real complaint here is that
{{#expr:(0.7 * 1000 * 1000) mod 1000}} is giving 69 when it
As I understand it, there is rightfully little interest in the
developer community to write a new parser function for every single
template need to come along.
Therefore, when it comes to a template like {{val}}, which now
generates rounding errors about 5–10% of the time because of the
Hoi,
Let us please appreciate what is being said here: Wikipedia is a horrible
place to copy templates from. We pride ourselves of being open source and
the current templates make us as bad as the worst proprietary vendor. We
have what is effectively an API and it is not documented at all.
Thanks,
How is the api not documented? Between the docs on
Mediawiki.org and the fact that every parameter is
documented (with examples), I'd say its highly
documented.
-Chad
On Feb 1, 2009 12:18 AM, Gerard Meijssen gerard.meijs...@gmail.com
wrote:
Hoi,
Let us please appreciate what is being said here:
On Sat, Jan 31, 2009 at 9:16 PM, Gerard Meijssen
gerard.meijs...@gmail.com wrote:
Hoi,
Let us please appreciate what is being said here: Wikipedia is a horrible
place to copy templates from. We pride ourselves of being open source and
the current templates make us as bad as the worst
How is the api not documented? Between the docs on
Mediawiki.org and the fact that every parameter is
documented (with examples), I'd say its highly
documented.
I think he means on wiki, most people probably won't know to look for
information on how to use it at the main/official mediawiki
Then that's solely enwikis fault for having poor docs.
If developers have documented where expected (in
code and on mw.org) then they've done their part.
-Chad
On Feb 1, 2009 12:33 AM, K. Peachey p858sn...@yahoo.com.au wrote:
How is the api not documented? Between the docs on Mediawiki.org
Output a big red error when giving numbers that will encounter a
floating point error?
Perhaps also provide a # of use limited #expr equivalent that will use a
bignum library rather than normal numbers which can be used in cases
where that big red error shows up.
~Daniel Friesen (Dantman,
33 matches
Mail list logo