Issue 28246 - IEEE / Microsoft Binary Format double single precision
Summary: IEEE / Microsoft Binary Format double single precision
Status: CLOSED WONT_FIX
Alias: None
Product: utilities
Classification: Unclassified
Component: automation (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P3 Trivial (vote)
Target Milestone: OOo Later
Assignee: ab
QA Contact: Unknown
URL:
Keywords: oooqa
Depends on:
Blocks:
 
Reported: 2004-04-22 23:14 UTC by giorgiodemontis
Modified: 2008-05-17 22:59 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description giorgiodemontis 2004-04-22 23:14:42 UTC
Oristano, April 2004

Hi
I'm Italian – Sardinia Ooo End User (44 years old).

I have a bad problem converting procedure writed in ms basic to procedure 
written in OOo basic.

OOO Basic read and write from disk IEEE format. 

There are a lot of data file writed in Microsoft Basic with Microsft binary 
format (MBF).

Problem is reading and writing file that contains single and double precision 
number

What do you think about write and include in OOO native function a function for 
convert single and double precision Microsoft binary format??
I'm converting a lot of MS basic program in OOO basic, but this format for me 
is a very hard strong barrier.

Format of single and double precision in Microsoft binary format (MBF)is 
different from IEEE single and double precision format.

Differences between MBF and IEEE format
Byte and bits order is reversed on then disk 
Sign bit is not a the end but is between mantissa bits and exponent bits
( Bill  love international standards like smoke in the eyes...)

thanks 
Giorgio Demontis

Now i explain with a file, pippo.ter. I cannot read the double precision number.

This is the hex dump of file pippo.ter

Pippo.ter contains two record 30 byte each long

First record is header,  first number (2 byte integer) contains number of 
records in the file

second record is data record. 

Data record structure

First data field is a negative integer number corresponding to the record number

	Second field is a description

		Third field is a double precision number

		Fourth fieLd is a double precision number

2 byte is filler

Header 							 	Contents
 01 00 01 00 20 20 20 20-20 20 20 20 B2 DB 19 ED	 1 1, other not 
interesting
 AC 0F 4F C3 1B 11 F7 C2-F6 87 1E EF 1A EF 

 First data record 
 FF FF 70 74 30 30 30 30 30 30-30 31 00 00 00 00 	-1 pt000001 1.0 1.0
 00 00 00 81 00 00 00 00 00 00-00 81  00 00 


(1.0 double precision IEEE, writed with OOo, like 00 00 00 00 00 00 F0 3F)

Thanks 
Giorgio Demontis
Comment 1 gregor.hartmann 2004-04-23 09:30:21 UTC
Seems to be a task for you Andreas.
Comment 2 ab 2004-07-27 13:24:47 UTC
No task for OOo 2.0
Comment 3 ab 2005-07-26 10:03:32 UTC
ab->giorgiodemontis:
Sorry, but I see no priority for this issue. I'm afraid that it would mean 
a lot of work and I doubt that the old MBF format is widely used. Not
even Visual Basic has direct support for this format any more, as you 
can see here: http://support.microsoft.com/kb/q140520/

There are also some hints how this problem can be solved without
direct support in (Visual) Basic, e.g. by using a DLL they provide.

-> WONTFIX
Comment 4 ace_dent 2008-05-17 20:58:28 UTC
The Issue you raised has been marked as 'Resolved' and not updated within the
last 1 year+. I am therefore setting this issue to 'Verified' as the first step
towards Closing it. If you feel this is incorrect, please re-open the issue and
add any comments.

Many thanks,
Andrew
 
Cleaning-up and Closing old Issues
~ The Grand Bug Squash, pre v3 ~
http://marketing.openoffice.org/3.0/announcementbeta.html
Comment 5 ace_dent 2008-05-17 22:59:57 UTC
As per previous posting: Verified -> Closed.
A Closed Issue is a Happy Issue (TM).

Regards,
Andrew