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

Localization broken #37

Open
calimeroteknik opened this issue Jan 10, 2017 · 7 comments
Open

Localization broken #37

calimeroteknik opened this issue Jan 10, 2017 · 7 comments

Comments

@calimeroteknik
Copy link

SVN r515 was fine, but since the new build system was introduced (in SVN r516), localization is broken and fbpanel displays with the C locale.
This of course isn't noticeable to English-language users.

@lodgerz
Copy link

lodgerz commented Feb 10, 2018

confirm, my system is in italian language but systemmenu of fbpanel is english. how can i solve?

@calimeroteknik
Copy link
Author

@lodgerz this bug has been around for years, this is starting to smell of abandonware.
When the build system was changed at revision 515, localization was broken in the process.

As for solving, you need to copy the missing files, as I do in that packaging script:
https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=fbpanel-git

I guess the author has an English locale and therefore does not care.

@mckaygerhard
Copy link

a 👍 here @calimeroteknik this is the only real issue in the hole list of issues.. @lodgerz me too noted this problem..

@aanatoly this are some king of irresponsability.. seems do you not noted that you are using only english desktop..

but @calimeroteknik please dont paste link to shit script that in future can be dissapear (specially from a distro that are a fashion way of made thigs)

here are the manual fix of:

    cd po
    for mofile in *.mo;do
        install -Dm755 "$mofile" "{{prefix}}/usr/share/fbpanel/locale/${mofile%%_*}/LC_MESSAGES/fbpanel.mo"
    done

of course due the configure scrip must be tuned.. i'm too busy right now and this manual fix works for debian of course

@calimeroteknik
Copy link
Author

No reason to be irate or rude, though; you're not paying anything to the author, this is all voluntary work.

@mckaygerhard
Copy link

i can make a PR but seems will be ignored for a time! ... does that mean if are free are less important?

@calimeroteknik
Copy link
Author

I don't really understand what you mean.
If that answers your question, I believe that you can't demand anything from software that is available to you for free.

Since this can be forked freely, you may just as well have your own fixed fork ; of course this is some trouble, and it's much more interesting to upstream your patches, but when the original author/maintainer hasn't replied about such as simple fix for more than 3 years and you're in a relative hurry, you might as well maintain it your own fork.
You know — it's free software.

Besides, with Wayland being the next display manager norm, fbpanel is in need of either a rewrite for some Wayland compositor protocol for panels like wlroot's, or just a replacement.

@mckaygerhard
Copy link

@calimeroteknik I will repeat: I can make a Pull Request CALLED "PR" to be seen by the author, but in first place. seems author are not very alert respect fbpanel repository..
and in second place: but the objective of fbpanel is not to be more complex or to give support to more complex things... (neither things that are criticited to be far away of unix spirit) but to the simple things... wayland and several monitors is already something more complex than just showing the panel and painting a menu in it.

in last and most important way: "you're not paying" and "voluntary work", what does that means? if it's voluntary and free you don't have to put in the same effort as if it were something paid for? it's not strange because the bosses always say "put in some real software" instead of using free software.. or else when they use free software they alter it and never return what's really important (like androit and azure)

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

No branches or pull requests

3 participants