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-lFebruary 2012

wikitech-l@lists.wikimedia.org
  • 135 participants
  • 154 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
Report on WebFonts deployment
by Siebrand Mazeland (WMF) 08 May '12

08 May '12
Dear all,My apologies up front for the long e-mail that follows. In this e-mail youwill find a comprehensive status overview of the recent WebFonts deployment.On Monday December 12 at 18:00 UTC we deployed the extension WebFonts[1] to40 wikis in 11 Indic languages and Wikimedia Incubator -- all wikis inAssamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Nepali, Oriya,(Eastern) Punjabi, Sankrit and Telugu have WebFonts now. WebFonts was notdeployed on Malayalam and Tamil projects. The reason for this was thatcommunity members had requested us not to. We are confident that in time,the communities will request that WebFonts is enabled on their projects.WebFonts aims to resolve the issue that users see incomplete web pages,because the fonts to properly render the page is not present in the localsystem by downloading the font through the browser.One of our great challenges developing this functionality is the multitudeof scripts and the low availability of freely licensed fonts that may bemodified and redistributed.Over the past few months we have tried to build out a collection of fontsin the extension mainly for Indic languages, and we have performed manytests. We have solicited community involvement through messaging in villagepumps, e-mails on mailing lists, blog posts on personal blogs as well as onthe Wikimedia Foundation blog, at developer events, through personale-mails and through our bug tracker, and gotten some feedback, althoughunfortunately not for all the languages we would like to have gotten itfor. We will of course continue our efforts in this area. Next to thecommunity involvement, we have had a two day session with the Red HatLocalisation team in Pune, India.Since the deployment, we have been criticised for not communicating enough-- or not through the right channels, not with the right people, not intime, or too soon, or not with the right messages. I'm not really sure howto respond to that, except for uttering a general "mea culpa, mea maximaculpa". We are working really hard in continuously improving the work thatwe do, and the way that we do it. We make mistakes, we are human after all,and when we become aware of our mistakes, we will do everything in ourpower to make it better.With our team we support the mission of the Wikimedia Foundation to"imagine a world in which every single human being can freely share in thesum of all knowledge." I care about that -- a lot. We all care, and I ampretty certain that we're not ignorant, dismissive or incapable. Iacknowledge that we as the Localisation team are a relatively new entitywithin the MediaWiki development community and within the WikimediaFoundation, with a very wide scope, and that we are dealing with a lot oftechnical details on which we are simply not able to assess the finalquality; there are after all 7.500 languages in this world of over 7billion people that we theoretically all cover, some 350 of those languagesare supported in MediaWiki, and 280 within Wikimedia.I accept that we cannot keep everybody happy -- doesn't keep us fromtrying, though. I want to try and work with as many people as possible in aconstructive way. With these numbers, that's not always easy to coordinate.To channel the input on languages, we have set up "Language SupportTeams"[2]. We do not yet have a language support team for every language.Please sign up if you care about the technical facilitation of yourlanguage in the Wikimedia movement. Let's use the mediawiki-i18n mailinglist[3] to have constructive discussions about language support. Let's usethe #mediawiki-i18n IRC channel[4] on Freenode to have real-timediscussions. Let's usebugzilla.wikimedia.org to report bugs[5]. Link [5]explains the bug reporting procedure. If you already know how, reportissues quickly using this link:http://ur1.ca/6ov9a .Since the deployment, we have been made aware of about 17 issues. Some veryserious in nature, others not requiring immediate attention. Yesterday anissue with web fonts not loading in Firefox was resolved in theinfrastructure. Today around 15:30 UTC, we have deployed fixes for anadditional hand full of issues[6]: functionality disabled in IE6, IE8 onWindows XP, selection buttons not working properly in IE7 and hiding theSamyak fonts in the font selector. During our current sprint, we areworking on a framework for multi-lingual and localised user documentationas well as feature based feedback functionality for WebFonts, Narayam andTranslate. In the future we will also explore what is known as "darklaunch" by some, a kind of hidden live deployment of a feature, only usablebe for example manipulating a URL. This would allow us to deploy a featurein a live environment, without having the "full deployment" impact.Thanks for reading through this. I am looking forward to working with you!Please read on for details on all the issues that were reported on WebFontsrecently.Cheers!Siebrand MazelandProduct Manager LocalisationWikimedia Foundation======================================= Links=======================================[1]https://www.mediawiki.org/wiki/Extension:WebFonts[2]https://translatewiki.net/wiki/Language_support_team[3]https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n[4]https://translatewiki.net/wiki/Special:WebChat[5]https://www.mediawiki.org/wiki/Bugzilla[6]https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106204======================================= Open issues=======================================https://bugzilla.wikimedia.org/33004 -- Old cached pages do not have webfonts enabledPriority: HIGH--------------------------------------------------------------------------------------Wikimedia is able to serve this many pages with relative few serversbecause of very aggressive caching strategies, especially for anonymoususers. WebFonts requires the addition of JavaScript for anonymous users,which is not being done for pages that are in the squid cache at the momentWebFonts was enabled. All squid cache objects for wikis on which WebFontswas deployed need to be purged. An internal RT ticket created for theWikimedia Operations team to get anonymous squid caches purged. This maytake up to a week or longer to be resolved.https://bugzilla.wikimedia.org/33018 -- Firefox 5 on Windows XP has scripttime-outsPriority: MEDIUM--------------------------------------------------------------------------------------The Localisation team has tested this report, and was not yet able toconfirm the observation. The reason for using a non-recent version ofFirefox for the report was the alleged lower memory usage. Brion noted thatMozilla has been actively working on lowering memory usage over the lastyear, so the reporter may be better off with the current versions than theold ones.https://bugzilla.wikimedia.org/33110 -- Google Crome on Windows XP dispaysgibberishPriority: LOW--------------------------------------------------------------------------------------Observed very rarely on a page on Wikimedia Incubator, and we have not beenable to reproduce this observation, let alone reproduce it reliably. Ascreenshot is present in the bug report. Except for reporting upstream, noaction is being taken on this issue at this point in time.https://bugzilla.wikimedia.org/33054 -- Hinting issues in Lohit fontsPriority: MEDIUM--------------------------------------------------------------------------------------Confirmed in Windows XP. We can do something to the font by adding hinting,but this is a lot of work if it needs to be done manually. The stem of theLohit glyphs could do with more width and darkness. This may not bedesirable for platforms (Linux) which render it perfectly, because italready has hinting and anti-aliasing on an operating system level. Samegoes got Windows 7.https://bugzilla.wikimedia.org/33100 -- Page crashes on Webkit browserswith WebFonts enabled.Priority: MEDIUM (could be HIGH if we find many occurances)--------------------------------------------------------------------------------------A page in Nepali Wikipedia makes a tab on Mac OS X 10.7.2 with Google Cromecrash. This behaviour was also reported for Mac OS X 10.7.2 (11C74) withSafari 5.1.1 (7534.51.22, r102522) [This is a webkit nightly build] bythedj. This is most probably related to the WebFonts code, because if, as alogged in user, web fonts is disabled in preferences, the page does notcrash Chrome.Developer Derk-Jan Hartman was asked to report this bug in the WebKit.Please make us aware of any additional pages that would cause thisbehaviour in any wiki.https://bugzilla.wikimedia.org/33102 -- OSX 10.7.2/Opera 11.60 has nofallback for Latin charactersPriority: MEDIUM--------------------------------------------------------------------------------------This is a bug that needs to be reported upstream. No technical measureshave been taken so far to mitigate this issue. One of the Localisation teammembers has been in contact with a high level executive of Opera, and willcontact that person again. We're going to wait for a few days for anoutcome -- if there is no expectation of a relatively quick fix, we mightdisable WebFonts for Opera completely. Opera unfortunately does not have apublic bug tracker.https://bugzilla.wikimedia.org/33027 -- Narayam and WebFonts both loadingslows down pagePriority: MEDIUM--------------------------------------------------------------------------------------The reporter claims that the functionality is quicker ontranslatewiki.netthan it is in Wikimedia wikis. A commenter statesthat more functionalityusually means more code, means more data that needs to be transferred, andwithout changing bandwidth, that causes longer load times.This currently isn't our highest priority, but eventually we will look intothis a little deeper. We're inviting volunteers to do some of the datagathering and analysis for us. What is needed in our opinion is insight inthe data volume added by WebFonts, as well as an assessment of the codequality with regards to size optimisation. All referenced properly, ofcourse :). There are alternate EOT conversion tools that have a goodcompression ratio. Needs to be explored, but EOT is not required for modernbrowsers since they started using WOFF fonts which are compressed OpenTypefonts.https://bugzilla.wikimedia.org/33085 -- Integration of updated Lohit-TamilFontPriority: MEDIUM--------------------------------------------------------------------------------------Request to update WebFonts with a font that is updated upstream. This issomething the Localisation team checks regularly. Will probably be closedthis week, pending issues the have a higher priority.https://bugzilla.wikimedia.org/32942 -- Provide help page and bug reportlink for WebFontsPriority: HIGH--------------------------------------------------------------------------------------More recently developed tools by the Wikimedia Foundation have oftenincluded feedback mechanisms. The Localisation team plans on implementingthese for the functionality of the WebFonts, Narayam and Translateextension. Besides that, we also want to provide multi-lingual andlocalised documentation. This needs some thinking and some work to providein a structured and navigable way. We'll keep you posted. It will mostprobably involve translatable *user* documentation onMediaWiki.org andhopefully it is possible to have one feedback location per feature acrossthe multiple Wikimedia wikis -- this is something we're going to contactthe ArticleFeedback and MoodBar teams for.======================================= Closed issues=======================================https://bugzilla.wikimedia.org/33025 -- When changing to a non-default webfont, the content does not--------------------------------------------------------------------------------------This issue was a side effect of a feature to allow multiple web fonts to beused using the "lang" attribute. It was resolved inhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/105980 and has beendeployed.https://bugzilla.wikimedia.org/33034 -- Web fonts not loading in Firefox--------------------------------------------------------------------------------------Duplicate reports were 33038 and 33044. This issue originated fromhttp://www.w3.org/TR/css3-fonts/#same-origin-restriction. Almost allbrowsers except for Firefox ignore that specification. A fix was designedand deployed:https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106092,https://gerrit.wikimedia.org/r/1501. Thanks to Roan, Brion and Ryan fortheir help.https://bugzilla.wikimedia.org/32775 -- Gibberish in Internet Explorer 8 onWindows XP--------------------------------------------------------------------------------------This is an unexplained phenomenon only observed in Internet Explorer onWindows XP. It is also hard to reproduce. One of the developers was able tomake something somewhat reproducible on a clean, fully patched installationof Windows XP with Internet Explorer 8. See bug report for details.Based on these observations we think it is a bad idea to keep supportingWebFonts in Internet Explorer 8 on Windows XP and we have disabled it inhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix hasbeen deployed.https://bugzilla.wikimedia.org/33096 -- Internet Explorer 6 does not havefont fallback--------------------------------------------------------------------------------------IE6 not having font fallback causes Latin characters to display as squareswhen a web font is loaded that does not contain glyphs for the Latinscript. A screenshot is available athttp://media.crossbrowsertesting.com/users/34057/screenshots/window/z669002….Based on this observation, we think it is a bad idea to keep supportingWebFonts in Internet Explorer 6 and we have disabled it inhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix hasbeen deployed.https://bugzilla.wikimedia.org/33024 -- WebFonts menu buttons not workingin IE7--------------------------------------------------------------------------------------This was caused by the JavaScript $( '<input type="radio" />' ) . attr("name" ,"font"); not working in IE6 and IE7. Updating name attributes oncethey have been created is not possible. We think there may be moreoccurances of this in our code (one occurance in jQuery has already beenidentified: resources/jquery/jquery.validate.js:59). A fix was made inhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/106175. This fix hasbeen deployed.https://bugzilla.wikimedia.org/33040 -- Overlap in Samyak font for Hindiand Sanskrit--------------------------------------------------------------------------------------This issue occurs in Windows XP and Windows 7 (possibly also in WindowsVista) when using Google Chrome. It is not observed when using Chrome withMac OS X 10.7.2 or several Linux distributions (Debian and Fedora). SamyakDevanagari is available as a non-default web font in Hindi, Marathi, andSanskrit. Samyak Gujarati is available for Gujarati as a non-default font.This font needs to be corrected. The maintainers will be notified of theobserved issues, and mean while, the fonts will be removed from theWebFonts selection list (but can still be used using the font-familyproperty. A fix was made inhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/106179. This fix hasbeen deployed.https://bugzilla.wikimedia.org/33039 -- Overlap in Madan font for Nepali--------------------------------------------------------------------------------------This report was invalid. The reporter was not aware of the correct glyphfor the Nepali script.Comments on this bug report resulted in two odd observations (Crome crash,Opera font fallback), that have been split off into separate bug reports:https://bugzilla.wikimedia.org/33100 andhttps://bugzilla.wikimedia.org/33102.https://bugzilla.wikimedia.org/33095 -- WebFonts menu can expand off thescreen--------------------------------------------------------------------------------------If the translations for "Select font" and "Login / Register" are reallyshort, like inhttp://mr.wiktionary.org, expanding the WebFonts menu foranonymous users will display a menu that is partially off the screen. Itwas resolved inhttp://www.mediawiki.org/wiki/Special:Code/MediaWiki/106186,http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106197,http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106201,http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106202. Theserevisions also depend on a few small UI changes of both WebFonts andNarayam, and will be deployed on December 19, 2011.<no bugzilla report> -- WebFonts menu expands under the control forcustomised input method in IE6 on transliteration--------------------------------------------------------------------------------------There are issues with the z index in IE6. Because ofhttps://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172, WebFonts isno longer available in IE6, so this issue is obsolete. Observing that theHindi projects Wikipedia and Wiktionary are using an custom input methodstool, we would like to invite them to test Narayam which contains manyinput methods in a MediaWiki extension. We are very open to having theHindi input method InScript tested and add a transliteration input methodwith some community representatives, as we have done with other Indiclanguages. We hope this will eventually lead to Narayam being adopted bythe Hindi community, and the custom input method being abandoned.
13 15
0 0

