As a result of a recent software update, a change requested by some
Wikidata users has been enabled on Meta.
Now the outdated translations, marked by the !!FUZZY!! markers in
translation units pages, are hidden from the translation pages: where
you used to see pink-coloured paragraphs, there's now the English text.
We have about 700 such translations on Meta, because some hard-working
users are migrating several pages to Translate: updating them is often
very quick, and you'll restore readers with sometimes crucial pages in
their language; just remember to remove the !!FUZZY!! tag when you're done.
You can see the pages that need updating LanguageStats for your
(CC’ing translators-l also.)
Le Fri, 22 Mar 2013 14:27:44 +0100, Guillaume Paumier
<gpaumier(a)wikimedia.org> a écrit:
> Last November, I started to clean up on the Glossary page on meta, as
> an attempt to revive it and expand it to include many technical terms,
> notably related to Wikimedia Engineering (see e-mail below).
> There were (and are) already many glossaries spread around the wikis:
> * one for MediaWiki: https://www.mediawiki.org/wiki/Manual:Glossary
> * one for Wikidata: https://www.wikidata.org/wiki/Wikidata:Glossary
> * one for Labs: https://wikitech.wikimedia.org/wiki/Help:Terminology
> * two for the English Wikipedia:
> https://en.wikipedia.org/wiki/Wikipedia:Glossary &
> * etc.
> My thinking at the time was that it would be better to include tech
> terms in meta's glossary, because fragmentation isn't a good thing for
> glossaries: The user probably doesn't want to search a term through a
> dozen glossaries (that they know of), and it would be easier if they
> could just search in one place.
> The fact is, though, that we're not going to merge all the existing
> glossaries into one anytime soon, so overlap and duplication will
> remain anyway. Also, it feels weird to have tech content on meta, and
> the glossary is getting very long (and possibly more difficult to
> maintain). Therefore, I'm now reconsidering the decision of mixing
> tech terms and general movement terms on meta.
> Below are the current solutions I'm seeing to move forward; I'd love
> to get some feedback as to what people think would be the best way to
> * Status quo: We keep the current glossaries as they are, even if they
> overlap and duplicate work. We'll manage.
> * Wikidata: If Wikidata could be used to host terms and definitions
> (in various languages), and wikis could pull this data using
> templates/Lua, it would be a sane way to reduce duplication, while
> still allowing local wikis to complement it with their own terms. For
> example, "administrator" is a generic term across Wikimedia sites
> (even MediaWiki sites), so it would go into the general glossary
> repository on Wikidata; but "DYK" could be local to the English
> Wikipedia. With proper templates, the integration between remote and
> local terms could be seamless. It seems to me, however, that this
> would require significant development work.
> * Google custom search: Waldir recently used Google Custom Search to
> created a search tool to find technical information across many pages
> and sites where information is currently fragmented:
> . We could set up a similar tool (or a floss alternative) that would
> include all glossaries. By advertising the tool prominently on
> existing glossary pages (so that users know it exists), this could
> allow us to curate more specific glossaries, while keeping them all
> searchable with one tool.
> Right now, I'm inclined to go with the "custom search" solution,
> because it looks like the easiest and fastest to implement, while
> reducing maintenance costs and remaining flexible. That said, I'd love
> to hear feedback and opinions about this before implementing anything.
Given each community/wiki develops its own speak, it’s probably better to
keep all pages. Additionally it would be valuable for the global Wikimedia
community to have a simple glossary on meta to ease learning for newcomers
and for translations. So it’s probably good to write down on meta basic
terms and link to specialized glossaries and possibly set up a custom
search as you suggest.
I created some time ago a template on meta for a glossary and applied it
to very basic terms , mainly with translation in mind. Another idea is
to use the translate extension on [[meta:Glossary]] to uniformize the
presentation accross languages and to use the translation memory (although
it don’t apply to parts of messages AFAIK). Possibly it can also filled
Extension:WikimediaMessages with some other very basic Wikimedia terms
in translations, but it would probably demands a lot of maintenance for
all languages with declensions.
Related to the Wiktionary, some of the terms have a place on the
Wiktionary (analytics, API, backlog, boldness, etc.) but certainly not
all. Given this fact and your suggestion of using Wikidata, I had the idea
of an application based on Wikidata/Omegawiki to create custom
dictionaries, which could hold many specialized lexicons (e.g. wikispeak,
internet slang, etc.). I am going to the [[Wiktionary future]] page :)
> On Tue, Nov 20, 2012 at 7:55 PM, Guillaume Paumier
> <gpaumier(a)wikimedia.org> wrote:
>> The use of jargon, acronyms and other abbreviations throughout the
>> Wikimedia movement is a major source of communication issues, and
>> barriers to comprehension and involvement.
>> The recent thread on this list about "What is Product?" is an example
>> of this, as are initialisms that have long been known to be a barrier
>> for Wikipedia newcomers.
>> A way to bridge people and communities with different vocabularies is
>> to write and maintain a glossary that explains jargon in plain English
>> terms. We've been lacking a good and up-to-date glossary for Wikimedia
>> "stuff" (Foundation, chapter, movement, technology, etc.).
>> Therefore, I've started to clean up and expand the outdated Glossary
>> on meta, but it's a lot of work, and I don't have all the answers
>> myself either. I'll continue to work on it, but I'd love to get some
>> help on this and to make it a collaborative effort.
>> If you have a few minutes to spare, please consider helping your
>> (current and future) fellow Wikimedians by writing a few definitions
>> if there are terms that you can explain in plain English. Additions of
>> new terms are much welcome as well:
>> Some caveats:
>> * As part of my work, I'm mostly interested in a glossary from a
>> technical perspective, so the list currently has a technical bias. I'm
>> hoping that by sending this message to a wider audience, people from
>> the whole movement will contribute to the glossary and balance it out.
>> * Also, I've started to clean up the glossary, but it still contains
>> dated terms and definitions from a few years ago (like the FundCom),
>> so boldly edit/remove obsolete content.
I am the developer of Der Mundo, a multilingual link sharing tool that enables users to share links to any page in any language. Its part of a larger cross-language content discovery platform.
Its pretty simple. You give it a URL, it provides a shortcut URL to share. Whenever someone follows that link, the service detects each user's language preference and if translation is needed, auto-translates the page using the best available translation engine (we use several). Try it out at www.dermundo.com
I want to complement the machine translation with an option to wikify the machine translated texts. The process would go something like this.
1) convert the source web page to markdown and strip out superfluous texts as much as possible
2) insert machine translations beneath each source text
3) users can then edit or replace the machine translations from there
In the previous incarnation of the service, we emphasized human translation first, but found that because people were linking to content that aged rapidly, few items would be translated. With this version, we turn it around so that people can intervene if they want to, for example, if an article is a long form essay that deserves close attention. For many situations, machine translation is "good enough" though.
I'd like to talk with someone who's knowledgeable about the wikimedia platform to figure out how best to do this, what the hosting requirements are, and so forth. If you're interested, drop me a line, and if you like the idea behind Der Mundo, spread the word.
Thanks for your time.
Intended to send you the mail before, though no idea, if of any (potential) interest to any of you or acquaintances (or Web-Acquaintances) - part of the information is from Wikipedia's Web-Site.
Attached some links related to the subject and some links, which might useful with planning activities (of this kind) in Africa (the list was established for another purpose - but part of the links might be of interest)
I recently came across an article on co-working in the news and, while investigating into the matter, learned about your community and its activities on your website.In this context I would like to submit a proposition and share your opinion on the following matter:What about investing in a more adventurous site - further afield, in the "outback", (or even) in an emerging country, or whatever...The project could be "limited in size" (the size of a house instead of an office building), financed by a(n) (international) group of prospective users, to reduce the cost of the investment.It could be used in a way to somehow combine a kind of "holiday feeling" with business purposes, on a commercial or non-profit basis, depending on the location and the financial means of the investors..."Extremely exotic locations" might require additional investments in solar devices (for energy), pumps (for water), filters and chemicals (to clean the water), and similar...The local communities might benefit from the availability and / or the opportunity to use and get acquainted and familiar with modern technology, working techniques and media, and, in a certain way and to a certain extent "networking" (which might, among others, for example, be realised by suspending courses at the example of "Walldorf" schools in Germany)...... or positive effects on the activities of local communities... Be assured, that I would love to take part in a project of this kind, though unfortunately, due to given circumstances, it is not possible and certainly would not mind a feedback of any kind.