Changes

Line 138: Line 138:  
: Tags give more context in which to place the activity. This is used to allow users to find activities more easily in the journal, the home view, [http://activities.sugarlabs.org http://activities.sugarlabs.org], etc.
 
: Tags give more context in which to place the activity. This is used to allow users to find activities more easily in the journal, the home view, [http://activities.sugarlabs.org http://activities.sugarlabs.org], etc.
   −
== Activity name localization/translation ==
+
== Localization/translation of the activity name and tags ==
    
Localized 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:
 
Localized 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:
Line 154: Line 154:  
             activity.linfo
 
             activity.linfo
   −
At this time, only translations for the 'name' key from the 'activity.info' file is supported.  A localized 'de_DE/activity.linfo' file would look like:
+
At this time, only translations for the 'name' and 'tags' keys from the 'activity.info' file is supported.  A localized 'de_DE/activity.linfo' file would look like:
    
  [Activity]
 
  [Activity]
 
  name = Web
 
  name = Web
 +
tags = erforschung;web
    
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.
 
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.
647

edits