[Hrusa][2.0.23] Searching in katakana does not yield correct results

This subforum contains all the issues which we already resolved.
maso
Manual Inserter
Manual Inserter
Posts: 2
Joined: Sat Nov 30, 2024 7:54 am
Contact:

[Hrusa][2.0.23] Searching in katakana does not yield correct results

Post by maso »

I am playing in Japanese. I searched in katakana to find a logistic group that includes katakana, but I couldn't find the logistic group I was looking for.

This issue occurs consistently with any word, as long as it is in katakana.
You can confirm this by creating a logistic group named in katakana, and then attempting to search using the same katakana string. Naming it "ベルト" is one example.

As a supplementary note, if a corresponding logistic group named in hiragana (e.g., "べると") is additionally created to pair with a logistic group named in katakana (e.g., "ベルト"), neither group will appear when searching in katakana. However, searching in hiragana will return both groups. Based on my understanding, the expected behavior is that searching in katakana should return two results, and searching in hiragana should also return the same two results.
searched_in_katakana.png
searched_in_katakana.png (28.38 KiB) Viewed 548 times
searched_in_hiragana.png
searched_in_hiragana.png (23.24 KiB) Viewed 548 times
This issue occurs specifically in the search function for logistic group and, to the best of my knowledge, does not occur when searching within the technology list or inventory.
This text was machine-translated.
User avatar
xargo-sama
Long Handed Inserter
Long Handed Inserter
Posts: 55
Joined: Mon Jun 05, 2023 1:04 pm
Contact:

Re: [Hrusa][2.0.23] Searching in katakana does not yield correct results

Post by xargo-sama »

Hello,

thank you for letting us know.

A lot of small windows were still using the old search system without wider language support. I have fixed it for the next release.

Sorry about the inconvenience.
Attachments
fixed_logistics.png
fixed_logistics.png (27.46 KiB) Viewed 459 times
Post Reply

Return to “Resolved Problems and Bugs”