github-actions[bot] commented on PR #40169:
URL: https://github.com/apache/superset/pull/40169#issuecomment-4544840298

   <!-- translation-regression-bot -->
   ## ⚠️ Translation Regression Detected
   
   This PR causes existing translations to become fuzzy or be removed in `cs`, 
`fr`, `ja`, `lv`, `ru`, `sk`, `uk`. Please fix the affected `.po` files before 
merging.
   
   | Language | Before | After | Lost |
   |----------|-------:|------:|-----:|
   | `cs` | 4033 | 4032 | -1 |
   | `fr` | 3731 | 3730 | -1 |
   | `ja` | 4502 | 4501 | -1 |
   | `lv` | 4529 | 4528 | -1 |
   | `ru` | 4510 | 4509 | -1 |
   | `sk` | 4050 | 4049 | -1 |
   | `uk` | 4531 | 4530 | -1 |
   
   ### How to fix
   
   **1. Install dependencies** (if not already set up):
   
   ```bash
   pip install -r superset/translations/requirements.txt
   sudo apt-get install gettext   # or: brew install gettext
   ```
   
   **2. Re-extract strings and sync `.po` files:**
   
   ```bash
   ./scripts/translations/babel_update.sh
   ```
   
   This rewrites `superset/translations/messages.pot` from the current source 
files and merges the changes into every `.po` file. Strings whose `msgid` 
changed will be marked `#, fuzzy`.
   
   **3. Resolve the fuzzy entries** in the affected language files (`cs`, `fr`, 
`ja`, `lv`, `ru`, `sk`, `uk`):
   
   ```bash
   grep -n '#, fuzzy' superset/translations/<lang>/LC_MESSAGES/messages.po
   ```
   
   For each fuzzy entry, either rewrite the `msgstr` to match the new string 
and remove the `#, fuzzy` line, or clear the `msgstr` to `""` if you cannot 
provide a translation.
   
   **4. Commit your changes to the `.po` files.**
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to