[13:07:38] hello [15:58:09] hi pginer [15:58:49] hi Nemo_bis [15:59:43] pginer: you made me worry, it's 17 UTC and not CET :) [16:02:02] Sorry for creating time confusion... [16:02:07] …but that will be nothing compared to the daylight saving time coming to Europe in some weeks. [16:04:30] pginer: why, at least we'll be again at usual distance from SF caput mundi [16:37:05] Wikimedia Language Engineering team office hours here in 23 minutes. [16:58:18] Wikimedia Language Engineering team office hours here in 2 minutes. [16:58:32] * YuviPanda waves [16:58:54] hey YuviPanda [16:59:06] hello everybody [16:59:07] * YuviPanda waves at siebrand from Kolkata [16:59:36] from Hyderabad, India [16:59:47] Hi malkum_ [16:59:51] hey santhosh_ [16:59:56] hey malkum_ [16:59:58] * siebrand is in San Francisco, USA [17:00:06] (for one more week) [17:00:23] hi Yuvi and Santhosh [17:00:30] Hello.. are we ready to start [17:01:04] * siebrand pings alolita, aharoni, Nikerabbit, pginer, santhosh_  [17:01:08] hello! [17:01:20] hi [17:01:35] hi malkum [17:01:49] Okay then… [17:01:53] ### Language Engineering Office Hour - Start ### [17:02:02] Interesting figure 146 ..how much we tried to bring it down..it keeps up :) [17:02:15] Welcome to the office hour of the Wikimedia Language Engineering Team. [17:02:33] My name is Runa and I am the Outreach and QA coordinator for our team. [17:02:48] Good to have you on the team Runa! [17:03:03] I have recently joined the Language Engineering team and I will be working closely on building relationships with our Language Communities for efficient interaction about the Language tools and issues that they face when using Language Wiki projects. [17:03:19] I work from India. :) [17:03:25] Thanks alolita [17:03:59] The other members of our team present today are: aharoni alolita pginer Nikerabbit santhosh_ siebrand [17:04:19] As our last office hour was 3 months ago, we have quite a lot of updates about what we have been working on. [17:04:33] After that we would be happy to answer any questions. [17:04:52] If you'd like to send in your questions before the Q&A, please send them to me over a private message. [17:05:27] As I mentioned before, we are the Wikimedia Language Engineering Team and we work on enabling Language tools for MediaWiki and Wikimedia projects. [17:06:01] This essentially means creating all the magic that would make the Wikimedia universe more diverse in terms of being usable in languages from around the world. [17:06:39] This brings forth lots of challenges in providing support for the way the languages are to be displayed, written, and prepared to be used just as well as English. [17:06:55] We still have a long way to go in our mission. [17:07:27] Presently, our primary focus is on extending input methods, fonts, and also creating advanced features for the Translate Extension (TUX). [17:07:42] Agenda for Today: [17:08:03] Since our last office hour, the team has been working to make our Language Tools better. [17:08:19] We shall be giving an update about: [17:08:34] 1. Release of the MediaWiki Language Extension Bundle (MLEB) [17:08:57] 2. Translate UX (TUX) [17:09:05] 3. Participation in various community events [17:09:33] Also we have some updates on two of the topics that were discussed during the last office hour. [17:10:00] 4 Language Team plans [17:10:12] Runa: can you also tell us more about our team's input methods support and progress made recently [17:10:17] 5. Testing Event plans [17:10:38] alolita: sure [17:11:17] Updates : [17:11:31] 1. Release of the MediaWiki Language Extension Bundle [17:11:55] MediaWiki Language Extension Bundle (in short MLEB) 2013.02 has been released. [17:12:27] The aim of MLEB is to provide easy to install (and update) package of useful language support and translation related extensions. [17:12:49] * Vogone knuddelt Mathonius ... [17:12:59] heh heh, not in the office! :P [17:13:02] :P [17:13:21] MLEB releases are made each month so that new features and bug fixes get quickly to the users, while avoiding the occassional breakages compared to using the development version of these extensions directly. [17:14:02] Future improvements considered for MLEB is to release version that supports MediaWiki 1.19 and running unit tests against the releases automatically. [17:14:14] Thats all for MLEB [17:14:31] 2. Translate UX [17:14:38] aka TUX [17:14:42] amir - can you post the link to the MLEB release notes for everyone to refer to - thanks! [17:16:26] The Language Engineering team is working on redesigning the Translate Extension. [17:17:03] The goal is to make the translation process more fluent and the presentation of information more clear. [17:17:43] You can take a look at the new UI at http://translatewiki.net/w/i.php?title=Special:Translate&tux=1 [17:18:01] The tool provides three views: [17:18:21] a list of messages to translate, [17:18:54] a page layout for translation (convenient for translatable pages), and [17:19:05] the proofread view [17:19:53] In the current sprint the focus is on improving the proofreading view, where logged-in users can verify translations from the community. [17:20:27] Feel free to test the new UI, and provide us with your questions and the issues you found. [17:20:44] pginer: would you like to add anything on this? [17:21:37] Just insist on asking for feedback. We don't know all languages (yet) so it is very helpful to see whether our tools meet the needs of the different language communities. [17:23:32] pginer: how do folks provide feedback? [17:23:42] http://hexm.de/TUX-testing -> Please use this link if you'd like to participate in a usability test with pginer [17:24:00] arrbee: is the new UI compatible with all skins/browsers/operating systems? [17:24:42] Vogone: translators need a modern browser with adequate JavaScript support. [17:25:36] okay [17:26:00] Vogone, not tested on all skins of MediaWiki. [17:26:02] Vogone: We are planning for implementing automated interation tests on most major browser platforms, so that use cases that are broken will surface more easily. [17:26:18] Indeed. Vector skin is highly advised. [17:26:38] * Vogone uses monobook [17:27:34] okay… I'll move on for now. [17:27:36] I am trying to understand the difference between List and Page views. [17:28:06] malkum_, List of translation, Page is visualising original and translated versions side by side [17:28:50] List shows a message per line, so long messages may not be shown completely. [17:29:35] Before moving on to the next item, here is the link to the release announcement for the latest MLEB release: [17:29:43] http://lists.wikimedia.org/pipermail/mediawiki-i18n/2013-February/000622.html [17:29:46] The page view shows messages completely, which makes it more suited for translating translatable pages for example since you can get more context information of what is above and below the current message. [17:31:16] 3. Participation in various community events [17:31:26] And also, the MLEB homepage: https://www.mediawiki.org/wiki/MLEB [17:31:42] The team also participated in various community events and you may have already read about them in our blogs. [17:31:59] This included FOSDEM at Brussels and GNUnify at Pune, India. [17:32:25] The other major event was the OpenSource Language Summit that was hosted jointly with Red Hat at Pune. [17:32:36] The event report is here: [17:32:45] http://www.mediawiki.org/wiki/Pune_LanguageSummit_February_2013/Event_Report [17:33:21] The shorter version is that we followed up on the discussions and work that was started during the last summit in November 2012 and also started with some new projects. [17:33:40] This includes: [17:33:46] In Proofread view , I would also like a provision for Unaccept the translation, just in case the user accepts a translation accidentally [17:34:05] like facebook Like / Unlike [17:34:14] malkum_: if there is something wrong with the translation after all, you should fix it [17:34:51] 1. Creating a document on the technical specifications of fonts of the Indian language scripts, and [17:35:17] 2. Detailed discussions about the internationalization and localization testing events conducted by Fedora. [17:35:55] We believe that based upon this we now have a better understanding of formulating similar testing events for our extensions. [17:35:59] Nikerabbit, agreed! but what if I accepted something accidentally which I dont know how to translate [17:36:14] More about this in a little while. [17:36:49] alolita: Do you have anything to add to the above? [17:37:07] malkum_: mark fuzzy? do a dummy change? [17:37:19] moinmoin [17:37:57] arrbee: i think pau did :-) [17:38:25] alolita: I meant for the OpenSource Language Summit :) [17:38:39] (it did get a bit muddled in there) [17:38:52] sorry - context switching :-) [17:39:25] we accomplished a lot at the core developer sprints at the language summit in feb [17:39:49] arrbee referred to a couple of accomplishments [17:40:33] including kicking off the work on the Indic language font specification by Santhosh and other collaborators from Red hat's i18n team [17:40:48] Nemo_bis, I didnot get you [17:40:54] https://github.com/santhoshtr/fontbook [17:40:57] we now have the font spec available on github [17:41:06] santhosh - thanks for the link! [17:41:40] I'd also like to add the part about IMEs that alolita referred to earlier. We added 60 new input methods to jQuery.ime during the 2 day event [17:42:08] the input methods added were a very significant contribution [17:42:11] malkum_: changing the message resets its proofread status; if you also mark it !!FUZZY!!, you explicitly request its update/check [17:42:40] our input method repository on github now is the largest open source repository for web based input methods [17:43:36] santhosh worked with parag nemade of red hat to make significant progress on adding and merging input methods to our github jQuery.ime repo [17:44:02] santhosh - do you have a current number of languages now supported by jQuery.ime [17:45:01] 70+ [17:45:12] thanks santhosh! [17:45:15] need to count for exact number :) [17:45:31] Thanks alolita santhosh_ [17:45:46] I'll go to the next item [17:45:52] 4. Language Team plans [17:46:34] We would like to leverage the language expertise from within the language communities to find an efficient way of gathering information about matters that are critical and need to be corrected without delay. [17:47:14] For this, we are working out the details of how we can equip volunteers from the language communities, with appropriate information and guidance to work closely with the Language Engineering team. [17:47:42] And more importantly on maintaining a continuous two-way communication. [17:47:59] We plan to have this ready sometime by the end of this month. [17:48:39] aharoni: Would you like to add anything more here? [17:49:02] Well, just a bit: [17:49:48] Basically, we shall need people who love their language and want to help us make it work better in Wikimedia projects. [17:50:15] It's a plan that will help us understand what different languages need. [17:51:01] We assume that at least some languages need more software support than they have now, and we want to help the people who speak them tell us what they need. [17:51:06] That's really the summary of it. [17:51:18] More details will be published very soon. [17:51:21] Thanks aharoni . [17:51:40] If you'd like to help us with some ideas on this, please feel free to ping me or aharoni . [17:51:50] we would also love to have wikimedians to report bugs on bugzilla.wikimedia.org if they see problems with their fonts and input methods [17:52:14] Quickly moving on to the last item in our agenda and then to Q&A [17:52:17] please ping arrbee if you would like us to help you report bugs on bugzilla [17:52:35] nod [17:52:40] 5. Language Tools testing event [17:52:50] We are presently working out a plan for organising testing events with users of Language Wikis and of the Language tools. [17:53:16] For this, we intend to have scheduled test day(s) with focus on specific tools. [17:53:49] Users can test the features using test cases/instructions and can record their observations and provide feedback. [17:54:11] We plan to organise these testing events regularly to coincide with important releases. [17:54:35] We'll have more information about this sometime by the end of this month. [17:54:55] That completes the updates. [17:55:08] Q & A: [17:55:26] Any questions for us? [17:56:24] Just adding a shameless plug for the Language Engineering team - we're hiring! we're looking for a solid Javascript developer - ping me 1:1 if you're interested :-) [17:57:27] some of our team also plans to be at the Amsterdam hackathon coming up in May (just a couple of months away) so join up if you're in the neighborhood and work with us [17:58:00] New UI rocks. Claps, Whistles, Hifi's to the development and design teams [17:58:16] :) [17:58:25] malkum_, and thanks for your random patches too. expecting more@! [17:58:28] we're also going to be participating with projects in this year's GSoC so keep track! [17:59:09] santhosh_, love to.. learning things by the way a lot. Appreciate yours and Nike's support. [17:59:12] We have a minute more [18:00:13] any more questions? again we're always on #mediawiki-i18n [18:00:29] please find us if you have any questions or feedback [18:00:53] If nothing more, we'll end this office hour for today. [18:01:16] Thanks everyone. As alolita mentioned, we are around on #mediawiki-i18n. [18:01:33] Please do feel free to ping us. [18:01:33] thanks everyone! for joining in! arrbee thanks for hosting the office hour today! See you here next month! [18:01:53] Thanks everybody [18:02:11] malkum: thanks for your participation :-) [18:02:16] We'll be announcing about the next office over the usual mailing lists. [18:02:28] ### Language Engineering Office Hour - Ends ###