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 2008

wikitech-l@lists.wikimedia.org
  • 89 participants
  • 67 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
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
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

13 Oct '09
I've been putting placeholder images on a lot of articles on en:wp.e.g. [[Image:Replace this image male.svg]], which goes to[[Wikipedia:Fromowner]], which asks people to upload an image if theyown one.I know it's inspired people to add free content images to articles inseveral cases. What I'm interested in is numbers. So what I'd need isa list of edits where one of the SVGs that redirects to[[Wikipedia:Fromowner]] is replaced with an image. (Checking which ofthose are actually free images can come next.)Is there a tolerably easy way to get this info from a dump? AnyWikipedia statistics fans who think this'd be easy?(If the placeholders do work, then it'd also be useful convincing somewikiprojects to encourage the things. Not that there's ownership ofarticles on en:wp, of *course* ...)- d.
7 11
0 0
en.wiki migrated to new search backend
by Robert Stojnic 05 Jun '09

05 Jun '09
Hi all,We now have english wikipedia fully migrated to new servers / new searchbackend. We cannot fully migrate other wikis until we resolve some hardwareissues. In the meantime, here is the overview of new features now deployedon en.wiki:1) Did you mean... - we now have search suggestions. Care has been taken toprovide suggestions that are context-sensitive, i.e. on phrases, propernames, etc..2) fuzzy and wildcard queries - a word can be made fuzzy by adding ~ to it'send, e.g. query sarah~ thompson~ will give all different spellings andsimilar names to sarah thompson. Wildcards can now be prefix and suffix,e.g. *stan will give various countries in central asia.3) prefix: - using this magic prefix, queries can be limited to pagesbeginning with certain prefix. E.g.mwsuggest prefix:Wikipedia:Village Pumpwill search all village pumps and archives for mwsuggest. This should beespecially useful for archive searching in concert with inputbox orsearchbox4) intitle: - using this magic prefix, queries can be limited to titles only5) generally improved quality of search results via usage of relatedarticles (based on co-occurrence of links), anchor text, text abstracts,proximity within articles, sections, redirects, improved stemming and suchCheers, Robert
6 7
0 0
new extension for embedded music scores
by River Tarnell 24 May '09

24 May '09
-----BEGIN PGP SIGNED MESSAGE-----Hash: SHA1hello,i have written a new extension to embed music scores in MediaWiki pages:https://secure.wikimedia.org/wikipedia/mediawiki/wiki/Extension:ABC unlike the Lilypond extension, this uses a simple input language (ABC) that ismuch easier to validate for security. ABC is mostly used to transcribe Irishtrad and other simple tunes, but it recently gained support for more advancedfeatures, e.g. multiple staves and lyrics. this is supported in the extensionusing the 'abcm2ps' tool.unlike the existing ABC extension (AbcMusic), it doesn't support openingarbitrary files as ABC input (which is a potential security issue), and hasseveral additional features:- - The original ABC can be downloaded easily- - The score can be downloaded as PDF, PostScript, MIDI or Ogg Vorbis- - A media player can be embedded in the page to play the media filei believe the ABC format is suitable for transcribing the majority of scorescurrently on Wikimedia projects. although it can't handle all of them, it isbetter than the current situation. plus, as ABC is simple, and existing ABCscores are easily available, it's easier for novice users to contribute.i would be interested to hear peoples' thoughts on enabling this extension onWikimedia.- river.-----BEGIN PGP SIGNATURE-----iD8DBQFJBwL+IXd7fCuc5vIRAqG6AJ9RxKTGjJ7ywdZoesrTJWrMPtBYrACgjgDXlIY552ilDFaVG1mLzqW1F/Y==7Tda-----END PGP SIGNATURE-----
14 24
0 0
Open Document Format
by Lars Aronsson 18 May '09

18 May '09
Can someone explain why the Wikimedia Commons accepts uploads of printable PDF documents (e.g. brochures) but not the editable source version in Open Document Format (e.g. .ODT). This seems to violate the open source principle.This should be an FAQ but, but it isn't obvious fromhttp://commons.wikimedia.org/wiki/Commons:File_types-- Lars Aronsson (lars(a)aronsson.se) Aronsson Datateknik -http://aronsson.se
11 25
0 0

