I've done a little weekend hacking experimenting with adding
higher-resolution output support for the Score extension -- the current PNG
images look pixelated or fuzzy when printed or viewed on high-DPI (eg
'Retina') displays.
There's two avenues I'm exploring:
* https://gerrit.wikimedia.org/r/#/c/62243/ - outputs SVG instead of PNG
In theory, SVGs will scale cleanly to any screen or print resolution; but
some older browsers (IE < 9 and Android < 3) won't display them.
Unfortunately I'm getting totally corrupted SVG output on my MacBook with
Lilypond 2.16.2. On my Ubuntu 12.04 machine with 2.14.something I get
complete-looking SVGs, but they're missing the XML namespace and so won't
render.
So far there's no PNG fallback made, which would be needed (either by
converting the SVGs or by running lilypond twice with different backends).
Also don't know if the SVGs are full-page or trimmed, since they don't
display.
* https://gerrit.wikimedia.org/r/#/c/62313/ - allows for producing
higher-resolution PNGs
This adds a $wgScoreScale setting, which can be cranked up from the 1.0
default to say 2.0 to render PNGs twice as big as normal and scale them
down in the browser.
This looks great in a PDF or on a Retina screen, but the scale-down might
not be ideal on traditional screens with some browsers.
Could be improved by outputting to multiple resolutions (1.0, 1.5, and 2.0
scale) and using 'srcset' to specify which image goes to which resolution.
(In this version, I'm storing the images' width/height in a .json file.)
Any ideas or preferences on which is the better way to go?
-- brion
+wikitech-l
I've confirmed the issue on my end; ?action=purge seems to have no effect
and the 'last modified' notification on the mobile main page looks correct
(though the content itself is out of date and not in sync with the 'last
modified' notification). What's doubly weird to me is the 'Last modified'
HTTP response headers says:
Last-Modified: Tue, 30 Apr 2013 00:17:32 GMT
Which appears to be newer than when the content I'm seeing on the main page
was updated... Anyone from ops have an idea what might be going on?
On Thu, May 2, 2013 at 10:01 PM, Yuvi Panda <yuvipanda(a)gmail.com> wrote:
>
> Encountered
https://en.wikipedia.org/wiki/Wikipedia:Village_pump_(technical)#Issue_with…
>
> Some people seem to be having problems with the mobile main page being
> cached too much. Can someone look into it?
>
>
> --
> Yuvi Panda T
> http://yuvi.in/blog
>
> _______________________________________________
> Mobile-l mailing list
> Mobile-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mobile-l
--
Arthur Richards
Software Engineer, Mobile
[[User:Awjrichards]]
IRC: awjr
+1-415-839-6885 x6687
Hi,
I'm looking for the history of extension usage in enwiki. I asked for
that in the IRC and was told that all the information can be found in
the two files: CommonSettings.php and InitialiseSettings.php.
One of my main problems is that there are so many ways extensions get
included in the CommonSettings.php…
for example:
include( $IP . '/extensions/Renameuser/Renameuser.php' );
include( "$IP/extensions/AntiBot/AntiBot.php" );
include $IP . '/extensions/AntiSpoof/AntiSpoof.php';
include "$IP/extensions/WikimediaMessages/WikimediaMessages.php";
require( "$IP/extensions/Oversight/HideRevision.php" );
require_once( "$IP/extensions/LocalisationUpdate/LocalisationUpdate.php" );
require "$IP/extensions/UserDailyContribs/UserDailyContribs.php";
(I don't think this list is complete)
The next problem is that I have to look at the InitialiseSettings.php
for a lot of extensions:
CommonSettings:
if ( $wmgUserDailyContribs ) {
require "$IP/extensions/UserDailyContribs/UserDailyContribs.php";
}
InitialiseSettings:
'wmgUserDailyContribs' => array(
'default' => true,
),
The other problem is getting all versions of these two files and
correlate them to figure out which extensions were live in enwiki.
Another idea was to look at the History of Special:Version
http://web.archive.org/web/20120126235208*/http://en.wikipedia.org/wiki/Spe…
but I don't think the history there is complete (there is a big gap in
2007).
Can anyone help me creating a list like this for enwiki:
EXTENSION_NAME; DEPLOYMENT_DATE; REMOVAL_DATE;
kind regards,
Lukas
Hi,
I am a 3rd year undergraduate student of computer science, pursuing my
B.Tech degree at RCC Institute of Information Technology. I am proficient
in Java, PHP and C#.
Among the project ideas on the GSoC 2013 ideas page, the one particular
idea that seemed really interesting to me is developing an Entity
Suggester for Wikidata. I want to work on it.
I am passionate about data mining, big data and recommendation engines,
therefore this idea naturally appeals to me a lot. I have experience with
building music and people recommendation systems, and have worked with
Myrrix and Apache Mahout. I recently designed and implemented such a
recommendation system and deployed it on a live production site, where I'm
interning at, to recommend Facebook users to each other depending upon
their interests.
The problem is, the documentation for Wikidata and the Wikibase extension
seems pretty daunting to me since I have not ever configured a mediawiki
instance or actually used it. (I am on my way to try it out following the
instructions at
http://www.mediawiki.org/wiki/Summer_of_Code_2013#Where_to_start.) I can
easily build a recommendation system and create a web-service or REST based
API through which the engine can be trained with existing data, and queried
and all. This seems to be a collaborative filtering problem (people who
bought x also bought y). It'll be easier if I could get some help about the
part where/how I need to integrate it with Wikidata. Also, some sample
datasets (csv files?) or schemas (just the column names and data types?)
would help a lot, for me to figure this out.
I have added this email as a comment on the bug report at
https://bugzilla.wikimedia.org/show_bug.cgi?id=46555#c1.
Please ask me if you have any questions. :-)
Thanks,
Nilesh
--
A quest eternal, a life so small! So don't just play the guitar, build one.
You can also email me at contact(a)nileshc.com or visit my
website<http://www.nileshc.com/>
Dear all,
I have applied for the Prototyping Inline Comments for the Google Summer of
Code.
Essentially, the project is an extension that allows any wiki user to
select text and then make an inline comment or a reply to an existing
inline comment. Imagine: a user lands in a Wikipedia article, selects one
sentence and leaves an inline comment that others can optionally read and
reply to.
Users can make useful comments regarding specific part of articles, which
will be a part of collaborative work. The key benefit is to users to
collaborate easily - because this actually allows you to point to something
and comment in direct reference to it. It's like pointing your finger to a
piece of paper and telling your friend sitting next to you, which can only
be done in person and is currently impossible over the Internet. So it's a
really powerful feature for collaborations since it makes one of the
Internet-impossibles into a possible action.
That was for the insertion of a new comment. For the replying part, it will
be a format will likely be similar to how threads are like in a forum, for
the prototype.
As I go along the project, I will be posting more technical details and
updates. From now til the end of the project, I do hope to get everyone's
feedback along the way :)
Hi,
On 05/03/2013 08:58 PM, hungers.to.nurture(a)gmail.com wrote:
> I submitted my proposal to Wikimedia yesterday via GSoC. Now in my
> dashboard of GSoC it's showing that I have withdrawn my proposal. But,*I
> didn't *do that. So, please help me.
Mentors and org admins can't withdraw proposals, only their authors.
Anyway, let's try to solve this:
"ALERT: The student has withdrawn this proposal. He/She can resubmit
this proposal by clicking the Resubmit button that is accessible to them
against the text "Withdraw proposal" on this page."
I have allowed you to edit your proposal only to see if you can
re-enable it. Please don't edit it further. You can keep editing your
wiki page.
If this doesn't work then please contact me personally. No need to
involve wikitech-l.
Thank you!
--
Quim Gil
Technical Contributor Coordinator @ Wikimedia Foundation
http://www.mediawiki.org/wiki/User:Qgil
Hi
I'm not sure I'm posting this in the right place, but I (and I expect lots of others!) can't use en.m.wikipedia.org via Opera Mini.
This is because the GO button next to the search box has disappeared.
This email and any attachments to it may contain information which is confidential, legally privileged, subject to the Official Secrets Act, or otherwise not disclosable by law, and is protected by copyright. It is intended only for the addressee named above. If you are not the intended recipient you must delete this email immediately and not use, distribute, copy, disclose or take any action in reliance on this email or its contents. If you have received this email in error please notify us by return email immediately.
Airwave Solutions Limited is a company registered in England and Wales having company number 03985643.
Registered Office: Airwave Solutions Ltd, Charter Court, 50 Windsor Road, Slough, Berkshire, SL1 2EJ.