On Tue, May 20, 2008 at 1:43 AM, Joe Smith <[EMAIL PROTECTED]> wrote:
> This probably is a bug, but it's not the biggest problem here.
>
> An easy way to avoid the issues is to not use File > Open at all, but
> instead use File > New > Text Document, then Insert > File. That imports the
> text file contents into an unnamed Writer document: much safer and there's
> no question about what app will open the file.
While that works, too, that's about as acceptable as opening the file
in Notepad then copy + pasting it. "File -> Open" isn't the kind of
thing that should require a workaround at all. If that's true then
either:
a) File -> Open should do exactly what File -> New then Insert -> File
does (I'm not sure why it wouldn't), or...
b) .txt files should be removed from the file open dialog filter,
since they aren't guaranteed to be opened in a consistent way.
I don't see why "Text Files" should exist as a separate file type from
"Encoded Text Files" either. It would make sense to get rid of the
encoded option, and just make All Files / Text Documents / Text Files
behave that way all the time for .txt...
The problem is only a minor annoyance at most (it does have a high
wtf-factor though), but fixing basic functionality seems good ("File
-> Open" in Writer should "open a file in Writer", I would think --
with no workarounds required). I didn't find it in the bug reports, I
will report it soon -- with any luck maybe it is an easy fix to make.
Jason
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
