[Libreoffice-commits] help.git: source/text

[Eike Rathke]

 source/text/scalc/05/OpenCL_options.xhp |    2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

New commits:
commit c122aa7574e363c9dce332f1ca8b69b1cccde202
Author: Eike Rathke <erack at redhat.com>
Date:   Wed Aug 31 11:58:24 2016 +0200

    change bad example for "Convert only if unambiguous" to something better
    
    Why is this even in the OpenCL_options help file?
    
    Change-Id: I319b59cea3d7f56b58de95292ca53b708e7e23c7

diff --git a/source/text/scalc/05/OpenCL_options.xhp b/source/text/scalc/05/OpenCL_options.xhp
index c434b31..39d3ea2 100644
--- a/source/text/scalc/05/OpenCL_options.xhp
+++ b/source/text/scalc/05/OpenCL_options.xhp
@@ -38,7 +38,7 @@ OpenCL™ is the first open, royalty-free standard for cross-platform, parallel
 <paragraph role="paragraph" id="par_id396740" xml-lang="en-US" l10n="NEW">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" l10n="NEW"><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" l10n="NEW"><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" l10n="NEW"><emph>Convert only if unambiguous:</emph> If the text represents a valid and unambiguous numeric value, convert it. Example: <item type="input">"+55.21.9.8822.8813"</item> will map to zero, because the numbers don't represent a numeric value.</paragraph>
+<paragraph role="paragraph" id="par_id3067110" xml-lang="en-US" l10n="NEW"><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_id8841822" xml-lang="en-US" l10n="NEW"><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>
 <paragraph role="heading" id="par_id4077578" xml-lang="en-US" l10n="NEW" level="3">Treat empty string as zero</paragraph>
 <paragraph role="paragraph" id="par_id9094515" xml-lang="en-US" l10n="NEW">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>