Martin Srebotnjak wrote:
Hi Martin,
maybe the verified builds would get a green check mark icon, and the others
a red question mark icon? There should also be a legend stating that builds
with the green check mark are supported and verified, whereas the others
might not work as expected. That being said, they can all be put on one
single page. If I understand correctly some of the Sun builds (the A-list
ones) are even not fully (100%) translated? If that is so (sorry, if I
misread some of the posts on this list), those builds are not better as
Slovenian ones, that are 100% translated since 2.0 or even before...
IMHO nobody has said this. ;-) We are doing full install sets when the
L10N has reached 75 or 80 %. Langpacks are always done.
Maybe the page could be made more readable if it is not in the tabular view?
Remember also, not all platforms are QAed for some languages!
Which makes it more complex IMHO. ;-(
One solution is to use a language selector and then an OS selector (the OS
selector would update itself upon language selection:
A- if a build does not exist it would say "no build available"
B- otherwise it would display a string: "status-icon OS-identifier
(OOo-version, size)" like this (imagine x icon graphically, I cannot draw in
text here): "x Linux 64-bit RPM (3.1.1, 95 Mb)", where x is a small icon
representing either a check or question mark.
We have already a selector for the JRE builds. Already today we have
exception where this does not apply (platforms for that no such build is
provided, e.g., Mac OS and Linux DEB). Introducing 2 more selectors
would be not good.
Ah, or do you mean a selection via 2-3 drop-down listboxes? This could
be better. But even this "magic" has to be created and for this we have
very limited time. Creating these websites in general is OK. But every
magic done via JavaScript needs much more time as it has to be invented
from scratch.
Very much like the main ooo page link to downloads (autorecognition of your
language and OS), but with more options and in a very clear, simple way,
stating clearly that some build might not be fully localized and/or tested.
Normally everything (version, platform, language) should work with our
one-click-download link. But just for problems the user can (has to)
select the appropriate build from the the other.html.
Same goes for langpacks.
@all:
Does anything speak against a try with the current setup for the current
3.1.1 release?
Then we can see what could be improved until 3.2.0. And with the 3.2.0
release we can try to collect the experiences and to improve the
websites to get it perfect.
Best regards
Marcus
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
