ie. this fine download page would have a sense when it lists all NL projects (including official mirrors for NL versions) and points to their download pages. It is not fair at all to ignore availability of NL version of oo.o to this short lists because of some language dependent issues - what do you propose? To use en-us version because NL version has issues? Excuse me, this sucks.
ain On Fri, Oct 16, 2009 at 23:24, Ain Vagula <avag...@gmail.com> wrote: > It doesnt matter at all. I have resources to distribute my native > language version by myself. I dont have resources to follow this > insane QA prodedure. Only a bit pity that all users who visit > Openoffice.org main website will have a false imagination that there > is no oo.o version in particular language. > > ain > > On Fri, Oct 16, 2009 at 22:06, Sophie <sgautier....@free.fr> wrote: >> Resent with the good adress and to l10n@ also, sorry. >> Hi Bernard, >> Bernard Marcelly wrote: >>> >>> Hi, >>> IMHO translation work is probably too cautious, and this hinders usage of >>> OpenOffice.org. >>> >>> Take swedish (sv) or spanish (es) languages : >>> - There is no full package available for 3.1.1, only version 3.1.0. >>> - The langpacks for 3.1.1 have not been released. >>> - But langpacks are available as 3.1.1RC2. So power users can install OOo >>> 3.1.1 in these languages, and be happy. >>> >>> Take italian (it) language : >>> - Full packages are released for 3.1.1 >>> - Langpacks for 3.1.1 are *not* released. >>> - But langpacks are available as 3.1.1RC2. >>> I don't understand why the full package is released but not the langpack. >>> >>> I don't understand why a langpack in RC2 stays unreleased. >>> RC2 means that it seems good enough for public tests. If there are some >>> strings not yet translated, or badly translated, this does not prevent from >>> using OpenOffice.org as a whole. If a user does not master one of the >>> published languages, it is better than nothing. And then users of this >>> language will find and report residual errors. >> >> This is not a matter of strings not translated, but of the stability of the >> version as Joost mentioned. >> >> Releasing or not releasing as stable has always been a difficult choice. >> User that faces a not fully functional version or version that crashes may >> never come back to OOo, however if you don't release the version, you will >> miss testers and their feedback. >> >> We have already seen language specific bugs and for that have decided that a >> version or language pack that is not tested should not become public. OOo >> has a QA process even for localized version, this what we have agreed on >> several times ago. >> >> I've offered my help to each l10n team to help them in this process, it is >> still valid my time is still dedicated to these teams because it will give >> more visibility to their versions if they are on the main network, but also, >> and more important to my eyes, to their teams and the work they have done. >> >> Kind regards >> Sophie >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org >> For additional commands, e-mail: dev-h...@l10n.openoffice.org >> >> > --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@l10n.openoffice.org For additional commands, e-mail: dev-h...@l10n.openoffice.org
