-
-
Notifications
You must be signed in to change notification settings - Fork 119
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
Locale file names #75
Comments
How exactly would be Linux packaging easier? Can you put some example here, please? :)
Why? |
I don't know whether this is a general Qt guideline or not, but when building a separate -lang package, some distros like openSUSE, Fedora, Mageia et al. use the %find_lang macro which fails to identify the locale files when a hyphen instead of an underscore is used as separator (see https://github.com/rpm-software-management/rpm/blob/master/scripts/find-lang.sh#L116). Regards |
So when you tried to use hyphens, it worked? Does replacing underscores with hyphens do the trick? If so, then I guess I could rename those files. |
The other way around, but yes. I apply this patch to package rssguard on openSUSE (the path is not relevant though). |
Nice patch! But why is directory |
Follow-up: You package RSS Guard "officially" for some distro? |
Oh no, the path is not important, I just changed it because every other app I encountered used the "lang" folder. Concerning the rest, I submitted rssguard to be included in the main repository, but these things take time. By the way, I recently updated the Italian translation on transifex if you want to integrate it. |
I see, I could change it too, "lang" is more self-descriptive.
Perfect, I will trigger the sync and push it to repo. |
Sorry, I still see locale filenames using hyphens instead of underscores. |
You need to check [dev] branch, https://github.com/martinrotter/rssguard/tree/dev |
Ouch, sorry. |
Linux packaging would be a tad easier if locale files had an
underscore instead of a hyphen in their names.
E.g. rssguard-en.ts -> rssguard_en.ts, otherwise they might not
be recognised as l10n.
The text was updated successfully, but these errors were encountered: