Issue 1145 - Date recognition broken - "feature" should be configurable
Summary: Date recognition broken - "feature" should be configurable
Status: CLOSED FIXED
Alias: None
Product: Calc
Classification: Application
Component: code (show other issues)
Version: 632
Hardware: PC Linux, all
: P2 Trivial (vote)
Target Milestone: ---
Assignee: frank
QA Contact: issues@sc
URL:
Keywords:
: 22315 25201 (view as issue list)
Depends on:
Blocks:
 
Reported: 2001-06-29 23:24 UTC by issues@www
Modified: 2013-08-07 15:15 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 issues@www 2001-06-29 23:24:49 UTC
I have had many problems with data files containing text looking vaguely like
dates, but _not_ being dates at all. For instance I have a text file with the
value 20-29 in a column, by which a mean a _range_. I want this to be considered
as text. But the spreadsheet tries to convert those strings into dates, giving
meaningless results and corrupting my data. I can't find a way to turn this
feature off.

The date recognition feature should be configurable (at least at an on/off
level).
Comment 1 frank 2001-07-02 08:58:30 UTC
Hi Didier,

it's yet configurable. If you have such values in a column, select the range
(column) where these values appear, choose format cells from the context menu
and go to the Tabpage Numbers. Select the category Text and press Ok. That's it.

Best regards
Frank
Comment 2 frank 2001-07-02 08:59:16 UTC
It's not an Issue.
Comment 3 frank 2001-07-02 10:35:23 UTC
Hi Didier,

I've found out, that you import comma separated values. To avoid date
recognition on import of such files simply select the column with such values
(in the import dialog) and set the column type to text. This should solve your
problem.

Best regards
Frank
Comment 4 issues@www 2001-07-07 12:12:17 UTC
Hi Frank,
thanks for your feedback. If I specify a column of type text when importing my
CSV file, this works at first. But then I try to make a pivot table (DataPilot)
from this data, and my headers are corrupted again because they're being
mistaken for dates. So I stand by my original statement that the automatic date
recognition is too intrusive. IMHO, there should never be a feature which
corrupts data unless you take special care to avoid it. Why not consider as
dates only what the user specified as such ?
Best regards,
                    Didier
Comment 5 frank 2001-07-09 06:43:37 UTC
Hi Didier,

as I stated in my first answer, it's configurable. 

The bug is that Datapilot changes textformat to Date format. So I reopened the
Issue.

Frank
Comment 6 frank 2001-07-09 06:44:19 UTC
.
Comment 7 niklas.nebel 2001-07-17 13:15:13 UTC
Must change the data pilot field name handling.
Comment 8 Unknown 2001-11-08 23:05:49 UTC
changing QA contact from bugs@ to issues@
Comment 9 frank 2003-10-28 08:11:16 UTC
nothing for ms_interop., so no blocking of 21783
Comment 10 niklas.nebel 2003-11-13 15:42:35 UTC
*** Issue 22315 has been marked as a duplicate of this issue. ***
Comment 11 ooo 2004-02-09 00:33:10 UTC
*** Issue 25201 has been marked as a duplicate of this issue. ***
Comment 12 niklas.nebel 2004-06-01 09:22:03 UTC
Fixed with the changes for numerical grouping on CWS "grouping".
Comment 13 niklas.nebel 2004-07-20 09:32:16 UTC
reopening to reassign
Comment 14 niklas.nebel 2004-07-20 09:32:43 UTC
reassigning to QA for verification
Comment 15 oc 2004-07-30 12:58:10 UTC
reset resolution to fixed
Comment 16 oc 2004-07-30 12:58:45 UTC
verified in internal build cws_grouping
Comment 17 frank 2004-08-12 10:34:32 UTC
found integrated on src680m50 using Linux, Solaris and Windows version
Comment 18 mfrasca 2008-04-11 08:13:03 UTC
if you stumble on this issue, you might want to check
http://www.openoffice.org/issues/show_bug.cgi?id=87999
(which is still open) and vote for it.