Apache OpenOffice (AOO) Bugzilla – Full Text Issue Listing |
Summary: | Wrong handling of Addin functions, which are also core functions | ||
---|---|---|---|
Product: | Calc | Reporter: | Regina Henschel <rb.henschel> |
Component: | save-export | Assignee: | AOO issues mailing list <issues> |
Status: | CONFIRMED --- | QA Contact: | |
Severity: | Trivial | ||
Priority: | P3 | CC: | daniel.rentz, issues, ooo |
Version: | OOo 3.2 | ||
Target Milestone: | --- | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Latest Confirmation in: | --- |
Developer Difficulty: | --- |
Description
Regina Henschel
2010-06-17 21:00:57 UTC
Saving ISEVEN_ADD as ISEVEN for ODF 1.2 is on purpose. We don't want two different functions that do the same. @dr: How could we tell Excel that a function internal to OOo should be an AddIn function in Excel? This applies to all functions that have ScCompiler::AddInMap.bMapDupToInternal=true in sc/source/core/tool/odffmap.cxx, so the Excel export should consider that. We may have to add some OpCode mapping to the struct respectively replace bMapDupToInternal with an OpCode to look functions up for export, but I do not want to maintain several places in the Excel export. |