|
79 | 79 | "getting-started.paragraph.create-translations-1": "Next create a folder to put your translations files in. I like to use",
|
80 | 80 | "getting-started.paragraph.create-translations-2": "at the root of the project, but really any folder will do.",
|
81 | 81 | "getting-started.paragraph.create-translations-3": "I recommend using JSON files but you can use use javascript with an object as their default export. Whatever the file extension, you translations inside are just regular strings in the ICU message syntax:",
|
| 82 | + "getting-started.paragraph.create-translations-4": "I prefer when the dictionary has a single level and using dots to create hierarchies like in the one above, but you can also nest objects like in the next example:", |
82 | 83 | "getting-started.paragraph.create-translations-5": "JSON is too constrained! I want more flexibility!",
|
83 | 84 | "getting-started.paragraph.create-translations-6": "You can also use JSON 5 features in your json files. That is, you can have comments, multi-line strings, single quotes, trailing commas... <br>It just works out of the box.",
|
84 | 85 | "getting-started.paragraph.create-translations-7": "I don't like curly braces",
|
|
99 | 100 | "configuration.paragraph.example-3": "This will get you going but lets dive deeper on it more.",
|
100 | 101 | "configuration.subsection.static-locales": "Load locales statically",
|
101 | 102 | "configuration.paragraph.static-locales-1": "Like in the previous example, the easiest way to add your translation keys is to just import them as modules and register them using",
|
102 |
| - "conw": "Note that despite the fact that you defined your translations in JSON files, in here you are importing them as javascript modules from", |
| 103 | + "configuration.paragraph.static-locales-2": "Note that despite the fact that you defined your translations in JSON files, in here you are importing them as javascript modules from", |
103 | 104 | "configuration.paragraph.static-locales-3": ". This is because the compiler has transformed your translations into a module with inline functions at built time.",
|
104 | 105 | "configuration.paragraph.static-locales-4": "This approach is loading all those languages even if only one is being displayed. Usually okay when kicking out a new project or if you only have a few of keys, but when your app grows you should start loading languages on demand.",
|
105 | 106 | "configuration.subsection.dynamic-locales": "Load locales dynamically",
|
|
0 commit comments