Issue 91199 - Writer shouldn't import Text Encoded into Calc
Summary: Writer shouldn't import Text Encoded into Calc
Status: CLOSED DUPLICATE of issue 84774
Alias: None
Product: Writer
Classification: Application
Component: open-import (show other issues)
Version: OOo 2.4.0
Hardware: Unknown Linux, all
: P3 Trivial (vote)
Target Milestone: ---
Assignee: michael.ruess
QA Contact: issues@sw
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-29 20:33 UTC by nicklevinson
Modified: 2008-07-01 08:50 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description nicklevinson 2008-06-29 20:33:11 UTC
Trying to open some files in Writer causes them to import into Calc as
spreadsheets instead. Some people report this difficulty while others report
difficulty reproducing the problem.

The issue is that Text Encoded files don't open in OOo 2.4 Writer if opening is
with "All files" in the file types menu. The solution to opening in Writer is to
set the menu to Text Encoded. Then they open in Writer.

The downside may be if you have a bunch of files in mixed formats (I usually
don't) or, worse, don't remember all their formats. I didn't try other file type
commands. Whether you set to open as read-only or read/write doesn't matter. I
didn't see any relevant setting in Calc. Changing Writer > Tools > Options >
OpenOffice.org > General > Open/Save dialogs > Use OpenOffice.org dialogs
doesn't make a difference, because after the dialog has been used is when Calc
takes over.

My files with this problem were usually edited in OOo 2.0 Beta which is 1.9.104
on a Linux platform, all as Text Encoded, or in Win 9x Notepad.

I'm using OOo 2.4.0 without Java Runtime Environment on Linux Fedora Core 4 on a
Pentium 4 laptop, coexisting with version 1.9.104.

I was able to make new text files in 2.4 Writer, so that function isn't
impaired. I kept the old OOo, so I can use that to open the files, but I'd like
to migrate completely to 2.4.

Programming suggestions, short of major: One approach: In the interim, interject
an alert or dialog if the user has opened using All files in the menu to tell
the user to try again but specify a format. Interjecting that step might be
faster than invisibly having Writer determine all the formats, if that's even
possible without errors.

Another approach is to follow the user's dialog setting by opening one file at a
time, each with a dialog asking for the format, with the file type entry preset
to the last one selected.

Thanks.

-- 
Nick
Comment 1 eric.savary 2008-06-29 21:33:30 UTC
1. From the description: it is not a P1.
Please have a look at
http://qa.openoffice.org/scdocs/ddIssues_EnterModify.html#priority

2. The issue you reprot is ("shouldn't" in the summary + description content) an
ENHANCEMENT, not a DEFECT.

3. Please attach a sample document and give a step by step description of what
you do, get and expect.
Comment 2 eric.savary 2008-06-29 21:34:33 UTC
4. Please also try a current build:
http://download.openoffice.org/680/?intcmp=1235
Comment 3 mhatheoo 2008-06-30 14:22:13 UTC
==>nicklevinson

I am dealing a lot with text encoded
so I am interessted where an issue in this could be.
but reading your text, I guess you have the wrong impression
of what the apropriate use of text-files with differing characterencoding is.
May be you need to attach a sample and inform about your usual file-extensions

Martin

Comment 4 michael.ruess 2008-07-01 08:48:47 UTC
Already tracked as issue 84774.

*** This issue has been marked as a duplicate of 84774 ***
Comment 5 michael.ruess 2008-07-01 08:50:14 UTC
Closing duplicate.