2011/4/5 Jeff Johnson <n3...@mac.com>: > No way Jose! > > rpmbuild (and *.rpm metadata) can NOT have any encoding > assumed. > > Encoding is for DISPLAY, not for octets. > > Put unicode into package metadata at your own peril. > > Meanwhile -- without an means to specify encoding in metadata -- > rpm in C has *ONLY* 8 bit clean octet's and the usual conventions > for NUL terminated strings. > > Until there's a well defined means of specifying encoding for all > tag strings -- and that's a fundamental design change to *.rpm packaging that > likely will NEVER happen -- the problem simply CANNOT be fixed to meet naive > luser expectations, and all attempts to "fix" anything > are just doomed. > > C has octest, not utf8, and rpmdb strings are _NOT_ based on LC_ALL > and other i18n/l10n conventions. > > You can of course put whatever garbage you wish into strings that > will be stored as keys in an rpmdb, subject to all the usual > GIGO conventions distro's wish to inflict upon their customers. Okay, my mistake anyways, I was looking into an issue with unicode strings, then I specified wrong locale when testing. I notice now that with properly specified locale, it accepts unicode characters.
Still though, using '%description -l', descriptions disappears.. :| -- Regards, Per Øyvind ______________________________________________________________________ RPM Package Manager http://rpm5.org Developer Communication List rpm-devel@rpm5.org
