Changes

Development Team/Almanac/Activity Bundles (view source)

Revision as of 09:11, 23 March 2007

271 bytes removed , 09:11, 23 March 2007

→‎Activity Name Localization/Translation

Line 82: Line 82:

= Activity Name Localization/Translation =

−

Localizated data lives in the ~~activity/~~localized/ directory. Localized keys from the 'activity.info' file are stored in the '.linfo' files in that directory. ~~Each language stores its localized keys in a <u>separate</u> '.linfo' file named for the language's ISO code.~~ For example, German-localized German (as opposed to Swiss-localized German) language translations are stored in the 'de_DE.linfo' file.

+

Localizated data lives in the locale directory. Each language stores its localized keys in a <u>separate</u> directory named for the language's ISO code. Localized keys from the 'activity.info' file are stored in the 'activity.linfo' files in that directory. For example, German-localized German (as opposed to Swiss-localized German) language translations are stored in the 'de_DE/activity.linfo' file.

−

At this time, only translations for the 'name' ~~and 'icon' keys~~ from the 'activity.info' file ~~are~~ supported. A localized 'de_DE.linfo' file would look like:

+

At this time, only translations for the 'name' key from the 'activity.info' file is supported. A localized 'de_DE.linfo' file would look like:

name = Web

−

'icon' keys only need to be localized when the icon itself includes language- or culture-specific material. For example, if the icon was the first letter of a word, that word may be different in other languages and therefore would need to be localized.

Keys in the languague-specific '.linfo' files selectively override keys from the 'activity.info' file; if a key is not present in the '.linfo' file the value from the 'activity.info' file is used instead.

−

= Other Technologies Comparison =

Anonymous user

87.5.119.17