Labs/Ubiquity/Meetings/2009-03-24 i18n Meeting: Difference between revisions

 
(7 intermediate revisions by the same user not shown)
Line 3: Line 3:
=== Time ===
=== Time ===


[http://doodle.com/4d3u5rk3tuk4wz44 TBA - vote!]
[http://www.timeanddate.com/worldclock/fixedtime.html?day=24&month=3&year=2009&hour=16&min=0&sec=0&p1=224 4:00pm Pacific time], [http://doodle.com/4d3u5rk3tuk4wz44 by vote]
 
<!--[http://www.timeanddate.com/worldclock/fixedtime.html?day=24&month=3&year=2009&hour=17&min=0&sec=0&p1=224 5:00pm Pacific time]-->


=== Location ===
=== Location ===
Line 15: Line 13:
** +1 416 848 3114 x92 Conf# 201 (Canada)
** +1 416 848 3114 x92 Conf# 201 (Canada)


== Agenda ==


* meeting times


== Attendees ==
== Attendees ==


# ?
# mitcho
# Seth B
# Jono
# Atul
# Aza (listening)
# fern
# cers (Christian) (listening)
# marsf
# felipc (Felipe)
# Blair (?)


== Notes ==
== Notes ==


* ?
* <b>meeting times</b>: this seems to be a good meeting time for many people... the latest doodle vote raised no objections. We'll try to continue to meet at this time weekly or so.
* <b>the new parser</b>: mitcho created a [http://mitcho.com/code/ubiquity/parser-demo/ demo] of the new parser design. ([http://bitbucket.org/mitcho/ubiquity-playground/ source available])
** The design pairs a universal parser class with individual languages' parameters, making it easy to add new languages.
** cers added a Danish parser <i>on the fly</i> (now added to the demo + bitbucket)
** Future plans:
*** Felipe may make a Portuguese parser
*** Aza feels it's a little slow... we should continue to optimize it.
*** We should incorporate this into Ubiquity proper as a Ubiquity parser plugin. This may break current commands, though, with its new way of specifying arguments by semantic role. Aza suggests the time to do this may be together with web-page commands.
* <b>thoughts on collecting data</b> (discussion of these two [http://mitcho.com/blog/projects/ubiquity-i18n-questions-to-ask/ blog] [http://mitcho.com/blog/projects/automating-the-linguists-job/ posts])
** Observation: people are excited and want to contribute, but not all can code.
** Consensus: asking for translations is easier than asking for someone to write a parser.
** Idea: we can build a "command-bank" of translated Ubiquity input and maybe train parsers over it—this could give us a good stab at many languages very quickly.
** Future plans:
*** Discuss how best to collect these types of data with l10n folks
*** mitcho will explore tools/scripts to automatically train parsers based on this kind of data.
308

edits