Josh Wood wrote: > > 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.) >
So, assuming that translations are provided by plugins that are installed typically, I would think that the change involved in moving how translations are handled now (by loading from system/locale) to a plugin would be pretty trivial, considering that plugins can already load additional translation files. It would just be a matter of loading into the main domain rather than the plugin's own domain. The trick would be, I think, that plugins currently load after the database is setup. So the installer would need to somehow load a plugin prior to having a database to know whether the plugin was active. This seems problematic. Perhaps this could be addressed with the bootstrap system we were discussing, or with a plugin early/pre-loader, which would also be useful for caching (to load only the cache and locale plugin, and then not load additional plugins if the cache was hit). Owen --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
