Skip to content

[1.21] Russian translation#379

Open
Bamberghh wants to merge 2 commits intowisp-forest:1.21from
Bamberghh:1.21
Open

[1.21] Russian translation#379
Bamberghh wants to merge 2 commits intowisp-forest:1.21from
Bamberghh:1.21

Conversation

@Bamberghh
Copy link
Copy Markdown

Note that the config reload button text (text.owo.config.button.reload) does not fit the reload button, so I had to contract it. You might want to fix that in the mod so that the button gets its size from its content or something like that, I'm not that experienced in the UI part of the mod yet.

Note that the config reload button text (`text.owo.config.button.reload`) does not fit the reload button, so I had to contract it. You might want to fix that in the mod so that the button gets its size from its content or something like that, I'm not that experienced in the UI part of the mod yet.
Copy link
Copy Markdown

@VladisCrafter VladisCrafter left a comment

Choose a reason for hiding this comment

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

Hi :D

Co-authored-by: VladisCrafter <122053125+VladisCrafter@users.noreply.github.com>
@Bamberghh
Copy link
Copy Markdown
Author

Hi, all of the suggestions are great, I've applied them all. Though IDK when the PR will be approved, that's on the repo maintainers.

@VladisCrafter
Copy link
Copy Markdown

According to this message from @Dragon-Seeker, this PR is pretty much ready to be merged 🙂

@VladisCrafter
Copy link
Copy Markdown

VladisCrafter commented Nov 6, 2025

Btw @Bamberghh, why did you make the same PR for 1.21.5? The devs could port your commit to multiple branches themselves.
Or they do differ somehow?

@Bamberghh
Copy link
Copy Markdown
Author

@VladisCrafter IDK, I think at that time there were 2 active branches and I thought that I had to make PRs for both of them. Now that I think about it that was unnecessary since they have the same changes. Should I maybe delete the other PR?

@VladisCrafter
Copy link
Copy Markdown

Should I maybe delete the other PR?

Yes, I think it'd be better to close the other PR since it doesn't have the requested fixes yet can be merged by mistake which is definitely not good.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants