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-lDecember 2013

wikitech-l@lists.wikimedia.org
  • 125 participants
  • 119 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
I know it has been annoying a couple of people other than me, so now that I've learned how to make it work I'll share the knowledge here.tl;dr: Star the repositories. No, seriously. (And yes, you need to star each extension repo separately.)(Is there a place onmw.org to put this tidbit on?)------- Forwarded message -------From: "Brian Levine" <support(a)github.com> (GitHub Staff)To: matma.rex(a)gmail.comCc:Subject: Re: Commits in mirrored repositories not showing up on my profileDate: Tue, 09 Jul 2013 06:47:19 +0200Hi BartoszIn order to link your commits to your GitHub account, you need to have some association with the repository other than authoring the commit. Usually, having push access gives you that connection. In this case, you don't have push permission, so we don't link you to the commit.The easy solution here is for you to star the repository. If you star it - along with the other repositories that are giving you this problem - we'll see that you're connected to the repository and you'll get contribution credit for those commits.CheersBrian-- Matma Rex
3 3
0 0
Are you good in swearing? WE NEED YOUHuggle 3 comes with vandalism-prediction as it is precaching the diffseven before they are enqueued including their contents. Each edit hasso called "score" which is a numerical value that if higher, the editis more likely a vandalism.If you want to help us improve this feature, it is necessary to definea "score words" list for every wiki where huggle is about to be used,for example on English wiki.Each list has following syntax:(seehttps://en.wikipedia.org/w/index.php?title=Wikipedia:Huggle/Config&diff=573…)score-words(score): list of words separated by comma, can contain newlines but commamust be presentexamplescore-words(200): these, are, some, words, which, presence, of, increases, the, score, each, word, by, 200,So, if you know english better than me, which you likely do, go aheadand improve the configuration file there, no worries, huggle's configparser is very syntax-error proof.If you have any other suggestion how to improve huggle's prediction,go ahead and tell us!
8 8
0 0

17 Jul '14
I have a log of what happens on when the commands:sudo apt-get install mediawiki2latexmediawiki2latex -uhttps://en.wikipedia.org/wiki/Adam_Ries -o AdamRies.pdfare entered on the command line of ubuntu (13.10) Better than TV...Happy to send it to anyone.Fred
6 11
0 0

09 Jun '14
Hi, in response to bug 54607 [1], we've changed the semantics of themobileformat parameter to action=parse== Summary ==Previously, it used to accept strings 'html' or 'wml', later just'html' and modify the structure of output (see below). This was problematicbecause you needed to retrieve the HTML from output in different ways,depending on whether mobileformat is specified or not. Now,mobileformat is a boolean parameter, that is if there's a 'mobileformat'parameter in request, it will be treated as "the output should bemobile-friendly", regardless of value. And the output structure willbe the same. For compatibility with older callers,mobileformat=(html|wml) will be special-cased to return the olderstructure at least for 6 month from now. These changes will startbeing rolled out to the WMF sites starting from tomorrow, TuesdayOctober 24th and this process will be complete by October 31st.== Examples ===== Non-mobile parse ===api.php?action=parse&format=xml{"parse": { "title": "...", "text": { "*": "foo" } }}api.php?action=parse&format=json<?xml version="1.0"?><api> <parse title="..." displaytitle="..."> <text xml:space="preserve">foo</text> </parse></api>=== Parse that outputs mobile HTML, old style ===api.php?action=parse&format=json&mobileformat=html{ "parse": { "title": "API", "text": "foo" }}api.php?action=parse&format=xml&mobileformat=html<?xml version="1.0"?><api> <parse title="..." text="foo" displaytitle="..."> </parse></api>=== Parse that outputs mobile HTML, new style ===api.php?action=parse&format=...&mobileformatSame as for non-mobile parses.== FAQ ==Q: I didn't use mobileformat before, does anything change for me?A: No.Q: I use mobileformat=html, will my bot/tool be broken now?A: No, you will have 6 months to switch to new style.Q: I'm only planning to use mobileformat, what should I do?A: Just use the new style.Q: How did this format discrepancy appear in the first place?A: To err is human.-----[1]https://bugzilla.wikimedia.org/show_bug.cgi?id=54607-- Best regards, Max Semenik ([[User:MaxSem]])
1 1
0 0
Currently I do:* clone a repo* setup git & hooks# patch 1:* apply my changes* commit* execute git-review# patch 2:* apply my changes* commitFAIL - the new commit it depending on previous commit - I can't pushWhat am I supposed to do in order to push multiple separate patches?GIT-IDIOT way please, no long explanations, just commands and examples. Thanks
6 11
0 0

11 May '14
Following change I189ba71de[0], the hierarchical list inSpecial:Allpages becomes a simple alphabetic pager if the total numberof pages exceeds a safety threshold. The threshold is designed toprotect wikis on which the load generated by the process of generatingthe hierarchical list would be prohibitively expensive (bug 56840[1]).I189ba71de resolved the immediate operational issue, but there is afurther question of whether we want to keep the hierarchical list atall, especially given that it cannot be enabled (in its currentimplementation, at least) on larger installations.>From my perspective, the ideal outcome of this discussion would bethat we agree that the hierarchical list is a poor fit for theMediaWiki of today, and we resolve to remove it from core.According to stats.grok.se, enwiki's Special:Allpages receivesapproximately 158 hits a day.[2] [0]:https://gerrit.wikimedia.org/r/#/c/94690/ [1]:https://bugzilla.wikimedia.org/show_bug.cgi?id=56840 [2]:http://stats.grok.se/en/latest90/Special:Allpages---Ori Livnehori(a)wikimedia.org
6 7
0 0
Results per page:

[8]ページ先頭

©2009-2025 Movatter.jp