https://bugs.documentfoundation.org/show_bug.cgi?id=152959

Stéphane Guillou (stragu) <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Blocks|                            |146076
            Version|7.3.7.2 release             |4.0.6.2 release
                 CC|                            |[email protected]
                   |                            |,
                   |                            |stephane.guillou@libreoffic
                   |                            |e.org
                 OS|Windows (All)               |All
            Summary|Editing: Find               |Find and Replace can't use
                   |                            |the lowercase Unicode
                   |                            |literal for soft hyphen
     Ever confirmed|0                           |1
             Status|UNCONFIRMED                 |NEW

--- Comment #1 from Stéphane Guillou (stragu) 
<[email protected]> ---
Thanks Jerzy!

The special handling of soft hyphen search was done for bug 73660.
Michael, as you fixed that one back 2016, do you think the lowercase version
should be added, for consistency? For example, a full stop can be found with
\u002e and \u002E.

See this comment to see what is accepted:
https://bugs.documentfoundation.org/show_bug.cgi?id=64495#c13

Regarding the issue with the diacritic-sensitive option: probably better to
open a dedicated bug report so it is tracked separately, as I am sure there
will be more discussion needed.

Tested on:

Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community
Build ID: 894efac210a3871214d95a52c322b0bee40f00ba
CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3
Locale: en-AU (en_AU.UTF-8); UI: en-US
Calc: threaded


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=146076
[Bug 146076] [META] Find & Replace Regular Expressions
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to