Translations update from Hosted Weblate#582
Merged
SupertigerDev merged 10 commits intoNerimity:mainfrom Feb 28, 2026
Merged
Conversation
Contributor
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (9)
📝 WalkthroughWalkthroughMultiple locale JSON updates: adjusted German and Polish server notice texts, added a new top-level Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
weblate
force-pushed
the
weblate-nerimity-nerimity-web
branch
2 times, most recently
from
c19c79a to
c82f112
Compare
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
🧹 Nitpick comments (2)
src/locales/list/fr-FR.json (1)
592-592: Align French tone with the rest of the locale (formal register).Line 592 uses informal French (“tu”), while most of this file uses formal phrasing. Consider using a formal variant for consistency.
Suggested wording
- "lastfmActivityDescription": "Partage ce que tu écoutes via Last.fm", + "lastfmActivityDescription": "Partagez ce que vous écoutez via Last.fm",🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/locales/list/fr-FR.json` at line 592, Replace the informal phrasing in the JSON value for the key "lastfmActivityDescription" with a formal register to match the rest of the locale; for example, change the string from the informal "Partage ce que tu écoutes via Last.fm" to a formal variant such as "Partagez ce que vous écoutez via Last.fm" (keep the same JSON key and punctuation).src/locales/list/es-es.json (1)
672-676: Consider using "Clave API" for terminology consistency.Line 676 uses "Llave API" while Line 684 uses "Clave secreta del cliente". In Spanish technical contexts, "Clave" is more commonly used for abstract keys (API keys, passwords), while "Llave" typically refers to physical keys.
Suggested change for consistency
- "lastfmApiKeyPlaceholder": "Llave API de Last.fm" + "lastfmApiKeyPlaceholder": "Clave API de Last.fm"🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In `@src/locales/list/es-es.json` around lines 672 - 676, Update the Spanish translation value for the key lastfmApiKeyPlaceholder to use "Clave" instead of "Llave" to match the terminology used elsewhere (e.g., "Clave secreta del cliente"); change the string from "Llave API de Last.fm" to "Clave API de Last.fm" so translations are consistent across lastfmApiKeyPlaceholder, lastfmActivity and related keys.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In `@src/locales/list/es-es.json`:
- Around line 672-676: Update the Spanish translation value for the key
lastfmApiKeyPlaceholder to use "Clave" instead of "Llave" to match the
terminology used elsewhere (e.g., "Clave secreta del cliente"); change the
string from "Llave API de Last.fm" to "Clave API de Last.fm" so translations are
consistent across lastfmApiKeyPlaceholder, lastfmActivity and related keys.
In `@src/locales/list/fr-FR.json`:
- Line 592: Replace the informal phrasing in the JSON value for the key
"lastfmActivityDescription" with a formal register to match the rest of the
locale; for example, change the string from the informal "Partage ce que tu
écoutes via Last.fm" to a formal variant such as "Partagez ce que vous écoutez
via Last.fm" (keep the same JSON key and punctuation).
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
src/locales/list/be-tarask.jsonsrc/locales/list/de-de.jsonsrc/locales/list/es-es.jsonsrc/locales/list/fr-FR.jsonsrc/locales/list/pl-pl.json
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/locales/list/es-es.json`:
- Around line 138-142: The translations have inconsistent capitalization for
"GIFs" between the "noResults" key and "favorites.noFavorites"; pick a
consistent form and update one of the values so both "noResults" and
"favorites.noFavorites" use the same capitalization (e.g., both "GIFs" or both
"gifs") to maintain uniform locale strings.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (5)
src/locales/list/be-tarask.jsonsrc/locales/list/de-de.jsonsrc/locales/list/es-es.jsonsrc/locales/list/fr-FR.jsonsrc/locales/list/pl-pl.json
🚧 Files skipped from review as they are similar to previous changes (2)
- src/locales/list/fr-FR.json
- src/locales/list/de-de.json
Comment on lines
+138
to
+142
| "noResults": "No se han encontrado GIFs", | ||
| "favorites": { | ||
| "title": "Favoritos", | ||
| "search": "Buscar favoritos", | ||
| "noFavorites": "No tienes gifs favoritos" |
Contributor
There was a problem hiding this comment.
Minor inconsistency: "GIFs" vs "gifs" capitalization.
Line 138 uses uppercase "GIFs" while line 142 uses lowercase "gifs". Consider unifying the capitalization for consistency.
"favorites": {
"title": "Favoritos",
"search": "Buscar favoritos",
- "noFavorites": "No tienes gifs favoritos"
+ "noFavorites": "No tienes GIFs favoritos"
}📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "noResults": "No se han encontrado GIFs", | |
| "favorites": { | |
| "title": "Favoritos", | |
| "search": "Buscar favoritos", | |
| "noFavorites": "No tienes gifs favoritos" | |
| "noResults": "No se han encontrado GIFs", | |
| "favorites": { | |
| "title": "Favoritos", | |
| "search": "Buscar favoritos", | |
| "noFavorites": "No tienes GIFs favoritos" |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/locales/list/es-es.json` around lines 138 - 142, The translations have
inconsistent capitalization for "GIFs" between the "noResults" key and
"favorites.noFavorites"; pick a consistent form and update one of the values so
both "noResults" and "favorites.noFavorites" use the same capitalization (e.g.,
both "GIFs" or both "gifs") to maintain uniform locale strings.
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Inline comments:
In `@src/locales/list/tr-tr.json`:
- Line 835: The translation key posts.replying contains a malformed rich-text
tag and a typo; replace the invalid "<1>{{username}}<1>" with a properly closed
rich-text tag surrounding the username (e.g., "<1>{{username}}</1>") and correct
the typo "kullanıcısna" to "kullanıcıya" so the value for posts.replying reads
something like "<1>{{username}}</1> kullanıcısna yanıt veriliyor." updated to
"<1>{{username}}</1> kullanıcıya yanıt veriliyor." ensuring posts.replying uses
the corrected tag and spelling.
ℹ️ Review info
Configuration used: defaults
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
src/locales/list/es_MX.jsonsrc/locales/list/tr-tr.json
✅ Files skipped from review due to trivial changes (1)
- src/locales/list/es_MX.json
| "mostLikedAllTime": "En Çok Beğenilen (Tüm Zamanlar)" | ||
| }, | ||
| "replying": "" | ||
| "replying": "<1>{{username}}<1> kullanıcısna yanıt veriliyor.", |
Contributor
There was a problem hiding this comment.
Fix broken rich-text tag and typo in posts.replying.
Line [835] has an invalid tag (<1>{{username}}<1>) and a typo (kullanıcısna). This can break rich-text rendering and show malformed text.
🔧 Proposed fix
- "replying": "<1>{{username}}<1> kullanıcısna yanıt veriliyor.",
+ "replying": "<1>{{username}}</1> kullanıcısına yanıt veriliyor.",📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
Suggested change
| "replying": "<1>{{username}}<1> kullanıcısna yanıt veriliyor.", | |
| "replying": "<1>{{username}}</1> kullanıcısına yanıt veriliyor.", |
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.
In `@src/locales/list/tr-tr.json` at line 835, The translation key posts.replying
contains a malformed rich-text tag and a typo; replace the invalid
"<1>{{username}}<1>" with a properly closed rich-text tag surrounding the
username (e.g., "<1>{{username}}</1>") and correct the typo "kullanıcısna" to
"kullanıcıya" so the value for posts.replying reads something like
"<1>{{username}}</1> kullanıcısna yanıt veriliyor." updated to
"<1>{{username}}</1> kullanıcıya yanıt veriliyor." ensuring posts.replying uses
the corrected tag and spelling.
e45fe55 to
9048189
Compare
Currently translated at 100.0% (987 of 987 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/de/
Currently translated at 100.0% (987 of 987 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/be_TARASK/
Currently translated at 99.8% (987 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/fr/
Currently translated at 100.0% (988 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/pl/
Currently translated at 100.0% (988 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/be_TARASK/
Currently translated at 100.0% (988 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/es/
Currently translated at 95.1% (940 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/tr/
Currently translated at 29.4% (291 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/zh_Hans/
Currently translated at 15.6% (155 of 988 strings) Translation: Nerimity/Nerimity Web Translate-URL: https://hosted.weblate.org/projects/nerimity/nerimity-web/zh_Hant/
weblate
force-pushed
the
weblate-nerimity-nerimity-web
branch
from
9048189 to
0341c8c
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
7 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Translations update from Hosted Weblate for Nerimity/Nerimity Web.
Current translation status:
Summary by CodeRabbit