Hi,

Le 1 nov. 08 à 13:57, Andrea Pescetti a écrit :


On 31/10/2008 Ivan M wrote:
You can see the design that we are intending to implement at:
http://www.patentpending.co.nz/openoffice/test/home.htm
Alexandro Colorado of the Spanish NL project contacted me about making
language selection easier, as many people who may not speak English
still go to openoffice.org, rather than specific NL projects. We hope
that this update will address this, by providing a clear link with an
icon.

This is definitely a good solution.

As I wrote on the website mailing list, it could be even better if, when
you hover (without clicking) on "Language Projects", a panel appeared
with links to the native-lang projects. If 100 projects are too many,
you could restrict this to the 43 "Level 2" projects or to the 20
languages for which OOo 3.0 is available as a full build; a link named
"Others..." would then lead to
http://projects.openoffice.org/native-lang.html . Of course, the current link to the same page would remain, as a fallback when the panel is not
available.

Unfortunately, CollabNet does not allow us to localize content such as
the header, so we have to use JavaScript, as many NL project pages
already do.

The new method seems very clear and easy to use to me, a concrete step
forward with respect to the usual CollabNet bashing in the native-lang
meeting at OOoCon! While I still believe (and, I guess, most of you
believe too) that CollabNet does not suit well our localization needs,
this is an extremely easy-to-use and flexible solution.

Other approaches, like the one the Serbian community is using, are
harder to implement and less flexible, even though they are technically
superior. Nevertheless, they can coexist with Ivan's proposal.

It is important to note the biggest limitation of this
approach - namely, if JavaScript is turned off, it will not work.

OK, but (as long as it degrades gracefully by showing the normal English content when JavaScript is turned off) I see no drawback with this. So I strongly support that we implement Ivan's proposal for a start: it will make life easier for many native-lang projects and reduce the number of
anti-CollabNet hacks in use in the localized sites.


On a personal point of view, I don't really see how this proposal improves the visibility of NL projects; but that's a matter of taste. Hassles from Collabnet put aside, you probably need to move your proposal forward on [EMAIL PROTECTED] if there is some consensus on this list.

Cheers,

Charles-H. Schulz.

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to