Welcome!
\n```\n\n### @import rules\n\nIf you don’t want to have all your locales in a single file or if you want to\nshare strings between several pages, you can use CSS-like `@import` rules.\n\nMore information on the [Language Selection](https://github.com/fabi1cazenave/webL10n/wiki/Language-Selection) page.\n\n### Pluralization\n\nThe following strings might be gramatically incorrect when `n` equals zero or one:\n\n```ini\n[en-US]\nunread = You have {{n}} unread messages\n[fr]\nunread = Vous avez {{n}} nouveaux messages\n```\n\nThis can be solved by using the pre-defined `plural()` macro:\n\n```ini\n[en-US]\nunreadMessages = {[ plural(n) ]}\nunreadMessages[zero] = You have no unread messages\nunreadMessages[one] = You have one unread message\nunreadMessages[other] = You have {{n}} unread messages\n[fr]\nunreadMessages = {[ plural(n) ]}\nunreadMessages[zero] = Vous n’avez pas de nouveau message\nunreadMessages[one] = Vous avez un nouveau message\nunreadMessages[other] = Vous avez {{n}} nouveaux messages\n```\n\nHere, `unreadMessages` is an array and `{[plural(n)]}` points to the selected index.\n\n`plural()` returns zero | one | two | few | many | other, depending on `n` and the current language, as specified in the Unicode rules. If one of these indexes isn’t found, the `[other]` index will be used by default.\n\n\n### innerHTML\n\nBy default, we currently assume that all strings are applied as `textContent`.\nHowever, you can modify the `innerHTML` property with a simple rule:\n\n```ini\nwelcome.innerHTML = welcome, {{user}}!\n```\n\nWarning: this raises a few security questions that we haven’t addressed yet. In a future version we might:\n* sanitize the localized string before applying it as `innerHTML` (like in the PHP ``strip_tags`` method)\n* provide text-to-HTML methods (e.g. markdown) throught pseudo-properties, for example:\n\n```ini\nwelcome#text = welcome, {{user}}!\nwelcome#html = welcome, {{user}}!\nwelcome#mark = welcome, **{{user}}**!\n```\n\n\nFurther thoughts\n----------------\n\n### Media queries\n\nFor mobile apps, here’s what I’d like to do:\n\n```html\n\n\n```\n\n### Multi-line strings\n\nMulti-line and wrapped strings aren’t supported at the moment. The *.properties way to extend a string on several lines is to use a backslash at the end of line… but there could be sharper/easier ways to handle that.\n\nYAML handles multi-line / wrapped strings nicely with the pipe and backslash operators, maybe we could reuse that in webL10n?\n\n\n### More structured syntax\n\nThere are cases where the entity has to be an array or a list (e.g. to handle plural rules), instead of a string. Currently we use the `entity[key]` notation but a more compact syntax could be supported as well.\n\nAlternatively, we could use a JSON- or YAML-like file format to handle the whole structure in a more modern way.\n\n\n### Logical expressions\n\nThe Mozilla l20n/LOL project introduces the concept of “expression”, which can be used to address most grammatical rules or some very specific situations.\n\nThe `plural()` macro above could be easily defined as an expression:\n\n```ini\nplural(n) = { n == 0 ? 'zero' : (n == 1 ? 'one' : 'other') }\n```\n\n\nBrowser support\n---------------\n\nTested on Firefox, Chrome, Opera and Internet Explorer 6 to 10.\n\n\nLicense\n-------\n\nBSD/MIT/WTFPL license. Use at your own risk.\n\n","maintainers":[{"name":"fabi1cazenave","email":"fabien@cazenave.cc"}],"time":{"modified":"2022-06-28T23:30:35.434Z","created":"2015-04-24T19:20:27.140Z","1.0.0":"2015-04-24T19:20:27.140Z"},"homepage":"https://github.com/fabi1cazenave/webL10n","keywords":["l10n","i18n"],"repository":{"type":"git","url":"https://github.com/fabi1cazenave/webL10n.git"},"author":{"name":"Fabien Cazenave"},"bugs":{"url":"https://github.com/fabi1cazenave/webL10n/issues"},"license":"WTFPL","readmeFilename":"README.md"}