Issue 13135 - Bibliographic indeces show all numbers (years/Volumes) as decimals
Summary: Bibliographic indeces show all numbers (years/Volumes) as decimals
Status: ACCEPTED
Alias: None
Product: bibliographic
Classification: Code
Component: code (show other issues)
Version: OOo 1.1 Beta
Hardware: Other Linux, all
: P3 Trivial
Target Milestone: OOo Later
Assignee: AOO issues mailing list
QA Contact: issues@bibliographic
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-04-07 20:04 UTC by helmerj
Modified: 2017-05-20 11:35 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 helmerj 2003-04-07 20:04:05 UTC
Hi, 
 
I use OO 1.1 beta (same with 1.0.2) to insert a bibliograpic index into a document. When I 
sample insert from the default biblio database, the created index is fine. 
 
When I add a data source (using sixpack, export to csv, OO import csv file as data source) of 
medline references and set the bibliograophic database manager to use that new database, the 
numbers show up all right (e.g. year 2000 shows as "2000") in the manager. When I use those 
references in a text and then build an index, all numbers get a decimal comma and a trainling 
zero: 
 
2000 becomes, 2000.0 and 1999 becomes 1999.0. Same is true for other numbers, like 
volume numbers. 
 
This also happens when I copy and paste the table with the new references from the new 
database into the biblio database (I figured the type (csv vs. dbase) might change 
something...). 
 
Juergen
Comment 1 helmerj 2003-04-07 20:05:30 UTC
I forgot to mention, that the column format in the database manager seems to be 
set to text for all entries and I can't make out any differences in the formating. 
 
Juergen 
Comment 2 dnwilson 2003-04-21 10:05:40 UTC
Frank, 
 
	This seems to a database issue. 
Comment 3 Frank Schönheit 2003-04-22 08:25:35 UTC
@Davin: not exactly, sorry :)

fs->os: output formatting is responsibility of the Writer. I suppose
that you for some reason assume the field is decimal - it may even be
that our CSV driver tells you this way, because it can only guess from
the .csv file. However, I suppose fields containing a year should
never contain a comma...?
Comment 4 Oliver Specht 2003-05-21 11:29:06 UTC
.
Comment 5 Frank Schönheit 2003-10-28 06:52:06 UTC
removing dependency to issue 21783 (which is the ms interop tracking
bug) - I don't think this is an interop issue. If somebody
re-introduces the dependency, please next time justify it.
Comment 6 andreas.martens 2004-06-17 14:52:43 UTC
Because of a shortage of resources we have to retarget this issue to OOo later. 
Comment 7 Marcus 2017-05-20 11:35:24 UTC
Reset assigne to the default "issues@openoffice.apache.org".