Issue 32785 - Excel Export BIFF5: missing character encoding
Summary: Excel Export BIFF5: missing character encoding
Status: ACCEPTED
Alias: None
Product: Calc
Classification: Application
Component: save-export (show other issues)
Version: 680m49
Hardware: All All
: P3 Trivial with 23 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
URL:
Keywords: oooqa
: 42933 54059 58726 61401 70824 80872 102886 106869 (view as issue list)
Depends on:
Blocks: 58726
  Show dependency tree
 
Reported: 2004-08-10 14:32 UTC by tuharsky
Modified: 2013-08-07 15:13 UTC (History)
8 users (show)

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


Attachments
Original XLS doc (93.50 KB, application/vnd.ms-excel)
2004-08-10 14:34 UTC, tuharsky
no flags Details
Saved from OOo 680_m49 (17.00 KB, application/vnd.ms-excel)
2004-08-10 14:34 UTC, tuharsky
no flags Details
exported from OOo680 as SXC (11.33 KB, application/vnd.sun.xml.calc)
2004-08-10 14:35 UTC, tuharsky
no flags Details
OOo3.2-good (original) (71.35 KB, image/png)
2010-05-17 07:33 UTC, tuharsky
no flags Details
OOo3.2-bad (saved) (41.33 KB, image/png)
2010-05-17 07:35 UTC, tuharsky
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description tuharsky 2004-08-10 14:32:55 UTC
I have a XLS file. If I save it from OOo and open with OOo 111 on Windows
machine, the diacritics is gone ('?' takes place instead of dacritical symbols),
although font seems unchanged. No way to change the behavior.

If I export the file as SXC, no problems.
Comment 1 tuharsky 2004-08-10 14:34:04 UTC
Created attachment 17040 [details]
Original XLS doc
Comment 2 tuharsky 2004-08-10 14:34:45 UTC
Created attachment 17041 [details]
Saved from OOo 680_m49
Comment 3 tuharsky 2004-08-10 14:35:29 UTC
Created attachment 17042 [details]
exported from OOo680 as SXC
Comment 4 frank 2004-08-10 15:49:13 UTC
Hi,

the underlying problem is the original xls file format. It's Excel 5 and
therefore not fully supported. To avoid this problem just save in OOo format or
use Excel 97/2000/XP.

@Daniel

As discussed for fixing with target Later

Frank
Comment 5 daniel.rentz 2004-08-10 18:03:38 UTC
accepted

DR->DR: todo: nobody has implemented the CODEPAGE record in BIFF5...
Comment 6 daniel.rentz 2004-09-10 11:21:26 UTC
title adjusted
Comment 7 daniel.rentz 2005-03-23 11:12:05 UTC
*** Issue 42933 has been marked as a duplicate of this issue. ***
Comment 8 frank 2005-09-22 10:39:23 UTC
*** Issue 54059 has been marked as a duplicate of this issue. ***
Comment 9 mellonedain 2005-12-02 10:43:38 UTC
*** Issue 58726 has been marked as a duplicate of this issue. ***
Comment 10 Martin Hollmichel 2006-09-28 12:54:55 UTC
@dr,fst: duplicates and voted, we should reconsider the target !
Comment 11 daniel.rentz 2006-09-28 13:25:02 UTC
new target
Comment 12 frank 2006-10-26 14:32:56 UTC
*** Issue 70824 has been marked as a duplicate of this issue. ***
Comment 13 kpalagin 2006-11-07 11:34:32 UTC
Dear developers,
is there any chance of fixing this issue in v2.2?
This is nasty bug, that can cause loss of work for the full work day (this has
happened twice with my users).
Comment 14 kpalagin 2007-05-07 04:58:00 UTC
Daniel,
it turns out that we have customers who do use MSO95 so they need  export 
filter that correctly handles encoding.
Any chance for 2.3?

Thanks a lot for your attention.
WBR,
Kirill Palagin.
Comment 15 daniel.rentz 2007-05-22 14:45:22 UTC
I will see if there is some time to fix this in 2.3
Comment 16 kpalagin 2007-07-12 20:50:05 UTC
Daniel,
any luck?
Comment 17 frank 2007-09-03 10:39:57 UTC
*** Issue 80872 has been marked as a duplicate of this issue. ***
Comment 18 kpalagin 2007-09-14 10:35:16 UTC
Maybe for 2.4?
Comment 19 Martin Hollmichel 2007-11-09 16:52:27 UTC
change target from 2.x to 3.x according to
http://wiki.services.openoffice.org/wiki/Target_3x
Comment 20 Martin Hollmichel 2007-12-06 11:33:20 UTC
given the number of duplicates and votes set target to 3.0. sorry for the noise,
choosing 3.x seems to be an oversight of mine.
Comment 21 kpalagin 2008-03-11 16:01:38 UTC
Daniel,
are we on track for 3.0 with this issue?
Comment 22 daniel.rentz 2008-03-11 17:36:40 UTC
I am too busy to do it for myself. Maybe there is a volunteer to provide a patch?
Comment 23 forsoft 2008-05-28 22:03:28 UTC
There is an article on the Microsoft server referring to the BIFF5 file 
creation: http://support.microsoft.com/kb/150447