02 Apr '12
Hey, I know it’s been a while since we last talked. I’m currently working on jump starting the ArchiveLinks project over on the Wikimedia Foundation side. I was wondering what the status is on your side?I understand that you've been waiting on some fixes and a feed from us. I plan on creating that feed by February 9th and will let you know when it is up.I'm tracking my progress athttp://www.mediawiki.org/wiki/User:Kevin_Brown/ArchiveLinks/status so you can keep informed.Thanks,Kevin BrownWikimedia GSoC Student 2011
2 1
0 0
Regarding GSoC 2012
by Aashish Mittal 29 Mar '12

29 Mar '12
Hello everyone,I am Aashish Mittal, a final year student from Mumbai University, India. Iaim to take part in GSoC 2012 with Mediawiki and wish to get an early startin knowing and understanding the software well.I am relatively new to the organizationg. I have been through the introsteps <http://www.mediawiki.org/wiki/How_to_become_a_MediaWiki_hacker> andthe project ideas of this year. I have started working on the code andsubmitted a patch for one of the bugs (bug33545<https://bugzilla.wikimedia.org/show_bug.cgi?id=33545>)and am looking into solving more bugs.I am going through the projects and the attached links. However, I wouldrequest some more details on the following projects:1. Integration of Mediawiki/Sakai: I have been a GSoC student with Sakai in2010, so I would like to explore the project more deeper.2. Convention extension for converting mediawiki wiki into website forconference. I have been through the links, but I would like to get a bettertechnical understanding of this project related to the implementation ofthe project. Any appropriate link or some useful guidelines would be great.Apart from the above two projects, I am interested in a couple of moreprojects (Create a way to have “books” forwikisource/wikibooks<https://bugzilla.wikimedia.org/show_bug.cgi?id=15071>andGive editors a way to sliceand dice their watchlists withgroups)<https://bugzilla.wikimedia.org/show_bug.cgi?id=5875>.I am going through the comments on their bugzilla page.Kindly provide me with some suggestions or tips which would help meunderstand the project and their implementation aspects better. Any helpregarding the same would be appreciated.Thanks in advance.Regards,Aashish-- Aashish MittalStudent at University of MumbaiGtalk: ashishmittal.mail(a)gmail.comLinkedIn:www.linkedin.com/in/aashishmittal
4 5
0 0

