https://bugs.documentfoundation.org/show_bug.cgi?id=146440
Eike Rathke <er...@redhat.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |NEW
Ever confirmed|0 |1
--- Comment #3 from Eike Rathke <er...@redhat.com> ---
It's complicated..
Formula = ... goes via ScCellObj::setFormula() (an implementation of
css::table::XCell::setFormula()) ScDocFunc::SetCellText() the bEnglish=true
case that for the result of ScStringUtil::parseInputString() distinguishes
between ScInputStringType::Formula, ScInputStringType::Number and
ScInputStringType::Text and does not apply any number format for the
ScInputStringType::Number case, apparently on purpose, but does force-apply the
Text format for ScInputStringType::Text via ScDocFunc::SetStringCell()
ScDocument::SetString() ... ScColumn::ParseString() for content that could be
numeric (the leading ' apostrophe was removed in
ScStringUtil::parseInputString()).
FormulaLocal = ... goes via ScCellObj::SetOnePropertyValue() SC_WID_UNO_FORMLOC
ScCellObj::SetString_Impl() ScDocFunc::SetCellText() the bEnglish=false case
ScDocFunc::SetNormalString() ScDocument::SetString() ...
ScColumn::ParseString() that does apply a number format if
aParam.mbDetectNumberFormat=true and the detected format is not compatible with
the previous format or none was set.
Questions remains, what would actually be expected for all cases.
--
You are receiving this mail because:
You are the assignee for the bug.
