On Mon, 2008-12-08 at 20:05 +0100, Niklas Nebel wrote: > On 12/08/08 19:34, [EMAIL PROTECTED] wrote: > > Modified: cws/ooxml02/offapi/com/sun/star/sheet/FormulaLanguage.idl > > ============================================================================== > > --- cws/ooxml02/offapi/com/sun/star/sheet/FormulaLanguage.idl Mon Dec > > 8 18:33:06 2008 (r265029) > > +++ cws/ooxml02/offapi/com/sun/star/sheet/FormulaLanguage.idl Mon Dec > > 8 18:33:13 2008 (r265030) > > @@ -63,6 +63,11 @@ > > */ > > const long NATIVE = 3; > > > > + /** Function names and operators as used in the English version of > > + Excel. This formula language is also used in VBA formulas and > > + OOXML import/export. > > + */ > > + const long XL_ENGLISH = 4; > > }; > > No, the map of Excel function names is supposed to be part of the Excel > filter, and that's how the import already works.
But what's the drawback? Defining a formula language here makes it easier to use in the filters as well as VBA formula parsing since it fits nicely in the current grammar framework. To me, not doing this would be a kludge. Kohei --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
