Movatterモバイル変換

[0]ホーム
URL:

Keyboard Shortcuts

Thread View

  • j: Next unread message
  • k: Previous unread message
  • j a: Jump to all threads
  • j l: Jump to MailingList overview
List overview
Download

Wikitech-lApril 2011

wikitech-l@lists.wikimedia.org
  • 99 participants
  • 94 discussions
Start a nNew thread
Database dumps
by Byrial Jensen 17 Apr '25

17 Apr '25
Until some weeks agohttp://dumps.wikimedia.org/backup-index.html usedto show 4 dumps in progress at the same time. That meant that newdatabase dumps normally was available within about 3 weeks for alldatabases except for enwiki and maybe dewiki where the dump process dueto size took longer time.However the 4 dumps processes at one time become 3 some weeks ago. Andafter massive failures at June 4, only one dump has been in progress atthe same time. So at the current speed it will take several months tocome thru all dumps.Is it possible to speed up the process again using several dumpprocesses at the same time?Thank you,Byrial
3 2
0 0
User-Agent:
by Domas Mituzas 17 Apr '25

17 Apr '25
Hi!from now on specific per-bot/per-software/per-client User-Agent header is mandatory for contacting Wikimedia sites.Domas
19 61
0 0
EBNF grammar project status?
by Steve Bennett 01 Apr '25

01 Apr '25
What's the status of the project to create a grammar for Wikitext in EBNF?There are two pages:http://meta.wikimedia.org/wiki/Wikitext_Metasyntaxhttp://www.mediawiki.org/wiki/Markup_specNothing seems to have happened since January this year. Also the comments onthe latter page seem to indicate a lack of clear goal: is this just a funproject, is it to improve the existing parser, or is it to facilititate anew parser? It's obviously a lot of work, so it needs to be of clearbenefit.Brion requested the grammar IIRC (and there's a comment to that effect athttp://bugzilla.wikimedia.org/show_bug.cgi?id=7), so I'm wondering what became of it.Is there still a goal of replacing the parser? Or is there some alternativeplan?Steve
26 217
0 0
Missing Section Headings
by Marc Riddell 13 Sep '24

13 Sep '24
Hello,I have been a WP editor since 2006. I hope you can help me. For some reasonI no longer have Section Heading titles showing in the Articles. This istrue of all Headings including the one that carries the Article subject'sname. When there is a Table of Contents, it appears fine and, when I clickon a particular Section, it goes to that Section, but all that is there is astraight line separating the Sections. There is also no button to edit aSection. If I edit the page and remove the "== ==" markers from the SectionTitles, the Title then shows up, but not as a Section Heading. Also, I don'thave any Date separators on my Want List. This started 2 days ago. Anythoughts?Thanks,Marc Riddell[[User:Michael David]]
10 11
0 0
MediaWiki to Latex Converter
by Hugo Vincent 18 Jun '12

18 Jun '12
Hi everyone,I recently set up a MediaWiki (http://server.bluewatersys.com/w90n740/) and I need to extra the content from it and convert it into LaTeX syntax for printed documentation. I have googled for a suitable OSS solution but nothing was apparent.I would prefer a script written in Python, but any recommendations would be very welcome.Do you know of anything suitable?Kind Regards,Hugo Vincent,Bluewater Systems.
6 13
0 0
About to commit improved DB2 database support
by Leons Petrazickis 21 Dec '11

21 Dec '11
I've been informally mentoring André, Tiago, Diego, and César. Theyare four students at Minho University who are currently working on aproject to improve DB2 database support in MediaWiki.So far, they've:- Fixed several outstanding issues with DB2 support involvingcharacter encoding, Windows vs Linux, etc- Added DB2 support to the new MediaWiki 1.17 Installer and Updater- Put in the appropriate Updater sql patches to reflect databaseschema changes since 1.14MediaWiki already had some DB2 support, but it's been broken since1.15 and never complete. As a result of their work, it's now possibleto successfully install MediaWiki on DB2 out of the box and to use thecore wiki features.I'll shortly commit their first patch using my SVN account (leonsp).I've taken some care to look over the code and make sure it abides bythe MediaWiki code guidelines.Regards,Leons Petrazickishttp://lpetr.org/blog/
7 9
0 0

11 May '11
I've modified Mediawiki:Common.js to include the following:document.getElementById("p1").innerHTML="New text!";I then created a page called testPage and inserted:<p id="p1">Hello World!</p>I'm expecting the text to change upon load but nothing is happening. Prior to the <p> tag addition I had an alert that was working as expected so at least I know Common.js is working.What is the best practice for adding custom javascript code in Mediawiki? While we're at it is there a real good tutorial on including AJAX calls w/o needing an extension anywhere?Thanks - Tod
5 16
0 0
MediaWiki Supported Browser List
by Trevor Parscal 11 May '11

11 May '11
After the question came up a few times, Ryan Kaldari and I decided todocument the official list of supported browsers and the information andlogic that surrounds this topic.http://www.mediawiki.org/wiki/Supported_browsers- Trevor
11 16
0 0

07 May '11
MediaWiki is currently developed in two branches, with everything goingto trunk, and a slower number of revisions getting also copied to thestable branch.That's also the way we want to continue working, having a trunk and astable branch.Currently we store the release notes in a file called RELEASE-NOTES inthe phase3 root of each branch. This is a problem when adding a revisionfor backport, since the release notes are not suitable to be added tothe trunk RELEASE-NOTES (they would go inside HISTORY)but it needs to be added to REL1_X RELEASE-NOTES.So we end up with release notes added in a different commit, orrevisions with merge conflicts for merging. Which is inconvenient.Thus, I propose that, from the point we branch 1.18, we keep the stablebranch release notes in trunk, and add trunk release notes in adifferent file. trunk and branch RELEASE-NOTES would effectively be thesame file (a revision modifing RELEASE-NOTES and not tagged for backportwould be a bug). This simple change would give us much cleaner merges.When tagging a new branch, the trunk RELEASE-NOTES would move toHISTORY, the trunk release notes file to RELEASE-NOTES and a new onewould be created for trunk.
2 3
0 0
API Sandbox
by SALIL P A 04 May '11

04 May '11
HiI was planning to make an api sandbox for mediawiki as a part of gsoc 2011.while going through mediawiki documentation, i found that many functionsneeded POST rather than GET requests. i am planning for flickr like apisandbox<http://www.flickr.com/services/api/explore/?method=flickr.contacts.getList>formediawiki.in flickr the documentation of every method has a link to api explorer(sandbox) where user can test different values for each parameter and theresult is displayed in a div in the same page.media wiki sandbox will display available parameters that can be used for aparticular method (drop-down if the values are previously known). the usercan fill the forms with his own values. the api then will send a GET or POSTrequest (AJAX request) according to the scenario (using JQuery or some otherJS library) and display the results in a div in the same page. the pageshall also display a url for executing the same ajax request.to make the api sandbox really useful, it ideally should have automatic phpcode generation too ( i don't know if it is overambitious ). for example forlogin and logout, user can just give his userid and password and the code hewould write for php is automatically displayed.i eagerly await for suggestions--SalilIRC : _Salil_
5 8
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp