Hi Simon, Simon Brouwer wrote:
Hi all,
Just to add my two cents,
On the other hand, there are A LOT of name changes, and new entries, and icons being moved all over the place. Do you think that each one should go through a community vote? If we did that, we wouldn't get anywhere. Hence... at most only a small minority of changes should go through community vote.
My opinion is that whoever does practically all the localization work for a certain language (which is really a LOT of work), reasonably has the final say on choice of its terminology.
So, what is the choice left in that case, a fork ?
This issue has been set has wontfix because this is Windows terminology and not what we consider good French :
http://www.openoffice.org/issues/show_bug.cgi?id=18565
This is not the only one (but the one that makes our community a bit nervous)
The name Stylist has been changed without any communication and without asking about any feedback.
But as the OOo community is a great factor in the success of SO/OOo, so it would be unwise if Sun did not involve the community or not take them seriously in matters such as these. Also, the community may add valuable insights.
I end by asking me if that has any matter. We have put a collaboration in place, but if the l10n issue we report doesn't fit with Office, they will be set as 'wontfix'. No need to waste our time here.
I am not convinced, though, that basing the choice of terminology on majority voting would be the best way to arrive at an optimal, consistent user interface.
I'm sure this is a stupid way to solve a communication issue more than anything else. But what is the way of communicating we have now ? Colm told that they have their own database of feedback for OOo (better than ours it seems), that mean that whatever we (fr community) will do, we will never have an OOo release, but what Sun think is the better for us, whatever again the feedback we can give and the quality we aimed.
I'm sorry, but this is not my view of sharing, I'd prefer to go away.
In the case of Dutch, a name change may actually be a good idea because "styles" is translated as "opmaakprofielen", and thus there has not been a clear link between the name "Stylist" and what the function is about, anyway. OTOH "opmaakprofielen en formattering" is hardly a catchy name for a distinctive feature like the Stylist...
Happy for you that you are able to choose what your users want.
Kind regards Sophie
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
