-
Notifications
You must be signed in to change notification settings - Fork 72
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
Notifications only in English? #287
Comments
Which language? The strings in AppConsole.vala notify_user() are translatable, but maybe those particular strings are not translated for whatever language you tried, or maybe there isn't even any XX.po for that language at all. It's several annoying steps to rig things up to debug notifications so I'll come back later with a set of steps to follow to kick off notifications on demand and generate log files from both mainline and notice.sh to see why it's choosing English. |
to debug, in this order: First, update to 1.4.1. Use the app to uninstall or un-hide as necessary, and reboot if necessary, to make it so that there is at least one available valid un-hidden kernel that is not installed, and you are running something older than the latest. Don't expect to see any notifications yet while doing this. You might, you might not, but we don't care yet. If you didn't have to reboot above just to downgrade, then reboot now regardless. It's just to ensure that there are no old notify.sh or sleep or notice.sh processes from before the 1.4.1 fixup. in a terminal run: A notification should appear. You can leave it up or dismiss it. Go look in There will likely be two *.e files and one *.p file. You are interested in the lower PID#.e file, aka the larger size one. You can then delete all 3 files and re-run the exact same command above and it will do another notification each time as though you never saw that yet or as though you were logging in after a reboot. You can paste the whole log here if you look it over and decide there is nothing like a password or anything in there. |
Here's the log file: _usr_lib_mainline_notice.sh.1638.e.zip |
Thank you. This shows that definitely there is nothing like a LANG=C in effect at the time either The gui app is So in both cases, the gui and the cli apps, all the language environment settings are the same and But I think I see a couple things to investigate. Could you please run just What I noticed and what I suspect is this: Another thing, or I guess probably this is the same thing, is the gettext manual says for vala: That MESSAGES vs ALL is sure suspicious considering this observed behavor. Especially if you can tell me that the help output comes out localized. Maybe it means that gettext is only translating strings that it thinks are messages? IE, only things that end up getting fed into printf() or any other functions it thinks are "message handlers" which could include all the gui widget display things, all probably handled by the Intl binding library for vala probably. So maybe there are two possible fixes to try, either pass that string through sprintf() or similar just so that it goes through a printf() of any flavor and "looks like a message", or maybe that ALL parameter would cause it to start being translated just where it is without changing anything else because it would no longer limit itself to "things that look like a message"? I'm poking at it now. |
Wait, it literally is exactly printf(): |
At least on Xfce (with non-English locales), notifications are being shown in English despite being translated in Mainline (various versions). Can someone confirm it?
The text was updated successfully, but these errors were encountered: