Re: [tdf-discuss] Calc usability issue (autocorrect of small letter to capital letter)

2011-03-10 Thread Kevin André
2011/3/8 Irmhild Rogalla irmhild.roga...@institut-pi.de

 Am 08.03.2011 16:14, schrieb Kevin André:

 Calc seems to autocorrect a small letter to a capital letter after a dot
 character.

 This is not a bug, it's a feature ;-)
 But you can stopp it:
 In Calc choose
 - Tools - AutoCorrect Options ...

Turning it off completely isn't the right solution :-)
Autocorrection makes mistakes sometimes, and a user should be able to
correct such mistakes when they happen. But that's not possible in
Calc right now (though it is possible in Writer).

By the way, did I send this to the right list? Or should I've sent it
to libreoff...@lists.freedesktop.org instead?

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***


[tdf-discuss] Calc usability issue (autocorrect of small letter to capital letter)

2011-03-08 Thread Kevin André
Calc seems to autocorrect a small letter to a capital letter after a dot
character.
But a dot character does not always mean the end of a sentence; in this case
it was used for an abbreviation. And sadly there is no way to undo a wrong
autocorrection: pressing undo will revert the entire input of the cell.
Please provide a way to undo the autocorrection, or make calc realise that
when a user changes 'R' to 'r' in a cell it shouldn't make it an 'R' again
:) That's really frustrating.

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***


Re: [tdf-discuss] Re: Do not support writing to OOXML format

2010-12-31 Thread Kevin André
On Fri, Dec 31, 2010 at 11:07, Gordon Burgess-Parker gbpli...@gmail.com wrote:

 1. It is arrogant to return a document in a format different to that which
 was sent to you. (That's why email clients always reply in the same format
 in which the original message was received)

I agree. And users will wonder why they can open a document they
received, make some simple changes, but are asked for different name
when saving the file. They will say why can't this program simply
save my changes?.

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***


Re: [tdf-discuss] Re: Do not support writing to OOXML format

2010-12-31 Thread Kevin André
On Fri, Dec 31, 2010 at 11:51, Ian Lynch ianrly...@gmail.com wrote:
 On 31 December 2010 10:37, Kevin André hyperquan...@gmail.com wrote:

 On Fri, Dec 31, 2010 at 11:07, Gordon Burgess-Parker gbpli...@gmail.com
 wrote:

  1. It is arrogant to return a document in a format different to that
 which
  was sent to you. (That's why email clients always reply in the same
 format
  in which the original message was received)

 I agree. And users will wonder why they can open a document they
 received, make some simple changes, but are asked for different name
 when saving the file. They will say why can't this program simply
 save my changes?.


 You can get away with being arrogant when you have 80% of the market.

Right. But LibreOffice doesn't have that kind of market share...

 Most
 of the people using a WP have no idea about file formats, they will assume
 if it comes in as  it needs to go out as . (Actually a lot will
 never even have used save as..) If there is no facility to do this there is
 a reasonable chance they will reject the use of the software out of hand.

Indeed. I argued that forcing users to save an OOXML document in
another format is something that users will not understand at first,
and they probably won't like it either.
As for the save as, with the read-only OOXML policy they will see a
dialog appear that they only expect to see when saving a brand new
document (that has no filename yet) or when explicitly doing save
as.

 This isn't about logic to a sophisticated computer user, it is about the
 average user who has no technical knowledge and has picked up a WP by trial
 and error.

And that is why I think it's a bad idea to have the application do
something they do not expect.

 MS by luck or judgement have been very good at exploiting
 ignorance. School systems don't teach word processing, they teach MS Word.
 It's why we need better education and a certification programme for users
 that covers stuff like file formats and the principles of WP not just one
 product.

Better education for users would be the optimal solution, but it's not
something you can force to happen. And it will not 'fix' all those
people that already got their 'education' in the past.

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***


Re: [tdf-discuss] Re: Do not support writing to OOXML format

2010-12-31 Thread Kevin André
On Fri, Dec 31, 2010 at 15:31, RGB ES rgb.m...@gmail.com wrote:
 A possible compromise???: move all (I mean ALL) non native formats to
 the Export menu and let save/save as for the native formats only.
 Also, disable the possibility to change the default format for saving
 documents: in my experience on forums, many problems are fixed when
 you explain users that it is not good idea to use ms formats to
 _store_ files, that they need to use ODF to store and export only when
 needed.

There are still people who can actually use OOo instead of MSO,
because of the option to change the default format.

I would suggest the following instead. Support OOXML completely, but
when the user saves his/her document in a proprietary format display a
confirmation message which says something like: You are saving your
file in a proprietary format. We cannot guarantee that the file will
still open correctly in another program. Please use an open file
format for saving your document if possible. Are you still sure you
wish to save in the current format? And display a checkbox below that
can disable the message, or maybe add a note You can disable this
message by going to Options-. and have no checkbox at all. And
the message would appear by default even for the binary MS formats
(.doc, .xls, .ppt, ...).

MS Office does the same thing when saving in ODF format, and they seem
to lack an option to disable the message, even when the document to be
saved uses only features that are completely supported by ODF.

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***


Re: [tdf-discuss] Re: Do not support writing to OOXML format

2010-12-31 Thread Kevin André
On Fri, Dec 31, 2010 at 17:14, Steven Shelton ste...@sheltonlegal.net wrote:

 On 12/31/2010 10:03 AM, Kevin André wrote:
 I would suggest the following instead. Support OOXML completely,
 but when the user saves his/her document in a proprietary format
 display a confirmation message which says something like: You are
 saving your file in a proprietary format. We cannot guarantee that
 the file will still open correctly in another program. Please use
 an open file format for saving your document if possible. Are you
 still sure you wish to save in the current format? And display a
 checkbox below that can disable the message, or maybe add a note
 You can disable this message by going to Options-. and have
 no checkbox at all. And the message would appear by default even
 for the binary MS formats (.doc, .xls, .ppt, ...).

 This is a much better idea. However, I should note that even ODF
 files--despite the hype--are not 100% on preserving formatting when
 moved from one application to another. I have my letterhead saved as
 ODF done in OOo, but when I open it in AbiWord the formatting is all
 over the place.

I know. But users need to be informed, even if it's with a short
message that is not 100 percent accurate.
Maybe a longer explanation could be provided in a help file or
something, and then provide a reference to it from the short message.

-- 
Unsubscribe instructions: E-mail to discuss+h...@documentfoundation.org
Archive: http://listarchives.documentfoundation.org/www/discuss/
*** All posts to this list are publicly archived for eternity ***