Hi Sophie,
At 22:18 21-1-2005, you wrote:
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 ?
I assume that the approach to localization at Sun is to optimize it for Star Office users/adopters; as long as the localization is palatable for those, I doubt it would be so seriously broken for OOo users that a fork could be worth the trouble. Don't underestimate how much work Sun is taking out of your hands by taking localization and building upon itself...
So another choice would be, trying to convince the localizers at Sun, which would be the easier if your solution is obviously better, and if they can't be convinced, living with it (hmm...)
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.
Providing regular milestone builds could count as communication, and we have the Issue Tracker for 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.
IMO, as many SO/OOo users have previous experience with MS Office, trying to make them feel "at home" with the UI of SO/OOo is a valid consideration. So at times going with the MS glossaries may be preferable to choosing a translation that may be strictly more correct, but unfamiliar to users. That said, an approach to try making SO/OOo look as much the same to MSO as possible, would be too simplistic. There should be quite a number of instances in which the MSO localizations can be considerably improved. I think choosing "Assistent" over "Wizard" is a good example, which even could be considered for the English version.
Maybe you should start a discussion about the general approach to terminology and localization on the [EMAIL PROTECTED] and/or the [EMAIL PROTECTED] mailinglist.
(...)
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.
It comes at a cost...
Vriendelijke groet, Simon Brouwer.
>>> nl.openoffice.org <<<
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
