Mediawiki-i18n

mediawiki-i18n@lists.wikimedia.org

568 discussions

FW: Translatewiki newsletter - translatewiki.net turns 6 - Party time!
by Siebrand Mazeland 20 Apr '11

20 Apr '11

Forwarding the translatewiki.net newsletter for April 2011. Feel free to join the celebrations! ;) Cheers! Siebrand Subject: Translatewiki newsletter - translatewiki.net turns 6 - Party time! This is the http://translatewiki.net e-mail newsletter for April 2011. We celebrate our six year long history by having a Translation Rally. Join our latest Translation Rally now <https://translatewiki.net/wiki/Project:Rally-2011-04> ! The project's success relies on your continued involvement and enthusiasm. We are 6 years young! Translatewiki.net was started as a small addition to a test wiki of Niklas Laxström. First the project became known as Betawiki until it matured and became translatewiki.net. We are grateful that our project is hosted for free and given room to grow by netcup.de <http://netcup.de> . The platform now supports localisation for 20 free and open source projects with almost 1,000 message groups, has 2,500 translators in over 200 languages. Its users have made over 3 million edits and contributed close to 2 million translations for Free and Open Source Software products. According to the s23 statistics, translatewiki.net is one of the largest independent MediaWiki installations around. Thank you all for your all your contributions in the past years. We are counting on your continued support in the years to come! Translation Rally: Contribute 500 translations and share in 1,000 Euro In 2011 we are happy we can once more continue having Translation Rallies. This time we have an additional sponsor in Wikia <http://wikia.com> , a collaborative publishing platform that enables communities to discover, create and share content on any topic in any language, to translatewiki.net and facilitated by Stichting Open Progress <http://openprogress.org> . We are very grateful for this wonderful support! The April 2011 translatewiki.net Translation Rally <http://translatewiki.net/wiki/Project:Rally-2011-04> starts at 23 April 2011 00:00 UTC and will run until 30 April 2011 24:00 UTC. Check out the project page for more details. Let's make this the best Translation Rally ever! New product support Translatewiki.net mostly "does stuff" and as an organisation we are notoriously averse of all things administrative. We hate it. One thing we like to improve is reaching out regularly to you. We would love to inform you on a monthly basis of how our community is able to help real users of real software be more productive, more educated, and more able to get things done. If you care and have the skills to help us, please let us know. We can use your help. Things however do get done: * Support for Toolserver was added. * Support for Pywikipedia was added. * Support for Mifos was added. * Support for iHRIS was added. * StatusNet has undergone major changes and is preparing a 1.0 release. * MediaWiki is preparing a 1.17 release. * FreeCol has rudimentary support for plural forms. * Over 100 Wikia extensions for MediaWiki are supported by now. * In a few weeks we expect to offer support for Encyclopedia of Life. * Within months, we hope to offer support for Europeana. If you are a developer of a promising Free and Open Source Software product and you are looking for a great community to localise your product, please get in touch with us! Operational news In the beginning of March we moved to a brand new server made available to use by netcup.de, who has been our computing sponsor since 2007. Our current hosting package will allow us to do whatever we need to support your continued translation efforts. More detailed news can be found on our News page <http://translatewiki.net/wiki/Project:News> . Follow translatewiki on Twitter <http://twitter.com/translatewiki> for the latest news. We welcome feedback about this newsletter. Please let us know by sending a reply to this mail. We will try to accommodate your wishes. Finally, of the 3,300 receiving this mail only 2,500 people are registered as translator. You may want to finish the steps that will get you the status of translatewiki.net translator. Siebrand Mazeland Translatewiki.net staff

1 0

Internationalizing MediaWiki: namespace strings
by Neil Kandalgaonkar 01 Apr '11

01 Apr '11

Is there any way to involve TranslateWiki in translated MediaWiki: namespace strings? Sometimes things are translated via subpages, e.g. MediaWiki:Foo/fr, MediaWiki:Foo/de, etc. That works okay for static texts, but it's hard to know when or if we're missing a translation. It gets worse on Commons where licenses are defined by MediaWiki:Licenses. Ignoring the "language hacks" that were done like "enownwork", this is really a data structure that has to be internationalized, and sometimes the different translations of the data structure get out of sync.... -- Neil Kandalgaonkar ( <neilk(a)wikimedia.org>

3 5

namespaceGenderAliases translations for 1.18?
by Ashar Voultoiz 05 Mar '11

05 Mar '11

Hello, We support namespaces aliases depending on the user gender. This is perfect for the USER and USER_TALK namespaces. As of february 2011, we add aliases languages per language (ex: r82719). Since people here probably have lot of international contacts, would it be possible to start translating the USER ns in as many languages as possible for the MediaWiki 1.18 release ? :) The bug report was https://bugzilla.wikimedia.org/27691 -- Ashar Voultoiz - WP++++ http://en.wikipedia.org/wiki/User:Hashar