15 Mar '12
A Wikipedia page loads. The last thing to load is the banner. Thispushes the page content down. If you've clicked on a link near the topof the page, the banner grabs it instead.This happened last year and it was reported then (and it wasincredibly annoying then too). It also fouls up stats on bannereffectiveness, as banners are clicked on without intention to do so.Please load the page with a space for the banner to avoid this effect.- d.
15 21
0 0
Who can make Gerrit/Labsconsole accounts?
by Sumana Harihareswara 11 Mar '12

11 Mar '12
As Ryan mentioned in an email to another list a couple weeks ago:> Everyone with access to create svn accounts can also link them to Labs> accounts. Feel free to make Labs accounts. Also feel free to add users> to the bastion project, and to any other project you are a member of.> Unless the user needs/wants Labs access, don't give them bastion or> other project access by default, though.It seems to me that the list of people who can make SVN accounts isunclear to the average newbie --https://meta.wikimedia.org/wiki/System_administrators doesn't have me onit. Is there a better list?How to make a Labs account:https://wikitech.wikimedia.org/view/OpenStack#Wiki_access which I amabout to merge intohttps://labsconsole.wikimedia.org/wiki/Help:Access .-- Sumana HarihareswaraVolunteer Development CoordinatorWikimedia Foundation
12 26
0 0
Results per page:
[8]ページ先頭
©2009-2025 Movatter.jp