Very interesting suggestion! As far as I can see, yes, once an
extension has been internationalized for two languages properly (or
even just one done right, theoretically) then the localized strings
could be extracted programmatically. Then it's easy to imagine a web
page in the spirit of google translator toolkit that would allow
contributors to fill them in. However some of it is not strings.
Anything under a "_locale" folder, such as HTML and image files, also
needs to be translated. That's v. difficult or impossible to provide
an auto-tool for.

  Other problems:
* i18n for extensions isn't ready yet, is it?
* Hard to see the context of some/many strings (an eternal translation
issue for software).
* A localization involves adding to the files inside the *.crx. It
could be inserted automatically by the Chrome Extensions site but this
screws around with the author's expectation, not to mention a question
of version numbering. I imagine the only reasonable path is that it
causes locale resources to be downloadable by the extension author so
they can check it into their version control. But each string resource-
affecting update they release puts the translations out of whack,
needing another delta from all the contributors. Putting the human
workflow through the extensions website is just awkward for this
model.
* Open to pranking.
* In the case of localized HTML or javascript files, possibility of
malicious tinkering. Original authors must check.

   Bit of a sourpuss, aren't I? But really I'm very keen on the idea
of a page that entices foreign language speakers to see that the
translation-requiring resources are just a few files e.g. "A.js",
"B.manifest", and "C.html". Let them download those to their own PCs
(maybe with auto-translations inserted?), so that they can manually
edit them and send them to the author.

   Googlers related to the extensions site, any thoughts?

Regards,

Akira

--

You received this message because you are subscribed to the Google Groups 
"Chromium-extensions" group.
To post to this group, send email to [email protected].
To unsubscribe from this group, send email to 
[email protected].
For more options, visit this group at 
http://groups.google.com/group/chromium-extensions?hl=en.


Reply via email to