Re: qestions about rpm localization and license display

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Le mer 14/01/2004 à 03:37, Joey Shen a écrit :
> Thanks Nicolas,
> 
> In that case, I'll keep the license file in %doc. And I'm not intending 
> to change the standard behavior and philosophy of rpm.
> 
> Any ideas about the localization problem? Although I didn't see any 
> localized rpm packages, I wonder if there could be some in theory.

You have two localisation options :
- use centralised translations like Redhat does ; this permits economies
of scale but sucks big time for stuff that isn't part of the core
distribution
- localise directly in the spec (I think Mandrake uses this tech). The
two main problems are :
  * spec encoding in undefined (though it's moving de-facto to UTF-8
now, so this shouldn't be a problem anymore)
  * US coders tend to be upset when strange strings they don't
understand start to pollute their file.

Anyhow, for i18n and localisation stuff you should really look at the
way non-US distributions handle it, since Americans tend to be real
insensitive to this kind of problems.

Cheers,

-- 
Nicolas Mailhot

Attachment: signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=


[Index of Archives]     [RPM Ecosystem]     [Linux Kernel]     [Red Hat Install]     [PAM]     [Red Hat Watch]     [Red Hat Development]     [Red Hat]     [Gimp]     [Yosemite News]     [IETF Discussion]

  Powered by Linux