Philippe Verdy wrote:
No! The starting language may also be any language (including British English). Launchpad can support a separate translation for English when needed.
If needed, yes. I'll grant you it's not a very "hard" assumption. What I mean is that en_US is a "hidden" language (meaning you can't add it to your preferred languages or get suggestions from it) because generally, it's the starting language. It differs from en_GB in that way.
Suppose you have an open-source software that will be used as a add-on for a Russian service (or example a TV channels selector over its internet access, with supplementary functions such as chats, forums, program selections...) that can be subscribed or accessed only in Russia, what is the interest of starting your package in English? Unless you want to extend later your software later so that it can interact with other similar services hosted elsewhere (and so, used with other TV channels bundles), but this may require further developments if the service provider uses other standards on its media server (notably for authenticating the subscriber, or allow him to change his preferences, or billing it for VoD contents)...
One advantage is that the software can go further: commercially, the authors may have no interest in having domestic competitors use the same software but get real benefit out of people using it abroad. Another is that you'd get more translation suggestions.
Jeroen
This is the launchpad-users mailing list archive — see also the general help for Launchpad.net mailing lists.
(Formatted by MHonArc.)