# Searching in second language

### **1. Introduction**

This release improves how the search functionality works inside the **Translations** section of **Org Settings**.

Previously, users could only search for text using the **Primary Language**, even when viewing translations in another language. This made it difficult to find and update translated content when users only knew the secondary language or noticed an issue directly in that language.

With this update, Unifize now supports searching in both the **Primary Language** and the **Translated Language**, making translation management faster, easier, and far more intuitive.

<figure><img src="/files/S8H8rRXXTKlNaj2aHoQG" alt=""><figcaption></figcaption></figure>

***

### **2. What this release covers**

* Users can now search directly in the **translated language**, instead of being limited to the Primary Language version of the text.
* The search bar now correctly identifies which language is selected in the Translations page and updates search results accordingly.
* Search results refresh immediately when searching in a secondary language, switching languages, or clearing the search bar.

These improvements make it easier for users to quickly locate labels or UI text that need updates, especially for non-English teams.

***

### **3. How this looks on the platform**

When you go to **Profile → Org Settings → Translations** and switch to another language (such as Chinese, Spanish, or French):

* Typing in the search bar will now search **the translated text**, not just the primary language text.
* Results update instantly to match the words you typed in the selected language.
* Clearing the search bar correctly resets the entire list of translations.
* Pagination updates smoothly to reflect the number of filtered results.
* Switching between languages automatically adjusts the search behaviour, so you always get accurate results for the language you’re working in.

This means you can now find translated labels the same way you find English labels—by simply typing what you see.

***

### **4. Before vs After**

| **Before**                                                                           | **After**                                                       |
| ------------------------------------------------------------------------------------ | --------------------------------------------------------------- |
| Users could only search in the primary language, and not in the translated language. | Users can search directly in the selected translated language.  |
| Search results often didn’t update when switching languages.                         | Search updates immediately based on the active language.        |
| Clearing search kept old results or stale data.                                      | Clearing search consistently resets results as expected.        |
| Pagination key stayed the same regardless of filtering.                              | Pagination accurately reflects filtered search results.         |
| Users saw incorrect or missing results when working in another language.             | Users now see fully accurate, language-specific search results. |

For more details on Language Translations, you can refer to the guides below.

[Language Translations Admin Guide](https://docs.unifize.com/admin-guide/profile/org-settings/translations)

[Language Translations User Guide](https://docs.unifize.com/user-guide/profile/org-settings/language-and-translations)


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.unifize.com/release-notes/december-2025/searching-in-second-language.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.