Skip to main content ↑ ↓
Install and upgrade localization Started by emanuele · · Read 4599 times 0 Members and 1 Guest are viewing this topic. previous topic - next topic

Install and upgrade localization

I'm starting to wonder if it make sense to keep them.

Apart from the fact I doubt people are going to download the package, download the languages, upload both and then install[1], there are pieces of the interface that are not and cannot be translated (unless we do lots of tricks), I'm thinking to the messages we use in the "sql" files, those are always in English.

So, what would you think if the install and the upgrade were "English-only"?
1 I think the general behaviour is download => install => go to the admin page and download/install the lang-pack.↵
Bugs creator.
Features destroyer.
Template killer.

Re: Install and upgrade localization

Reply #1 –

I think you are right. First download, then install, then more languages. So forget about install strings.

Re: Install and upgrade localization

Reply #2 –

I agree with you guys  ;)
sorry for my bad english

Re: Install and upgrade localization

Reply #3 –

Unless there's a way for the preferred lang pack to be selected, downloaded and deployed in the very first step of the install process, those strings are pretty much pointless.