Hi there again, Wikimedia translators!
It's been over a week already since my original request, and you did
absolutely amazing with providing translations of the slogan into the
missing language--thank you, I appreciate your help!
There are only five languages left that are missing translations now:
If there are people from India reading this mail, and also speakers of
Tagalog, please take a minute to translate this short sentence into
your language--and I will take care of moving the translation to Meta.
You can post the translation at
here's a small translation request for Wiki Loves Monuments'
CentralNotice campaign -- please help if you can!
---------- Forwarded message ----------
as you know, we'll be using the CentralNotice system again this year
to call people to participate in the competition.
[For those of you that don't know the technical details of
CentralNotice: we'll be geolocating our banners to visitors and users
only from the participating countries (35/36 at the moment). The
banners will be displayed on all Wikimedia projects in the language of
the user (or rather his/her browser), and will direct them to an
external Wiki Loves Monuments website for their country (hence the
geolocation) -- for example, users from Argentina will receive a
banner in Spanish (mostly), linking to the Argentinian website:
Just like last year, we need a catchy phrase to interest people in the
contest. Due to a lack of better ideas ;-) the current slogan is the
last year's: "Wiki Loves Monuments: Photograph a monument, help
Wikipedia and win!". This slogan is translated into 17 of the 33
languages used in the participating countries; we still miss the
* American English -- not sure if the US guys are going to keep the
phrase "monument"? :-)
* Belarusian (both in the normative ortography and the Taraškievica);
* Hindi (not sure if it's going to be used in India?);
There are also several other languages or dialect/variants I might
have missed (Romantsh, Canadian English, Austrian German, Swiss High
German, German-formal address, and several languages used in South
Africa and India come to my mind first), so if you find one and can
translate into it, please do so!
The slogans can be find at
and that's where the translation should appear also. And let's set
23:59:59 (UTC) as the deadline, because we need to move the
translations onto Meta in time :-))
---------- Forwarded message ----------
Thanks in advance,
Tomasz W. Kozłowski
Yes, it went live some time this morning. [after some translations that were finished later!]
On 15 Aug 2012, at 1:00, translators-l-request(a)lists.wikimedia.org wrote:
> It should be live now. (As noted on the translation page, after the
> translation has been finished, a Meta admin needs to copy it into the
> Mediawiki: namespace in order for it to appear in the banner.)
> On Tue, Aug 14, 2012 at 1:31 AM, ???????? <wiki.pedia(a)ntlworld.com> wrote:
>> I have translated the FDC nomination notice into Yiddish. (But I cannot see it anywhere)
the CentralNotice with the "last call" reminder for those Wikimedians
who are considering to volunteer on the new Funds Dissemination
Committee is going live shortly, and although it will include a link
to the translation page (and only be displayed to logged-in users),
and the linked nominations page is unfortunately English-only, it
would be great to have at least some of the larger languages available
from the start:
Note: I considered sending this out to via an all-languages
translation notification too, but was hesitant to do so because it is
a really short text and a short term matter (nominations close August
15, so many translators might find this notification on their talk
page only after it has become obsolete), and I think we need to be a
bit careful with the new system so as not to have people feel spammed
and sign off. I'd be interested in opinions though whether any and all
translations should be sent through the notification system.
Senior Operations Analyst (Movement Communications)
IRC (Freenode): HaeB
*Save on the dialog box or the "Upload updated version of file" tab? *
Save on the dialog box.
2012/8/5 Harry Burt <harryaburt(a)gmail.com>
> Hey Olli, thanks for your feedback, replies inline.
> On Sun, Aug 5, 2012 at 6:25 AM, Olli <ollinpostit(a)gmail.com> wrote:
> > 1. In begin there is box with title "First time translating SVG file this
> > way?" You can get rid of the box only by the X in upper right corner. It
> > should have big button where you could also click, since it's not very
> > friendly to need click the small X.
> Noted, sounds good.
> > 2. Coordinates won't fit in the fields.
> Yeah, Inkscape has an annoying habit of creating coordinates to 34
> decimal places (I exaggerate, but not by much). I'm not sure what the
> best thing to do is though - perhaps an elastic width box that fits
> the initial input + 2 characters.
> > 3. Underline checkbox is not in the same row with the text "Underline".
> Will look into this.
> > 4. Saving shortcut should be easier - maybe ALT+A would be enough.
> Save on the dialog box or the "Upload updated version of file" tab?
> > 5. For me , uploading translated version of the file, wont succeed, it
> > keeps loading forever.
> Intriguing, will have to run my own tests to try to replicate this.
> Thanks again,
> Harry Burt
> Google Summer of Code Participant
2012/8/5 Harry Burt <harryaburt(a)gmail.com>:
> On Sun, Aug 5, 2012 at 11:46 AM, Philippe Verdy <verdy_p(a)wanadoo.fr> wrote:
>> And then the multilingual version will be created by inserting the switch :
>> <g systemLanguage="fr">
>> (the source language is normally kept as the default fallback
>> language, the last in the switch). With this kind of layout, it will
>> be possible for a translation to add or remove tspans as necessary,
>> and to organize where line breaks will really appear, as their
>> translation may not match one for one at the <tspan> level, but only
>> at the <text> level.
> At the moment, the extension generates
> <text systemLanguage="xx">
> Both your structure and mine are not easy to convert to variable tspan
> numbers within the context of the Translate extension, which assumes 1
> to 1 parity.
>> Note also that the generated id's in the SVG for each successive
>> fallback in the list of child elements of the <switch> each time adds
>> a "fallback-" part before the new language code. This would create
>> overlong id's like:
>> The "fallback-" part should only appear in the generated ID on the
>> last child element of the switch. My opinion is that it is a bug of
>> the ID generator.
> It is, yes. Noted.
>> But even in this case, the "fallback-" part is never
>> needed (look at the correct generated ID's for the parent <text> which
>> just appends the distinct language code to the original IDs (note also
>> that this simpler methods does not warranty that the generated ID will
>> be really distinct, unless the original ID's before starting the
>> translation to not create collision elsewhere.
> The code checks for collisions. But yes, the fallback- part is totally
> unnecessary - another bug to squash.
>> Note also that the ":" character is allowed in an ID,
> Uniqueness isn't really an issue at this point, because the code does
> check for collisions. Also, using colons could be confusing because of
> their use as namespace prefixes in SVGs.
The values of ID's are NOT in any namespaces. They are defined only in
the scope of the document including them, which is the only virtual
namespace. It is even safe to rename all ID's of a XML document (but
this create problems when there are references to them as anchors from
****external**** documents, so if ID's are renamed, the document
should have its URL location changed.
Namespaces are for naming element types and attributes.
Yes you can use dashes, but here again you'll need some prefixing
rules to avoid collisions of IDs in the generated derived document. An
ID generation scheme needs a limited fomr of stability anyway to allow
SVGs to be translated in multiple steps without altering external
applications referencing the SVG with for example an external CSS
stylesheet using these IDs as selectors or anchors for the target URLs
of xml:href="URL#anchor" attributes.
[Apologies for the cross-post]
After a short delay while I sorted out a Wikimedia Labs account, I am
pleased to announce that version 2.0 of the TranslateSvg extension is
officially available for testing .
TranslateSvg enables the easy translation of virtually any (currently
93.1%, but increasing all the time) SVG image containing text, with
the result embedded into the SVG file so that graphical updates
instantly propagate to all language versions .
Available for testing are three images to give you a feel for the
interface. There's likely to be one future change - the introduction
of an extra dialog box - but it's 99% feature complete. Well, until
*you* tell me what's wrong with it :)
So what are you waiting for? Find ten minutes and get yourself to
Google Summer of Code student