On Fri, Apr 27, 2012 at 00:21:20 +0900, Osamu Aoki wrote: > I also see for libopencc1 (not mine but I am watching it...) > > [libopencc1 0.3.0-2] > usr/share/locale/zh_CN/LC_MESSAGES/opencc.mo > 2c2024df5378074f4727948eb7133516 mips s390 sparc s390x powerpc > 6a7df4d7f1f5383bd7461de8a0bb4957 kfreebsd-amd64 i386 armel armhf ia64 kfreebsd-i386 mipsel amd64 > usr/share/locale/zh_HK/LC_MESSAGES/opencc.mo > 66224514d0c66fd34bfbf95becf8cfd0 kfreebsd-amd64 i386 armel armhf ia64 kfreebsd-i386 mipsel amd64 > 6c6698b86bbf568baefc414d178108a0 mips s390 sparc s390x powerpc > usr/share/locale/zh_TW/LC_MESSAGES/opencc.mo > a7fe10a01d59cb26825678bb6c9c2402 kfreebsd-amd64 i386 armel armhf ia64 kfreebsd-i386 mipsel amd64 > d26ada42ce92c0cea19f4705ca89d433 mips s390 sparc s390x powerpc > > I guess the solution should be the same for now. > Not really. Mixed endian installs are probably going to be uncommon enough that it may be ok to ignore these until gettext grows a command-line flag to specify endianness of the .mo files it spits out. Cheers, Julien
Attachment:
signature.asc
Description: Digital signature