29 Apr '09
-----BEGIN PGP SIGNED MESSAGE-----Hash: SHA1Special:Version displays SVN version numbers for extensions out of$wgExtensionCredits, which seems to be done with $LastChangedRevision$keywords in the extension's entry point file.This produces massively incorrect numbers in many cases, since the entrypoint file is relatively rarely changed in non-trivial extensionsconsisting of multiple files. Updates to the body, class, i18n, andother files are not reflected.If we're running on a SVN checkout of the extension, we could check thedirectory for its current revision much as we do for MediaWiki itself;this would tell us for instance if an extension's subdirectory has beenupdated separately from the core MediaWiki.But if we aren't on a SVN checkout, or if individual files have beenupdated to different versions, this may or may not tell us anything useful.Anybody have a suggestion on how to best handle this?- -- brion-----BEGIN PGP SIGNATURE-----Version: GnuPG v1.4.8 (Darwin)Comment: Using GnuPG with Mozilla -http://enigmail.mozdev.orgiEYEARECAAYFAklb6VcACgkQwRnhpk1wk44MNACg2c0ztpocjHfsb5l+KxSu8e+IwXgAoMSrjFeTPzEnMY4904bxXZv+DiYf=GNqG-----END PGP SIGNATURE-----
9 24
0 0
On Wed, 03 Dec 2008 16:48:39 +0100, Roan Kattouw <roan.kattouw(a)home.nl> wrote:>> We had a pretty lengthy discussion about this before the summer, and the> consensus seemed to be that a fulltext-based approach looked most> viable. I actually wrote an extension that does that, and promised to> release it soon; that was quite a few months ago, and I never got around> to it. I'll release it properly when I have time, which will hopefully> be before Christmas :D>> The code needs some tweaking and refactoring, though. It's pretty> tightly integrated with the article text search (both functions in one> form) and has all kinds of weird features, because the guy who paid me> to write it wanted them. It also doesn't support three-letter word> searching (which core does these days, using a prefix hack), which is> pretty bad since categories with short titles (or stopword titles) won't> be found either.>> Roan Kattouw (Catrope)>>Hey Roan, does your code use the a new table for the category search (withfulltext index) and do you have the hooks for maintaining that table? Doyou display the the results on a new search results page, or did you hackthe existing one? Basically, I'm thinking that even if your stuff isn'tready for prime time, you may have already done a lot of the heavylifting... can we get our hands on it?Thanks!Aerik--http://eventfeed.org - An Initiative Promoting Syndication of Eventshttp://www.wikidweb.com - the Wiki Directory of the Webhttp://tagthis.info - Hosted Tagging for your website!
5 7
0 0
Am 10.10.2008 um 21:22 schrieb Erik Moeller:> 2008/10/10 Derbeth <derbeth(a)wp.pl>:>> I wonder about the legal aspects. In my opinion, when you create a >> ready-to-print version,>> you have to attach the text of GFDL license to it - directly, not >> as a link. Like it is done in>>http://en.wikibooks.org/wiki/Image:LaTeX.pdf.As Erik wrote: This is already implemented (either a title of an article or a URL to some license text can be set in LocalSettings.php), but it's currently not configured.>> Secondly, current version of the tool does a plagiarism - beacause >> it does not mention>> image authors and does not provide any mean (like by making images >> clickable) to check>> these authors.>> Ouch, thanks for pointing that out. Tricky to do this automatically> since it's all wiki-text with templates, but we'll investigate a> solution here.We'd highly appreciate input from the community regarding this topic!The printed books from PediaPress contain a list of figures where the license of each image is listed, together with the URL to the image description page. As some kind of "hotfix" this solution could be implemented in the PDF export of the Collection extension, too. But this doesn't really solve the problem.We think it's more of a technical/software thing, so I cross-posted (and set Reply-To) to Wikitech-l.In our opinion, license management/handling must be a core feature of MediaWiki, because the software is explicitely developed for the collaborative distribution of free content. Licenses of the containing articles and images should not be represented via some agreed-upon convention but via structured (and machine-readable) information, available for each relevant object in the wiki.Some information that would be desired:- Full (official) name of the license(s).- Whether the full text of the license has to be included or a reference sufficient.- Reference to the full text of the license(s) (in some rigidly defined format like wikitext).- Whether attribution is required. If so: The list of required attributions.So, basically all the information that's required to check if it's possible to take some part of the MediaWiki and use it somewhere else and all the information that has to be included in that other place. This information could be made accessible via MediaWiki API, but ideally it's contained in the wikitext and/or XHTML, too.All this could be handled via microformats, even inside of templates, but the main point is that any kind of new technique has to be enforced, ideally via MediaWiki software itself: In the commons wikis there are some conventions that can be used in software by people/ companies like us (although we have to work with hacks and workarounds), but oftentimes, in wikis with smaller communities this information doesn't even exist at all.-- Johannes Beigel
5 10
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp