Hi Winfried,
darn, another mail in the queue..
On Thursday, 2015-02-19 10:19:57 +0100, Winfried Donkers wrote:
> OK, then I suggest the following.
> Current situation:
> Calc UI ODF Excel
> FDIST LEGACY.FDISTFDIST
> F.DIST COM.M
Hi Eike,
> Looks good to me. However, we should keep the F.DIST.RT also in the UI for
> the case of loading it from OOXML, to prevent user worries or for users
> being used to it and resave it to OOXML as it was, and only map it to
> LEGACY.FDIST when writing to ODF, so that it will be UI FDIST wh
Hi Winfried,
On Wednesday, 2015-02-18 13:08:30 +0100, Winfried Donkers wrote:
> Ok, I suggest the following:
>
> Calc UI ODF-old names to be kept ODF-new names Excel
> F.DIST COM.MICROSOFT.F.DIST FDIST _xlfn.F.DIST
> FDISTCOM.MICROSOFT.F.DIST.RT LEGACY.FDIST _xlfn.F.DI
Resending to the dev-list...
Winfried
-Oorspronkelijk bericht-
Van: Winfried Donkers
Verzonden: woensdag 18 februari 2015 12:14
Aan: 'Eike Rathke'
Onderwerp: RE: Calc function names saved to file and backward compatibility
hi Eike,
> What we usually do is add a compatib
Hi Eike,
> What we usually do is add a compatibility name to older release branches
> so the next release there can read both, the new name and the old name,
> but continues to write the old name so earlier releases of the same
> (usually two) branches are not affected.
>
> Then for the next rele
Hi Winfried,
On Thursday, 2015-02-12 11:22:04 +0100, Winfried Donkers wrote:
> In Calc, the current situation is:
> Calc UIODF Excel
> FDIST LEGACY.FDIST FDIST
> F.DIST COM.MICROSOFT.F.DIST _xlfn.F.DIST
> F.DIST.RT COM.MICROSOFT.F.DIST.RT _xlfn.
Hi,
I'm working on tdf#40835 again and experience a problem that is easily solved
in the code, but does present backward compatibility problems in the saved
(ods) documents.
There are 2 ODF functions (FDIST and LEGACY.FDIST) and 3 Excel functions
(FDIST, F.DIST and F.DIST.RT).
In Calc, the cu
