Hei,

> So how does this work with OOo?
> OOo has versions with or without JRE for Windows, (and of course
> english and other
> languages, but more on that later on)
> OOo has versions in RPM and DEB format for Linux (and some with JRE,
> some without)
> OOo has versions for MacIntel, MacPPC, (all without JRE)
> OOo has versions for other systems as well.

I still don't see the big difference between OOo and Mozilla in that
regard. The only one i can see is JRE and that can be tested for like
anything else.

> So how would you guess a default for OOo?
> Default to english and still start the download? Bad, bad, bad for
> non-english users...

Detect language from the html agent.

> Default to version with JRE? Bad, bad, bad when the nl-community is
> not QA'ing the version

Detect Java plugin presence.

> of OOo that has JRE included, doesn't build versions with JRE at all
> (AFAIK only Sun does
> build versions with JRE)
> For Mac, what version would you default to? PPC or Intel? Probably
> Intel. But since QA is
> limited for Mac and not all languages go through the official
> QA-Process, how would you
> handle this?

Set up an infrastructure to mark QA'd packages and have them appear in
dedicated places...build a servlet to probe for available
packages...have that scriptlet spit out a JavaScript to probe for users
environment, pick the right download and inform the user about what he
gets.

> Native-language versions in general: How would you deal with different
> versions being
> QA'd / approved at different points in time?

Offer latest native language version AND latest english version, if
newer. Inform user.

In any case, always offer an option to unguided choice.

> I /still/ don't see a one-click solution, and honestly I still don't
> see what is wrong when
> the user has to do two clicks. Is the user really that dumb so that
> she doesn't know what
> operating system she runs?

I guess the question here is not if the user is dumb, but if you want
them to try OOo or if they want to try OOo.

André.

Attachment: signature.asc
Description: This is a digitally signed message part

Reply via email to