Skip to Main Content
HCL Domino Ideas Portal

Welcome to the #dominoforever Product Ideas Forum! The place where you can submit product ideas and enhancement request. We encourage you to participate by voting on, commenting on, and creating new ideas. All new ideas will be evaluated by HCL Product Management & Engineering teams, and the next steps will be communicated. While not all submitted ideas will be executed upon, community feedback will play a key role in influencing which ideas are and when they will be implemented.

For more information and upcoming events around #dominoforever, please visit our Destination Domino Page

Status Needs Clarification
Workspace Domino
Created by Guest
Created on Jan 30, 2023

Wildcard searches for Japanese words in the full text search

The following help is available.

How can I refine a search query using operators?
https://help.hcltechsw.com/notes/12.0.0/client/sch_refine_query_r.html
------------
A wildcard that can represent any extension of letters. It does not work with dates or numbers.

Examples

*one

Finds documents containing bone, cone, clone, crone, done, drone, gone, telephone (and any other words of any length that end with 'one').

Also,

*one*

Finds documents containing bone, cone, clone, lonely, phoned, stoned, pardoned.
------------

However, for this wildcard, it does not work correctly for Japanese searches.

For Example:

1. Create new documents containing each of the following words.

リンゴ
リンゴ酢

2. Create Full Text Index in the database.

3. If Notes user try to search "リンゴ" by full text search in search bar for full text search, all documents are hit.

4. However, if Notes user Notes user try to search "リンゴ*" with Wildcard, no documents are hit despite the existence of those documents with the word "リンゴ".

This result would be very inconvenient for Japanese users.
Therefore, we would like wildcards to work for Japanese word searches as well.

  • Attach files
  • Admin
    Thomas Hampel
    Reply
    |
    Mar 24, 2023

    That sounds like a bug, can you please open a support ticket to investigate this further?