source/text/shared/optionen/detailedcalculation.xhp | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
New commits:
commit 900d30047e754b7310ffb05a67d280b6ce7b2e7f
Author: Eike Rathke <er...@redhat.com>
AuthorDate: Tue Feb 4 14:51:29 2020 +0100
Commit: Eike Rathke <er...@redhat.com>
CommitDate: Tue Feb 4 15:00:17 2020 +0100
Add href to Converting Text to Numbers
Change-Id: I0bb8d28f1f1448915f0695b0ec443fdadaba7213
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/87979
Reviewed-by: Eike Rathke <er...@redhat.com>
Tested-by: Jenkins
diff --git a/source/text/shared/optionen/detailedcalculation.xhp
b/source/text/shared/optionen/detailedcalculation.xhp
index f9bf1119e..77fa10599 100644
--- a/source/text/shared/optionen/detailedcalculation.xhp
+++ b/source/text/shared/optionen/detailedcalculation.xhp
@@ -44,7 +44,7 @@
<paragraph role="paragraph" id="par_id396740" xml-lang="en-US">How to
treat text when encountered as operand in an arithmetic operation or as
argument to a function that expects a number instead. Unambiguous conversion is
possible for integer numbers including exponents and ISO 8601 dates and times
in their extended formats with separators. Fractional numeric values with
decimal separators or dates other than ISO 8601 are locale dependent. Note that
in locale dependent conversions the resulting numeric value may differ between
locales!</paragraph>
<paragraph role="paragraph" id="par_id4086428"
xml-lang="en-US"><emph>Generate #VALUE! error:</emph> Text found where numeric
data is expected will generate #VALUE! error. Example: <item
type="input">"123.45"</item> will generate a #VALUE! error, while <item
type="input">123.45</item> not.</paragraph>
<paragraph role="paragraph" id="par_id9024628"
xml-lang="en-US"><emph>Treat as zero:</emph> Any text found where numeric data
is expected will be considered as a number of value zero. Example: <item
type="input">"123.45"</item> will map to zero, while <item
type="input">123.45</item> not.</paragraph>
- <paragraph role="paragraph" id="par_id3067110"
xml-lang="en-US"><emph>Convert only if unambiguous:</emph> If the text
represents a valid and unambiguous numeric value, convert it. Example: <item
type="input">"123.456"</item> will generate a #VALUE! error because the text
contains a separator, while <item type="input">"123456"</item> will
not.</paragraph>
+ <paragraph role="paragraph" id="par_id3067110"
xml-lang="en-US"><emph>Convert only if unambiguous:</emph> If the text
represents a valid and unambiguous numeric value, convert it. Example: <item
type="input">"123.456"</item> will generate a #VALUE! error because the text
contains a separator, while <item type="input">"123456"</item> will
not.<br/>See <embedvar href="text/scalc/guide/numbers_text.xhp#numbers_text"
markup="ignore"/> for details.</paragraph>
<paragraph role="paragraph" id="par_id8841822"
xml-lang="en-US"><emph>Convert also locale dependent:</emph> convert values
valid in the locale representation. Example: <item type="input">"123,45"</item>
is a valid number in some locales because the comma is the decimal separator
there.</paragraph>
<h3 id="par_id4077578">Treat empty string as zero</h3>
<paragraph role="paragraph" id="par_id9094515" xml-lang="en-US">This
option determines how an empty string is treated when used in arithmetic
operations. If you have set "Conversion from text to number" to either
"Generate #VALUE! error" or "Treat as zero", you cannot choose (here) if
conversion of an empty string to a number will generate an error or if it will
treat empty strings as zero. Otherwise this option determines how empty strings
are treated.</paragraph>
_______________________________________________
Libreoffice-commits mailing list
libreoffice-comm...@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/libreoffice-commits
