Christian Lohmaier wrote:
On Thu, Oct 15, 2009 at 3:32 PM, Marcus Lange <[email protected]> wrote:
Hi Christian,
yes, much more were built but only a few were tested and approved for
release. Only these can be taken into account.
That is very unfortunate - one of the reasons for using language packs
is that there is no proper QA and people at first don't find their
NL-Version and download the en-US one. Then people tell "doesn't
matter, just download and install the small languagepack" and then
again people cannot find it.
if there wouldn't be a QA for langpacks, then they wouldn't get
released. Of course not every NL community is testing all files but fact
is that they get tested and released in general.
However, using langpacks because there is no QA cannot be correct. ;-)
It's up to the native lang teams to test also language packs if they want to
make them available for the endusers. :-)
Don't agree with the smiley here.
You created the page because only "power users" are aware of mirrors.
But now you're giving the argument that you need to be power user to
use languagepacks. How does a non-power-user know about that process
when it is nowhere mentioned on the page?
When you are able to install the full package, IMHO you are also able to
install a langpack.
At least add a prominent sentence like "If your language is not
listed, then have a look at rc directory on extended mirrors. It will
be only listed here when it has been approved by the corresponding
native-lang projects (link to the process description)
This website is about released versions. I don't want to mixup with not
released versions; even when a RC is close to it.
We should think of a different way to go.
After all, those projects who are doing qa, mainly do this on the full
versions - and users of those languages are likely to download the
localized version first and are looking for the less prominent
languages as an addition.
I think so, too.
Best regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
