Building with clang 21.1.8 and --enable-werror fails because glibc 2.43
adopted the C23 behavior for strrchr(), where it now returns const char*
when its input is const char*. Assigning the result to a plain char*
discards the const qualifier, which clang rejects as an error since the flag is passed.
Change-Id: Ib8eecd603bedb4a69c8f7bd93e49f01e8eba28d6
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/199863
Tested-by: Jenkins
Reviewed-by: Neil Roberts <bpeeluk@yahoo.co.uk>
* Update helpcontent2 from branch 'master'
to 4caf8d65a7b77638fdc9e59f2368b2661f5a922b
- tdf#171177 Document Unicode escapes in regex replace
Follow-up to tdf#106137. Added documentation explaining that unicode sequences can now be used in the replacement input field when regular expressions are enabled.
Change-Id: I329920ee9cd4724b1c35067af2e4a4a8490196e4
Reviewed-on: https://gerrit.libreoffice.org/c/help/+/201153
Tested-by: Jenkins
Reviewed-by: Olivier Hallot <olivier.hallot@libreoffice.org>
When using Find & Replace with regular expressions enabled,
\uhhhh and \Uhhhhhhhh sequences in the replacement string are
now expanded to their corresponding Unicode characters.
This uses i18nutil::processUnicodeEscapes(), introduced in the
parent commit.
Change-Id: Ifc2a634e9b5eb2589a46b309441ea7691d2321b7
Reviewed-on: https://gerrit.libreoffice.org/c/core/+/199924
Tested-by: Jenkins
Reviewed-by: Mike Kaganski <mike.kaganski@collabora.com>
AnamayNarkar