The list will change over time (as we make new spec releases) and, invariably, the spec team will screw up and and the list will be incorrect. :-) So we chose to not put such a list in the spec.
For each header defined by the spec, if the framework will use the header value in some way (e.g. Import-Package) then that header has framework semantics and the framework must not use any localization of the header. Others, like Bundle-Description, are never used by the framework. So, if you are implementing the framework, any header whose value you would need to use should be the original, unlocalized value. BJ Hargrave Senior Technical Staff Member, IBM OSGi Fellow and CTO of the OSGi Alliance [EMAIL PROTECTED] office: +1 407 849 9117 mobile: +1 386 848 3788 David Kemper <[EMAIL PROTECTED]> Sent by: [EMAIL PROTECTED] 11/13/2006 11:44 AM Please respond to OSGi Developer Mail List <osgi-dev@bundles.osgi.org> To osgi-dev@bundles.osgi.org cc Subject [osgi-dev] manifest localization Section 3.10.2 (Manifest Localization) of the R4 specification states that "All headers in a bundle's manifest can be localized. However, the Framework must always use the non-localized versions of headers that have Framework semantics." I can make a guess as to which of the 23 manifest headers (see 3.2.1.1 through 3.2.1.23) have "Framework semantics" but would appreciate the list from a more official source. Also, I suggest that the list be made more explicit in the next revision of the specification. If the list is made clear in the specification, maybe someone could point it out and accept my apologies? Thanks in advance. /djk _______________________________________________ OSGi Developer Mail List osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev _______________________________________________ OSGi Developer Mail List osgi-dev@bundles.osgi.org http://bundles.osgi.org/mailman/listinfo/osgi-dev
