Author Topic: Find does not work for uppercase non-ASCII characters  (Read 211 times)


  • Community Member
  • Posts: 71
  • Hero Points: 8
Find does not work for uppercase non-ASCII characters
« on: January 07, 2020, 12:04:22 pm »
Steps to reproduce:

1. Create a file with the following content (see attachment, the file uses encoding "Text, SBCS/DBCS mode"):
Code: [Select]


2. Run "find-in-files" and search for "æ" in "<Current Buffer>".
3. The "Search Results" output is:
Code: [Select]
Find all "æ", "<Current Buffer>", "*.*", Exclude: "moc_*;ui_*;*.docx;.vs\**"
File D:\æøå
  2 1:æøå
Total found: 1     Matching files: 1     Total files searched: 1
4. Since this was not a case sensitive search, line 3 should also had been part of the search result.  The search result is identical if one searches for "Æ" instead of "æ".

Here is my output from Help -> About SlickEdit:
Code: [Select]
SlickEdit Pro 2019 (v24.0.1.0 64-bit)

Serial number: WB943076
Licensed number of users: Single user
License file: C:\ProgramData\slickedit\24\slickedit.lic

Build Date: December 19, 2019
Emulation: CUA

OS: Windows 10 x64
OS Version: 10.00.0 
Memory: 55% Load, 18252MB/32648MB Physical, 27432MB/37512MB Page File, 5197MB/134217727MB Virtual
Shell Information: C:\tools\JPSoft\TCMD25\tcc.exe /LD /LH
Screen Size: 1920 x 1080, 1920 x 1080

Project Type: Microsoft Visual Studio Csharp
Language: . (Plain Text)
Encoding: Automatic

Installation Directory: C:\Program Files\SlickEdit Pro 24.0.1\ (non-removable drive,NTFS,92819MB free)
Configuration Directory: C:\Users\VikS\Documents\My SlickEdit Config\24.0.1\ (non-removable drive,NTFS,92819MB free)
Migrated from: C:\Users\VikS\Documents\My SlickEdit Config\24.0.0\


  • SlickEdit Team Member
  • Senior Community Member
  • *
  • Posts: 5168
  • Hero Points: 427
Re: Find does not work for uppercase non-ASCII characters
« Reply #1 on: January 07, 2020, 06:48:27 pm »
Reproduced. Obvious typo. Called a utf-8/unicode case compare function instead of the SBCS one.

This is not hot fixable. Fixed for 24.0.2. This is a very old bug. I guess these characters are mainly seen in unicode files. Case insensitive search in unicode files works fine.

Thanks for posting this. Very good example.