From ca8ca8c28742879220f3ff88ae0d71c8d69b11cd Mon Sep 17 00:00:00 2001 From: Kohei Yoshida Date: Mon, 10 Mar 2014 14:02:00 -0400 Subject: fdo#75950: Just set the right grammar and be done with it. Using the Excel A1 syntax with custom opcode was probably a hack back in the day. These days we can just set the right grammar and expect the compiler to do the right thing. Change-Id: Iae98f9f09a7da0b7b9549e06308d5d313bbff1ea --- sc/source/filter/excel/xeextlst.cxx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'sc/source/filter/excel/xeextlst.cxx') diff --git a/sc/source/filter/excel/xeextlst.cxx b/sc/source/filter/excel/xeextlst.cxx index 92fb6c6bac7f..852647c33cfc 100644 --- a/sc/source/filter/excel/xeextlst.cxx +++ b/sc/source/filter/excel/xeextlst.cxx @@ -63,7 +63,7 @@ XclExpExtCfvo::XclExpExtCfvo( const XclExpRoot& rRoot, const ScColorScaleEntry& if(pArr) { aFormula = XclXmlUtils::ToOUString( GetRoot().GetDoc(), rSrcPos, - pArr->Clone(), GetRoot().GetOpCodeMap() ); + pArr->Clone()); } maValue = OUStringToOString(aFormula, RTL_TEXTENCODING_UTF8 ); } -- cgit