Sausalito Developer's Guide - Parent Directory

More documents

Recommendations

Info

4—2 Chapter 4: Using i18n and l10n in Sausalito Beta Draft 11. Copyright ' 2001.Cobalt Networks, Inc. All Rights Reserved. Localization means the operation by which, in a set of programs already internationalized, the developer gives the program all needed information so that it can adapt itself to handle its input and output in a fashion that is correct for some native language and cultural habits. This is a particularisation process, by which language and cultural habits. This is a particularisation process, by which generic methods already implemented in an internationalized program are used in specific ways. The programming environment puts several functions to the programmers disposal which allow this runtime configuration. The formal description of specific set of cultural habits for some country, together with all associated translations targeted to the same native language, is called the locale for this language or country. Users achieve localization of programs by setting proper values to special environment variables, prior to executing those programs, identifying which locale should be used. How Internationalization Works The Sausalito architecture provides a simple-to-use interface into a database of localized strings used for internationalizing applications. This i18N interface is similar to the GNU gettext interface, and is, in fact, a higher-level wrapper than encapsulates GNU gettext functionality. Like GNU gettext, the Sausalito i18n library allows developers to create their own databases of localized strings, and provides an interface for accessing that database from within applications. The Sausalito i18n wrapper library adds the following new functionality: ¥ Strings fetched from the library are subject to an interpolation process, in which usersupplied variables and even other internationalized strings can be automatically substituted into the localized string. ¥ Access to a set of routines for properly escaping the fetched strings for use in web applications, that is, for use in HTML documents or JavaScript programs. ¥ Automatic negotiation of the best possible locale, from a preference-ordered list of locales.
Chapter 4: Using i18n and l10n in Sausalito 4—3 Beta Draft 11. Copyright ' 2001. Cobalt Networks, Inc. All Rights Reserved. Using Domains, Tags, and Locales Domains Tags Locale The Sausalito i18N library manages a database of localized strings. Each application or module is granted it’s own namespace within the database. This namespace is a called a domain. Within each domain, individual messages are identified a string known as the message tag. When an application retrieves a message from the i18N database based on the message’s domain and message tag, the i18n searches the database for a localized message that most closely matches the preferred locale. A domain is a grouping for a similar set of resources, for example, the sendmail package can be a unique domain. In practical terms, localization strings are packaged by domain. Each domain defines the default language for its use in its own prop file. This file contains only a locale specification. The file is located in the same directory and locale property files except that its name is derived from the domain rather than the locale, for example, cobalt.prop for the Cobalt domain. Developers retrieve message strings from the i18N database by specifying both the domain and the message identifier for each string. A tag identifies a text string within a domain of strings for used in interpolation and I18N. The tag identifies the localized string. The localized string is identified by the tag specified in the function call and the domain specified within the i18N object. The locale used is the one negotiated during the creation of the i18N object. Developers retrieve message strings from the i18N database by specifying both the domain and the message id for each string using the "[[domain.msgid]]" tags. Locales are specified by strings that start with an ISO-639 two-letter language code and an optional variant, all separated by underscore characters, for example, en_US.
Page 1 and 2: Sausalito Developer’s Guide Beta
Page 3 and 4: Contents iii Acknowledgements . . .
Page 5 and 6: Contents v Syntax: PROPERTY . . . .
Page 7 and 8: Contents vii Usage . . . . . . . .
Page 9 and 10: Contents ix removeIcon. . . . . . .
Page 11 and 12: Contents xi The BYE Command. . . .
Page 13 and 14: Chapter 1 Introducing The Sausalito
Page 15 and 16: Chapter 1: Introducing The Sausalit
Page 17 and 18: Chapter 1: Introducing The Sausalit
Page 19 and 20: Chapter 2 About The Sausalito Archi
Page 21 and 22: Chapter 2: About The Sausalito Arch
Page 29 and 30: Chapter 3 User Interface Chapter Co
Page 31 and 32: Chapter 3: User Interface 3—3 Bet
Page 39 and 40: Chapter 3: User Interface 3—11 Be
Page 41: Chapter 4 Using i18n and l10n in Sa
Page 45 and 46: Chapter 4: Using i18n and l10n in S
Page 57 and 58: Chapter 5 Introducing The Cobalt Co
Page 59 and 60: Chapter 5: Introducing The Cobalt C
Page 93 and 94:
Chapter 5: Introducing The Cobalt C
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Chapter 6 Making Sausalito-Aware Ap
Page 107 and 108:
Chapter 6: Making Sausalito-Aware A
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Appendix A User Interface Foundatio
Page 131 and 132:
Appendix A: User Interface Foundati
Page 133 and 134:
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Page 167 and 168:
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Appendix B Utility Classes ArrayPac
Page 201 and 202:
Appendix B: Utility Classes B—3 B
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Appendix C l About Style Style File
Page 209 and 210:
Appendix C: About Style C—3 Beta
Page 211 and 212:
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Appendix D Base Data Types Scalar W
Page 237 and 238:
Appendix D: Base Data Types D—3 B
Page 239 and 240:
Appendix D: Base Data Types D—5 B
Page 241 and 242:
Appendix E Cobalt System Configurat
Page 243 and 244:
Appendix E: Cobalt System Configura
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Appendix F CCE Class Definitions Ch
Page 255 and 256:
Appendix F: CCE Class Definitions F
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Index Symbols .pkg file format 6-1
Page 263 and 264:
event_object( ) 5-42 event_oid( ) 5
Page 265:
MacAddress A-28 MailListName A-28 M
show all

Sausalito Developer's Guide - Parent Directory

Create successful ePaper yourself

Delete template?

Save as template?