I can't help you, but ... am pretty curious: Can't you create your own wording to avoid that kind of thing? e.g. eliminate the "styles" and perhaps a different reference in the question?
Just curious - why it has to be ver batum. > Hi and sorry for crossposting ... > > the issue happnes with almost every release and > it is > really a pain for localization teams (causes us > to file > issues, needs rework of Ui at a very late time > and causes > discussions when we are close to a release). > After all > ..it is annoying for everione of us. > What's the issue? Descriptive texts on command > buttons. > At the moment I have this in > sfx2/source/doc/doc.src > > If a document is loaded which is based on a > template, for > which the styles have changed, the information > "The > template '$(ARG1)' on which this document is > based, has > been modified. Do you want to update style based > formattings according to the modified template?" > is > given. > The buttons then are: > "Update styles" and "Keep old styles". This > would > (correctly) translate to "Formatvorlagen > aktualisieren" > and "Alte Formatvorlagen beibehalten" (slighly > more text > than in english - and will produce quite ugly > UI). > So - why have these strings been choosen, even > if a > simple "Yes" and "No" would have perfectly done > the job? > > If you think, the issue is not that important - > I know > some companies who have a very simple method to > teach a developer, how > important that is. Each developer who introduces > such > strings (and each UX member who accepts such a > change) > should donate 5 EUR to the project + 1 EUR for > each > localization team that cannot correctly > translate such > strings. > > Btw - the same thing happens on all UI elements. > But > Buttons are more sensitive, as for labels and > other > stuff, we normaly have more space - but not for > Buttons. > > André --------------------------------------------------------------------- To unsubscribe, e-mail: discuss-unsubscr...@openoffice.org For additional commands, e-mail: discuss-h...@openoffice.org