4 3

Fwd: Re: [Mediawiki-api] is there a way to get the English name of a language?
by Michael Dale 18 Jan '11

18 Jan '11

3 3

Fwd: [Translators-l] Dialects like "en-gb" on MediaWiki extensions
by Casey Brown 15 Dec '10

15 Dec '10

Hey Yannis, The discussion list for the localization of the MediaWiki software is actually MediaWiki-i18n, so I've forwarded your e-mail to that list. I've also included Guillaume Paumier and Neil Kandalgaonkar on this e-mail, since they're the ones who made the Upload Wizard. :-) Thanks for reporting the issues you encountered! Casey ---------- Forwarded message ---------- From: Yannis A. <yannanth(a)gmail.com> Date: Tue, Dec 14, 2010 at 7:08 PM Subject: [Translators-l] Dialects like "en-gb" on MediaWiki extensions To: translators-l(a)lists.wikimedia.org I’m not sure if this is the right place to write about this, but there’s something of the problem with the language detection (sorry, I don’t know the technical terms) module of several MediaWiki extensions and templates, such as the newly-released Wikimedia Commons Upload Wizard and... many templates! For example, when I go over to the Upload Wizard for testing and casual uploading, there's a banner at the top telling me that the language was not found and that it “defaulted back to English”. Obviously, this would not be a problem with a speaker of British English, but it could potentially be a problem in all sorts of frameworks with someone who picked a language code like “arz”—Egyptian Arabic, which would predictably default to English even though a Standard Arabic version of the tutorial is available, which the average arz speaker would definitely be more familiar with! The problem, therefore, is how MediaWiki handles dialects as separate languages, and if it’s not fixed now, it could be a much bigger problem as the usability initiative affects more and more components of the website. Could some programmer fix this? I don't have the first clue about how PHP works... (sorry for the long post, by the way) _______________________________________________ Translators-l mailing list Translators-l(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/translators-l -- Casey Brown Cbrown1023

5 4

Standardizing MediaWiki Japanese Translation/MediaWiki日本語翻訳の統一
by aokomoriuta 03 Dec '10

03 Dec '10

[en] Hi, MediaWiki Japanese users and translators! (Cc: Japanese Wikimedian) Thanks to many contribution, Japanese localization of MediaWiki and its extensions messages are almost completed now (usually 99.9%). Therefore we're getting new phase - standardize the translations such as; * translate a same English term to the same Japanese term. ** en<->ja dictionary for MediaWiki * which punctuation mark we should use e.g. "、" and "。" for punctuation * check and modifying translation errors etc. See [[Portal:Ja/Standardizing MediaWiki Translation]][1] for more detail, and leave your comment on talk page[2]. thanks. -- aokomoriuta, as a Japanese translator on translatewiki.net [ja] MediaWikiの日本語利用者、翻訳者のみなさん（Cc：ウィキメディアの日本語利用者のみなさん）大勢の方々の協力のおかげで、日本語におけるMediaWikiとその地域化は、現在ほぼ完了しておりほぼ常に最新の状態を保っています（平均して99.9%）。そこで次の段階として、以下の様な翻訳の統一を実施します。 * 同じ英単語は、同じ日本語の単語に翻訳する（訳語の統一） ** MediaWikiのための英和と和英辞書の作成 * どの約物を使うか決める（例えば、句読点は「、」と「。」） * 翻訳誤りの確認と修正詳しくは[[Portal:Ja/Standardizing MediaWiki Translation]][1]をご覧ください。トークページ[2]へのご意見等もお待ちしてます。 --translatewiki.net日本語翻訳者青子守歌 [1] http://translatewiki.net/wiki/Portal:Ja/Standardizing_MediaWiki_Translation [2] http://translatewiki.net/wiki/Portal talk:Ja/Standardizing_MediaWiki_Translation -- ======================================================== 青子守歌 aokomoriuta e-mail: aokomoriuta(a)enmps.net URL: http://bgs.jpn.ph/ blog: http://bgs.jpn.ph/blog/ twitter: http://twitter.com/aokomoriuta jawp: http://ja.wikipedia.org/wiki/User:aokomoriuta mixi: http://mixi.jp/show_friend.pl?id=19926155 ========================================================

