|
|
| Line 4: |
Line 4: |
|
| |
|
| L20n is a localization format and an API that is aiming at remodeling the way developers internationalize their code and how localization is being done. | | L20n is a localization format and an API that is aiming at remodeling the way developers internationalize their code and how localization is being done. |
|
| |
| === Contract ===
| |
|
| |
| L20n provides a notion of a contract between a developer and a localizer which is expressed in a form of a unique ID defined by the developer. Under this contract the developer defines the message that should be carried to the user, UI in which the string will be used and parameters required to build the message.
| |
| Localizer provides a fully localized and tailored entity in return that is bind to the given identifier.
| |
|
| |
| === Communication layer ===
| |
|
| |
| The communication layer between the developer and the localizer is set in a very different point than in most other localization systems. The developer is expected to provide a single entity ID and, optionally, a set of parameters required to build the message, and receive a complete result, no matter of the language.
| |
|
| |
| Whole logic that is required to build the message should be hidden and separated from the code logic and is a part of localization format. It's also separated from any other localization so that different locales do not leak onto each other their custom requirements and linguistic features.
| |
|
| |
|
| == Goals == | | == Goals == |