From 4f1ce46b8d65360436e09750242101b566e6186c Mon Sep 17 00:00:00 2001 From: Maxim Monastirsky Date: Mon, 16 May 2016 17:14:37 +0300 Subject: tdf#35208 Allow choosing encoding for old Excel files Lots of BIFF2-BIFF5 files out there don't have CODEPAGE record at all, or have one with a wrong value, and/or FONT records with wrong charset value. To solve that, this patch adds a new "Choose Encoding" entry to the file picker, so that users could specify the encoding to use for a given file, instead of relying on the information that might be present (or not) inside the file. It can be also used in headless mode, e.g. --infilter="MS Excel (encoded)":61 This doesn't affect BIFF8 import, nor the default behavior when not explicitly using the "Choose Encoding" entry. Change-Id: I89d850d7679b81bd399044478fac7a02e8b7680e --- sc/source/ui/inc/docsh.hxx | 1 + 1 file changed, 1 insertion(+) (limited to 'sc/source/ui/inc') diff --git a/sc/source/ui/inc/docsh.hxx b/sc/source/ui/inc/docsh.hxx index 079b542e68dc..914f369d6ba1 100644 --- a/sc/source/ui/inc/docsh.hxx +++ b/sc/source/ui/inc/docsh.hxx @@ -398,6 +398,7 @@ public: static OUString GetLotusFilterName(); static OUString GetDBaseFilterName(); static OUString GetDifFilterName(); + static OUString GetExcelEncodingFilterName(); static bool HasAutomaticTableName( const OUString& rFilter ); DECL_LINK_TYPED( RefreshDBDataHdl, Timer*, void ); -- cgit