https://bugzilla.novell.com/show_bug.cgi?id=386298
User jsuchome@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=386298#c11
--- Comment #11 from Jiří Suchomel
The list of trans packages is autogenerated (from yast2-trans-allpacks). So yast, too, knows in advance which packages exist and can figure out that trans-pt_PT does not.
yast2-trans-allpacks is completely unrelated to the running YaST.
How do you handle Czech, for example? There's only trans-cs (and not cs_CZ, too).
Steffen, please read comment 5. YaST has this algorithm: "for each locale, take yast2-trans-[language-code].rpm. (e.g. yast2-trans-cs, yast2-trans-de). If for given locale there exist more country codes (and these are only en, pt, zh), take yast2-trans-[locale_code].rpm. (e.g. yast2-trans-en_US)" This works for every language except pt, because yast2-trans-pt, unlike en and zh doesn't use the full locale in the package name although there are more country codes for it.
If you really must, use trial and error to fetch a suitable trans package; but I will not symlink all possible long locale names to the short ones.
I'm asking you for one symlink to the package that has IMHO wrong name.
Renaming the packages is not a good idea, because, e.g., de is _not_ the same as de_DE but a fallback for all de_*.
Again, I call for renaming only yast2-trans-pt to fit the schema used by other package names. I hope it is clearer now. If you still refuse to create symlink, I could add a workaround to YaST. But do not forget to include yast2-trans-pt.rpm, currently it is not there. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.