To comment on the following update, log in, then open the issue:
http://www.openoffice.org/issues/show_bug.cgi?id=92974
------- Additional comments from [EMAIL PROTECTED] Sun Aug 31 10:39:20 +0000
2008 -------
You didn't see a difference between the failed and okay files, so I tried
opening them in different applications: The failed one is a failure in Notepad
but okay in WordPad. Since the extension .doc opens WordPad but also Microsoft
Word whereas .txt opens Notepad, and .txt allows more generic cross-platform
compatibility, Notepad compatibility is important.
The main failure is that paragraphs are combined into one very long paragraph.
Also, it adds a mysterious string to the front ("" without quote marks),
probably to tell OOo what format it's in but still not shown in Text Encoded, so
keeping Text Encoded is helpful for that reason, too.
Some applications apparently can get around problems (as you noticed) but if we
can get rid of the problem in the first place compatibility will go up.
Abbreviated summary of my test, while running Gnome desktop but no JRE:
-- New file via Paste Special of unformatted (non-HTML) text.
-- Save as Text Encoded into a subfolder (not root).
-- Choose ISO-8859-1 and CR&LF.
-- Leave file open on screen.
-- Select all text in the file.
-- Delete all.
-- Paste Special new content.
-- Give Save As command and see Save dialog.
-- Go up one directory level (going up is important).
-- Create new subdirectory in same medium (same flash stick, disk, etc.).
As a result, you'll have gone up, over, and then down in the directory
hierarchy.
-- Don't do anything about file type except to confirm any message.
-- Save.
The result will be that the first file you saved is Text Encoded but the second
one is Text, not Text Encoded. If you read the cautionary dialog carefully, you
saw that, but most people will easily miss it, and there's no reason within user
usability why the change should occur unsolicited.
I'm not sure that Paste Special is important, versus typing or pasting, but I
mention it because it's relevant to my work.
I think going up a directory level is the key, that apparently being when Text
Encoded is forgotten and Writer judges the file type rather than remembering
your setting, thus changing to Text.
Perhaps someone can repeat the test on OOo's latest beta. My version is native
(and only recently released). Not everyone can use JRE, and I don't, so the test
should be without it. Gnome and KDE have different effects, so the test should
be with Gnome.
Either the unsolicited change should be stopped or a separate alert should be
inserted so the user can reselect the desired format.
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]
