The Wikimedia Language Engineering team is pleased to announce the
first release of the MediaWiki Language Extension Bundle. The bundle
is a collection of selected MediaWiki extensions needed by any wiki
which desires to be multilingual.
This first bundle release (2012.11) is compatible with MediaWiki 1.19,
1.20 and 1.21alpha.
Get it from https://www.mediawiki.org/wiki/MLEB
The Universal Language Selector is a must have, because it provides an
essential functionality for any user regardless on the number of
languages he/she speaks: language selection, font support for
displaying scripts badly supported by operating systems and input
methods for typing languages that don't use Latin (a-z) alphabet.
Maintaining multilingual content in a wiki is a mess without the
Translate extension, which is used by Wikimedia, KDE and
translatewiki.net, where hundreds of pieces of documentation and
interface translations are updated every day; with Localisation Update
your users will always have the latest translations freshly out of the
oven. The Clean Changes extension keeps your recent changes page
uncluttered from translation activity and other distractions.
Don't miss the chance to practice your rusty language skills and use
the Babel extension to mark the languages you speak and to find other
speakers of the same language in your wiki. And finally the cldr
extension is a database of language and country translations.
We are aiming to make new releases every month, so that you can easily
stay on the cutting edge with the constantly improving language
support. The bundle comes with clear installation and upgrade
installations. The bundle is tested against MediaWiki release
versions, so you can avoid most of the temporary breaks that would
happen if you were using the latest development versions instead.
Because this is our first release, there can be some rough edges.
Please provide us a lot of feedback so that we can improve for the
next release.
-Niklas
--
Niklas Laxström
Hi,
after a user reported a discrepancy between two versions of the autonym for
the Czech language used in different contexts in MediaWiki, I noticed it
comes from a difference between the MediaWiki core Names.php and CLDR data
(via the CLDR extension’s CldrNames). Originally, I just intended to submit
a patch to Names.php unifying those two to the CLDR version, but then I
thought the problem might exist in other languages, too.
So, I compiled a list [1][2] of 39 differences in language names between MW
core and the CLDR extension. Some of those differences are just case
changes, some of them might be errors in one of the sources, some of them
just random choices between two equally valid versions (like in the Czech
case, it’s not like one of them is generally better than the other, it’s
just that consistency would be better).
I definitely do not intend to change all those languages I do not
understand, but maybe other people could be interested in checking their
language in the list…
-- [[cs:User:Mormegil | Petr Kadlec]]
[1]
http://translatewiki.net/wiki/User:Mormegil/CLDR_language_names_differences
[2] https://gist.github.com/mormegil-cz/7240262
Dear all,
My apologies up front for the long e-mail that follows. In this e-mail you
will find a comprehensive status overview of the recent WebFonts deployment.
On Monday December 12 at 18:00 UTC we deployed the extension WebFonts[1] to
40 wikis in 11 Indic languages and Wikimedia Incubator -- all wikis in
Assamese, Bengali, Gujarati, Hindi, Kannada, Marathi, Nepali, Oriya,
(Eastern) Punjabi, Sankrit and Telugu have WebFonts now. WebFonts was not
deployed on Malayalam and Tamil projects. The reason for this was that
community members had requested us not to. We are confident that in time,
the communities will request that WebFonts is enabled on their projects.
WebFonts aims to resolve the issue that users see incomplete web pages,
because the fonts to properly render the page is not present in the local
system by downloading the font through the browser.
One of our great challenges developing this functionality is the multitude
of scripts and the low availability of freely licensed fonts that may be
modified and redistributed.
Over the past few months we have tried to build out a collection of fonts
in the extension mainly for Indic languages, and we have performed many
tests. We have solicited community involvement through messaging in village
pumps, e-mails on mailing lists, blog posts on personal blogs as well as on
the Wikimedia Foundation blog, at developer events, through personal
e-mails and through our bug tracker, and gotten some feedback, although
unfortunately not for all the languages we would like to have gotten it
for. We will of course continue our efforts in this area. Next to the
community involvement, we have had a two day session with the Red Hat
Localisation team in Pune, India.
Since the deployment, we have been criticised for not communicating enough
-- or not through the right channels, not with the right people, not in
time, or too soon, or not with the right messages. I'm not really sure how
to respond to that, except for uttering a general "mea culpa, mea maxima
culpa". We are working really hard in continuously improving the work that
we do, and the way that we do it. We make mistakes, we are human after all,
and when we become aware of our mistakes, we will do everything in our
power to make it better.
With our team we support the mission of the Wikimedia Foundation to
"imagine a world in which every single human being can freely share in the
sum of all knowledge." I care about that -- a lot. We all care, and I am
pretty certain that we're not ignorant, dismissive or incapable. I
acknowledge that we as the Localisation team are a relatively new entity
within the MediaWiki development community and within the Wikimedia
Foundation, with a very wide scope, and that we are dealing with a lot of
technical details on which we are simply not able to assess the final
quality; there are after all 7.500 languages in this world of over 7
billion people that we theoretically all cover, some 350 of those languages
are supported in MediaWiki, and 280 within Wikimedia.
I accept that we cannot keep everybody happy -- doesn't keep us from
trying, though. I want to try and work with as many people as possible in a
constructive way. With these numbers, that's not always easy to coordinate.
To channel the input on languages, we have set up "Language Support
Teams"[2]. We do not yet have a language support team for every language.
Please sign up if you care about the technical facilitation of your
language in the Wikimedia movement. Let's use the mediawiki-i18n mailing
list[3] to have constructive discussions about language support. Let's use
the #mediawiki-i18n IRC channel[4] on Freenode to have real-time
discussions. Let's use bugzilla.wikimedia.org to report bugs[5]. Link [5]
explains the bug reporting procedure. If you already know how, report
issues quickly using this link: http://ur1.ca/6ov9a .
Since the deployment, we have been made aware of about 17 issues. Some very
serious in nature, others not requiring immediate attention. Yesterday an
issue with web fonts not loading in Firefox was resolved in the
infrastructure. Today around 15:30 UTC, we have deployed fixes for an
additional hand full of issues[6]: functionality disabled in IE6, IE8 on
Windows XP, selection buttons not working properly in IE7 and hiding the
Samyak fonts in the font selector. During our current sprint, we are
working on a framework for multi-lingual and localised user documentation
as well as feature based feedback functionality for WebFonts, Narayam and
Translate. In the future we will also explore what is known as "dark
launch" by some, a kind of hidden live deployment of a feature, only usable
be for example manipulating a URL. This would allow us to deploy a feature
in a live environment, without having the "full deployment" impact.
Thanks for reading through this. I am looking forward to working with you!
Please read on for details on all the issues that were reported on WebFonts
recently.
Cheers!
Siebrand Mazeland
Product Manager Localisation
Wikimedia Foundation
=======================================
Links
=======================================
[1] https://www.mediawiki.org/wiki/Extension:WebFonts
[2] https://translatewiki.net/wiki/Language_support_team
[3] https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
[4] https://translatewiki.net/wiki/Special:WebChat
[5] https://www.mediawiki.org/wiki/Bugzilla
[6] https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106204
=======================================
Open issues
=======================================
https://bugzilla.wikimedia.org/33004 -- Old cached pages do not have web
fonts enabled
Priority: HIGH
--------------------------------------------------------------------------------------
Wikimedia is able to serve this many pages with relative few servers
because of very aggressive caching strategies, especially for anonymous
users. WebFonts requires the addition of JavaScript for anonymous users,
which is not being done for pages that are in the squid cache at the moment
WebFonts was enabled. All squid cache objects for wikis on which WebFonts
was deployed need to be purged. An internal RT ticket created for the
Wikimedia Operations team to get anonymous squid caches purged. This may
take up to a week or longer to be resolved.
https://bugzilla.wikimedia.org/33018 -- Firefox 5 on Windows XP has script
time-outs
Priority: MEDIUM
--------------------------------------------------------------------------------------
The Localisation team has tested this report, and was not yet able to
confirm the observation. The reason for using a non-recent version of
Firefox for the report was the alleged lower memory usage. Brion noted that
Mozilla has been actively working on lowering memory usage over the last
year, so the reporter may be better off with the current versions than the
old ones.
https://bugzilla.wikimedia.org/33110 -- Google Crome on Windows XP dispays
gibberish
Priority: LOW
--------------------------------------------------------------------------------------
Observed very rarely on a page on Wikimedia Incubator, and we have not been
able to reproduce this observation, let alone reproduce it reliably. A
screenshot is present in the bug report. Except for reporting upstream, no
action is being taken on this issue at this point in time.
https://bugzilla.wikimedia.org/33054 -- Hinting issues in Lohit fonts
Priority: MEDIUM
--------------------------------------------------------------------------------------
Confirmed in Windows XP. We can do something to the font by adding hinting,
but this is a lot of work if it needs to be done manually. The stem of the
Lohit glyphs could do with more width and darkness. This may not be
desirable for platforms (Linux) which render it perfectly, because it
already has hinting and anti-aliasing on an operating system level. Same
goes got Windows 7.
https://bugzilla.wikimedia.org/33100 -- Page crashes on Webkit browsers
with WebFonts enabled.
Priority: MEDIUM (could be HIGH if we find many occurances)
--------------------------------------------------------------------------------------
A page in Nepali Wikipedia makes a tab on Mac OS X 10.7.2 with Google Crome
crash. This behaviour was also reported for Mac OS X 10.7.2 (11C74) with
Safari 5.1.1 (7534.51.22, r102522) [This is a webkit nightly build] by
thedj. This is most probably related to the WebFonts code, because if, as a
logged in user, web fonts is disabled in preferences, the page does not
crash Chrome.
Developer Derk-Jan Hartman was asked to report this bug in the WebKit.
Please make us aware of any additional pages that would cause this
behaviour in any wiki.
https://bugzilla.wikimedia.org/33102 -- OSX 10.7.2/Opera 11.60 has no
fallback for Latin characters
Priority: MEDIUM
--------------------------------------------------------------------------------------
This is a bug that needs to be reported upstream. No technical measures
have been taken so far to mitigate this issue. One of the Localisation team
members has been in contact with a high level executive of Opera, and will
contact that person again. We're going to wait for a few days for an
outcome -- if there is no expectation of a relatively quick fix, we might
disable WebFonts for Opera completely. Opera unfortunately does not have a
public bug tracker.
https://bugzilla.wikimedia.org/33027 -- Narayam and WebFonts both loading
slows down page
Priority: MEDIUM
--------------------------------------------------------------------------------------
The reporter claims that the functionality is quicker on
translatewiki.netthan it is in Wikimedia wikis. A commenter states
that more functionality
usually means more code, means more data that needs to be transferred, and
without changing bandwidth, that causes longer load times.
This currently isn't our highest priority, but eventually we will look into
this a little deeper. We're inviting volunteers to do some of the data
gathering and analysis for us. What is needed in our opinion is insight in
the data volume added by WebFonts, as well as an assessment of the code
quality with regards to size optimisation. All referenced properly, of
course :). There are alternate EOT conversion tools that have a good
compression ratio. Needs to be explored, but EOT is not required for modern
browsers since they started using WOFF fonts which are compressed OpenType
fonts.
https://bugzilla.wikimedia.org/33085 -- Integration of updated Lohit-Tamil
Font
Priority: MEDIUM
--------------------------------------------------------------------------------------
Request to update WebFonts with a font that is updated upstream. This is
something the Localisation team checks regularly. Will probably be closed
this week, pending issues the have a higher priority.
https://bugzilla.wikimedia.org/32942 -- Provide help page and bug report
link for WebFonts
Priority: HIGH
--------------------------------------------------------------------------------------
More recently developed tools by the Wikimedia Foundation have often
included feedback mechanisms. The Localisation team plans on implementing
these for the functionality of the WebFonts, Narayam and Translate
extension. Besides that, we also want to provide multi-lingual and
localised documentation. This needs some thinking and some work to provide
in a structured and navigable way. We'll keep you posted. It will most
probably involve translatable *user* documentation on MediaWiki.org and
hopefully it is possible to have one feedback location per feature across
the multiple Wikimedia wikis -- this is something we're going to contact
the ArticleFeedback and MoodBar teams for.
=======================================
Closed issues
=======================================
https://bugzilla.wikimedia.org/33025 -- When changing to a non-default web
font, the content does not
--------------------------------------------------------------------------------------
This issue was a side effect of a feature to allow multiple web fonts to be
used using the "lang" attribute. It was resolved in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/105980 and has been
deployed.
https://bugzilla.wikimedia.org/33034 -- Web fonts not loading in Firefox
--------------------------------------------------------------------------------------
Duplicate reports were 33038 and 33044. This issue originated from
http://www.w3.org/TR/css3-fonts/#same-origin-restriction. Almost all
browsers except for Firefox ignore that specification. A fix was designed
and deployed: https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106092,
https://gerrit.wikimedia.org/r/1501. Thanks to Roan, Brion and Ryan for
their help.
https://bugzilla.wikimedia.org/32775 -- Gibberish in Internet Explorer 8 on
Windows XP
--------------------------------------------------------------------------------------
This is an unexplained phenomenon only observed in Internet Explorer on
Windows XP. It is also hard to reproduce. One of the developers was able to
make something somewhat reproducible on a clean, fully patched installation
of Windows XP with Internet Explorer 8. See bug report for details.
Based on these observations we think it is a bad idea to keep supporting
WebFonts in Internet Explorer 8 on Windows XP and we have disabled it in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has
been deployed.
https://bugzilla.wikimedia.org/33096 -- Internet Explorer 6 does not have
font fallback
--------------------------------------------------------------------------------------
IE6 not having font fallback causes Latin characters to display as squares
when a web font is loaded that does not contain glyphs for the Latin
script. A screenshot is available at
http://media.crossbrowsertesting.com/users/34057/screenshots/window/z669002….
Based on this observation, we think it is a bad idea to keep supporting
WebFonts in Internet Explorer 6 and we have disabled it in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172. This fix has
been deployed.
https://bugzilla.wikimedia.org/33024 -- WebFonts menu buttons not working
in IE7
--------------------------------------------------------------------------------------
This was caused by the JavaScript $( '<input type="radio" />' ) . attr(
"name" ,"font"); not working in IE6 and IE7. Updating name attributes once
they have been created is not possible. We think there may be more
occurances of this in our code (one occurance in jQuery has already been
identified: resources/jquery/jquery.validate.js:59). A fix was made in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106175. This fix has
been deployed.
https://bugzilla.wikimedia.org/33040 -- Overlap in Samyak font for Hindi
and Sanskrit
--------------------------------------------------------------------------------------
This issue occurs in Windows XP and Windows 7 (possibly also in Windows
Vista) when using Google Chrome. It is not observed when using Chrome with
Mac OS X 10.7.2 or several Linux distributions (Debian and Fedora). Samyak
Devanagari is available as a non-default web font in Hindi, Marathi, and
Sanskrit. Samyak Gujarati is available for Gujarati as a non-default font.
This font needs to be corrected. The maintainers will be notified of the
observed issues, and mean while, the fonts will be removed from the
WebFonts selection list (but can still be used using the font-family
property. A fix was made in
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106179. This fix has
been deployed.
https://bugzilla.wikimedia.org/33039 -- Overlap in Madan font for Nepali
--------------------------------------------------------------------------------------
This report was invalid. The reporter was not aware of the correct glyph
for the Nepali script.
Comments on this bug report resulted in two odd observations (Crome crash,
Opera font fallback), that have been split off into separate bug reports:
https://bugzilla.wikimedia.org/33100 and
https://bugzilla.wikimedia.org/33102.
https://bugzilla.wikimedia.org/33095 -- WebFonts menu can expand off the
screen
--------------------------------------------------------------------------------------
If the translations for "Select font" and "Login / Register" are really
short, like in http://mr.wiktionary.org, expanding the WebFonts menu for
anonymous users will display a menu that is partially off the screen. It
was resolved in http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106186,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106197,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106201,
http://www.mediawiki.org/wiki/Special:Code/MediaWiki/106202. These
revisions also depend on a few small UI changes of both WebFonts and
Narayam, and will be deployed on December 19, 2011.
<no bugzilla report> -- WebFonts menu expands under the control for
customised input method in IE6 on transliteration
--------------------------------------------------------------------------------------
There are issues with the z index in IE6. Because of
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/106172, WebFonts is
no longer available in IE6, so this issue is obsolete. Observing that the
Hindi projects Wikipedia and Wiktionary are using an custom input methods
tool, we would like to invite them to test Narayam which contains many
input methods in a MediaWiki extension. We are very open to having the
Hindi input method InScript tested and add a transliteration input method
with some community representatives, as we have done with other Indic
languages. We hope this will eventually lead to Narayam being adopted by
the Hindi community, and the custom input method being abandoned.
Hello,
Happy New Year to all!
I would like to announce the release of MediaWiki Language Extension
Bundle 2013.12. This bundle is compatible with MediaWiki 1.21.3 and
MediaWiki 1.22.0 releases.
* Download: https://translatewiki.net/mleb/MediaWikiLanguageExtensionBundle-2013.12.tar…
* sha256sum: 2ef19e31d685dd0d6e50088ec8bbb1cd3e74c694096dfa333efb61dcfee9c3c0
Quick links:
* Installation instructions are at: https://www.mediawiki.org/wiki/MLEB
* Announcements of new releases will be posted to a mailing list:
https://lists.wikimedia.org/mailman/listinfo/mediawiki-i18n
* Report bugs to: https://bugzilla.wikimedia.org
* Talk with us at: #mediawiki-i18n @ Freenode
Release notes for each extension are below.
-- Kartik Mistry
== Babel, CLDR and LocalisationUpdates ==
* Only localization updates.
== CleanChanges ==
* Bug 58439: Fix Monobook skin by removing extra
<nowiki></div></nowiki> creating invalid HTML.
* Localization updates.
== Translate ==
=== Noteworthy changes ===
* Translator Sandbox:
** Translator Sandbox is a feature to simplify the sign-up process for
new translators. It can be enabled using "$wgTranslateUseSandbox =
true;", but it will only be useful in conjunction with the
TwnMainPage, which is not included in MLEB (at least yet).
** Stash and translator approval pages are now usable.
** When a user is accepted, a bare-bones user page with a Babel box is created.
* TUX editor:
** Bug 53748: Message group related calls were made two order of
magnitudes faster, making Special:Translate's group selector, workflow
state selector etc. fast enough even on wikis with hundreds or
thousands groups.
** Add useful shortcuts to TUX editor. All buttons to insert/replace
text (insertables and then translation aids in order; "discard
changes" is skipped) are numbered from 1 up and can be accessed with
both alt+<num> and arrow up and down.
** Update the statusbar at the bottom of the TUX message tables when
saving or proofreading.
* Added support to MediaWiki localisation format from PHP files to
JSON files. This is part of the Localization Format RFC (
https://www.mediawiki.org/wiki/Requests_for_comment/Localisation_format
).
** Add support for JSON in mediawiki-defines.txt, allowing the
handling of MediaWiki extension that us the new format. Documentation
about the updates in MessageGroup configuration can be found at:
https://www.mediawiki.org/wiki/Help:Extension:Translate/Group_configuration…
** Fixed JsonFFS for properly importing and exporting Authors.
** targetPattern in group configuration is now optional.
** Migrate the Translate extension itself to JSON based i18n files
from PHP files. This change is transparent to all users of extension.
* Support xliff 1.1 files in addition to xliff 1.2 as well, but
without validation.
=== Breaking changes ===
Special:FirstSteps has been removed from Translate. If you want the
feature, you'll have to download it separately.
== UniversalLanguageSelector ==
=== Noteworthy changes ===
* Language selector now opens an order of magnitude faster (see
https://github.com/wikimedia/jquery.uls/pull/122 for details).
* Initial support for webfonts in MobileFrontend:
** Currently, support for webfonts in MobileFrontend is disabled by
default. It can be enabled by setting $wgULSMobileWebfontsEnabled =
true; in LocalSettings.php file. Note that, even then it will only be
enabled for users who has opted in for the mobile beta mode.
=== Fonts ===
* Bug 57767: Enable Amiri font for Soranî language.
* Bug 58381, 58382: Add Lateef and Scheherazade fonts for Soranî and
Farsi languages.
* Update Autonym font to version 20131205:
** Fixed Autonym for Old Slavonic.
** Fixed glyphs for the Glagolitic script.
** Removed Reserved Font Name (RFN) and documentation updates.
--
Kartik Mistry/કાર્તિક મિસ્ત્રી | IRC: kart_
{kartikm, 0x1f1f}.wordpress.com
Per conversations with Amir, Santhosh, Siebrand, and Jon, I would like to
beta test mobile webfonts on 1 wiki and then possibly add more wikis later
if the beta test does not cause any adverse effects. To this end, I have
identified seven candidate wikis that I would like your help to narrow down
further. These seven wikis meet the following criteria:
1. The language of the wiki would benefit from loading a webfont by default
2. The default font would be less than 50K in size
3. The wiki has at least 50 active users (i.e. a community)
Language Code Articles Users Active Users Font Size Punjabi pa 8,069 6,818
61 12.6K Gujarati gu 24,623 17,696 59 28K Marathi mr 39,621 39,114 135
36.4K Nepali ne 24,944 14,379 73 36.5K Hindi hi 109,045 101,837 274 37.3K
Oriya or 4,535 5,937 76 47.8K Kannada kn 14,384 17,455 177 48K
The main variables that I don't know are:
1. How bad is the experience on each of these wikis without webfonts?
2. Do we already have a working relationship with the communities on any of
these wikis?
If you guys could help me narrow down this list to one or two choices, it
would be greatly appreciated!
Ryan Kaldari
I felt I'd mess it up by sending this to i18n through NNTP and design
through e-mail... Let's see if sending to both by NNTP will fix that.
On 12/11/2013 06:41 PM, Matthew Flaschen wrote:
> That's almost certainly not possible in every language. It could work
> as a suggestion, though ("If possible...").
Jared said that it doesn't even have to be treated as a sentence, can be
something like "Editing: [article name]".
> However, it might be better to wrap the title (language aside, it could
> provide better usability for some scenarios, e.g. if you lock your phone
> when editing, then come back to it and want to see what page you're on).
I'm not sure if I understand the example use case. Also, this solution
has all sorts of other problems. Let's say we try to do it in PHP, we
don't even know the browser window width. Let's say we do it in
JavaScript, we know the browser window width, but we don't know how many
characters will fit in a single line... For those reasons I'd rather
stick with text-overflow: ellipsis in CSS.
--
Juliusz
Dear list readers,
The Wikimedia Foundation teams for VisualEditor and Language Engineering
have put together a document that proposes a change in the MediaWiki
localisation format.
Please provide your input at
https://www.mediawiki.org/wiki/Talk:Requests_for_comment/Localisation_format
We have also proposed to discuss this RfC in the upcoming RfC review
meeting of 2013-12-18[1]. As far as we know, no time has been set for this
meeting, yet.
Thank you for your insights.
Cheers!
--
Siebrand Mazeland
Product Manager Language Engineering
Wikimedia Foundation
M: +31 6 50 69 1239
Skype: siebrand
Support Free Knowledge: http://wikimediafoundation.org/wiki/Donate
If you are in beta on mobile now, there's a new look for the editor. The
heading of the editor now says "Editing [article name]" in English.
The problem is that designers want this to be always one line long at
most and truncate it when it's longer. This is fine in English where
"Editing" is at the beginning, not OK in some languages, e.g. Japanese:
http://tinyurl.com/qftpgy4 (click the pencil icon)
where "editing" ("編集中") is at the end. If we truncate this, it won't
make much sense.
Should I suggest in the message description that the translators should
use such a grammatical construction so that the word "editing" stays at
the beginning? That's what designers suggested.
--
Juliusz
Hello,
This is a reminder that the Wikimedia Language Engineering team will be
hosting an IRC office hour from 1700 to 1800UTC later today on
#wikimedia-office (FreeNode). Please see below for the event details.
Thanks
Runa
=== Event Details ===
What: WMF Language Engineering Office hour
When: December 11, 2013 (Wednesday). 1700-1800 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131211T1700
Where: IRC Channel #wikimedia-office on FreeNode
---------- Forwarded message ----------
From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org>
Date: Fri, Dec 6, 2013 at 3:19 PM
Subject: Language Engineering IRC Office Hour on December 11, 2013
(Wednesday) at 1700 UTC
To: MediaWiki internationalisation
<mediawiki-i18n(a)lists.wikimedia.org>, Wikimedia Mailing List
<wikimedia-l(a)lists.wikimedia.org>, Wikimedia developers
<wikitech-l(a)lists.wikimedia.org>,
wikitech-ambassadors(a)lists.wikimedia.org
[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting an IRC office
hour on Wednesday, December 11, 2013 between 17:00 - 18:00 UTC on
#wikimedia-office. (See below for timezone conversion and other
details.) We will be talking about some of our recent and upcoming
projects and then taking questions for the remaining time.
Questions and any other concerns can also be sent to me directly
before the event. See you there!
Thanks
Runa
=== Event Details ===
What: WMF Language Engineering Office hour
When: December 11, 2013 (Wednesday). 1700-1800 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131211T1700
Where: IRC Channel #wikimedia-office on FreeNode
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
[x-posted]
Hello,
The Wikimedia Language Engineering team will be hosting an IRC office
hour on Wednesday, December 11, 2013 between 17:00 - 18:00 UTC on
#wikimedia-office. (See below for timezone conversion and other details.)
We will be talking about some of our recent and upcoming projects and then
taking questions for the remaining time.
Questions and any other concerns can also be sent to me directly before the
event. See you there!
Thanks
Runa
=== Event Details ===
What: WMF Language Engineering Office hour
When: December 11, 2013 (Wednesday). 1700-1800 UTC
http://www.timeanddate.com/worldclock/fixedtime.html?iso=20131211T1700
Where: IRC Channel #wikimedia-office on FreeNode
--
Language Engineering - Outreach and QA Coordinator
Wikimedia Foundation
