To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=84774
User nicklevinson changed the following:
What |Old value |New value
================================================================================
CC|'' |'nicklevinson'
--------------------------------------------------------------------------------
------- Additional comments from [EMAIL PROTECTED] Wed Jul 2 00:22:00 +0000
2008 -------
This follows issue 91199, since closed as a duplicate of this one (84774) which
I hadn't found in a keyword search. Issue 84774 is similar but differences
exist, and I was asked for an attachment, which I'll try to supply here, if I
can figure out how in time. This response is partly in light of comments within
91199.
Most users of a word processor opening a document will expect it to open in the
word processor. That's not an enhancement. The violation of the normal
expectation is a failure, thus a defect.
I've now seen the priority-setting information. Thank you. I accept the
correction.
Here are the steps for opening Text-Encoded-test.txt in read/write mode:
Writer > File > Open > select file. The unlabeled drop-down list for which the
tooltip says "Select which types of files are shown" already reads "All files".
Click Open. Result: Text Import dialog. Set Character set to Western Europe
(ISO-8859-1) (which I used for document creation) instead of default Unicode
(UTF-8). Click OK. Calc opens with the document. Not good.
Writer > File > Open > select file. Change the unlabeled drop-down list for
which the tooltip says "Select which types of files are shown" to Text Encoded.
Click Open. ASCII Filter Options dialog already shows proper charset 8859-1 and
proper paragraph break CR & LF (I used 8859-1 for document creation and prefer
CR&LF). Click OK. Writer opens the document. That's good.
Writer > File > Open > select file. Select File type > Text documents. Leave
the unlabeled drop-down list for which the tooltip says "Select which types of
files are shown" at "All files". File type > Text documents (which includes
txt). Click Open. Result: Text Import dialog. Set Character set to Western
Europe (ISO-8859-1) (which I used for document creation) instead of default
Unicode (UTF-8). Click OK. Calc opens with the document. Not good.
Writer > File > Open > select file. Select File type > Text documents. Leave
the unlabeled drop-down list for which the tooltip says "Select which types of
files are shown" at "All files". File type > Text Encoded. Click Open. ASCII
Filter Options dialog already shows proper charset 8859-1 and proper paragraph
break CR & LF (I used 8859-1 for document creation and prefer CR&LF). Click OK.
Writer opens with the document. That's good.
How I made the file: Writer > File > New > Text Document. Enter text. File >
Save As > File type > Text Encoded; enter Name; checkmark Edit filter settings;
click Save button. Message on format or content incompatility. Click Yes. ASCII
Filter Options dialog already shows proper charset 8859-1 and proper paragraph
break CR & LF (I prefer 8859-1 and CR&LF). Click OK.
The file extension is that added automatically by OOo, namely, .txt. That's
good, since I also open, edit, and save the same file on Win machines and back
again in OOo.
When opening files, counterintuitivity occurs when the dialog proposes to open
all the files when it perhaps won't open any. It occurs again when file type's
pick list has text documents long before text encoded, leading us to apply the
former.
I understand the problem of Writer being told to open a file but not knowing
what type it is. But the solution is not to hand it off to Calc. Rather,
perhaps add a dialog after the file-open dialog has been clicked to Open when
All files has been selected and ask the user to reconsider, and state at that
point that All files and nothing in the picklist is too general, so users
change something rather than watch Calc take over and turn a memo into a
spreadsheet and not know what to do. This is a usability defect.
Version 2.4 just came out, and downloading and upgrading, in my recent
experience, take time. I imagine you already know if this fault has been fixed,
but since a search told me nothing about the issue, I doubt it was fixed for
2.4.1.
Thanks.
--
Nick
---------------------------------------------------------------------
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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
