Account confirmers, canmove, Confirmed users
2,357
edits
L20n/Design: Difference between revisions
m
no edit summary
m (moved L20n:Design to L20n/Design: L20n is not a namespace.) |
mNo edit summary |
||
| Line 6: | Line 6: | ||
; localize objects, not string : It turns out that one challenge in localizing applications is keeping things together. Labels and accesskeys, for example. But for things like composing application names and toolkit messages, you want to find the gender of your application name next to your application name. Or the different plural forms don't really spread all over your localization file, they're an array. Localization applies to objects and it uses objects. Thus, L20n provides lists of localizable objects, <code>lol</code> in short, rather than a flock of strings. | ; localize objects, not string : It turns out that one challenge in localizing applications is keeping things together. Labels and accesskeys, for example. But for things like composing application names and toolkit messages, you want to find the gender of your application name next to your application name. Or the different plural forms don't really spread all over your localization file, they're an array. Localization applies to objects and it uses objects. Thus, L20n provides lists of localizable objects, <code>lol</code> in short, rather than a flock of strings. | ||
<div style="text-align:right"><b>[[L20n | <div style="text-align:right"><b>[[L20n/Characteristics|Next: Characteristics]]</b></div> | ||
[[category:L20n]] | [[category:L20n]] | ||