To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=106960





------- Additional comments from e...@openoffice.org Fri Jan 15 01:31:44 +0000 
2010 -------
@famo:

I re-read your first and last comments and there's something I completly 
overlooked:
You have filed this issue to the "UI" component. So a very "visual" and general
stuff concerning most of the time the display and look&feel of OOo (dialogs,
toolbars, appearance...).

So now I don't understand your report anymore :(

Please mention very concrete occurrences of what you describe: where should what
look how when you do what?
(Ex:
- importing a csv in Calc - Dialog view and data insertion?
- inserting a formatted field in Writer?
- AutoCorrection in Writer tables
- ...?) :)

To your other comments I can give you an answer at rhetorical level even if I
missed the full content: :)

> In the following points you are contradicting yourself IMHO:...
>> "In other words, the machine has to adapt to the people, not the contrary."
...
>> "... why should we (software makers) respect locales and standards if we give
the user the
possibility to break those standards?"

No I don't :) Because with "standards" I didn't mean "computer standards" but
"locale standards" which pre-existed when the computer technology decided to
translate them - maybe with bugs? - for the machine.

I meant standards defined by country governments (so let's talk about "humans"),
not the interpretation of those made by non-native computer specialists.

Your request sounds to me right now like: "I want to use your grammar checker
but I want it not to mark 'he doesn't know *no*thing' as correct"...

-> contradiction

In other words: it sounds to me as if you want a software to give you the
opportunity to overrule human rules (grammar/decimal sign/thousand separator)
with your own (as person) needs. Am I wrong?


> Also in 1) you mention your locale has spaces as thousands separators.
> This fact (almost) makes the whole discussion obsolete, because this means OOo
> should have/had this possibility already in the fist place! (In order to
> maintain / not break locale standards.)

It does have! If you have the correct locale (while importing, in the UI... or
whatever... it depends of what you mean - "what, where, when"...)

Once again: please give concrete examples.

3) To your alternative proposals: we will discuss this further when we will have
first defined "what, where, when" :)



I'd like to stress followings:
- My "feeling" is (Just "feeling" because I know now I might not have fully
understood you) that your request is not an improvement but a regression.
- But the way you express it is worth of a discussion.
- That I should normally reassign to the general "requirements" pile where it
might remain untouched during decades...
- And that I'd like your proposal to be seriously analyzed before that term. :)

So once again: please expose this again on disc...@ux.openoffice.org.
There, you will get real time attention from very different people but all
committed in improving our software.



---------------------------------------------------------------------
Please do not reply to this automatically generated notification from
Issue Tracker. Please log onto the website and enter your comments.
http://qa.openoffice.org/issue_handling/project_issues.html#notification

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@ui.openoffice.org
For additional commands, e-mail: issues-h...@ui.openoffice.org


---------------------------------------------------------------------
To unsubscribe, e-mail: allbugs-unsubscr...@openoffice.org
For additional commands, e-mail: allbugs-h...@openoffice.org

Reply via email to