Eclipse Babel Project Meeting: 4/07/08 (cont’d from 3/31/08)
Attendees:
- Chris Nguyen
- Kit Lo
- Pat Huff
- Pascal Essiembre
- Margaret Wong
- Gabe O’Brien
- Denis Roy
- Nigel Westbury
- Jeff
- Message Editor – RESUMED HERE – 4/7/08
- The key being translated doesn’t show the context of each key
- This makes it hard to actually do the translation
- We need some type of UI to traces the key back to the code or give information on that particular string
- General problem for the translation tool, we cannot solve this right away
- Work around: Use Runtime Editor
- Incentives for people to join
- Most contributions page
- Denis is working on a page that pulls down the top 10 translators
- Put something on the project page that we’re looking for code contributions (not only language contributions)
- ACTION ITEM: Gabe to do this
- Eclipse Platform Page
- We should work with the platform team to have a link to Babel there – these are high traffic pages and if people are looking, these pages will get hit first
- URL: download.eclipse.org/eclipse
- Link for 3.2.1 page but no link for Babel
- ACTION ITEM: Kit to open a bug against Platform Team for this
- Start adding “Help Wanted” for bugs when we create a bug that needs help
- Update site for the Messages editor – may grab interest for developers
- We have an update site for language packs – rebuilt every week
- Babel page in the download section
- Strings not to be translated
- Create a UI to show which strings not to translate
- Should bring up a wizard to externalize the string
- Helps you figure out which ones being with a %
- Eclipse offers way to externalize strings
- Maybe we can tie this to the message editor
- Server code has a bug that the string that shouldn’t be localized
- Flag a string that it should be the same across your languages
- We may have to improve the way code is imported into the server so that it is not presented to the translators
- ACTION ITEM: Kit will open a bug to improve this process and will mention the server code to tie them together
- Add Notification to show which strings that were already translated have been changed
- Once a day we go through all of the day’s changes and flag people which strings have been translated to go back and check it
- Should it be once or day? Or automated?
- ACTION ITEM: Margaret to open the bug for this.
- Some people need read access to the data
- Would we be using web services?
- Services to access the language database to get problematic access to DB
- ACTION ITEM: Pascal to update the bug about this – we need an API into the DB to write to this if you have a bugzilla account: Bug #223036
- Put some inboxes into your watch list for Babel related messages
- Within Bugzilla, go to “Preferences” link (bottom of the page) that will lead you to “email preferences”
Within there you can go to the “watch list”