A few notes: Taking an application with a relatively large set of localizations, laconica, I see their most recent distribution is a 2.2Mb gzipped tarchive. This expands to a 10.9 Mb directory, wherein the `locale` subdirectory consumes 6Mb. It is, in other words, the largest directory in the install, larger than the application source.
The 'average' habari localization is about a 80Kb .po and a 20Kb .mo, remembering that this will vary towards double with multi-byte translation character sets. If we distribute 10, we distribute at least 1Mb of localizations. For 100, 10Mb. It scales in a rather scary way in proportion to the Habari source, and these are low estimates. > Another nice idea is, as Owen says, downloading language packages on > the fly when the installer is running. The first step should be > choosing the language, the installer should then download the language > package and after that the installation would run in the user's > language. This is close to where I ended up after time to think about it and get desktop-app preconceptions out of my head. Languages other than en-US should be like plugins, available through the -extras mechanism now and through the (already proposed) select-your-plugins-and-download mechanism in the future. (Rather than delivering them through some new and secondary interface.) -Josh --~--~---------~--~----~------------~-------~--~----~ 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/habari-dev -~----------~----~----~----~------~----~------~--~---
