On Mon, May 19, 2008 at 9:05 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > Ok, is it possible that these are not genuine plain text only files? > > How are they created in the first place? Is there something in the file that > makes OO think that calc is more appropriate than writer?
They are are plain text files. This one in particular was created with xemacs on Windows. I can verify that they are plain LF-line ending text files by looking at them in a hex editor. OO Writer is the only program that has this issue. > Just trying to think past the obvious. > > You could create a file that you know will be plain text at a command prompt > like this: > > c:\>echo blah > blah.txt > > and see what writer does with that Well, in the Windows command shell, creating a text file that way works fine in OO Writer. However, using MinGW's bash shell echo in the same way, OO Writer still has the problem. The only difference between the two is the windows shell echo uses CRLF line endings, the bash shell echo uses LF line endings. Going off this, I took the original file that caused problems (which, like I mentioned in earlier post, has LF line endings) and converted the line endings to CRLF and lo and behold it opened in Writer. Therefore it appears that OO Writer chokes (quite consistently on my system at least, I've been able to intentionally reproduce it 100% now) on text files with LF line endings under Windows, and for some reason attempts to open them in OO Calc instead (to rant, OO Writer shouldn't be making decisions like this at all -- if I wanted to use Calc I would've double-clicked the Calc icon not the Writer icon). However, like I mentioned, it does work if I choose the "Text Encoded" file type from the load dialog. The correct behavior should be that the ASCII Filter Options dialog is display for the other 3 options (Text Files, All Files, and Text Documents) as well, rather than the Calc import data dialog. Jason > > Neil > > Jason Cipriani wrote: >> >> Neil, >> >> Thanks for your quick reply. >> >> On Mon, May 19, 2008 at 8:22 PM, [EMAIL PROTECTED] <[EMAIL PROTECTED]> >> wrote: >> >>> >>> I can't replicate your problem on WinXP OO 2.4. It opens a text doco fine >>> in >>> writer for me. >>> >>> However when you go File | Open in writer what happens if you select >>> "Text >>> Documents" or "Text (*.txt)" in Files of Type? >>> >> >> I actually did try "Text (*.txt)" already and it had no effect, but >> now I am trying some other options, and: >> >> "All Files (*.*)" -- doesn't work, opens in Calc >> "Text Documents" -- doesn't work, opens in Calc >> "Text (*.txt)" -- doesn't work, opens in Calc >> "Text Encoded (*.txt)" -- works, opens in Writer! >> >> So when I choose Text Encoded, it works (displays ASCII filter options >> first, initial character set selection is Windows-1252, if that's >> significant). >> >> Looking at the text file, it uses LF line endings only (it is plain >> ASCII text, not Unicode; also my language is set to US English in >> Windows, fyi). Maybe that is somehow affecting the decision? This >> doesn't seem right, though, it's clearly not what I want to happen, >> because I'm opening the file from the file menu in Writer, not in >> Calc. >> >> I can't explain why it's happening but at least I can open the document. >> >> Thanks, >> Jason >> >> >>> >>> Neil >>> >>> Jason Cipriani wrote: >>> >>>> >>>> When I start Writer, and go to File -> Open and choose a .txt file, it >>>> then displays the data import dialog and opens it in Calc instead >>>> (...huh?). I don't want this to happen. I want to open the file in >>>> Writer. Currently the only way I can do this is open the file in >>>> notepad then copy + paste the text into writer. >>>> >>>> I'm using: >>>> Windows XP SP2 >>>> OpenOffice.org 2.4.0 >>>> Default program for .txt files is notepad. >>>> >>>> Thanks, >>>> Jason >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >>> >> >> --------------------------------------------------------------------- >> 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] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