There is a demonstration code available for downloading there. On the first 
look, the code seems to be available for free to use in any application.

(It's a bit strange as the Microsoft seems to be supporting Open Source, but it 
looks that way. But, perhaps, I'm mistaken, somehow)
Comment 24 forsoft 2008-06-11 13:03:59 UTC
I have got yet another point.

The OpenOffice does read the Excel 95 files correctly. So, the correct 
translation from BIFF5 is implemented already. The problem is just in the 
export to the BIFF5.

It should be relatively simple to use the import code page to create a proper 
export code page. It's quite possible no other changes will be necesary.
Comment 25 daniel.rentz 2008-06-11 13:35:25 UTC
The imported codepage is not stored anywhere. Additionally, the Excel95 export
filter has to work for all files, also for new files and files imported from
other formats such as ODS and Excel97+ which use Unicode and thus do not contain
a codepage. The codepage has to be received from the operating system depending
on the current locale, and this has to work on all supported platforms (Windows,
Linux, Solaris, Mac...)
Comment 26 kpalagin 2008-10-17 08:30:37 UTC
Please see http://www.openoffice.org/issues/show_bug.cgi?id=9709#desc43 for a 
way to get system encoding.
Comment 27 pavel.lastovicka 2009-01-29 14:18:22 UTC
*** Issue 61401 has been marked as a duplicate of this issue. ***
Comment 28 kpalagin 2009-06-18 14:59:29 UTC
*** Issue 102886 has been marked as a duplicate of this issue. ***
Comment 29 frank 2009-11-13 08:36:56 UTC
*** Issue 106869 has been marked as a duplicate of this issue. ***
Comment 30 thackert 2010-01-16 17:27:23 UTC
Hello tuharsky,
I stumbled upon this issue during my TCM test for the Germanophone version of
OOO320_m9. It looks O.K. under Debian SID AMD64, but as I can neither read nor
understand the text in the file, I may be wrong ... ;) Could have a look at this
issue to confirm, if it is fixed, please? If it is fixed, it would be nice, if
you could close this issue :)
Have fun
Thomas.
Comment 31 tuharsky 2010-01-18 10:29:52 UTC
I'll test with 3.2 stable. However, with 3.1.1 the problem persists.
Comment 32 tuharsky 2010-01-18 10:30:50 UTC
I'll test with 3.2 stable. However, with 3.1.1 the problem persists.
Comment 33 thackert 2010-05-12 18:35:57 UTC
Hello tuharsky, *,
just as a reminder: Have you tested it in the meanwhile, like you wrote on Jan
18th 2010? If not: Would you be so kind to test it with 3.2 or OOO320m17, please?
TIA
Thomas.
Comment 34 tuharsky 2010-05-17 07:30:09 UTC
With OOo3.2m12(@Ubuntu10.4) bug still present. Should there be any difference
with m17?
Comment 35 tuharsky 2010-05-17 07:33:13 UTC
Created attachment 69473 [details]
OOo3.2-good (original)
Comment 36 tuharsky 2010-05-17 07:35:08 UTC
Created attachment 69474 [details]
OOo3.2-bad (saved)
Comment 37 raal 2010-05-20 18:15:01 UTC
Ubuntu 9.10, DEV300m77 - save file ihriská.xls(Original XLS doc) as excel5
crashes OOo.
- open file ihriská.xls
- save as - format excel 5
- crash  -  no crash report created 
Comment 38 niklas.nebel 2010-05-21 10:02:44 UTC
For the crash in m77, I created a separate issue (issue 111745), because the fix
for the crash doesn't resolve the encoding problem.
Comment 39 thackert 2010-05-30 07:50:09 UTC
Hello  tuharsky, *,
sorry for the delay. Too busy since my last entry, sorry ... :(
You wrote
<quote>
------- Additional comments from tuharsky Mon May 17 06:30:09 +0000 2010 -------
With OOo3.2m12(@Ubuntu10.4) bug still present. Should there be any difference
with m17?
</quote>

I have not read the release notes (neither for m12 nor for m17), but there are
always changes between the release ... ;) But as both are outdated, it would be
nice, if you could test it again with OOO320m18 ... ;)
HTH
Thomas.
P.S.: I still cannot reproduce it with the Germanophone version of OOO320m18
under Debian SID/Experimental AMD64 ... :(
Comment 40 logicdaemon 2010-05-31 13:31:10 UTC
thackert, apparently you cannot reproduce because all German letters are in 
Latin-1 codepage? See http://en.wikipedia.org/wiki/ISO/IEC_8859-1
Comment 41 urmasd 2012-01-11 18:27:56 UTC
Of course it's still here.

Also, is OpenOffice abandoned now?
Comment 42 T. J. Frazier 2012-01-11 20:09:54 UTC
Good news: OO is alive and well.

Bad news: This bug, for writing a format that's a decade out of date, is unlikely to be fixed.

More bad news: the @ openoffice.org email addresses are going away very soon. If you use one here, log in and click on the Preferences link at the top of the page, and change it. BZ is smart: you'll still have all your old issues and comments properly linked.