On Apr 7, 6:04 pm, Owen Winkler <[email protected]> wrote:
> Sean T Evans wrote:
>
> > My initial thought based on no experience with either translation or
> > scripting is this:
> > How many people will need more than one language installed on their
> > site? Would it be more productive to create a script that can create a
> > package for each language that is complete from our repositories?
>
> From my purely "building a distribution package" point of view, I would
> prefer to build only one distributable.
>
> The idea of having more easily downloadable packages is a good one.
> Should we consider enhancing the installer to download language packs on
> the fly? If not automatically installing them, then at least providing
> in-that-language instructions for how to apply them?
Instead of or even in addition to dynamically creating the download
package, which is a good idea btw, we should have a way of downloading
a package containing the translations you want.
If I install 0.7, and then a month later decide that I need to have
Norwegian and Swedish translations, I shouldn't have to redownload the
entire distribution package to get the new translations. Besides,
translations might have other "release cycles" than the main Habari
versions.
Of course, as soon as we have an automatic plugin/theme/translation
installation service, this won't be needed, in the interim we should
make downloading translations easier.
Christian
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
