Issue 76602

Summary: SYLK: support <ESC>N escaped characters and offer choice of text encoding
Product: Calc Reporter: kpalagin <kpalagin>
Component: open-importAssignee: AOO issues mailing list <issues>
Status: ACCEPTED --- QA Contact:
Severity: Trivial    
Priority: P3 CC: issues, laalaalay, rail_ooo, scottmsanders, vz-openoffice
Version: OOo 2.2   
Target Milestone: ---   
Hardware: All   
OS: All   
Issue Type: ENHANCEMENT Latest Confirmation in: ---
Developer Difficulty: ---
Description Flags
Problematic SYLK file
Screenshot of other spreadsheet with SYLK file loaded none

Description kpalagin 2007-04-23 08:16:37 UTC
Please see attached file. In cells A3 and A4 it contains Russian characters.
Calc does not import the file correctly. Competing spreadsheet shows Russian 
characters just fine (see attached screenshot).
Comment 1 kpalagin 2007-04-23 08:17:36 UTC
Created attachment 44601 [details]
Problematic SYLK file
Comment 2 kpalagin 2007-04-23 08:51:45 UTC
Created attachment 44602 [details]
Screenshot of other spreadsheet with SYLK file loaded
Comment 3 frank 2007-04-23 10:12:33 UTC
Hi Eike,

as the SYLK Format is ASCII based, we should offer the Encoding dialog as we do
for Lotus or DBase files.

Comment 4 ooo 2007-04-23 17:17:54 UTC
Well, actually here it is _not_ ASCII based, that's what this issue is about ;-)

FYI: Currently. SYLK files are opened in the text encoding of the session the
application runs in. So usually the result is fine if the file is opened on the
same machine where it was written.
Comment 5 kpalagin 2007-04-23 18:18:46 UTC
are you talking about localle setting or UI language?
Also, what should I choose to import this particular file correctly?

Thanks a lot.
Kirill Palagin.
Comment 6 ooo 2007-05-02 14:18:52 UTC

> are you talking about localle setting or UI language

Neither.. the process encoding is determined from the environment (as is
the locale if set to Default under Tools->Options), e.g. en_US.UTF-8 is
UTF-8 encoding, de_DE would be ISO-8859-1 encoding, ro_RO.ISO8859-2 the
ISO-8859-2 encoding. A Western European Windows may be Windows-1252
encoding. Alas, this doesn't help here..

> Also, what should I choose to import this particular file correctly?

Currently there is no way to do so if you don't find a specialized tool,
because the file isn't in any standard encoding. The <ESC>N mechanism
used is some Multiplan/microsoftish rubbish to encode non-ASCII ISO
codes, whatever they may call ISO there.. see the "Summary of all currently
used sylk fields" download.

Furthermore, even Excel can't handle that properly in different
environments, it depends on what encoding the escape sequences are
translated. If I load the file in an English Excel on an English Windows
I get Umlauts and other ISO-8859-1 (respectively Windows-1252)
characters, but I don't see any Cyrillic character as shown in your
attached JPG.

So, what this issue will be about is to convert the escape sequences,
and offer a choice of different encodings as well.

Comment 7 kpalagin 2007-05-29 21:12:10 UTC
Thanks for the response. 
Comment 8 rail_ooo 2008-03-28 06:35:56 UTC
add CC
Comment 9 xlaalaa 2009-04-17 20:54:21 UTC
add CC too
Comment 10 Marcus 2017-05-20 11:13:34 UTC
Reset assigne to the default "".