Hi again.
I was psyched to see that the API accepts a locale parameter as we have a good number of international users of our product. Upon testing, though, it doesn't seem like there's translations for Spanish or Portugese in the plugin yet.
Can you let me know where this is in the pipeline?
If it's a matter of getting the translated Strings, I may be able to help with a couple of languages.
My biggest i18n concern is that some dude is going to click all our buttons to install BP and then come back a wk later and keep seeing the prompts to authorize access to the services and not being able to understand how to get it to not always prompt.
Thanks!
---Marc
Hey Marc,
As you've already seen in the API i18n has been important from the get go. Our friends from Y! china and the i18n experts here at Yahoo have been reviewing the platform to ensure we'll be able to rapidly localize.
That said, while the platform should run regardless of what your default language is, we've got a couple services that still need work, and we've got a short checklist of stuff to do before we're ready to start L10n work.
I'd expect that by the end of january we'll complete required platform changes and have a list of about 100 strings that need to be translated to localize the platform. We may go with a strategy that combines professional translation and user contributed translations. As soon as we're ready we'll get a system set up where we can quickly accept and integrate user contributed translations.
The good news is - by design, we've got minimal user interface that requires localization, so once we get our homework done we should be able to rapidly add language support (where the pace with which we move will be directly related to user contributions :)lloyd
