Bug 37477

Summary: FILEOPEN ascii text with linefeeds doesn't open in writer
Product: LibreOffice Reporter: noname <a6569208>
Component: WriterAssignee: Not Assigned <libreoffice-bugs>
Status: RESOLVED INVALID    
Severity: normal CC: LibreOffice, sasha.libreoffice
Priority: medium    
Version: 3.4.0 RC1   
Hardware: x86 (IA32)   
OS: Windows (All)   
Whiteboard:
Crash report or crash signature: Regression By:
Attachments: text file with linefeed
text import window
text is opened in calc instead of writer

Description noname 2011-05-22 14:16:52 UTC
Created attachment 47017 [details]
text file with linefeed

If you open an ASCII text file which only has linefeeds (0a) in writer, the new preview window displays it correctly. But after pressing 'OK', it doesn't open it in writer, but in *calc* instead.
Example included.

Win2k [LibreOffice 3.4.0 OOO340m1 (Build:11)]
Comment 1 Rainer Bielefeld Retired 2011-05-22 23:35:32 UTC
NOT reproducible with "LibreOffice 3.4.0RC1  – WIN7  Home Premium  (64bit) German UI [OOO340m1 (Build:11)]". Might be related to particular OS and / or LibO settings?.

@reporter:
May I ask you to read  hints on <http://wiki.documentfoundation.org/BugReport> carefully?
Then please:
- Attach screenshots with comments (you can add information using LibO DRAW
  and then attach your screenshot with comments as PDF) if necessary
- Contribute a step by step instruction containing every key press and every 
  mouse click how to reproduce your problem 
- add information 
  -- what File dialog you use (OS or LibO)?
  -- how you get the mentioned "preview window". I see something like that
     when I use WIN file dialog.
  -- what exactly is unexpected
  -- and why do you believe it's unexpected
  -- concerning your OS default program settings for ".txt"
  -- concerning your localization (UI language)
  –- other Libo settings that might be related to your problems 
  -- how you launch LibO
  -- everything else crossing your mind after you read a.m. URL

Can you please file Bug reports with status UNCONFIRMED if your are not absolutely sure that you contributed all required background information and that the problem will be reproducible with information you can provide? 

Thank you!
Comment 2 noname 2011-05-23 11:39:36 UTC
Created attachment 47061 [details]
text import window
Comment 3 noname 2011-05-23 11:40:46 UTC
Created attachment 47062 [details]
text is opened in calc instead of writer
Comment 4 noname 2011-05-23 12:06:41 UTC
@Rainer

Sorry for not producing enough information. My very first report and not enough time. 

- Screenshots attached.
- File Dialog is OS type.
- Win2k pro sp4 [LibreOffice 3.4.0 OOO340m1 (Build:11) US UI]
- Locale set to Dutch.

To reproduce:

- 'file' -> 'open'
- Select file.
- Now you end up with the new 'text import' window, see screenshot https://bugs.freedesktop.org/attachment.cgi?id=47061.
- Select 'Fixed Width'.
- [Western Europe ISO-8859-1]
- Deselect everything else.
- Press 'OK'.

Now calc opens a seperate window, with the text loaded in A1-A140 (with this file). See screenshot: https://bugs.freedesktop.org/attachment.cgi?id=47062

Works when selecting 'insert' -> 'file' and set in the old ascii window, paragraph break to LF.
Comment 5 Rainer Bielefeld Retired 2011-06-06 02:18:37 UTC
@xdmx:
Numbered items for the step by step instruction will ease to reference to your observations for other users.
I still can't reproduce your problem. It's crystal clear that the result will be a spredsheet when you get the CALC text import dialog after you double clicked the document in the file open dialog. The interesting question ix WHY you get the CALC text import dialog for "COPYING.txt" after double click in the file open dialog. 

I can see your results when I open your sample document from WIN Explorer after I selected CALC as default application for *.txt. But even with that selection LibO will open your sample document in WRITER from file open dialog. 

What are your results from WIN Explorer?
Comment 6 noname 2011-06-06 10:33:09 UTC
When opening the text file from WIN Explorer selecting Writer (default set to notepad), I get the old 'ASCII filter options' window. Writer then imports the file correctly.
Also when selecting the file directly from 'File' -> 'Recent Documents', Writer opens the file correctly.
But when choosing from within Writer (new project), I get the 'text import window', after which the file loads in Calc.
Comment 7 Rainer Bielefeld Retired 2011-06-22 10:18:22 UTC
@xdmx:
We don't have had the breakthrough until now ;-)
In between you contributed a lot of information, unfortunately still many fragments are missing, we never got a complete step by step instruction (for example you never told the document type settings in file open dialog). I did all tests with File Dialog from LibO Start Center and OOo dialog, and every thing works fine for me except situation from "Bug 38479 - FILEOPEN *.txt csv table in Writer althoug "Spreadsheets" file type selected".

In general all the same result with OS dialog, nothing unexpected.

What the heck means "choosing from within Writer (new project)"?

BTW, the CALC text import dialog is not new.

The only chance I currently see is that you attach a Presentation with screenshots for every step similar to the one from Bug 34451. May be so I can find out the very little something that causes the different behavior (but it also might be caused by the different OS Version). 
For that please use English LibO UI!
Comment 8 Rainer Bielefeld Retired 2011-08-12 10:31:25 UTC
@xdmx:
Any idea how we can get this from the desk? Still a problem for you with 3.4.2?
Comment 9 noname 2011-08-13 10:39:39 UTC
This problem still exists with LO 3.4.2

- opening with icon = ok
- 'insert->file' = ok
- 'file->open' & selecting 'text encoded' in the dialog window = ok
- 'file->open' & selecting the text = not ok
- open the file from the main libreoffice window (the one where you can start the different programs) = not ok

Do you have any idea what to check next (register parameter, LO setting) ?
And why does the text loads fine when setting 'encoded' ?
Maybe 'encoded' should be set as default then.
Comment 10 Rainer Bielefeld Retired 2011-08-13 23:15:17 UTC
(In reply to comment #9)
 
> Do you have any idea what to check next 

Unfortunately not, except that you could try with a renamed user profile (you know, in Application Data ...) May be so we can limit the possible roots a little.
Comment 11 noname 2011-08-14 11:56:10 UTC
Renaming the user profile didn't help at all.

Installed LibreOffice 3.3.4 OOO330m19 (Build:401) and opening the ascii file now works correctly.

I expect, when I install 3.4.x again (in an empty directory), the file doesn't load the way it should.
Comment 12 Björn Michaelsen 2011-12-23 12:07:43 UTC
[This is an automated message.]
This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it
started right out as NEW without ever being explicitly confirmed. The bug is
changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back
to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases.
Details on how to test the 3.5.0 beta1 can be found at:
http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1

more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Comment 13 Björn Michaelsen 2011-12-23 17:02:37 UTC
needinfo keyword redundant by needinfo status.
Comment 14 sasha.libreoffice 2012-01-06 00:37:59 UTC
I can reproduce this behaviour only if rename extension of original file to .CSV. My by on Your computer Windows configured to open txt files in Excel or Calc by default?
Comment 15 sasha.libreoffice 2012-04-12 03:21:03 UTC
Resembles Bug 38310, but here is Windows specific bug, and there is Linux specific
Comment 16 Florian Reisinger 2012-08-14 14:00:43 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 17 Florian Reisinger 2012-08-14 14:01:50 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 18 Florian Reisinger 2012-08-14 14:06:32 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian
Comment 19 Florian Reisinger 2012-08-14 14:08:34 UTC
Dear bug submitter!

Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs.

To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement

Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem.

Yours!

Florian