@intlayer/docs 5.7.8 → 5.8.0-canary.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/blog/ar/intlayer_with_next-i18next.md +3 -4
- package/blog/ar/intlayer_with_next-intl.md +3 -4
- package/blog/ar/intlayer_with_react-i18next.md +1 -1
- package/blog/ar/intlayer_with_react-intl.md +1 -1
- package/blog/de/intlayer_with_next-i18next.md +3 -4
- package/blog/de/intlayer_with_react-intl.md +1 -1
- package/blog/en/intlayer_with_next-i18next.md +3 -4
- package/blog/en/intlayer_with_next-intl.md +3 -4
- package/blog/en/intlayer_with_react-i18next.md +1 -1
- package/blog/en/intlayer_with_react-intl.md +1 -1
- package/blog/en-GB/intlayer_with_next-i18next.md +3 -4
- package/blog/en-GB/intlayer_with_next-intl.md +3 -4
- package/blog/en-GB/intlayer_with_react-i18next.md +1 -1
- package/blog/en-GB/intlayer_with_react-intl.md +1 -1
- package/blog/es/intlayer_with_next-i18next.md +3 -4
- package/blog/es/intlayer_with_next-intl.md +3 -4
- package/blog/es/intlayer_with_react-i18next.md +1 -1
- package/blog/es/intlayer_with_react-intl.md +1 -1
- package/blog/fr/intlayer_with_next-i18next.md +3 -4
- package/blog/fr/intlayer_with_next-intl.md +3 -4
- package/blog/fr/intlayer_with_react-i18next.md +1 -1
- package/blog/fr/intlayer_with_react-intl.md +1 -1
- package/blog/hi/intlayer_with_next-i18next.md +3 -4
- package/blog/hi/intlayer_with_next-intl.md +3 -4
- package/blog/hi/intlayer_with_react-i18next.md +1 -1
- package/blog/hi/intlayer_with_react-intl.md +1 -1
- package/blog/it/intlayer_with_next-i18next.md +3 -4
- package/blog/it/intlayer_with_next-intl.md +3 -4
- package/blog/it/intlayer_with_react-i18next.md +1 -1
- package/blog/it/intlayer_with_react-intl.md +1 -1
- package/blog/ja/intlayer_with_next-i18next.md +3 -4
- package/blog/ja/intlayer_with_next-intl.md +3 -4
- package/blog/ja/intlayer_with_react-intl.md +1 -1
- package/blog/ko/intlayer_with_next-i18next.md +3 -4
- package/blog/ko/intlayer_with_next-intl.md +3 -4
- package/blog/ko/intlayer_with_react-intl.md +1 -1
- package/blog/pt/intlayer_with_next-i18next.md +3 -4
- package/blog/pt/intlayer_with_next-intl.md +3 -4
- package/blog/pt/intlayer_with_react-intl.md +1 -1
- package/blog/ru/intlayer_with_next-i18next.md +3 -4
- package/blog/ru/intlayer_with_next-intl.md +3 -4
- package/blog/ru/intlayer_with_react-i18next.md +1 -1
- package/blog/ru/intlayer_with_react-intl.md +1 -1
- package/blog/zh/intlayer_with_next-i18next.md +3 -4
- package/blog/zh/intlayer_with_next-intl.md +3 -4
- package/blog/zh/intlayer_with_react-i18next.md +1 -1
- package/blog/zh/intlayer_with_react-intl.md +1 -1
- package/dist/cjs/generated/docs.entry.cjs +41 -0
- package/dist/cjs/generated/docs.entry.cjs.map +1 -1
- package/dist/esm/generated/docs.entry.mjs +41 -0
- package/dist/esm/generated/docs.entry.mjs.map +1 -1
- package/dist/types/generated/docs.entry.d.ts +1 -0
- package/dist/types/generated/docs.entry.d.ts.map +1 -1
- package/docs/ar/formatters.md +239 -0
- package/docs/ar/interest_of_intlayer.md +162 -49
- package/docs/ar/introduction.md +3 -3
- package/docs/ar/packages/intlayer/index.md +3 -3
- package/docs/ar/packages/next-intlayer/index.md +3 -3
- package/docs/de/formatters.md +239 -0
- package/docs/de/interest_of_intlayer.md +161 -47
- package/docs/de/introduction.md +3 -3
- package/docs/de/packages/intlayer/index.md +3 -3
- package/docs/de/packages/next-intlayer/index.md +3 -3
- package/docs/de/packages/react-intlayer/index.md +3 -3
- package/docs/en/formatters.md +250 -0
- package/docs/en/interest_of_intlayer.md +159 -46
- package/docs/en/introduction.md +3 -3
- package/docs/en/packages/intlayer/index.md +3 -3
- package/docs/en/packages/next-intlayer/index.md +3 -3
- package/docs/en/packages/react-intlayer/index.md +3 -3
- package/docs/en-GB/formatters.md +239 -0
- package/docs/en-GB/interest_of_intlayer.md +160 -53
- package/docs/en-GB/packages/intlayer/index.md +3 -3
- package/docs/en-GB/packages/next-intlayer/index.md +3 -3
- package/docs/en-GB/packages/react-intlayer/index.md +3 -3
- package/docs/es/formatters.md +239 -0
- package/docs/es/interest_of_intlayer.md +159 -47
- package/docs/es/introduction.md +3 -3
- package/docs/es/packages/intlayer/index.md +3 -3
- package/docs/es/packages/next-intlayer/index.md +3 -3
- package/docs/fr/formatters.md +239 -0
- package/docs/fr/interest_of_intlayer.md +160 -46
- package/docs/fr/introduction.md +3 -3
- package/docs/fr/packages/intlayer/index.md +3 -3
- package/docs/fr/packages/next-intlayer/index.md +3 -3
- package/docs/fr/packages/react-intlayer/index.md +3 -3
- package/docs/hi/formatters.md +239 -0
- package/docs/hi/interest_of_intlayer.md +158 -42
- package/docs/hi/introduction.md +3 -3
- package/docs/hi/packages/intlayer/index.md +3 -3
- package/docs/hi/packages/next-intlayer/index.md +3 -3
- package/docs/hi/packages/react-intlayer/index.md +3 -3
- package/docs/it/formatters.md +239 -0
- package/docs/it/interest_of_intlayer.md +160 -46
- package/docs/it/introduction.md +3 -3
- package/docs/it/packages/intlayer/index.md +3 -3
- package/docs/it/packages/next-intlayer/index.md +3 -3
- package/docs/it/packages/react-intlayer/index.md +3 -3
- package/docs/ja/formatters.md +261 -0
- package/docs/ja/interest_of_intlayer.md +157 -48
- package/docs/ja/introduction.md +3 -3
- package/docs/ja/packages/intlayer/index.md +3 -3
- package/docs/ja/packages/next-intlayer/index.md +3 -3
- package/docs/ja/packages/react-intlayer/index.md +3 -3
- package/docs/ko/formatters.md +258 -0
- package/docs/ko/interest_of_intlayer.md +160 -48
- package/docs/ko/introduction.md +3 -3
- package/docs/ko/packages/intlayer/index.md +3 -3
- package/docs/ko/packages/next-intlayer/index.md +3 -3
- package/docs/ko/packages/react-intlayer/index.md +3 -3
- package/docs/pt/formatters.md +239 -0
- package/docs/pt/interest_of_intlayer.md +162 -47
- package/docs/pt/introduction.md +3 -3
- package/docs/pt/packages/intlayer/index.md +3 -3
- package/docs/pt/packages/next-intlayer/index.md +3 -3
- package/docs/pt/packages/react-intlayer/index.md +3 -3
- package/docs/ru/formatters.md +239 -0
- package/docs/ru/interest_of_intlayer.md +168 -50
- package/docs/ru/introduction.md +3 -3
- package/docs/ru/packages/intlayer/index.md +3 -3
- package/docs/ru/packages/next-intlayer/index.md +3 -3
- package/docs/ru/packages/react-intlayer/index.md +3 -3
- package/docs/zh/formatters.md +239 -0
- package/docs/zh/interest_of_intlayer.md +158 -48
- package/docs/zh/introduction.md +3 -3
- package/docs/zh/packages/intlayer/index.md +3 -3
- package/docs/zh/packages/next-intlayer/index.md +3 -3
- package/docs/zh/packages/react-intlayer/index.md +3 -3
- package/package.json +12 -12
- package/src/generated/docs.entry.ts +41 -0
|
@@ -24,7 +24,6 @@ Sia next-i18next che Intlayer sono framework di internazionalizzazione (i18n) op
|
|
|
24
24
|
Entrambe le soluzioni includono tre nozioni principali:
|
|
25
25
|
|
|
26
26
|
1. **Dichiarazione dei Contenuti**: Il metodo per definire i contenuti traducibili della tua applicazione.
|
|
27
|
-
|
|
28
27
|
- Chiamata `resource` nel caso di `i18next`, la dichiarazione dei contenuti è un oggetto JSON strutturato contenente coppie chiave-valore per traduzioni in una o più lingue. Vedi [documentazione di i18next](https://www.i18next.com/translation-function/essentials) per ulteriori informazioni.
|
|
29
28
|
- Chiamata `file di dichiarazione dei contenuti` nel caso di `Intlayer`, la dichiarazione dei contenuti può essere un file JSON, JS o TS che esporta i dati strutturati. Vedi [documentazione di Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/it/doc/concept/content) per ulteriori informazioni.
|
|
30
29
|
|
|
@@ -213,8 +212,8 @@ const content = {
|
|
|
213
212
|
content: {
|
|
214
213
|
myTranslatedContent: t({
|
|
215
214
|
en: "Hello World",
|
|
216
|
-
fr: "Bonjour le monde",
|
|
217
215
|
es: "Hola Mundo",
|
|
216
|
+
fr: "Bonjour le monde",
|
|
218
217
|
}),
|
|
219
218
|
},
|
|
220
219
|
} satisfies Dictionary;
|
|
@@ -231,8 +230,8 @@ const content = {
|
|
|
231
230
|
content: {
|
|
232
231
|
myTranslatedContent: t({
|
|
233
232
|
en: "Hello World",
|
|
234
|
-
fr: "Bonjour le monde",
|
|
235
233
|
es: "Hola Mundo",
|
|
234
|
+
fr: "Bonjour le monde",
|
|
236
235
|
}),
|
|
237
236
|
},
|
|
238
237
|
};
|
|
@@ -246,8 +245,8 @@ module.exports = {
|
|
|
246
245
|
content: {
|
|
247
246
|
myTranslatedContent: t({
|
|
248
247
|
en: "Hello World",
|
|
249
|
-
fr: "Bonjour le monde",
|
|
250
248
|
es: "Hola Mundo",
|
|
249
|
+
fr: "Bonjour le monde",
|
|
251
250
|
}),
|
|
252
251
|
},
|
|
253
252
|
};
|
|
@@ -23,7 +23,6 @@ Sia next-intl che Intlayer sono framework di internazionalizzazione (i18n) open-
|
|
|
23
23
|
Condividono tre notioni principali:
|
|
24
24
|
|
|
25
25
|
1. **Dichiarazione del Contenuto**: Il metodo per definire il contenuto traducibile della tua applicazione.
|
|
26
|
-
|
|
27
26
|
- Chiamato `content declaration file` in Intlayer, che può essere un file JSON, JS o TS che esporta i dati strutturati. Consulta la [documentazione di Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/it/concept/content) per ulteriori informazioni.
|
|
28
27
|
- Chiamato `messages` o `locale messages` in next-intl, solitamente in file JSON. Consulta la [documentazione di next-intl](https://github.com/amannn/next-intl) per ulteriori informazioni.
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -247,8 +247,8 @@ const content = {
|
|
|
247
247
|
// Ogni chiamata "t" è un nodo di traduzione separato
|
|
248
248
|
heading: t({
|
|
249
249
|
en: "Hello World",
|
|
250
|
-
fr: "Bonjour le monde",
|
|
251
250
|
es: "Hola Mundo",
|
|
251
|
+
fr: "Bonjour le monde",
|
|
252
252
|
}),
|
|
253
253
|
description: t({
|
|
254
254
|
en: "My i18n description text...",
|
|
@@ -118,8 +118,8 @@ const content = {
|
|
|
118
118
|
// Ogni chiamata a t() dichiara un campo traducibile
|
|
119
119
|
helloWorld: t({
|
|
120
120
|
en: "Hello World",
|
|
121
|
-
fr: "Bonjour le monde",
|
|
122
121
|
es: "Hola Mundo",
|
|
122
|
+
fr: "Bonjour le monde",
|
|
123
123
|
}),
|
|
124
124
|
description: t({
|
|
125
125
|
en: "This is a description",
|
|
@@ -24,7 +24,6 @@ Both next-i18next and Intlayer are open-source internationalization (i18n) frame
|
|
|
24
24
|
Both solutions include three principal notions:
|
|
25
25
|
|
|
26
26
|
1. **コンテンツ宣言**: アプリケーションの翻訳可能なコンテンツを定義するための方法。
|
|
27
|
-
|
|
28
27
|
- `i18next`の場合は`resource`として名付けられ、コンテンツ宣言は、1つまたは複数の言語の翻訳のためのキー-バリューのペアを含む構造化されたJSONオブジェクトです。詳細については、[i18nextのドキュメント](https://www.i18next.com/translation-function/essentials)を参照してください。
|
|
29
28
|
- `Intlayer`の場合は`content declaration file`として名付けられ、コンテンツ宣言は構造化データをエクスポートするJSON、JS、またはTSファイルになることができます。詳細については、[Intlayerのドキュメント](https://intlayer.org/fr/doc/concept/content)を参照してください。
|
|
30
29
|
|
|
@@ -209,8 +208,8 @@ const content = {
|
|
|
209
208
|
content: {
|
|
210
209
|
myTranslatedContent: t({
|
|
211
210
|
en: "Hello World",
|
|
212
|
-
fr: "Bonjour le monde",
|
|
213
211
|
es: "Hola Mundo",
|
|
212
|
+
fr: "Bonjour le monde",
|
|
214
213
|
}),
|
|
215
214
|
},
|
|
216
215
|
} satisfies Dictionary;
|
|
@@ -227,8 +226,8 @@ const content = {
|
|
|
227
226
|
content: {
|
|
228
227
|
myTranslatedContent: t({
|
|
229
228
|
en: "Hello World",
|
|
230
|
-
fr: "Bonjour le monde",
|
|
231
229
|
es: "Hola Mundo",
|
|
230
|
+
fr: "Bonjour le monde",
|
|
232
231
|
}),
|
|
233
232
|
},
|
|
234
233
|
};
|
|
@@ -242,8 +241,8 @@ module.exports = {
|
|
|
242
241
|
content: {
|
|
243
242
|
myTranslatedContent: t({
|
|
244
243
|
en: "Hello World",
|
|
245
|
-
fr: "Bonjour le monde",
|
|
246
244
|
es: "Hola Mundo",
|
|
245
|
+
fr: "Bonjour le monde",
|
|
247
246
|
}),
|
|
248
247
|
},
|
|
249
248
|
};
|
|
@@ -23,7 +23,6 @@ next-intl と Intlayer は、Next.js アプリケーション向けに設計さ
|
|
|
23
23
|
それぞれは、3 つの主要な概念を共有しています。
|
|
24
24
|
|
|
25
25
|
1. **コンテンツ宣言**: アプリケーションの翻訳可能なコンテンツを定義するためのメソッド。
|
|
26
|
-
|
|
27
26
|
- Intlayer では `content declaration file` と呼ばれ、構造化データをエクスポートする JSON、JS、または TS ファイルです。詳細は [Intlayer documentation](https://intlayer.org/fr/doc/concept/content) を参照してください。
|
|
28
27
|
- next-intl では `messages` または `locale messages` と呼ばれ、通常は JSON ファイルにあります。詳細は [next-intl documentation](https://github.com/amannn/next-intl) を参照してください。
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -24,7 +24,6 @@ both next-i18next와 Intlayer는 Next.js 애플리케이션용으로 설계된
|
|
|
24
24
|
두 솔루션은 세 가지 주요 개념을 포함합니다:
|
|
25
25
|
|
|
26
26
|
1. **콘텐츠 선언**: 애플리케이션의 번역 가능한 콘텐츠를 정의하는 방법입니다.
|
|
27
|
-
|
|
28
27
|
- `i18next`의 경우 `resource`라고 명명된 콘텐츠 선언은 하나 이상의 언어로된 번역의 키-값 쌍을 포함하는 구조화된 JSON 객체입니다. 자세한 내용은 [i18next 문서](https://www.i18next.com/translation-function/essentials)를 참조하십시오.
|
|
29
28
|
- `Intlayer`의 경우 `content declaration file`이라고 명명된 콘텐츠 선언은 구조화된 데이터를 내보내는 JSON, JS 또는 TS 파일이 될 수 있습니다. 자세한 내용은 [Intlayer 문서](https://intlayer.org/fr/doc/concept/content)를 참조하십시오.
|
|
30
29
|
|
|
@@ -213,8 +212,8 @@ const content = {
|
|
|
213
212
|
content: {
|
|
214
213
|
myTranslatedContent: t({
|
|
215
214
|
en: "Hello World",
|
|
216
|
-
fr: "Bonjour le monde",
|
|
217
215
|
es: "Hola Mundo",
|
|
216
|
+
fr: "Bonjour le monde",
|
|
218
217
|
}),
|
|
219
218
|
},
|
|
220
219
|
} satisfies Dictionary;
|
|
@@ -231,8 +230,8 @@ const content = {
|
|
|
231
230
|
content: {
|
|
232
231
|
myTranslatedContent: t({
|
|
233
232
|
en: "Hello World",
|
|
234
|
-
fr: "Bonjour le monde",
|
|
235
233
|
es: "Hola Mundo",
|
|
234
|
+
fr: "Bonjour le monde",
|
|
236
235
|
}),
|
|
237
236
|
},
|
|
238
237
|
};
|
|
@@ -246,8 +245,8 @@ module.exports = {
|
|
|
246
245
|
content: {
|
|
247
246
|
myTranslatedContent: t({
|
|
248
247
|
en: "Hello World",
|
|
249
|
-
fr: "Bonjour le monde",
|
|
250
248
|
es: "Hola Mundo",
|
|
249
|
+
fr: "Bonjour le monde",
|
|
251
250
|
}),
|
|
252
251
|
},
|
|
253
252
|
};
|
|
@@ -23,7 +23,6 @@ next-intl과 Intlayer는 Next.js 애플리케이션을 위해 설계된 오픈
|
|
|
23
23
|
이들은 세 가지 주요 개념을 공유합니다:
|
|
24
24
|
|
|
25
25
|
1. **콘텐츠 선언**: 애플리케이션의 번역 가능한 콘텐츠를 정의하는 방법입니다.
|
|
26
|
-
|
|
27
26
|
- Intlayer에서 `content declaration file`이라고 불리는 이 파일은 구조화된 데이터를 내보내는 JSON, JS 또는 TS 파일이 될 수 있습니다. 자세한 내용은 [Intlayer 문서](https://github.com/aymericzip/intlayer/blob/main/docs/docs/ko/concept/content)에서 확인하세요.
|
|
28
27
|
- next-intl에서는 일반적으로 JSON 파일에서 `messages` 또는 `locale messages`라고 불립니다. 자세한 내용은 [next-intl 문서](https://github.com/amannn/next-intl)에서 확인하세요.
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -24,7 +24,6 @@ Tanto next-i18next quanto Intlayer são frameworks de internacionalização (i18
|
|
|
24
24
|
Ambas as soluções incluem três noções principais:
|
|
25
25
|
|
|
26
26
|
1. **Declaração de Conteúdo**: O método para definir o conteúdo traduzível de sua aplicação.
|
|
27
|
-
|
|
28
27
|
- Nomeado `resource` no caso do `i18next`, a declaração de conteúdo é um objeto JSON estruturado contendo pares chave-valor para traduções em um ou mais idiomas. Veja a [documentação do i18next](https://www.i18next.com/translation-function/essentials) para mais informações.
|
|
29
28
|
- Nomeada `content declaration file` no caso do `Intlayer`, a declaração de conteúdo pode ser um arquivo JSON, JS ou TS exportando os dados estruturados. Veja a [documentação do Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/pt/doc/concept/content) para mais informações.
|
|
30
29
|
|
|
@@ -209,8 +208,8 @@ const content = {
|
|
|
209
208
|
content: {
|
|
210
209
|
myTranslatedContent: t({
|
|
211
210
|
en: "Hello World",
|
|
212
|
-
fr: "Bonjour le monde",
|
|
213
211
|
es: "Hola Mundo",
|
|
212
|
+
fr: "Bonjour le monde",
|
|
214
213
|
}),
|
|
215
214
|
},
|
|
216
215
|
} satisfies Dictionary;
|
|
@@ -227,8 +226,8 @@ const content = {
|
|
|
227
226
|
content: {
|
|
228
227
|
myTranslatedContent: t({
|
|
229
228
|
en: "Hello World",
|
|
230
|
-
fr: "Bonjour le monde",
|
|
231
229
|
es: "Hola Mundo",
|
|
230
|
+
fr: "Bonjour le monde",
|
|
232
231
|
}),
|
|
233
232
|
},
|
|
234
233
|
};
|
|
@@ -242,8 +241,8 @@ module.exports = {
|
|
|
242
241
|
content: {
|
|
243
242
|
myTranslatedContent: t({
|
|
244
243
|
en: "Hello World",
|
|
245
|
-
fr: "Bonjour le monde",
|
|
246
244
|
es: "Hola Mundo",
|
|
245
|
+
fr: "Bonjour le monde",
|
|
247
246
|
}),
|
|
248
247
|
},
|
|
249
248
|
};
|
|
@@ -23,7 +23,6 @@ Tanto o next-intl quanto o Intlayer são frameworks de internacionalização (i1
|
|
|
23
23
|
Eles compartilham três noções principais:
|
|
24
24
|
|
|
25
25
|
1. **Declaração de Conteúdo**: O método para definir o conteúdo traduzível da sua aplicação.
|
|
26
|
-
|
|
27
26
|
- Chamado de `arquivo de declaração de conteúdo` no Intlayer, que pode ser um arquivo JSON, JS ou TS exportando os dados estruturados. Veja [documentação do Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/pt/doc/concept/content) para mais informações.
|
|
28
27
|
- Chamado de `messages` ou `locale messages` no next-intl, geralmente em arquivos JSON. Veja [documentação do next-intl](https://github.com/amannn/next-intl) para mais informações.
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -118,8 +118,8 @@ const content = {
|
|
|
118
118
|
// Cada chamada a t() declara um campo traduzível
|
|
119
119
|
helloWorld: t({
|
|
120
120
|
en: "Hello World",
|
|
121
|
-
fr: "Bonjour le monde",
|
|
122
121
|
es: "Hola Mundo",
|
|
122
|
+
fr: "Bonjour le monde",
|
|
123
123
|
}),
|
|
124
124
|
description: t({
|
|
125
125
|
en: "This is a description",
|
|
@@ -24,7 +24,6 @@ slugs:
|
|
|
24
24
|
Обе решения включают три основных понятия:
|
|
25
25
|
|
|
26
26
|
1. **Декларация контента**: Метод определения переводимого контента вашего приложения.
|
|
27
|
-
|
|
28
27
|
- Называемый `resource` в случае `i18next`, декларация контента - это структурированный объект JSON, содержащий пары ключ-значение для переводов на одном или нескольких языках. Смотрите [документацию i18next](https://www.i18next.com/translation-function/essentials) для получения дополнительной информации.
|
|
29
28
|
- Называемый `content declaration file` в случае `Intlayer`, декларация контента может быть JSON, JS или TS файлом, экспортирующим структурированные данные. Смотрите [документацию Intlayer](https://github.com/aymericzip/intlayer/blob/main/docs/docs/ru/doc/concept/content) для получения дополнительной информации.
|
|
30
29
|
|
|
@@ -213,8 +212,8 @@ const content = {
|
|
|
213
212
|
content: {
|
|
214
213
|
myTranslatedContent: t({
|
|
215
214
|
en: "Hello World",
|
|
216
|
-
fr: "Bonjour le monde",
|
|
217
215
|
es: "Hola Mundo",
|
|
216
|
+
fr: "Bonjour le monde",
|
|
218
217
|
}),
|
|
219
218
|
},
|
|
220
219
|
} satisfies Dictionary;
|
|
@@ -231,8 +230,8 @@ const content = {
|
|
|
231
230
|
content: {
|
|
232
231
|
myTranslatedContent: t({
|
|
233
232
|
en: "Hello World",
|
|
234
|
-
fr: "Bonjour le monde",
|
|
235
233
|
es: "Hola Mundo",
|
|
234
|
+
fr: "Bonjour le monde",
|
|
236
235
|
}),
|
|
237
236
|
},
|
|
238
237
|
};
|
|
@@ -246,8 +245,8 @@ module.exports = {
|
|
|
246
245
|
content: {
|
|
247
246
|
myTranslatedContent: t({
|
|
248
247
|
en: "Hello World",
|
|
249
|
-
fr: "Bonjour le monde",
|
|
250
248
|
es: "Hola Mundo",
|
|
249
|
+
fr: "Bonjour le monde",
|
|
251
250
|
}),
|
|
252
251
|
},
|
|
253
252
|
};
|
|
@@ -23,7 +23,6 @@ slugs:
|
|
|
23
23
|
Они делят три основных понятия:
|
|
24
24
|
|
|
25
25
|
1. **Декларация содержимого**: Метод определения переводимого содержимого вашего приложения.
|
|
26
|
-
|
|
27
26
|
- Называется `content declaration file` в Intlayer, что может быть JSON, JS или TS файлом, экспортирующим структурированные данные. Смотрите [документацию Intlayer](https://intlayer.org/fr/doc/concept/content) для получения дополнительной информации.
|
|
28
27
|
- Называется `messages` или `locale messages` в next-intl, обычно в JSON-файлах. Смотрите [документацию next-intl](https://github.com/amannn/next-intl) для получения дополнительной информации.
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -247,8 +247,8 @@ const content = {
|
|
|
247
247
|
// Каждый вызов "t" - это отдельный узел перевода
|
|
248
248
|
heading: t({
|
|
249
249
|
en: "Hello World",
|
|
250
|
-
fr: "Bonjour le monde",
|
|
251
250
|
es: "Hola Mundo",
|
|
251
|
+
fr: "Bonjour le monde",
|
|
252
252
|
}),
|
|
253
253
|
description: t({
|
|
254
254
|
en: "My i18n description text...",
|
|
@@ -118,8 +118,8 @@ const content = {
|
|
|
118
118
|
// Каждый вызов t() объявляет переводимое поле
|
|
119
119
|
helloWorld: t({
|
|
120
120
|
en: "Hello World",
|
|
121
|
-
fr: "Bonjour le monde",
|
|
122
121
|
es: "Hola Mundo",
|
|
122
|
+
fr: "Bonjour le monde",
|
|
123
123
|
}),
|
|
124
124
|
description: t({
|
|
125
125
|
en: "This is a description",
|
|
@@ -24,7 +24,6 @@ both next-i18next 和 Intlayer 是为 Next.js 应用程序设计的开源国际
|
|
|
24
24
|
这两种解决方案包括三个主要概念:
|
|
25
25
|
|
|
26
26
|
1. **内容声明**:定义应用程序可翻译内容的方法。
|
|
27
|
-
|
|
28
27
|
- 在 `i18next` 的情况下称为 `resource`,内容声明是一个结构化的 JSON 对象,包含一种或多种语言翻译的键值对。有关更多信息,请参阅 [i18next 文档](https://www.i18next.com/translation-function/essentials)。
|
|
29
28
|
- 在 `Intlayer` 的情况下称为 `content declaration file`,内容声明可以是导出结构化数据的 JSON、JS 或 TS 文件。有关更多信息,请参阅 [Intlayer 文档](https://intlayer.org/fr/doc/concept/content)。
|
|
30
29
|
|
|
@@ -213,8 +212,8 @@ const content = {
|
|
|
213
212
|
content: {
|
|
214
213
|
myTranslatedContent: t({
|
|
215
214
|
en: "Hello World",
|
|
216
|
-
fr: "Bonjour le monde",
|
|
217
215
|
es: "Hola Mundo",
|
|
216
|
+
fr: "Bonjour le monde",
|
|
218
217
|
}),
|
|
219
218
|
},
|
|
220
219
|
} satisfies Dictionary;
|
|
@@ -231,8 +230,8 @@ const content = {
|
|
|
231
230
|
content: {
|
|
232
231
|
myTranslatedContent: t({
|
|
233
232
|
en: "Hello World",
|
|
234
|
-
fr: "Bonjour le monde",
|
|
235
233
|
es: "Hola Mundo",
|
|
234
|
+
fr: "Bonjour le monde",
|
|
236
235
|
}),
|
|
237
236
|
},
|
|
238
237
|
};
|
|
@@ -246,8 +245,8 @@ module.exports = {
|
|
|
246
245
|
content: {
|
|
247
246
|
myTranslatedContent: t({
|
|
248
247
|
en: "Hello World",
|
|
249
|
-
fr: "Bonjour le monde",
|
|
250
248
|
es: "Hola Mundo",
|
|
249
|
+
fr: "Bonjour le monde",
|
|
251
250
|
}),
|
|
252
251
|
},
|
|
253
252
|
};
|
|
@@ -23,7 +23,6 @@ next-intl 和 Intlayer 是为 Next.js 应用程序设计的开源国际化 (i18n
|
|
|
23
23
|
它们共享三个主要概念:
|
|
24
24
|
|
|
25
25
|
1. **内容声明**: 定义应用程序可翻译内容的方法。
|
|
26
|
-
|
|
27
26
|
- 在 Intlayer 中称为 `content declaration file`,可以是导出结构化数据的 JSON、JS 或 TS 文件。有关更多信息,请参见 [Intlayer 文档](https://github.com/aymericzip/intlayer/blob/main/docs/docs/zh/concept/content.md)。
|
|
28
27
|
- 在 next-intl 中称为 `messages` 或 `locale messages`,通常在 JSON 文件中。有关更多信息,请参见 [next-intl 文档](https://github.com/amannn/next-intl/blob/main/docs/zh/introduction.md)。
|
|
29
28
|
|
|
@@ -170,8 +169,8 @@ const content = {
|
|
|
170
169
|
content: {
|
|
171
170
|
helloWorld: t({
|
|
172
171
|
en: "Hello World",
|
|
173
|
-
fr: "Bonjour le monde",
|
|
174
172
|
es: "Hola Mundo",
|
|
173
|
+
fr: "Bonjour le monde",
|
|
175
174
|
}),
|
|
176
175
|
},
|
|
177
176
|
} satisfies Dictionary;
|
|
@@ -188,8 +187,8 @@ const content = {
|
|
|
188
187
|
content: {
|
|
189
188
|
helloWorld: t({
|
|
190
189
|
en: "Hello World",
|
|
191
|
-
fr: "Bonjour le monde",
|
|
192
190
|
es: "Hola Mundo",
|
|
191
|
+
fr: "Bonjour le monde",
|
|
193
192
|
}),
|
|
194
193
|
},
|
|
195
194
|
};
|
|
@@ -205,8 +204,8 @@ module.exports = {
|
|
|
205
204
|
content: {
|
|
206
205
|
helloWorld: t({
|
|
207
206
|
en: "Hello World",
|
|
208
|
-
fr: "Bonjour le monde",
|
|
209
207
|
es: "Hola Mundo",
|
|
208
|
+
fr: "Bonjour le monde",
|
|
210
209
|
}),
|
|
211
210
|
},
|
|
212
211
|
};
|
|
@@ -728,6 +728,47 @@ const docsEntry = {
|
|
|
728
728
|
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/hi/dictionary/translation.md"), "utf8")
|
|
729
729
|
)
|
|
730
730
|
},
|
|
731
|
+
"./docs/en/formatters.md": {
|
|
732
|
+
en: Promise.resolve(
|
|
733
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/en/formatters.md"), "utf8")
|
|
734
|
+
),
|
|
735
|
+
fr: Promise.resolve(
|
|
736
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/fr/formatters.md"), "utf8")
|
|
737
|
+
),
|
|
738
|
+
ru: Promise.resolve(
|
|
739
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/ru/formatters.md"), "utf8")
|
|
740
|
+
),
|
|
741
|
+
ja: Promise.resolve(
|
|
742
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/ja/formatters.md"), "utf8")
|
|
743
|
+
),
|
|
744
|
+
ko: Promise.resolve(
|
|
745
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/ko/formatters.md"), "utf8")
|
|
746
|
+
),
|
|
747
|
+
zh: Promise.resolve(
|
|
748
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/zh/formatters.md"), "utf8")
|
|
749
|
+
),
|
|
750
|
+
es: Promise.resolve(
|
|
751
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/es/formatters.md"), "utf8")
|
|
752
|
+
),
|
|
753
|
+
de: Promise.resolve(
|
|
754
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/de/formatters.md"), "utf8")
|
|
755
|
+
),
|
|
756
|
+
ar: Promise.resolve(
|
|
757
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/ar/formatters.md"), "utf8")
|
|
758
|
+
),
|
|
759
|
+
pt: Promise.resolve(
|
|
760
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/pt/formatters.md"), "utf8")
|
|
761
|
+
),
|
|
762
|
+
"en-GB": Promise.resolve(
|
|
763
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/en-GB/formatters.md"), "utf8")
|
|
764
|
+
),
|
|
765
|
+
it: Promise.resolve(
|
|
766
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/it/formatters.md"), "utf8")
|
|
767
|
+
),
|
|
768
|
+
hi: Promise.resolve(
|
|
769
|
+
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/hi/formatters.md"), "utf8")
|
|
770
|
+
)
|
|
771
|
+
},
|
|
731
772
|
"./docs/en/how_works_intlayer.md": {
|
|
732
773
|
en: Promise.resolve(
|
|
733
774
|
(0, import_promises.readFile)((0, import_path.join)(dir, "../../../docs/en/how_works_intlayer.md"), "utf8")
|