On 1/10/11 4:28 PM, Robin Berjon wrote:
On Jan 10, 2011, at 16:00 , Marcos Caceres wrote:
I would be happier if we could break up the Widget P&C spec into:
* Packaging (zip only requirements) * XML Configuration for
widgets * XML Localization and Folder-based Localization
I could live with that. It's not that I'm against l12n, I just don't
think that it needs to be part of the standard given its complexity
cost and likely actual usage.
I would argue that it's not particularly complicated to implement, and
we are seeing it used in Opera extensions: we have extensions in 15
languages as of today in our catalog [0].
Here is a breakdown (these are not exclusive to one language, most use
English and some other language - and please be mindful our catalog is
very new):
English: 262
Russian: 33
Polish: 16
German: 5
Japanese: 3
Turkish: 3
Slovak: 2
Portuguese: 2
Italian: 2
Norwegian: 2
Spanish: 1
Belarusian: 1
Czech: 1
Hungarian: 1
Northern Sami: 1
TOTAL (all languages): 335 of which 74 use another language (20% of the
catalog). 20% is fairly significant and certainly indicative of "actual
usage". To put into perspective, we have had over 4 million downloads of
extensions since launch.
Most of those use 2 languages in the same widget, and some up to 3. For
example [1]:
<widget xmlns="http://www.w3.org/ns/widgets"; version="2.3-D">
<name xml:lang="en">AutoComplete</name>
<name xml:lang="ru">AutoComplete（Автозаполнение）</name>
<name xml:lang="ja">AutoComplete（自動入力補完）</name>
<description xml:lang="en">Provides the Autocomplete for the text
input box.</description>
<description xml:lang="ru">Обеспечивает автозаполнения для текстового
поля ввода.</description>
<description xml:lang="ja">テキストフォームに自動入力補完機能を提供し
ます。</description>
</widget>
It's evident that the i18n model is usable by runtimes, widget
galleries, and developers.
[0] http://www.operaextensions.com
[1] https://addons.opera.com/addons/extensions/details/autocomplete/2.3-D/