1 0

Pseudolocalization
by Neil Kandalgaonkar 02 Oct '10

02 Oct '10

So, a designer here at the foundation just found one of their designs doesn't work so well for German, which has significant "text swell" versus English. That just reminded me of a technique I've seen used elsewhere, pseudolocalization. Basically the system has a pseudo-locale, something like "xx-pseudo", where "Some text" is automatically transformed to something like "____ §ømë †ëx† ____" The idea is that you can test for three things even before the translators get to it: - which parts of the system aren't internationalized yet (they are noticeable since they don't get this pseudolocalization) - text swell (150%-200% is a good ratio) - any transformations that don't preserve unicode Does MediaWiki or interwiki do anything like this? Would you like it if we did? -- Neil Kandalgaonkar ( ) <neilk(a)wikimedia.org>

6 10

Re: [Mediawiki-i18n] [Potlatch-dev] Internationalization
by Ævar Arnfjörð Bjarmason 31 Aug '10

31 Aug '10

On Tue, Aug 31, 2010 at 09:29, Richard Fairhurst <richard(a)systemed.net> wrote: > Ævar Arnfjörð Bjarmason wrote: >> >> On Sun, Aug 29, 2010 at 16:54, Nop<ekkehart(a)gmx.de> wrote: >>> >>> And on a more general note: Is there a concept for the >>> internationalization >>> of P2? >> >> It could use the system that Potlatch v1 does. It's relatively easy to >> add support for that. > > P2 is a slightly different kettle of fish because Flex is involved. You > can't just pull stuff in at runtime (as P1 does) without making the .mxml > files unspeakably horrible. Yeah, I haven't looked at how to do it in PL2... > This is the best alternative I've found: > http://www.gridlinked.info/amazing-i18n-solutions-for-flex-3-4/ > which I guess could be wired up to translatewiki somehow. ..but whatever it ends up using should be easy to hook into Translatewiki. It's just a matter of the messages being available somewhere for Translatewiki to pull them from, and for it to update it and submit them back to PL2. > (From my point of view, the one thing I'd like to improve over P1's > internationalisation is that the English messages should be in the source, > not in en.yml. It makes the UI much more readable and maintainable.) Yeah, we discussed this on IRC a while back. You'd like something more gettext-like, while Translatewiki is more geared around the "abstract key => translation" model. But it can do gettext-like too, it does this for Status.Net already. It just does so by deriving a key from the raw message itself. This means though that when you change the original message you won't get the old message for context in the history, and translators will see it as a brand new message instead of seeing a diff between the old and new. This is partly just due to lack of support in Translatewiki, but it's also somewhat inherent in the gettext model. GNU gettext sometimes fails to mark messages as fuzzy on upgrades and thinks they're brand new messages if you move the source around a bit. So while it might be a bit easier for English speaking developers to read gettext-y source it's also useful to keep in mind the extra work that may be created for translators. And much of the issue for developers can be easily mitigated by choosing more understandable keys in the first place, something that Potlatch 1 *didn't* do, mostly because the YAML has was a flat namespace and I had to work with existing code, so they weren't very internally consistent. The Rails Port is a lot better in this regard. Anyway, whatever PL2 ends up going for I'd be happy to help with it.

1 1

Auto Reply: Auto Reply: Re: [Potlatch-dev] Internationalization
by leo.st-jacques＠hc-sc.gc.ca 31 Aug '10

31 Aug '10

This is an auto-replied message. I am out of office right now and will return Tuesday September 7, 2010

1 0

Auto Reply: Re: [Potlatch-dev] Internationalization
by leo.st-jacques＠hc-sc.gc.ca 31 Aug '10

31 Aug '10

This is an auto-replied message. I am out of office right now and will return Tuesday September 7, 2010

1 0

← Newer
1
...
42
43
44
45
46
47
48
...
57
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

Mediawiki-i18n