8000 Translation should not default to Ukrainian when using Russian locale · Issue #5671 · fyne-io/fyne · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Translation should not default to Ukrainian when using Russian locale #5671

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

Open
2 tasks done
ztx-lyghters opened this issue Apr 15, 2025 · 4 comments
Open
2 tasks done
Labels
enhancement New feature or request

Comments

@ztx-lyghters
Copy link
Contributor
ztx-lyghters commented Apr 15, 2025

Checklist

  • I have searched the issue tracker for open issues that relate to the same problem, before opening a new one.
  • This issue only relates to a single bug. I will open new issues for any other problems.

Describe the bug

With Fyne v2.6.0, if app is run with ru_RU.UTF-8 locale, Ukrainian base translation is being used. Since there is no Russian base translation, English should be used by default instead, as it was in v2.5.3.

How to reproduce

  1. Create new Go module with the example code below
  2. Run the app with LANG="ru_RU.UTF-8": LANG="ru_RU.UTF-8" go run .
  3. Get Ukrainian translation in confirmation dialog buttons

Screenshots

Image

Example code

main.go:

package main

import (
	"fyne.io/fyne/v2/app"
	"fyne.io/fyne/v2/dialog"
)

func main() {
	a := app.New()
	w := a.NewWindow("test")

	dialog.ShowConfirm("test", "testing", func(b bool) {}, w)

	w.Show()
	a.Run()
}

Fyne version

2.6.0

Go compiler version

1.23.5

Operating system and version

Linux

Additional Information

No response

@ztx-lyghters ztx-lyghters added the unverified A bug that has been reported but not verified label Apr 15, 2025
andydotxyz added a commit to andydotxyz/fyne that referenced this issue Apr 15, 2025
@andydotxyz
Copy link
Member

Thanks for this report. The system we use to resolve languages decided that the two were more similar, but I understand the request.
The pull request changes the lookup as suggested.

@andydotxyz andydotxyz added enhancement New feature or request and removed unverified A bug that has been reported but not verified labels Apr 15, 2025
@andydotxyz andydotxyz added this to the F fixes (v2.6.x) milestone Apr 15, 2025
@lifedaemon-kill
Copy link
lifedaemon-kill commented Apr 22, 2025

i just wrote my own file base.ru.json and used lang="ru_RU.UTF-8" And it worked, it is necessary to make a pull request so that the developers add a translation

@ztx-lyghters
Copy link
Contributor Author
ztx-lyghters commented Apr 22, 2025

i just wrote my own file base.ru.json and used lang="ru_RU.UTF-8" And it worked, it is necessary to make a pull request so that the developers add a translation

there was an ongoing pull request with Russian translation, which I suggested a few fixes to, but apparently it was based on the wrong branch or something. I have contributed a few changes on Weblate, but I don't know what else there is to be done

@andydotxyz
Copy link
Member

Weblate changes automatically merge in - you can test develop branch to see the Russian translation in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants
0