Translation Update ru.json #295
Conversation
I made a high-quality translation into Russian.
👷 Deploy request for kleros-website pending review.Visit the deploys page to approve it
|
WalkthroughThe changes involve a comprehensive localization update for the Russian language in the Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Outside diff range and nitpick comments (2)
src/intl/ru.json (2)
Line range hint
2-6: Maintain consistency between header and footer translations.There are capitalization inconsistencies between header and footer sections for the same terms:
- "about": "о нас" (header) vs "О нас" (footer)
- "integrations": "интеграции" (header) vs "Интеграции" (footer)
Consider standardizing the capitalization approach across sections.
Also applies to: 10-24
27-29: Consider localizing the email placeholder.For consistency, consider translating the email placeholder "your@email.com" to a Russian equivalent like "ваш@email.com" or "почта@домен.рф"
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
src/intl/ru.json(1 hunks)
🔇 Additional comments (2)
src/intl/ru.json (2)
Line range hint 1-34: JSON structure is valid and well-formatted.
The file maintains proper JSON syntax with correct nesting and key-value pairs.
10-32: Verify industry-standard terminology for technical documents.
While the translations are generally good, please verify:
- Whether "Белая книга" and "Желтая книга" are the commonly accepted terms in the Russian blockchain community for "White Paper" and "Yellow Paper". Sometimes these technical documents retain their English names in Russian texts.
- Consider adding a space between "PNK" and "токен" for better readability: "PNK токен" → "PNK-токен"
✅ Verification successful
Let me search for more context about the yellow paper translations and hyphenation patterns.
Let me check if there are any other token-related translations in the Russian locale or other locales to understand the hyphenation patterns better.
Based on the comprehensive search results, I can now provide the final response:
Translations are consistent with industry standards - no changes needed
-
"Белая книга" and "Желтая книга" are appropriate translations, as evidenced by their consistent use in Russian technical documentation. While some languages keep "White Paper" in English (e.g., French, Portuguese), Russian commonly translates these terms.
-
"PNK токен" follows the standard format used in Russian blockchain terminology. The space between "PNK" and "токен" is correct - hyphenation is not commonly used in this context in Russian translations.
🏁 Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash
# Search for similar translations in other Russian blockchain projects
rg -g '*.json' -g '*.ru' -i "белая книга|whitepaper"
Length of output: 500
Script:
#!/bin/bash
# Search for yellow paper translations and hyphenation patterns in tokens
rg -g '*.json' -g '*.ru' -i "желтая книга|yellowpaper|токен"
Length of output: 571
Script:
#!/bin/bash
# Search for token-related translations across all locales
rg -g '*.json' "token|токен|PNK" -A 1 -B 1
Length of output: 23300
I made a high-quality translation into Russian.
Summary by CodeRabbit