Hello Tbayer (WMF), and welcome to the Wikimedia Meta-Wiki! This website is for coordinating and discussing all Wikimedia projects. You may find it useful to read our policy page. If you are interested in doing translations, visit Meta:Babylon. You can also leave a note on Meta:Babel or Wikimedia Forum (please read the instructions at the top of the page before posting there). Happy editing!
Latest comment: 13 years ago2 comments2 people in discussion
Hi, Tbayer. Where is the translation page for this message [1] (Open Call for 2012 Wikimedia Fellowship Applicants )? "Please help translate it", but nobody gave us the guide or link where to go to translate :)))) Kubura04:25, 26 December 2011 (UTC)Reply
Hi Kubura, the idea was to add a translation right in the same thread on the same page where the message is posted (as people have done here or here, for example). Do you have an idea for a clearer wording? Perhaps "Please help by adding a translation below."?
Ich schau es mir an, vielen Dank schon mal für den Rest! Was Garfield im "Financials"-Abschnitt schreibt, wiederholt sich ja von Monat zu Monat in großen Teilen, lediglich mit sich ändernden Zahlen, so dass es sich lohnt, die Übersetzung des entsprechenden Abschnitts für September (von Giftpflanze) und Oktober zu vergleichen (siehe auch meine Anmerkungen in der translation request bzw. auf Translators-l). Leider bietet die Translation-Extension - in der Form wie sie im Moment auf Meta installiert ist - noch keine Möglichkeit, in einer solchen Situation einen Übersetzungsvorschlag zu generieren. Grüße, Tbayer (WMF)07:07, 15 January 2012 (UTC)Reply
Thanks for the notice! It was actually marked in time before the mailing list announcement and translation notifications went out, but yes, ideally it should be already be done when the blog version is published; in this case I had to take a break inbetween. Regards, Tbayer (WMF) (talk) 01:48, 27 July 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
As I was translating the June Report to Swahili which is 100% complete as of now, I came across the section on Data trends which I think needs a small correction in the first line. From previous reports I think it should be an integer citing a +ve or a -ve in the percentages. ₫ӓ₩₳Talk to Me.Email Me.01:19, 27 July 2012 (UTC)Reply
Latest comment: 11 years ago3 comments2 people in discussion
Hi,
I'm translating the highlights, and there's something that will make translation a lot more efficient: putting the data and metrics information in a translatable template. If that will be done, the part won't have to be translated manually every month to every language, and entering the numbers once will be enough.
(For those reading along, Amir and I had since talked in person about this idea; for some reasons including the fact that the composition of the Financials table changes every now and then, it seemed preferable to rely on the translation memory instead, which became available not long after that.)
Latest comment: 12 years ago5 comments2 people in discussion
Hei Tilman, sind ja nun recht viele Übersetzungen auf einen Schlag eingetroffen, deshalb vergleich doch mal hier die bereits vorhandenen Übersetzungen mit den bereits übertragenen; da fehlen nämlich noch welche, z. B. Tatarisch (tt) hatte ich noch ergänzt (von der Disk. übertragen, sah ok aus). Bei Gujarati würde ich auch auf eine fehlende 0 tippen, die 1 sieht auch genauso aus wie die 1 bei der 15 im anderen Text. Würd ich so auch nicht übertragen, wenn es keine Rückmeldung gibt, außer du findest eine 0 auf Gujarati, die du noch vorher dort einfügen kannst, z. B. in der dortigen WP. ;-) Und kann man es nicht irgendwie bei so was zukünftig technisch hinbekommen, dass man die Fallbacksprachen nicht alle noch einzeln eintragen muss, wenn der Text gleich bleibt? Viele Grüße --Geitostdiskusjon21:14, 13 August 2012 (UTC)Reply
Tatarisch hatte ich erst mal weggelassen, da sich der Übersetzer ja noch unsicher schien, aber wenn du es für brauchbar hältst, gerne. (Ich schreibe auf Englisch weiter, um es etwaigen Mitlesern einfacher zu machen, sich in die Diskussion einzuschalten.) In general I agree that a formal proofreading step by native speakers is not always necessary; most of the times it will be fine to rely on a cursory check first (using Google Translate and a quick look at the translator's edit history), and let the corresponding language community find and fix any remaining errors, wiki-like.
I think most of the other translations have been covered already, except the Chinese variants - as I said on the translation page, every Meta admin would be welcome to help with keeping the translations up to date, as I can't monitor them constantly.
I didn't quite understand the remark about fallback languages, could you rephrase it?
Lieber auf Deutsch rephrasen. ;-) Ich verstehe einfach nicht, warum man die Sprachen überhaupt eintragen muss und nicht automatisch für de-ch und de-at und de-formal die bereits existente de-Variante übernommen wird. Dann bräuchte man nur noch die Fallbacksprachen zusätzlich einzugeben, wo es auch tatsächlich einen Unterschied gäbe. Leider wird aber bei Nichtexistenz nicht de: ausgegeben, sondern en:. Das Problem gab es ja schon öfters und sollte mal gelöst werden. Die vielen verschiedenen Orte, wo das schon Thema war, hab ich grad nicht parat. Falls ich sie noch mal wiederfinde …
Bei Tatarisch wusste der Übersetzer nur nicht, wie er es eingeben muss, er hat das Translate-System noch nicht verstanden, das sieht man auch auf seiner Disk. Bei der Übersetzung war er sich schon sicher, ist ja auch Muttersprachler, hat es dann halt nur stattdessen auf die Disk. gesetzt. :-) Also um Proofreading ging's dabei ja nicht.
Gujarati hat sich geklärt, haben halt ein anderes Zahlsystem, etwas verwirrend, hab mal etwas herumgelesen und bin soeben bei de:Indische Zahlendarstellung#Indische Varianten angekommen, also gibt es das Tausender-System zusätzlich dort auch. Ähnliche parallele System gibt es auch im Norwegischen, so existiert dort die deutsche Variante "einundzwanzig" neben der englischen "twenty-one" – auch ein Unterschied zwischen Bokmål und Nynorsk. --Geitostdiskusjon23:23, 13 August 2012 (UTC)Reply
Bei Tatarisch (tt) müsste man wohl denselben Text auch noch mal unter tt-cyrl eintragen, da auch dort Fallback nicht funzen wird und dann en: zu lesen ist. Wär natürlich gut, hätte er es direkt auch in latein. Schrift für tt-latn angegeben. Noch mal nachhaken? --Geitostdiskusjon23:33, 13 August 2012 (UTC)Reply
Forgot to say: looks like you didn't, so I did so myself; remember to enable the languages you add translations for. Cheers, Nemo15:52, 14 August 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
Hi, sorry to bother you, but I was wondering, has anyone ever pointed out to WMF staff that such documents should be uploaded on Commons so that local communities can access them more easily, comment or just be aware that they exist? I am pretty sure this is part of someone's job. --Elitre (talk) 09:12, 14 August 2012 (UTC)Reply
I see your point. As far as I am aware, the Annual Plan had indeed only been uploaded to the WMF wiki without a license statement in previous years. This time (after getting a request to reuse two charts from the plan, which I extracted and uploaded to Commons; they were used in this Signpost article) I asked Sue if we could release it under CC-BY-SA and she said it was OK, so I did so, meaning that everyone is now free to upload a copy to Commons. As this would just take a minute or so, I guess who does this is not a major concern in terms of workload. From the WMF side, uploading it officially to Commons at this point might necessitate some additional thought on whether this could create confusion over which version is the authoritative one, and which one to maintain in the (hopefully unlikely) case that there might be errata or such. I think releasing it under a free license was the most important step here, but I'll keep the Commons upload in mind for the rollout of the next plan. Regards, Tbayer (WMF) (talk) 15:21, 14 August 2012 (UTC)Reply
Latest comment: 12 years ago1 comment1 person in discussion
Hi, Thanks for publish the Notice in Urdu. Now I have one question about Urdu Font used in WikiMedia Notices. Why such notices arnt published in original and widely used Urdu Font (Jameel Noori Nastaleeq)?? --Muhammad Shuaib (talk) 19:44, 14 August 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
Hello, could you please stop sending notifications like this, without any link to a page where to give feedback, ask any question or understand the feature better? This is a minimum requirement also in Global message delivery/Spam, which obviously applies here as well. We're getting lots of clueless and confused translators, see for instance questions on TR talk (some of them asked first on their own talk page, waiting for an answer for months). --Nemo11:38, 20 August 2012 (UTC)Reply
"without any link to a page ..." - it appears that you overlooked this link in the message. A link about the notifications feature in general seems a good idea, but I believe the natural place for this is in the autogenerated part ("You are receiving this notification because you signed up as a translator to Italian on Meta"). Let me know if you need help in finding the people who installed the system here on Meta, I'm sure they can tell you location where one can change that system message to include such a link. I'll manually link Special:TranslatorSignup in the next notifications I send out. This new system is obviously still buggy in other ways, e.g. in your example "A new page" should have linked back to Meta instead of the Italian Wikiquote, but I can't prevent that when sending the notification.
With global message delivery, I too favor a personal signature (and have consistently advised others to use one). However, for the translation notification system, the generic signature -"Meta translation administrators, 13:04, 20 ago 2012 (CEST)" in your example - is a hard-coded design decision which cannot be overriden at the moment; you may want to file a bug for that.
"We're getting lots of clueless and confused translators, see for instance questions on TR talk" - it is not clear to me which questions on Talk:Translation requests you are referring to.
I did not 100% of the German translation, but please have somebody else finish it. I will not sign or accept things I am not sure about. I'll do the meta glossary asap to have exact translations for MWF own names. Please care about German special characters like ÄÖÜäöüß, sometimes the HTML replacements have been used. --Hans Haase (talk) 12:04, 21 August 2012 (UTC)Reply
Vielen Dank! HTML entities are fine to use (they display properly both here on the wiki and in Qualtrics). A dictionary for consistent translations of Wikimedia-specific terms would be very valuable and I believe there may have been various efforts in that direction already (I myself compiled a very small topic-specific one here a while ago), although the "translation memory" feature of the Translate extension might also serve that need, it is supposed to be activated soon here on Meta. Regards, Tbayer (WMF) (talk) 12:39, 21 August 2012 (UTC)Reply
One more reason for WMF to stop using "Global South": the translator hired (?) by WMF to produce the initial Chinese translation has decided to translate "Global South" as "the southern hemisphere". Deryck C.12:51, 27 August 2012 (UTC)Reply
Latest comment: 12 years ago2 comments2 people in discussion
Hello, TBayer,
I've already done the translation you requested via email. I'm a bit confused, however, as to why it came from Wikimedia. As far as I can remember, I've only joined the Babel and Wikipedia Translate us projects, but I may be wrong. Could you please explain to me how this hapenned? Either here or on my Wikipedia User page (http://en.wikipedia.org/wiki/User:Cocolacoste). Thank you.
Regards,
PS, I am not complaining, quite the contrary: glad to have been of service. But I'm curious.
--Cocolacoste 09:04, 14 October 2012 (UTC)Reply
Thanks for the translation! To my knowledge, the system only notifies those translators who have signed up at Special:TranslatorSignup. If you are sure that you have never been on that page, then it should probably be investigated why you received this notification. As said in the notification message that was just sent out, Talk:Translation requests is a good page to ask such questions - I don't mind replying here, but on that page, other knowledgeable people might be able to chip in. Regards, Tbayer (WMF) (talk) 14:14, 14 October 2012 (UTC)Reply
Thanks for replying and apologies all around: after a bit of a research, I found out I DID sign up to at Special:TranslatorSignup, only that I didn't realise it was WikiMedia – I'm a newbie, slowly getting a handle on all this (sighs). On a side note, sorry for my previous message coming across as ambiguous. By "here" I meant my talk page on Wikimedia, not your own talk page.
Regards,
--Cocolacoste 00:43, 15 October 2012 (UTC)
Latest comment: 12 years ago2 comments2 people in discussion
In your movement communications role I thought you might want to be aware of this if you're not already: lists.wikimedia.org/pipermail/wikimedia-l/2012-October/122323.html
Latest comment: 12 years ago2 comments2 people in discussion
Hi, could you please change the text of this CentralNotice from in Englisch to auf Englisch? It is a better language. Regards, --IW18:24, 16 October 2012 (UTC)Reply
Latest comment: 12 years ago1 comment1 person in discussion
Hi Tbayer, in the future I for one would appreciate getting more advance notice of things like Sue's proposals at User:Sue Gardner/Narrowing focus. I found out about this roughly two days before she planned to "wrap up" the subject, and I announced the discussion to wikimedia-l and research-l. I think it would have been bad if a lot of the discussion that's currently happening there hadn't happened because people didn't learn about Sue's proposals until after October 14, and I get the impression that some WMF staff also weren't aware of these proposals. Would you please see to it that at least wikimedia-l is informed of Meta postings like this one, at least a week before they're set to close? It also might help to inform the Signpost and post to Goings-on. Thanks. --Pine✉18:16, 17 October 2012 (UTC)Reply
Latest comment: 12 years ago1 comment1 person in discussion
Hello Tilman, do you think it's appropriate to link to Facebook or Twitter pages in a sitenotice like this? I'd say absolutely not, or maybe if the account is controlled by a chapter or other affiliate (but nothing is said about that channel on Microblogging handles). --Nemo11:09, 10 November 2012 (UTC)Reply
Latest comment: 12 years ago1 comment1 person in discussion
Hi Tim, will gladly finish the translating work these days and will try to do it every month. I guess this is the best way to become more popularised in Bulgaria as an organisation or community. I have just during the past 5 months had to write on three occasions to newspapers clarifying the terms Wikimedia, Wikipedia, etc.. Do you have channels to reach specifically the Bulgarian community or how do you target the different countries?— The preceding unsigned comment was added by Dimi z (talk)
Thanks!
Currently, the translated versions of the Wikimedia Highlights are publicized as follows:
With the @wikimedia feed on Twitter/Identi.ca (example), to followers in all languages
With the Wikipedia feed on Facebook (>1.1 million Likes), one post language-targeted (i.e. displayed to those using Facebook in that language) and one post geo-targeted (i.e. displayed in the country or countries where the language is prevalent).
Posted to the village pumps of the projects in that language (example).
I'm thinking about additional channels such as mailing lists, it just needs to be scalable (for the above channels, I wrote a script to automate the process of generating the announcement message from the translated wiki page, or it would have become too time-consuming).
Latest comment: 12 years ago4 comments2 people in discussion
Hey there,I´ve received a notification to translate this page to Spanish language and when I visited the page says "this page cannot to be translated to Spanish",if there a error,please notice to me,I´ll be glad if I can be useful translating :) Carliitaeliza (talk) 01:41, 13 February 2013 (UTC)Reply
Ugh, this looks like a return of bug 42715 (I certainly didn't send this second, repeated notification myself - I wasn't near my computer when it started, and it's actually not in the log). At least the email notifications do not seem to have been sent out a second time. Thanks for pointing it out, we'll investigate. Regards, Tbayer (WMF) (talk) 15:46, 13 February 2013 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
My Dear Tbayer (WMF)! With profound grief I have to inform you that I have been BLOCKED INDEFINITELY on English Wikipedia. Nobody came forward to rescue me. Not only this some people have also blocked me for a month on Hindi wiki. I am very much frustrated now. You can see my talkpage on English & Hindi wikis. Some distructive elements are there on wiki who have some user rights. They are biting so badly that a very senior person like me can not tolerate such type of non sense. Now that is why I have stopped editing on other wikis.
Please do not mind if any thing has been written here against your policies.
Hope to hear from you. Regards,
Krantmlverma (talk) 08:17, 14 February 2013 (UTC)Reply
Latest comment: 11 years ago3 comments2 people in discussion
Hallo Tilman. I wanted to correct the stuff generated by the element <languages/>. But I did not find how to do that. Do you have any idea ? --Nnemo (talk) 18:49, 30 March 2013 (UTC)Reply
That box with the language list is generated automatically by the MediaWiki software (the Translate Extension, to be exact). I think its design pretty much hardcoded, so you could contact the development team with suggestions (or ask on the #mediawiki-i18n IRC channel on Freenode). However, there has been work going on over the last half year or so to completely redesign the user interface of the whole extension (see e.g. here) - I don't know when this new design will become available here on Meta-Wiki, but it seems worth finding out before sinking too much energy into improving the present design. If you were just asking about the text in that list (i.e. the language names and the "Other languages:"/"Autres langues :"), that should be correctable somewhere on translatewiki.net, like most software interface messages of this wiki. Regards, Tbayer (WMF) (talk) 01:51, 31 March 2013 (UTC)Reply
Thank you for these details. I want to edit the way the languages are displayed. The redesign does not seem to be about that. So I want to contribute to the code of this extension. Cheers ! --Nnemo (talk) 09:31, 31 March 2013 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
FYI, the Italian banner is all wrong again. (And I'm sick of fixing.) All my observations still apply. --Nemo20:16, 30 March 2013 (UTC)Reply
That's pretty vague as a bug report ;) My first guess is you are referring to this discussion (and that you not using "all" in the sense of "100%"). I'm not sure if you saw it, but I had been following the advice you gave back then and added message documentation clarifying that comments don't need to be in English (here and here). Let me know in case your advice no longer applies, though (the documentation seems to have caused some translators to deviate from the original and add an explicit remark about the comment language, which is well-intended but makes the already long messages even longer). I also just added that "The translation should not imply that $1.2 million is the entire amount of money ever donated ...", in case someone assumed that. Regards, Tbayer (WMF) (talk) 01:29, 31 March 2013 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
See also: Research_talk:Wikipedia_Editor_Survey_2012#How_long. I confess I am really unclear about how often we conduct surveys, what questions are asked, where the raw data ends up, where anonymized versions are published (and how regularly). Also how researchers can get their ideas into the pipeline for the next survey. It would help other wiki-researchers out there to know "in what areas WMF is going to conduct a canonical annual survey" and how they can contribute to regular surveys that cover other areas or cross-sections of the community.
We have tried to run big, hulking surveys 5 times now (!!) since 2007, with what I think is limited success -- not because each individual survey wasn't well done, but because each one only addressed a small part of the universe of possible questions to ask! Each of these surveys has been plagued by the sort of uncertainty and timeline changes natural for research groups, but which uncertainty could be smoothed out by a far-ranging wikisearch network.
An alternate idea for the future:
a 'simple survey' framework that makes it easy for anyone to propose a short survey, which would be shown to a randomized 1/10,000th of the readers or 1/100th of editors
a 'simple approval' framework that makes it easy to approve such proposals
an automatic anonymization step, that removes most identifying data from the survey and makes it suitable for admins to analyze
various tools, scripts, &c for working with that partly-anonymized data. guidelines for how to further anonymize results before broad publication.
Then let all the community and researcher groups that want to run surveys suggest their own, and even suggest how they want their 10,000th or 100th portion to be meted out. Larger surveys could advocate for getting more input if they feel they must. But I suspect almost all interesting projects would find a way to get what they need from this sort of simple-survey. Please note that "filling out surveys" is not a particularly painful process, when it is about some interesting topic or a self-evaluation. Social sites like tickle.com at one point consisted entirely of such surveys. [of course to make it more fun you should show people some immediate feedback based on their submission when they are done, and let them compare themselves to the community average once all is compiled :]
Hi SJ, as you may or may not have seen, I am giving a presentation at Wikimania this week ("Editor surveys: Taking the pulse of the community") which should be the perfect venue to discuss this kind of general questions about editor survey, you are very welcome to attend! Also, I'm still focused on wrapping up the present survey at the moment (will present some highlights of the results in Hong Kong as well). But let me jot down a few quick points regarding your thoughtful remarks:
We have tried to run big, hulking surveys - there is a case for small, quick surveys when the population size is small; e.g. my WMF colleagues in Grantmaking, Program development/Evaluation and in Engineering (Product) have gained quite some experience with them. For small groups like all participants in a particular grant process, one can reasonably aim at a high response rate. But for large populations such as our editing communities, there are statistical reasons why small sample sizes are of limited value - even with the big editor surveys, where the confidence intervals (error sizes) are small for results based on the entire sample, we quickly re-enter that zone of uncomfortable uncertainty when breaking them down to smaller sub-samples (say, Chinese-language Wikipedians, one example we did we tried out last fall).
5 times now (!!) since 2007 - I'm only aware of four large editor surveys since 2008, but I guess you included the 2011 reader survey in the five you were referring to? And why the exclamation marks?
I know the information page for the 2012 survey is a bit long to read, but I would have hoped that e.g. your unertainty about "where anonymized versions are published" is avoided by (stating that "a data set consisting of anonymized responses will be made available, which others can use to do their own analyses." (In case we change the publication venue from http://dumps.wikimedia.org/other/surveys/ to a different site like Datahub.io, I'll see to announce it there.)
shown to a randomized 1/10,000th of the readers or 1/100th of editors - CentralNotice in its current form does not allow this, but it might be an interesting project - not without privacy concerns though. But again, 1/100th might not be enough for many applications.
a 'simple approval' framework that makes it easy to approve such proposals - you are right, the lack of this is a big issue for researchers, affecting even well-designed surveys by reputable institutions. You may be interested in the Research Committee's past work on developing such a framework, although it didn't quite come to a conclusion. As long as we aim to not run surveys against community consensus (consensus, as you know, can change), there won't be a "simple" process to approve surveys with certainty, especially not multilingual ones. Instead, a lengthy phase of outreach to the community, taking into account community feedback etc., is likely to remain part of the process.
an automatic anonymization step - sounds great in theory. In practice, the anonymization procedure will need to be adjusted according to the content of each survey's questions (for an example, have a look at the process description for the last survey), and might also require legal advice (I'm currently in the process of getting the final OK from WMF legal for the anonymizaton process of the 2012 dataset). For the 2012 survey I automated several other steps that had required time-consuming manual work in 2011, but I'm not convinced that it's worth the effort in case of the actual anonymization steps.
Please note that "filling out surveys" is not a particularly painful process, when it is about some interesting topic or a self-evaluation. - For many kinds of questions, maybe yes, but there is still the concern of whether we can make this a good investment of people's time. Just one additional question can amount to days of repondents' lifetime. This is particularly relevant to the free-form questions, which editor respondents seem to love because they are not restrained to pre-defined answers, but where we have in the past failed to do this justice by evaluating them in more than the most cursory manner. I'm proud to say that for the 2012 survey, we will have in-depth analyses for two of these questions, but those required significant skill and effort.
uncertainty could be smoothed out by a far-ranging wikisearch network - I didn't quite understand the logic here, would love more explanation. The experience so far from the editor surveys is that 1. unfortunately, the reuse of the publicly released datasets is not necessarily happening automatically (I'm more optimistic about the 2012 survey, where we already have interest from academic researchers, and would love it if you could help me to get people interested in using the upcoming dataset; but it has to be said that I'm not aware of significant published analysis based on the two 2011 datasets). And 2., a large part of the delay getting the results of the current survey ready was precisely because devolving part of the workload to third parties (services/contractors) did not work out as expected, and required time-consuming fixes by myself (and Beckie). That said, I too would love to enable more involvement by community and academic researchers both on the input and output sides, I just don't regard it as a time-saver for the actual execution of the survey.
Anyway, I appreciate your thoughts a lot, and look forward to discussing some of your other ideas with you at Wikimania.
Latest comment: 11 years ago6 comments3 people in discussion
Hi Tilman. I have a question about translation requests. A while back I requested this Evaluation glossary page to be translated. The top of the page says "This page contains changes which are not marked for translation." We really need to get the ball rolling on translating this page, and I'm at a loss based on the translation instructions on what to do now. Do I have to just sit back and wait and hope someone stumbles across it...or.....what? Thanks for your help. :) SarahStierch (talk) 21:34, 27 August 2013 (UTC)Reply
Hi Sarah, the terminology and that message on top of the page are perhaps not super clear:
The page has been tagged for translation (i.e. <translate> tags have been inserted to designate the text that should be translated), but not marked for translation (which activates the translation functionality on that page, and includes it on the lists of translatable pages). To have it marked for translation, you need to approach a translation administrator. Which coincidentally you have just done ;) - I could mark the page for you right now. However, after a brief look I would also recommend to modify the tagging - to make life easier for translators, we usually try to exclude layout code from translation, like in this case the complex table structure (similar example: the tagging of the "Revenue" table here - basically, just put <translate> at the beginning of each translatable table cell, and </translate> after it).
Look, guys, the problem is in fact not in tagging itself. Imagine: smb translated the page. Will the alphabetical order be preserved? 100% no. How will anyone find anything there?
Sarah, I advise you to look at Wikidata glossary, which faced the same problem and found a solution in making groups of words without using tables. (If your glossary were a huge one, I would recommend to use subpages, but it looks like a bad idea for a small amount of content.) What do you think? -- Ата(talk)10:04, 4 September 2013 (UTC)Reply
That wasn't Sarah's question, but yes, it's another good point about that page (and an example why it's better to think about translations from the beginning when starting such a page, rather than just activating translations in retrospect).
Another workaround, if one wants to preserve the alphabetical sorting in the translated version, might be to use a sortable table - but that would require an additional click by the user on the column header to sort it in the translated language; and it would be one big table without the separation into sections by initials.
Actually, come to think about it, it might be worth considering to include the English term as the first (non-translated) column in the translations, so that the glossary also serves as a dictionary to translate the English terms into the corresponding terms in the local language (and back), before then defining the term in the local language. (I.e. "ACTIVITIES | AKTIVITÄTEN | (translated definition) | ..." instead of "AKTIVITÄTEN | (translated definition) | ..."). The Translate extension normally hides the English original corresponding to a unit of translated text.
It took me a long time to make that thing into a table, I"m not that savvy, and probably won't get around into modifying it for a while due to other things I have to do. The important factor is to get the words translated, more than the layout at this time, but, I'll just have to out put on my to do list for a later time. SarahStierch (talk) 16:01, 4 September 2013 (UTC)Reply
If there is a non-translated column with term, there will be two columns with the same word in English. ;)
For the past few months, Legoktm has built a replacement to the current message delivery system called MassMessage. MassMessage uses a proper user interface form (no more editing a /Spam subpage), works faster (it can complete a large delivery in minutes), and no longer requires being on an access list (any local administrator can use it). In addition, many tiny annoyances with the old system have been addressed. It's a real improvement! :-)
You can test out MassMessage here: testwiki:Special:MassMessage. The biggest difference you'll likely notice is that any input list must use a new {{#target:}} parser function. For example, {{#target:User talk:Jimbo Wales}} or {{#target:User talk:Jimbo Wales|test2.wikipedia.org}}. For detailed instructions, check out mw:Help:Extension:MassMessage.
Latest comment: 11 years ago9 comments3 people in discussion
Hello Tbayer, Sorry made a mistake. Is the Wikimedia Highlights, September 2013 also send in that particular language, as it appeared previous - not checked recently - that even while it was translated on meta it wasn't translated on the local projects, what really was a pity. Greetings - Romaine (talk) 16:20, 1 November 2013 (UTC)Reply
Hi Romaine, no worries about that link. Am I understanding your question correctly in that you are asking about talk page/village pump deliveries of links to the translated version (like this)? Yes, I'm routinely sending these out once a translation looks completed. I don't think there was a completed Dutch translation for the August and July issues, so it was not possible to send them out in these cases. But in general there is a slight chance that I miss the completion of a translation if it comes in a bit later (unfortunately the Translate extension doesn't offer notifications when translations reach 100% - it relies on the assumption that translators change the status of the translation to e.g. "Ready", which most don't), or that I'm too busy for a few days to send them out - I have some recently completed ones on my todo list right now. In that case, feel free to remind me, or actually just send them out yourself - I see you are already on the list of those permitted to use the Global Message Delivery bot.
Another question is whether there is interest in subscribing for the *translated* version of the Highlights to one's talk page, just as it is now possible for the English version. This was already suggested a while ago when the distribution of the Highlights via Global Message Delivery was launched, but it hasn't been set up yet. Do you think there are users on the Dutch projects who would be interested in that, and if yes, would you be able to promote this option a bit if we make it happen? Then I could prioritize that a bit.
Yes, such delivery was I talking about. Apparently there it went fine. Some time ago it took a lot of time to get the highlights translated but when I saw the posting of EdwardsBot later on it appeared it wasn't translated and felt a pity. Probably it was a situation as you describe. Good to know what caused that. You say users should change the status to ready, I don't understand how I can do that... I see no way to do that. I must say that the translation tool is improved over time but still keeps having counter intuitive and clumsy parts in the way it works.
I am active as technical ambassador but I try also to promote communication from chapters/WMF/Wikimedia towards the community and back. I think it is a good way to reach out to the community more, and I am certainly willing to promote this on nl-wiki(projects). Yes I think users on Dutch projects are interested, but with that a Dutch version would make it more easier for them to read. (Even while many Dutch people learned English in school, it remains back-holding to read.) I think especially translations in Arab, French and Spanish and possible Portuguese should help to reach out to the worldwide community as priority. In those I am not so good ;) but I can promote the highlights in the Dutch projects. It is a great idea to work on translated highlights. Romaine (talk) 21:10, 1 November 2013 (UTC)Reply
PS: I have seen the Global Delivery being used for delivering with only one run, based on the contentlanguage or default (English):
The Highlights was delivered 2 or 3 times, I removed the doubles. The switch option looks easier for usage as it only needs one run. Romaine (talk) 01:23, 2 November 2013 (UTC)Reply
Thanks for fixing it on De Kroeg. This appears to be an EdwardsBot bug - it rejected the first key for no apparent reason but still ran, and then posted twice with the same key (it's supposed to check if a message with the same key is already present). I hope - no, I'm sure - it isn't part of MZ's campaign to have the bot replaced with the Massmessage extension ;) (Which might happen soon in any case.)
I'm familiar with the switch technique that the Tech newsletter uses. But trying to publish all translations at the same time has its drawbacks - I did that for a while with the Highlights (regarding publication on WikimediaAnnounce-l), but stopped doing it because there were always some translators who found the given timespan too short, even when on the other hand most of the other translations were completed way before the deadline. In other words, it was too inflexible. The Tech newsletter is shorter and is published more often, so these concerns may be less serious in that case, but even there, the rigid publication timeline apparently makes it necessary to provide part of the text in advance for early translation, which complicates things further.
I noticed several wiki's where admins have blocked extensions that were supposed to deliver messages or did that in the past. That includes nl-wiki. I did the best I could to explain why it should not be blocked, but is still on the edge. Hostile wiki's/users should be taken into account, I hope the developers really have taken that into account for the Massmessage extension.
Hi. EdwardsBot occasionally posts twice to the same talk page. It's a hackish system that is hopefully on its way out.
MassMessage is scheduled to be deployed to all Wikimedia wikis on Thursday, November 14. I encourage everyone to test it out on the test Wikipedia as soon as possible. I believe that individual wikis can "opt out" of message delivery by blocking the account that will be used to send messages ("MediaWiki message delivery" is the name currently chosen), though Legoktm would know for sure. Obviously I think disabling message delivery would be a poor idea for any wiki, but that's a local community decision to make, as far as I'm concerned. --MZMcBride (talk) 18:45, 2 November 2013 (UTC)Reply
I don't have the patience or inclination to fully debug this issue, but this edit that inappropriately removed the </source> tag is almost certainly part of the hiccup(s) here. --MZMcBride (talk) 19:05, 2 November 2013 (UTC)Reply
Fixed, thanks (I should have taught this Norwegian exception to my own script, which pre-generates these messages, or remember it myself as I did the last two times). Say hi to the sender of these emails, and convey my apologies for shouting at him. Regards, Tbayer (WMF) (talk) 06:46, 7 November 2013 (UTC)Reply
Latest comment: 11 years ago1 comment1 person in discussion
Hi. You're being contacted as you're listed as an EdwardsBot user.
MassMessage has been deployed to all Wikimedia wikis. For help using the new tool, please check out its help page or drop a note on Meta-Wiki.
With over 400,000 edits to Wikimedia wikis, EdwardsBot has served us well; however EdwardsBot will no longer perform local or global message delivery after December 31, 2013.
Latest comment: 11 years ago3 comments2 people in discussion
Hello Tbayer, You wrote the Highlights of October. Perhaps it is an idea to add in the Highlights that Wikisource is celebrating its 10th anniversary in November 2013. Greetings - Romaine (talk) 14:57, 26 November 2013 (UTC)Reply
Latest comment: 11 years ago2 comments2 people in discussion
Hello. I would like to inform you that I have granted you editor flag at the Arabic Wikipedia, all your edits there will be automatically marked as patrolled. Best regards.--Avocato(talk) 06:40, 7 December 2013 (UTC) Edited font tags to fix formatting issue affecting the rest of this page. Regards, Tbayer (WMF) (talk) 01:29, 4 February 2019 (UTC)Reply
Latest comment: 10 years ago1 comment1 person in discussion
Hi Tbayer,
I am planning to work on the project titled "Tools for mass migration of legacy translated wiki content" this summer under Google Summer of Code. I have drafted a proposal for the same over the past few weeks. This project is going to help the translation adminstrators like you in a great way, as it would completely automate the tedious manual task of preparing a page for translation and then importing the translations into the Translate extension. You can check the proposal page for detailed information on how I plan to accomplish this.
As you would be an end user of this tool, it would be great if you could go through the proposal and provide feedback/suggestions. Your feedback would definitely help me improve the proposal as well help in creating an even better tool. You can do the same on the discussion page of the proposal or reply here, whichever is convenient for you. I look forward to hearing from you! Thank you!
P.S: I need to submit the proposal to Google by March 19, 2014.
Latest comment: 10 years ago4 comments2 people in discussion
Hi,
I'm confused myself, but pretty sure the Signpost and the monthly research newsletter are different. So, I don't think the draft monthly research newsletter should have had its contents moved. [4] I'm definitely an outsider on this but looking to contribute to the Research Newsletter and now am a bit confused. Computermacgyver (talk) 17:41, 25 March 2014 (UTC)Reply
Ok, I should have read your comment completely that the text would be ported back over. This just leaves me wondering where I should contribute my article summary at the moment. I'm going to put it on the Research Newsletter but feel free to move as you like. Computermacgyver (talk) 17:49, 25 March 2014 (UTC)Reply
Hi Computermacgyver, as noted on the Etherpad, the content should be added to the draft Signpost page. We publish (syndicate) the newsletter both in its standalone form here on Meta and the Wikimedia blog, and as monthly section in the Signpost. This arrangement is a reflection of its dual audience (community members and outside academic researchers), and goes back to 2011. Sorry about the confusion, perhaps we should add a clarifying remark to the top of the Etherpad. Regards, Tbayer (WMF) (talk) 17:53, 25 March 2014 (UTC)Reply
Thanks, Tbayer (WMF), that makes perfect sense. I just had read the etherpad yesterday and didn't look back at it---hence my confusion. All great now and I'll know for future contributions. Thanks. Computermacgyver (talk) 18:00, 25 March 2014 (UTC)Reply
Latest comment: 10 years ago4 comments2 people in discussion
This is incredible. The blog is one thing, it won't be updated often because controbutors cannot edit it.
But Meta can perfectly translate everything and the message you reverted made sense in any language, not just for translators: the page itself can be viewed without even visiting the bloc (which itself is mostly untranslated except a few pages).
This is tour revert that is pointless. Even translators may read another source language than English. As if they all lived in America or Europe and why wouldn't they read Chinese, Thai or Arabic ?
There's nothing wrong coordinating translations in MEta, but what is wrong is to assume that Meta is only used by Englush readers or is just a throwable place for building other websites. verdy_p (talk) 20:19, 11 April 2014 (UTC)Reply
Note: I see that sessions for now do not last long on Meta; just a few seconds after an edit posted here I was disconnected to correct a typo in the title. Visibly there's a problem with the OpenSSL update that now looses sessions too frequently. I constantly need to relogin, or some certificates have not been correctly deployed on all wikis and they break the SUL system. verdy_p (talk) 20:30, 11 April 2014 (UTC)Reply
This was a sngle sentence not crearing lot of work for translators and not modifying the content of the blog post. it's intent was for MEta itself whose content is dedicated to be fully multilingual, as much as possible including for its navigation. It makes no sense to have a page fully translated except a sentence at top that should be translated as well and not be written only in an unrealted language. verdy_p (talk) 20:50, 11 April 2014 (UTC)Reply
Latest comment: 10 years ago1 comment1 person in discussion
Nemo and I have independently done some formatting and rearranging on the Annual Plan talk page. If anything is confusing please feel free to contact me on my talk page where I'm most likely to see your question. Thanks, --Pine✉06:56, 14 April 2014 (UTC)Reply
PS: Can I translate somewhere the bottom line "About · Subscribe · Distributed via MassMessage (wrong page? Correct it here)" ? Romaine (talk) 12:17, 28 May 2014 (UTC)Reply
Latest comment: 10 years ago1 comment1 person in discussion
As a Google Summer of Code Intern, I have been working on the Mass Migration tools project for Wikimedia. We are now ready with a minimal working product. The tool helps translators and translation administrators import the old translations into the Translate Extension.
An instance of the same has been set up on labs. You can find some useful instructions on the main page.
Please test the tool and report bugs/suggestions using the link provided on the main page itself. You can have a look at the tracking bug to check already reported bugs.
Latest comment: 10 years ago3 comments3 people in discussion
Hi Tilman, there are some questions here, as well as here on the enwiki gender gap task force talk page, about when the results are going to be released, and specifically anything pertinent to the gender gap. It would be good to have updated figures about the percentage of women editing. Hoping you can help. Best, SlimVirgin(talk)01:13, 4 September 2014 (UTC)Reply
Latest comment: 9 years ago3 comments2 people in discussion
Re: this reversion. Can you tell me precisely why a "community engagement" didn't include listening to feedback that said that the feature should not have been implemented or that it should not be presented to anyone but editors that have specifically requested that it be activated for their individual use? The bulk of the feedback that you received seems to have precisely of that nature, but I see no sign that the WMF has acknowledged that feedback or taken it into account while planning MV's future.Kww (talk) 05:27, 19 September 2014 (UTC)Reply
Hi Kww, as I said in the linked edit summary, that list was about improvements to the feature itself ("to identify any critical issues with this new experience, based on your feedback"), not about its default activation status. There were ample possibilities to discuss the latter elsewhere, and also, the consultation specifically left open the possibility that you mentioned, in case these improvements would not happen ("If agreed upon critical issues cannot be resolved in the near term, the Wikimedia Foundation will temporarily move the feature back into opt-in beta globally").
In other words, that page was focused on the actual work to improve that software feature as much as possible, while the politics of the situation were already highlighted extensively elsewhere (including e.g this widely promoted page, where one may have noted the absence of edits or edit-wars by WMF staffers despite ample opportunity to correct omissions of important facts, one-sided arguments or distorted statements). I agree it's important to discuss relations between WMF and editors, and to voice overall opinions on the activation status of a feature, but there also has to be space where the discussion about actionable, specific UX issues is not sidetracked, so I felt justified in removing sentences like "Only the WMF refuses to listen to it'a [sic] communities in regard of this topic" from this particular consultation page.
Sorry for not having noticed your four-month delay in responding until another few months had gone by. I had assumed that you were simply ignoring us again. Your quote actually illustrates the problem: "If agreed upon critical issues cannot be resolved in the near term, the Wikimedia Foundation will temporarily move the feature back into opt-in beta globally" assumes first that WMF has the right to decide whether a particular community's complaints are worth listening to and further that WMF has the right to make software opt-out over the objections of that community. There was no need to discuss user interface improvements as some kind of condition for disabling the software: the software should have been disabled or made opt-in on the Wikipedia versions that had rejected it, and then the WMF could have discussed what would be necessary for making it opt-in, with the understanding that under no circumstances would they make it opt-in again without community approval. By refusing to deactivate the software in deference to community concerns while making polite noises about how much they cared about those same community concerns, the WMF demonstrated that they were only concerned about getting their way on the issue.Kww (talk) 03:47, 22 April 2015 (UTC)Reply
Latest comment: 10 years ago1 comment1 person in discussion
Hello Tillman
I just submitted a draft for the announcement of the beginning of Wiki Loves Africa photo contest.
Link: [5]
The launching date will be October 1st. Waiting for your feedback :)
Hi Muzammil, unfortunately your Oct 8 email got lost in Gmail's spam filter - sorry about that and thanks for alerting me to it. I just replied by email and also made some edits to the draft. Regards, Tbayer (WMF) (talk) 03:42, 14 October 2014 (UTC)Reply
Latest comment: 10 years ago3 comments2 people in discussion
Hi Tilman, could you please let us know what the results of the 2012 editor survey were in relation to women editors? I would like to update the figures we have, and the last ones we have from the Foundation (that I know of) are from 2011. I left you a note here in September, [6] and also sent you an email, but haven't heard back from you yet. Many thanks, SlimVirgin(talk)21:48, 12 January 2015 (UTC)Reply
Latest comment: 10 years ago2 comments2 people in discussion
Hello, I sent an email to the blog mailing list two days ago, but I got a message saying it was moderated. Then nothing. Who is in charge of blogs ? I have an entry to propose :) Anthere (talk) 15:20, 19 February 2015 (UTC)Reply
Replied here (TLDR: as described in the blog documentation, it's recommended to contact the blog team directly instead; I approved your email and pinged Fabrice and other from the team about it some 20 hours ago, I assume that they will get back to you soon).
Hi Muzammil, I have moved on to another department in the Foundation; Fabrice and Andrew from the current blog team (see here) will take care of it - I will notify them by email; fell free to approach them directly next time. Regards, Tbayer (WMF) (talk) 06:50, 23 February 2015 (UTC)Reply
Hi Tilman, Thank you for the update and your email.
Latest comment: 6 years ago2 comments1 person in discussion
Indeed, the ur1.ca dump was broken most of the time (I've updated the description of my item). The URLTeam crawler just went through all the possibilities, so it should start from the oldest. The search by subject is more complete and seems to confirm that the original 2013 upload is the oldest. The file seems private, you could ask the 301works collection admin (Jeff Kaplan) for a copy. He usually replies from info@archive.org.
The most reliable solution would be to ask Evan Prodromou in private for a dump of whatever he has. He's usually helpful when people help wrap up his projects. --Nemo09:21, 8 April 2018 (UTC)Reply
Well done, and sure. If you send me an URL I can download, or even a WeTransfer or whatever, I'll upload the item right away. Then I'll try to make a dump in the URLteam format so that (eventually?) it can also end up in the wayback machine or whatever system Internet Archive actively exposes to users. Nemo07:41, 6 February 2019 (UTC)Reply
Latest comment: 6 years ago1 comment1 person in discussion
Hi,
You get this message because you’ve previously participated in the Community Wishlist Survey. I just wanted to let you know that this year’s survey is now open for proposals. You can suggest technical changes until 11 November: Community Wishlist Survey 2019.
You can vote from November 16 to November 30. To keep the number of messages at a reasonable level, I won’t send out a separate reminder to you about that. /Johan (WMF)11:24, 30 October 2018 (UTC)Reply
Latest comment: 5 years ago3 comments2 people in discussion
Hello Tbayer (WMF),
The Meta-Wiki community has approved a new bot inactivity policy which states that bots that are inactive for a continued period of 14 months should be subject to review. A bot you operate, HaeBot (talk·contribs) meets the inactivity criteria. In accordance with the bot inactivity policy, if you wish to retain the bot flag for the named account, please answer to this message no later than 6 April 2019 on Meta:Requests for help from a sysop or bureaucrat. After that date if the bureaucrats have not received any reply, the bot flag for the named account will be removed.