Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Fix] Fix some Locales Seemingly Made Using Google Translate #82

Closed
wants to merge 1 commit into from

Conversation

Spatison
Copy link
Member

Описание PR

#1006

@Spatison Spatison requested a review from Remuchi October 10, 2024 19:26
@Spatison Spatison self-assigned this Oct 10, 2024
Copy link
Contributor

coderabbitai bot commented Oct 10, 2024

Walkthrough

This pull request includes modifications to localization strings in the ghost-respawn.ftl file. The changes involve rephrasing and clarifying messages related to ghost respawn functionality, enhancing user understanding of the respawn mechanics and rules.

Changes

File Path Change Summary
Resources/Locale/en-US/_white/ghost/ghost-respawn.ftl - Updated ghost-respawn-time-left for clarity.
- Modified ghost-respawn-max-players message.
- Simplified title for respawn rules.
- Rephrased footer message regarding rule violations.
- Updated ghost-respawn-same-character to specify character selection.
- Adjusted log message for grammatical consistency.

Possibly related PRs

Suggested labels

Changes: Localization, Status: Needs Review

Suggested reviewers

  • Remuchi

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?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

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)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Outside diff range and nitpick comments (1)
Resources/Locale/en-US/_white/ghost/ghost-respawn.ftl (1)

7-7: LGTM with suggestion: Improved clarity in rules footer

The rephrasing of the rules footer significantly improves clarity. It now provides a clear warning about the consequences of using knowledge from a previous character and directs users to the server rules for more details. The use of colored text effectively emphasizes important parts of the message.

Consider adding a space after the comma in "Please, read" for better readability:

-ghost-respawn-window-rules-footer = By respawning, you [color=#ff7700]agree[/color] [color=#ff0000]not to use any knowledge gained as your previous charactrer[/color]. Violation of this rule may constitute a server ban. Please, read the server rules for more details.
+ghost-respawn-window-rules-footer = By respawning, you [color=#ff7700]agree[/color] [color=#ff0000]not to use any knowledge gained as your previous charactrer[/color]. Violation of this rule may constitute a server ban. Please, read the server rules for more details.

Also, there's a typo in "charactrer" which should be corrected to "character".

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL

📥 Commits

Files that changed from the base of the PR and between 4c2f775 and 7de0476.

📒 Files selected for processing (1)
  • Resources/Locale/en-US/_white/ghost/ghost-respawn.ftl (1 hunks)
🧰 Additional context used
🔇 Additional comments (6)
Resources/Locale/en-US/_white/ghost/ghost-respawn.ftl (6)

1-4: LGTM: Improved clarity in respawn time message

The rephrasing of this message is clearer and more direct, emphasizing the need to wait before attempting to respawn. The pluralization logic is correctly maintained, ensuring proper grammar for both singular and plural cases.


5-5: LGTM: Enhanced clarity in max players message

The revised message is more precise and informative. It clearly communicates the current inability to respawn and the condition for respawning (fewer than a specific number of players). This change improves user understanding of the respawn mechanics.


6-6: LGTM: Simplified window title

The simplification of the window title from "Rules for returning to the round" to "Respawn rules" is a good improvement. It's more concise while maintaining the essential meaning, which enhances readability and user understanding.


8-8: LGTM: Improved guidance for character selection

The updated message provides clearer instructions to the user. It now specifically directs them to select a different character in their preferences, which is more actionable and helpful for users encountering this situation.


9-12: LGTM: Enhanced clarity in log message

The adjustments to this log message improve grammatical consistency and clarity. The phrasing "after respawning with a similar name" is more natural and precise. The conditional logic for "joined" or "tried to join" is correctly maintained, ensuring appropriate logging for different scenarios.


1-12: Overall: Significant improvements in clarity and localization quality

The changes in this file consistently enhance the clarity and user-friendliness of the ghost respawn messages. The modifications address the PR objective of fixing locales that appeared to be made using Google Translate. The rephrased messages are more natural, precise, and informative, which should improve the user experience and understanding of the ghost respawn mechanics.

To ensure consistency across other locales, please run the following script:

This script will help identify any inconsistencies or missing translations in other locale files that may need to be addressed in future PRs.

✅ Verification successful

Verification Complete: Localization Consistency Confirmed

The script results indicate that all key strings in ghost-respawn.ftl are present in both en-US and ru-RU locales. No inconsistencies or missing translations were found, ensuring localization quality across the supported languages.

🏁 Scripts executed

The following scripts were executed for the analysis:

Script:

#!/bin/bash
# Description: Check for inconsistencies in ghost-respawn.ftl across different locales

# Find all ghost-respawn.ftl files
files=$(fd -t f "ghost-respawn.ftl" Resources/Locale)

# Compare the number of lines in each file
for file in $files; do
  echo "File: $file"
  wc -l "$file"
done

# Check for the presence of key strings in all files
key_strings=("ghost-respawn-time-left" "ghost-respawn-max-players" "ghost-respawn-window-title" "ghost-respawn-window-rules-footer" "ghost-respawn-same-character" "ghost-respawn-log-character-almost-same")

for string in "${key_strings[@]}"; do
  echo "Checking for '$string' in all files:"
  rg -l "$string" $files
done

Length of output: 3447

@Remuchi
Copy link
Collaborator

Remuchi commented Oct 11, 2024

это будет при полном мерже EE

@Remuchi Remuchi closed this Oct 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants