Update:Extension Localization Update Issues: Difference between revisions

Update:Extension Localization Update Issues (view source)

2 bytes added , 18 August 2006

no edit summary

Confirmed users, Bureaucrats and Sysops emeriti

1,217

edits

@@ Line 12: / Line 12: @@
 There are two ways that extensions can be localized:
-# The extension author can include any number of locales directly in the extension. Localizers send extension authors localizations for inclusion in the extension. This is the traditional way to localize extensions, but it has significant coordination overhead for extension authors and localizers. Online collaborative l10n tools such as ... (can't find it!) can help.
+# The extension author can include any number of locales directly in the extension. Localizers send extension authors localizations for inclusion in the extension. This is the traditional way to localize extensions, but it has significant coordination overhead for extension authors and localizers. Online collaborative l10n tools such as http://babelzilla.org/ can help.
 # The extension is released in one main language (typically English); each localizer releases an "extension language pack". Currently there is some client support for these l10n packs, but not support for nifty features like downloading the correct langpack on demand. Need robstrong to fill in details here...
 #* what data can automated tools grab from install.rdf to identify an extension langpack?
 Note, also, that we should support application langpacks for our apps. UI would probably be very similar to [[Update:Remora Idea Dump#Dictionaries|Dictionaries]].