Hi
Another patch to try to improve the template parsing.
This patch provides the following features :
- Prevents recursive loop with templates
- Prevents too big insertions (more than n chars)
- Makes a cache for templates (include 1000 {Le} is now possible)
Cordialy
Emmanuel
--
-------------------------------------------------------------------------
UNIX n'est pas aimé des utilisateurs car avec UNIX,
un incompétent passe vraiment pour un incompétent.
-------------------------------------------------------------------------
Emmanuel Engelhart ICQ UIN : 53388731 TEL (+49)(0)6.22.15.88.03.31
Tim Starling wrote:
> Timwi wrote:
>
>> Someone just checked in a software change that will [...]
>
> I think you're jumping the gun a bit here. We're currently branched with
> experimental code in HEAD. Unless someone backports this to REL1_3,
> it'll be weeks before it goes live.
Hm, I see. Maybe we need to be clearer about when we are planning for
something to go live. You see, a few weeks ago I fixed something and it
went live the next day (of course, it is entirely possible that someone
back-ported it for me), so that's why I "jumped the gun" here.
Please do understand that I was acting in good faith - I anticipated
that the change might potentially annoy non-English contributors, so I
thought it'd be important to let them know.
Moving discussion thread back to tech list. Please reply only there.
Timwi
Tim Starling wrote:
> Modified Files:
> Tag: REL1_3
> DefaultSettings.php MessageCache.php Setup.php
> Log Message:
> allow messages to be drawn from another database, off by default
This still requires the secondary database to be on the same server as
the main database, doesn't it?
Please may I humbly ask for the <center> and the <font> tag to be
removed from the site notice, and the desired effect to be achieved with
CSS instead?
Thanks,
Timwi
I have searched through Wikipedia and Meta for the last hour or so and can't find it:
- how do you change the upload limit of 2 MB?
I assume it is in LocalSettings.php or somewhere, but I couldn't find it there either.
-- Michael Richards
PS This is for Gartnerpedia, our in-house Mediawiki installation
FYI, I have just commited a preliminary version of a GEO mode (location
management, if you will) to CVS HEAD. You will have to set
"$wgUseGeoMode = true ;" in LocalSettings for that to work.
Currently, it does not do *that* much: It uses the ISBN mechanism, but
with the GEO keyword, like "GEO 1.22.33:-4.55.66". This is converted to
a link to a "SpecialGeo" page, which currently only shows a link to the
according MapQuest page.
As a special option, I hard-coded a regular expression
search-and-replace that will work on the RamBot articles (like
"38°30'10" North, 90°38'42" West"); coordinates on these pages
will thus be linked likewise.
At the moment, it does *not* store the coordinates/article data pair in
a special database table, which will be required for "real" functions,
like "what's near this location". I might implement that later, unless
someone beats me to it (hint! :-)
Magnus
Hi Brion,
thanks for your advise. Unfortunately I do not have any access to my MySQL settings. Is there any other way to fix the problem?
Thanks for your kind advise and best regards
Michael
--- Ursprüngliche Nachricht ---
Von: brion(a)pobox.com
An: wikitech-l(a)wikimedia.org
Betreff: Re: [Wikitech-l] Problems with the search function at Rev. 1.2.6
> Wiki WIKI wrote:
> > I am using MediaWiki Rev. 1.2.6 and I am facing troubles with the search function.
> > Strings with less than 4 characters are not searchable, however I set the parameter
> > in the DefaultSettings.php.
> >
> > I have set the $wgDBminWordLen = 2 and ran rebuildtextindex.php but no change.
>
> You need to configure MySQL's fulltext index to change the default
> minimum word length; $wgDBminWordLen should match that setting. Please
> see the documentation on mysql.com.
>
> -- brion vibber (brion @ pobox.com)
>
>
_____________________________________________________
Powered by Diabetes-Kids Mail - www.diabetes-kids.de
Bei Missbrauch unseres Webmail Services schreibt bitte an abuse(a)diabetes-kids.de
Timwi wrote:
> Update of /cvsroot/wikipedia/phase3/includes
> In directory sc8-pr-cvs1.sourceforge.net:/tmp/cvs-serv2125/includes
>
> Modified Files:
> SkinPHPTal.php
> Log Message:
> Little bugfix in user CSS preview
I apologise for this mammoth patch that was almost only whitespace
changes. The real change was this (line 541):
- $this->usercss = '@import
"'.$this->makeUrl('-','action=raw
&gen=css&smaxage=0&maxage=0').');'."\n";
+ $this->usercss = '@import
"'.$this->makeUrl('-','action=raw
&gen=css&smaxage=0&maxage=0').'";'."\n";
"Delirium" wrote:
> Timwi wrote:
>
> > Delirium wrote:
> >
> >> Timwi wrote:
> >>
> >>> You should probably give us more information on how Greek month
> >>> names work. You have only told us what does *not* work. I might be
> >>> able to come up with a technical solution if you explain to me what
> >>> morphological properties of Greek need to be satisfied in the month
> >>> names.
> >>
> >>
> >> There may be cases I'm not covering, but for the one I can
> >> immediately see in the interface, the issue is that "day month" type
> >> dates use the possessive form of the month name, while month names
> >> used by themselves use a simple noun form.
> >
> > [... etc. ... 'Maios' vs. '5h Maiou']
> >
> > Ah-ha. I kind of thought so. So why don't you just do this:
> >
> > - Set the month name to "Maio"
> > - In a sentence like "{{MONTHNAME}} is nice", write "{{MONTHNAME}}s
> > estis bioutiphulos"
> > - Set the date format to "{{DAY}} {{MONTHNAME}}u {{YEAR}}"
> > http://mail.wikipedia.org/mailman/listinfo/wikitech-l
>
> Well, unfortunately one part I had left out were the accents, which
> shift when the word becomes possessive. To take the example from
> Andreas's email, the simple noun form of June is "Io?nios", whereas the
> possessive form is "Ioun?ou". So it would really need a separate
> {{MONTHNAMEPOSSESSIVE}} or something of that sort.
>
> -Mark
I think that in most of the languages the "{{CURRENTMONTHNAME}}u" solution
will solve the problem. (In Hebrew, for example, we say "Yanuar" for Jan,
but "15 beYanuar" for Jan 15 - of course, in Hebrew chcracters - and when a
date is needed, we use to write "{{CURRENTDAY}} be{{CURRENTMONTHNAME}}" and
it's all fine.)
Anyway, I have a different solution: There is another already-present month
template - {{CURRENTMONTHNAMEGEN}} - that I don't know for which purpose it
is used, but it seems to be really redundant. So, you can use
{{CURRENTMONTHNAMEGEN}} for the simple form and {{CURRENTMONTHNAME}} for
possessive, etc.
Naftali
I heard there was some complain surrounding the fundraising message.
I would like to clarify a couple of points, and make a suggestion or two.
The fundraising banner was set because there was an ongoing interview of Jimbo on Slashdot.
Given the number of visits we have each time WP is slashdotted, and given that the last time WP was on /. there were many discussions about donations and other means to get money to run the project, it appeared to be a good choice to make "donation link" temporarily much more visible.
This fundraising banner will only stay up for a couple of days.
This was not planned so we could not really discuss it in length beforehand. It was more an opportunity.
As far as I know, the message was initially set only to be on en.I understood that the message was then made active on all wikipedias, without warning.
And several languages were quite upset by this message. Several criticisms were voiced, and in particular the fact it was not translated.
Some people then started translating the message in their respective languages.
Finally, while several languages were already translated, the message was removed from the non english wikipedias, again without warning. further upsetting some people.
I was not there when that happened but a couple of people told me about it yesterday, in particular Sj who I think helped on the translations, and I saw comments on the french wikipedia as well, since a vote was started to have the banner removed.
I was also nicely explained I should have made a page to explain why the banner was on, how long it would stay on and so on. Of course, that page should have been in 50 languages all at once.
I agree with all this, but it is just not possible that one, or even two people make this all by themselves, in particular when time is short.
This is only possible if more people are automatically made aware of the issue, and can come and help.
Here are the points which were pointed at
1. the fundraising campaign was not discussed beforehand2. Non english wikipedias were not warned before the message was set3. Non english wikipedias were not warned before the message was removed4. Non english wikipedias were not explained the reasons why the message was set,so it came unexpectedly. They were not told either it would be temporary.5. The message appeared everywhere in english, and people did not know how to have it translated6. The message is not pretty (location in the page, red border, police size...)7. The message appears on every page (not enough discretion)
If we let aside the fact it was decided very quickly, so not discussed before hand, I see two major issues at stake here.
First, the message is not pretty and is �defacing� the wikipedia pages. Each time this banner is up, people complain about it.
Would it be possible that someone try to think where it would be best to place it, and to have it be visible, but not outrageously visible ?
The second issue is simple. It is just a communication issue between projects.
We discussed it with Sj yesterday, and here is a proposal.
Within one project, communication works quite well.
Mailing lists is another channel, but it only covers some of the people. Not everyone is registered to wikipedia-l or foundation-l or wikitech-l. And not everyone understands english. And unfortunately, it seems few of those understanding take the time to have the information flow.
IRC is a great information channel when speed is required, but again, not everyone is on irc.
Meta is getting slowly a rather good information channel, but only those visiting meta know the information, and again do not necessarily spread it. I doubt very much goings-on are regularly updated on most projects. The source is reliable, but structurally very slow, because people do not come everyday.
So, in the end, the ONLY way to have information be known on all projects, by everyone and very rapidly, is this little red banner. This is why we use it for server downtime warning, for elections warning, for fundraising and such.
I think another tool would be very much welcome. What I would like to see is something similar to the current �you have a message�. A little warning at the top of every page (anonymous included), indicating the editor that new global information is available. For example, when a down time is planned 48 hours in advance, do we really need a huge and highly visible message on each page for 48 hours ? Not really, we just need to be warned once, and the highly visible banner could be set just before the down actually occur.I could figure an additional link in the menu, where we could add global information, for example [[Global news]].
The information could be added one paragraph at a time on meta, and in english. It could be in a mediawiki page or a form.
Once edited, it would appear on all projects, in english by default, but will be editable easily for translation (just as a mediawiki page, and in this case, it will always be a unique mediawiki page, so users won�t have to look for the page to translate it). That way, anyone reading the message first, could translate it at once for the other readers.
Each time the meta message page is updated (each time a message is added to the meta page, or through a form), a warning of the type �you have a message� would appear to all users on all projects. They can click on it to access the global news page.
Once the page is read, the warning message would disappear, but the information still be available from the menu in the �global news� page.
Each language would be responsible from cleaning up their message page little by little, for translating it, or not translating it (depending on the local editors)I do not foresee a new message being added every day. We should be careful not to abuse of it, and really use it for relevant information, when we want information to be delivered very quickly or when we really want to ensure every one is informed.
I view it a bit like the announcement-l mailing list which was an attempt to do this, but never really worked. I think doing it directly on the website would ensure that everyone is really aware of the announcement and every one can easily participate to its translation.
Is this technically possible ? Is this suitable ? What do you think ? Do you have other ideas ?
---------------------------------
Do you Yahoo!?
Yahoo! Mail is new and improved - Check it out!