source/text/scalc/01/func_regex.xhp | 2 +- source/text/shared/01/02100001.xhp | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-)
New commits: commit ba3b8d5bc6416cec3ab2d86ba8452c292681086e Author: Eike Rathke <[email protected]> AuthorDate: Tue Jun 7 13:46:52 2022 +0200 Commit: Eike Rathke <[email protected]> CommitDate: Tue Jun 7 13:53:03 2022 +0200 Include metacharacters fragment in ICU regexp URI So it leads to Regular Expression Metacharacters instead of just the page that starts with all sort of developer information not relevant to users. Change-Id: Id1efca75302d023a83b45a4bc81654ffe8c2980f Reviewed-on: https://gerrit.libreoffice.org/c/help/+/135471 Reviewed-by: Eike Rathke <[email protected]> Tested-by: Jenkins diff --git a/source/text/scalc/01/func_regex.xhp b/source/text/scalc/01/func_regex.xhp index 3b29f7492..82119a3df 100644 --- a/source/text/scalc/01/func_regex.xhp +++ b/source/text/scalc/01/func_regex.xhp @@ -29,7 +29,7 @@ <embed href="text/scalc/01/ful_func.xhp#func_head_syntax"/> <paragraph role="code" id="par_id701542231253817" xml-lang="en-US">REGEX( Text ; Expression [ ; [ Replacement ] [ ; Flags|Occurrence ] ] )</paragraph> <paragraph role="paragraph" id="par_id621542232197446" xml-lang="en-US"><emph>Text</emph>: A text or reference to a cell where the regular expression is to be applied.</paragraph> - <paragraph role="paragraph" id="par_id211542232209275" xml-lang="en-US"><emph>Expression</emph>: A text representing the regular expression, using <link href="https://unicode-org.github.io/icu/userguide/strings/regexp.html"; name="ICU REGEXP">ICU regular expressions</link>. If there is no match and <emph>Replacement</emph> is not given, #N/A is returned.</paragraph> + <paragraph role="paragraph" id="par_id211542232209275" xml-lang="en-US"><emph>Expression</emph>: A text representing the regular expression, using <link href="https://unicode-org.github.io/icu/userguide/strings/regexp.html#regular-expression-metacharacters"; name="ICU REGEXP">ICU regular expressions</link>. If there is no match and <emph>Replacement</emph> is not given, #N/A is returned.</paragraph> <paragraph role="paragraph" id="par_id581542232755604" xml-lang="en-US"><emph>Replacement</emph>: Optional. The replacement text and references to capture groups. If there is no match, <emph>Text</emph> is returned unmodified.</paragraph> <paragraph role="paragraph" id="par_id421542232246840" xml-lang="en-US"><emph>Flags</emph>: Optional. "g" replaces all matches of <emph>Expression</emph> in <emph>Text</emph>, not extracted. If there is no match, <emph>Text</emph> is returned unmodified.</paragraph> <paragraph role="paragraph" id="par_id421542232246841" xml-lang="en-US"><emph>Occurrence</emph>: Optional. Number to indicate which match of <emph>Expression</emph> in <emph>Text</emph> is to be extracted or replaced. If there is no match and <emph>Replacement</emph> is not given, #N/A is returned. If there is no match and <emph>Replacement</emph> is given, <emph>Text</emph> is returned unmodified. If <emph>Occurrence</emph> is 0, <emph>Text</emph> is returned unmodified.</paragraph> diff --git a/source/text/shared/01/02100001.xhp b/source/text/shared/01/02100001.xhp index 273f41b19..b7caadd4a 100644 --- a/source/text/shared/01/02100001.xhp +++ b/source/text/shared/01/02100001.xhp @@ -315,7 +315,7 @@ </tablecell> </tablerow> </table> -<paragraph xml-lang="en-US" id="par_id5311440" role="paragraph">For a full list of supported metacharacters and syntax, see <link href="https://unicode-org.github.io/icu/userguide/strings/regexp.html"; name="ICU Regular Expressions documentation">ICU Regular Expressions documentation</link></paragraph> +<paragraph xml-lang="en-US" id="par_id5311440" role="paragraph">For a full list of supported metacharacters and syntax, see <link href="https://unicode-org.github.io/icu/userguide/strings/regexp.html#regular-expression-metacharacters"; name="ICU Regular Expressions documentation">ICU Regular Expressions documentation</link></paragraph> <paragraph role="paragraph" id="par_id261559577375317">Regular expression terms can be combined to form complex and sophisticated regular expressions for searches as show in the following examples.</paragraph> <h2 id="hd_id5311441">Examples</h2>
