Bug #32680
open
[ja_JP/zh_CN/fr_FR] Search box background text is not marked as a translatable string
Description
Description of problem: String at background of Search box is not marked as translatable string.
Version-Release number of selected component (if applicable): Version 2.5.0 RC2
How reproducible: Always
Steps to Reproduce:
1. Login to Foreman 2.5 instance with French/Japanese/Chinese language.
2. Click on Organization and Location drop down, string at background is not marked
Actual results: String is present in English language.
Expected results: String should be marked for translation.
Additional info: Right after product name text "FOREMAN", look for drop down to click.
Please see attached screenshot.
Files
| TS1_Search-box-text-not-marked.png | View TS1_Search-box-text-not-marked.png | 244 KB | Organizations drop down | ||
| TS2_Search-box-text-not-marked.png | View TS2_Search-box-text-not-marked.png | 249 KB | Locations drop down | ||
| 1.png | View 1.png | 157 KB | English locale | ||
| ja_JP-Search-string-Orgnization-dropdown-not-marked.png | View ja_JP-Search-string-Orgnization-dropdown-not-marked.png | 192 KB | ja_JP Search string Organizations dropdown | ||
| ja_JP-Search-string-Locations-dropdown-not-marked.png | View ja_JP-Search-string-Locations-dropdown-not-marked.png | 204 KB | ja_JP Search string Locations dropdown | ||
| I18Ni18n-19058_Screenshot_from_2022-09-05_17-22-08.png | View I18Ni18n-19058_Screenshot_from_2022-09-05_17-22-08.png | 96.9 KB | Search text string is not marked. |
Updated by vijaykumar sawant almost 3 years ago
- Category set to Internationalization
Updated by vijaykumar sawant over 2 years ago
This issue is also found in version 3.1 RC-2 build
Updated by vijaykumar sawant about 2 years ago
- File ja_JP-Search-string-Locations-dropdown-not-marked.png ja_JP-Search-string-Locations-dropdown-not-marked.png added
- File ja_JP-Search-string-Orgnization-dropdown-not-marked.png ja_JP-Search-string-Orgnization-dropdown-not-marked.png added
- Triaged changed from No to Yes
This issue is being observed in Foreman 3.2.0 build as well. please look at attached screenshots.
Updated by vijaykumar sawant almost 2 years ago
This issue has been observed in Foreman 3.3 rc2 build.
Updated by vijaykumar sawant over 1 year ago
- File I18Ni18n-19058_Screenshot_from_2022-09-05_17-22-08.png I18Ni18n-19058_Screenshot_from_2022-09-05_17-22-08.png added
This issue has been observed in Foreman 3.4 rc1 build