@intlayer/docs 7.3.1 → 7.3.2-canary.1
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/README.md +0 -2
- package/blog/ar/compiler_vs_declarative_i18n.md +1 -2
- package/blog/ar/i18n_using_next-i18next.md +8 -0
- package/blog/ar/i18n_using_next-intl.md +7 -0
- package/blog/ar/intlayer_with_next-intl.md +8 -0
- package/blog/ar/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/de/compiler_vs_declarative_i18n.md +1 -2
- package/blog/de/i18n_using_next-i18next.md +8 -0
- package/blog/de/i18n_using_next-intl.md +7 -0
- package/blog/de/intlayer_with_next-intl.md +8 -0
- package/blog/de/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/en/compiler_vs_declarative_i18n.md +1 -2
- package/blog/en/i18n_using_next-i18next.md +8 -0
- package/blog/en/i18n_using_next-intl.md +7 -0
- package/blog/en/intlayer_with_next-intl.md +8 -0
- package/blog/en/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/en/list_i18n_technologies/frameworks/svelte.md +19 -3
- package/blog/en/list_i18n_technologies/frameworks/vue.md +16 -2
- package/blog/en-GB/compiler_vs_declarative_i18n.md +1 -2
- package/blog/en-GB/i18n_using_next-i18next.md +8 -0
- package/blog/en-GB/i18n_using_next-intl.md +7 -0
- package/blog/en-GB/intlayer_with_next-intl.md +8 -0
- package/blog/en-GB/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/es/compiler_vs_declarative_i18n.md +1 -2
- package/blog/es/i18n_using_next-i18next.md +8 -0
- package/blog/es/i18n_using_next-intl.md +7 -0
- package/blog/es/intlayer_with_next-intl.md +8 -0
- package/blog/es/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/fr/compiler_vs_declarative_i18n.md +1 -2
- package/blog/fr/i18n_using_next-i18next.md +8 -0
- package/blog/fr/i18n_using_next-intl.md +7 -0
- package/blog/fr/intlayer_with_next-intl.md +8 -0
- package/blog/fr/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/hi/compiler_vs_declarative_i18n.md +2 -3
- package/blog/hi/i18n_using_next-i18next.md +8 -0
- package/blog/hi/i18n_using_next-intl.md +7 -0
- package/blog/hi/intlayer_with_next-intl.md +8 -0
- package/blog/hi/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/id/compiler_vs_declarative_i18n.md +1 -2
- package/blog/id/i18n_using_next-i18next.md +8 -0
- package/blog/id/i18n_using_next-intl.md +7 -0
- package/blog/id/intlayer_with_next-intl.md +8 -0
- package/blog/id/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/it/compiler_vs_declarative_i18n.md +1 -2
- package/blog/it/i18n_using_next-i18next.md +8 -0
- package/blog/it/i18n_using_next-intl.md +7 -0
- package/blog/it/intlayer_with_next-intl.md +8 -0
- package/blog/it/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/ja/compiler_vs_declarative_i18n.md +1 -2
- package/blog/ja/i18n_using_next-i18next.md +8 -0
- package/blog/ja/i18n_using_next-intl.md +7 -0
- package/blog/ja/intlayer_with_next-intl.md +8 -0
- package/blog/ja/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/ko/compiler_vs_declarative_i18n.md +2 -3
- package/blog/ko/i18n_using_next-i18next.md +8 -0
- package/blog/ko/i18n_using_next-intl.md +7 -0
- package/blog/ko/intlayer_with_next-intl.md +8 -0
- package/blog/ko/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/pl/compiler_vs_declarative_i18n.md +1 -2
- package/blog/pl/i18n_using_next-i18next.md +8 -0
- package/blog/pl/i18n_using_next-intl.md +7 -0
- package/blog/pl/intlayer_with_next-intl.md +8 -0
- package/blog/pl/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/pt/compiler_vs_declarative_i18n.md +1 -2
- package/blog/pt/i18n_using_next-i18next.md +8 -0
- package/blog/pt/i18n_using_next-intl.md +7 -0
- package/blog/pt/intlayer_with_next-intl.md +8 -0
- package/blog/pt/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/ru/compiler_vs_declarative_i18n.md +1 -2
- package/blog/ru/i18n_using_next-i18next.md +8 -0
- package/blog/ru/i18n_using_next-intl.md +7 -0
- package/blog/ru/intlayer_with_next-intl.md +8 -0
- package/blog/ru/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/tr/compiler_vs_declarative_i18n.md +2 -3
- package/blog/tr/i18n_using_next-i18next.md +8 -0
- package/blog/tr/i18n_using_next-intl.md +7 -0
- package/blog/tr/intlayer_with_next-intl.md +8 -0
- package/blog/tr/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/vi/compiler_vs_declarative_i18n.md +1 -2
- package/blog/vi/i18n_using_next-i18next.md +8 -0
- package/blog/vi/i18n_using_next-intl.md +7 -0
- package/blog/vi/intlayer_with_next-intl.md +8 -0
- package/blog/vi/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/blog/zh/compiler_vs_declarative_i18n.md +1 -2
- package/blog/zh/i18n_using_next-i18next.md +8 -0
- package/blog/zh/i18n_using_next-intl.md +7 -0
- package/blog/zh/intlayer_with_next-intl.md +8 -0
- package/blog/zh/list_i18n_technologies/frameworks/flutter.md +0 -22
- package/dist/cjs/generated/docs.entry.cjs +19 -0
- package/dist/cjs/generated/docs.entry.cjs.map +1 -1
- package/dist/esm/generated/docs.entry.mjs +19 -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/bundle_optimization.md +6 -2
- package/docs/ar/compiler.md +133 -0
- package/docs/de/bundle_optimization.md +6 -2
- package/docs/de/compiler.md +133 -0
- package/docs/de/intlayer_with_nextjs_15.md +1 -1
- package/docs/de/per_locale_file.md +1 -1
- package/docs/en/bundle_optimization.md +6 -2
- package/docs/en/cli/index.md +2 -2
- package/docs/en/compiler.md +133 -0
- package/docs/en/intlayer_with_nextjs_14.md +0 -1
- package/docs/en-GB/bundle_optimization.md +6 -2
- package/docs/en-GB/compiler.md +133 -0
- package/docs/en-GB/packages/intlayer/getTranslation.md +1 -3
- package/docs/en-GB/packages/react-intlayer/t.md +1 -1
- package/docs/en-GB/packages/react-intlayer/useI18n.md +1 -1
- package/docs/es/bundle_optimization.md +6 -2
- package/docs/es/compiler.md +133 -0
- package/docs/fr/bundle_optimization.md +6 -2
- package/docs/fr/compiler.md +133 -0
- package/docs/fr/packages/react-intlayer/useI18n.md +1 -1
- package/docs/hi/bundle_optimization.md +6 -2
- package/docs/hi/compiler.md +133 -0
- package/docs/id/bundle_optimization.md +6 -2
- package/docs/id/compiler.md +133 -0
- package/docs/id/formatters.md +0 -1
- package/docs/id/intlayer_with_nextjs_14.md +1 -2
- package/docs/id/intlayer_with_nextjs_15.md +1 -1
- package/docs/it/bundle_optimization.md +6 -2
- package/docs/it/compiler.md +133 -0
- package/docs/ja/bundle_optimization.md +6 -2
- package/docs/ja/compiler.md +133 -0
- package/docs/ko/bundle_optimization.md +6 -2
- package/docs/ko/cli/index.md +20 -20
- package/docs/ko/compiler.md +133 -0
- package/docs/pl/bundle_optimization.md +6 -2
- package/docs/pl/compiler.md +133 -0
- package/docs/pl/formatters.md +0 -1
- package/docs/pl/intlayer_with_nextjs_14.md +1 -2
- package/docs/pl/intlayer_with_nextjs_15.md +1 -1
- package/docs/pt/bundle_optimization.md +6 -2
- package/docs/pt/compiler.md +133 -0
- package/docs/ru/bundle_optimization.md +6 -2
- package/docs/ru/compiler.md +133 -0
- package/docs/tr/bundle_optimization.md +6 -2
- package/docs/tr/compiler.md +133 -0
- package/docs/tr/intlayer_with_nextjs_14.md +2 -0
- package/docs/vi/bundle_optimization.md +6 -2
- package/docs/vi/compiler.md +133 -0
- package/docs/vi/intlayer_with_nextjs_14.md +1 -2
- package/docs/vi/intlayer_with_nextjs_15.md +1 -1
- package/docs/zh/bundle_optimization.md +6 -2
- package/docs/zh/compiler.md +133 -0
- package/package.json +10 -9
- package/src/generated/docs.entry.ts +19 -0
package/README.md
CHANGED
|
@@ -24,8 +24,6 @@
|
|
|
24
24
|
<a href="https://github.com/aymericzip/intlayer/blob/main/LICENSE" target="_blank" rel="noopener noreferrer nofollow"><img src="https://img.shields.io/github/license/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="license"/></a>
|
|
25
25
|
<a href="https://github.com/aymericzip/intlayer/commits/main" target="_blank" rel="noopener noreferrer nofollow"><img src="https://img.shields.io/github/last-commit/aymericzip/intlayer?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="last commit"/>
|
|
26
26
|
</a>
|
|
27
|
-
<a href="https://bountyhub.dev/bounties?repo=intlayer" target="_blank" rel="noopener noreferrer nofollow"><img src="https://img.shields.io/badge/Bounties-on%20BountyHub-yellow?style=for-the-badge&labelColor=000000&color=FFFFFF&logoColor=000000&cacheSeconds=86400" alt="Bounties on BountyHub"/>
|
|
28
|
-
</a>
|
|
29
27
|
</p>
|
|
30
28
|
|
|
31
29
|

|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: كيفية تعريب تطبيق Next.js الخاص بك باستخدام next-i18next
|
|
5
5
|
description: إعداد i18n باستخدام next-i18next - أفضل الممارسات ونصائح تحسين محركات البحث لتطبيقات Next.js متعددة اللغات، تغطي التعريب، تنظيم المحتوى، والإعداد الفني.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: كيفية تعريب تطبيق Next.js الخاص بك باستخدام next-intl
|
|
5
5
|
description: إعداد i18n باستخدام next-intl - أفضل الممارسات ونصائح تحسين محركات البحث لتطبيقات Next.js متعددة اللغات، مع تغطية التعريب، تنظيم المحتوى، والإعداد الفني.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-10-29
|
|
4
4
|
title: كيفية أتمتة ترجمات JSON الخاصة بـ next-intl باستخدام Intlayer
|
|
5
5
|
description: أتمتة ترجمات JSON الخاصة بك باستخدام Intlayer و next-intl لتعزيز التدويل في تطبيقات Next.js.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -114,28 +114,6 @@ slugs:
|
|
|
114
114
|
|
|
115
115
|
---
|
|
116
116
|
|
|
117
|
-
### 4. Intlayer
|
|
118
|
-
|
|
119
|
-
الموقع الإلكتروني: [https://intlayer.org/](https://intlayer.org/)
|
|
120
|
-
|
|
121
|
-
**نظرة عامة**
|
|
122
|
-
**Intlayer** هو حل مفتوح المصدر للتوطين يهدف إلى تبسيط دعم متعدد اللغات عبر عدة أطر، بما في ذلك **Flutter**. يركز على نهج إعلاني، نوع قوي، ودعم SSR في أنظمة بيئات أخرى - على الرغم من أن SSR ليست نموذجية في Flutter القياسي، قد تجد تآزراً إذا كان مشروعك يستخدم Flutter web أو أطر متقدمة.
|
|
123
|
-
|
|
124
|
-
**المميزات الرئيسية**
|
|
125
|
-
|
|
126
|
-
- **ترجمة إعلانية**: تعريف قواميس الترجمة سواء على مستوى الواجهة أو في ملف مركزي لهندسة أكثر نظافة.
|
|
127
|
-
- **TypeScript وإكمال تلقائي (Web)**: بينما تستفيد هذه الميزة بشكل رئيسي أنظمة الويب، إلا أن نهج الترجمة المميزة يمكن أن يوجه الكود المنظم في Flutter أيضاً.
|
|
128
|
-
- **تحميل غير متزامن**: تحميل الأصول الترجمة ديناميكياً، مما قد يقلل من حجم الحزمة الابتدائية لتطبيقات متعددة اللغات.
|
|
129
|
-
- **الاندماج مع Flutter**: يمكن إعداد تكامل أساسي للاستفادة من نهج Intlayer لترجمات منظمة.
|
|
130
|
-
|
|
131
|
-
**الاعتبارات**
|
|
132
|
-
|
|
133
|
-
- **نضوج Intlayer المحدد بـ Flutter**: بينما ينمو، فإن مجتمع Intlayer الخاص بـ Flutter أصغر، لذا قد تجد دروس أو أمثلة شيفرة أقل من المكتبات الأخرى.
|
|
134
|
-
- **SSR**: تدعم المكتبة بشكل قوي SSR في السياقات المعتمدة على الويب، لكن استخدام SSR في Flutter أكثر تخصصاً (مثل Flutter web أو أساليب الخادم المخصصة).
|
|
135
|
-
- **إعداد مخصص**: يتطلب التكوين الأولي ليتناسب مع تدفق `MaterialApp` أو `CupertinoApp` في Flutter.
|
|
136
|
-
|
|
137
|
-
---
|
|
138
|
-
|
|
139
117
|
### الأفكار الختامية
|
|
140
118
|
|
|
141
119
|
عند تقييم نهج i18n لـ Flutter:
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Wie Sie Ihre Next.js-Anwendung mit next-i18next internationalisieren
|
|
5
5
|
description: Richten Sie i18n mit next-i18next ein: Best Practices und SEO-Tipps für mehrsprachige Next.js-Apps, einschließlich Internationalisierung, Inhaltsorganisation und technischer Einrichtung.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Wie Sie Ihre Next.js-Anwendung mit next-intl internationalisieren
|
|
5
5
|
description: Richten Sie i18n mit next-intl ein: Best Practices und SEO-Tipps für mehrsprachige Next.js-Apps, einschließlich Internationalisierung, Inhaltsorganisation und technischer Einrichtung.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-10-29
|
|
4
4
|
title: So automatisieren Sie Ihre next-intl JSON-Übersetzungen mit Intlayer
|
|
5
5
|
description: Automatisieren Sie Ihre JSON-Übersetzungen mit Intlayer und next-intl für eine verbesserte Internationalisierung in Next.js-Anwendungen.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -114,28 +114,6 @@ Repository: [https://pub.dev/packages/flutter_i18n](https://pub.dev/packages/flu
|
|
|
114
114
|
|
|
115
115
|
---
|
|
116
116
|
|
|
117
|
-
### 4. Intlayer
|
|
118
|
-
|
|
119
|
-
Website: [https://intlayer.org/](https://intlayer.org/)
|
|
120
|
-
|
|
121
|
-
**Übersicht**
|
|
122
|
-
**Intlayer** ist eine Open-Source-i18n-Lösung, die darauf abzielt, die mehrsprachige Unterstützung über mehrere Frameworks, einschließlich **Flutter**, zu vereinfachen. Sie betont einen deklarativen Ansatz, starke Typisierung und SSR-Unterstützung in anderen Ökosystemen – obwohl SSR nicht typisch in standardmäßigem Flutter ist, könnten Sie Synergien finden, wenn Ihr Projekt Flutter-Web oder fortschrittliche Frameworks verwendet.
|
|
123
|
-
|
|
124
|
-
**Wesentliche Funktionen**
|
|
125
|
-
|
|
126
|
-
- **Deklarative Übersetzung**: Definieren Sie Übersetzungswörterbücher entweder auf Widget-Ebene oder in einer zentralen Datei für eine sauberere Architektur.
|
|
127
|
-
- **TypeScript & Autocompletion (Web)**: Während dieses Feature hauptsächlich Web-Frameworks zugutekommt, kann der typisierte Übersetzungsansatz dennoch strukturierenden Code in Flutter leiten.
|
|
128
|
-
- **Asynchrones Laden**: Laden Sie Übersetzungsressourcen dynamisch, was die anfängliche Bundle-Größe für mehrsprachige Apps reduzieren kann.
|
|
129
|
-
- **Integration mit Flutter**: Eine grundlegende Integration kann eingerichtet werden, um den Intlayer-Ansatz für strukturierte Übersetzungen zu nutzen.
|
|
130
|
-
|
|
131
|
-
**Überlegungen**
|
|
132
|
-
|
|
133
|
-
- **Maturität von Flutter-spezifisch**: Während wachsend ist die Flutter-Community von Intlayer kleiner, sodass Sie möglicherweise weniger Tutorials oder Codebeispiele als bei anderen Bibliotheken finden.
|
|
134
|
-
- **SSR**: Die Bibliothek unterstützt SSR in webbasierenden Kontexten stark, aber die Nutzung von SSR in Flutter ist spezialisierter (z. B. Flutter-Web oder benutzerdefinierte Serveransätze).
|
|
135
|
-
- **Benutzerdefinierte Einrichtung**: Erfordert eine anfängliche Konfiguration, um in den Fluss von `MaterialApp` oder `CupertinoApp` von Flutter zu passen.
|
|
136
|
-
|
|
137
|
-
---
|
|
138
|
-
|
|
139
117
|
### Abschließende Gedanken
|
|
140
118
|
|
|
141
119
|
Bei der Bewertung eines i18n-Ansatzes für Flutter:
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: How to internationalize your Next.js application using next-i18next
|
|
5
5
|
description: Set up i18n with next-i18next - best practices and SEO tips for multilingual Next.js apps, covering internationalization, content organization, and technical setup.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: How to internationalize your Next.js application using next-intl
|
|
5
5
|
description: Set up i18n with next-intl - best practices and SEO tips for multilingual Next.js apps, covering internationalization, content organization, and technical setup.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-11-06
|
|
4
4
|
title: How to automate your next-intl JSON translations using Intlayer
|
|
5
5
|
description: Automate your JSON translations with Intlayer and next-intl for enhanced internationalization in Next.js applications.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -115,28 +115,6 @@ Repository: [https://pub.dev/packages/flutter_i18n](https://pub.dev/packages/flu
|
|
|
115
115
|
|
|
116
116
|
---
|
|
117
117
|
|
|
118
|
-
### 4. Intlayer
|
|
119
|
-
|
|
120
|
-
Website: [https://intlayer.org/](https://intlayer.org/)
|
|
121
|
-
|
|
122
|
-
**Overview**
|
|
123
|
-
**Intlayer** is an open-source i18n solution aiming to simplify multilingual support across multiple frameworks, including **Flutter**. It emphasizes a declarative approach, strong typing, and SSR support in other ecosystems though SSR is not typical in standard Flutter, you might find synergy if your project uses Flutter web or advanced frameworks.
|
|
124
|
-
|
|
125
|
-
**Key Features**
|
|
126
|
-
|
|
127
|
-
- **Declarative Translation**: Define translation dictionaries either at a widget level or in a centralized file for cleaner architecture.
|
|
128
|
-
- **TypeScript & Autocompletion (Web)**: While this feature mostly benefits web frameworks, the typed translation approach can still guide structured code in Flutter.
|
|
129
|
-
- **Asynchronous Loading**: Load translation assets dynamically, potentially reducing initial bundle size for multi-language apps.
|
|
130
|
-
- **Integration with Flutter**: Basic integration can be set up to leverage the Intlayer approach for structured translations.
|
|
131
|
-
|
|
132
|
-
**Considerations**
|
|
133
|
-
|
|
134
|
-
- **Flutter-Specific Maturity**: While growing, Intlayer’s Flutter community is smaller, so you might find fewer tutorials or code samples than with other libraries.
|
|
135
|
-
- **SSR**: The library strongly supports SSR in web-based contexts, but Flutter’s SSR usage is more specialized (e.g., Flutter web or custom server approaches).
|
|
136
|
-
- **Custom Setup**: Requires initial configuration to fit into Flutter’s `MaterialApp` or `CupertinoApp` flow.
|
|
137
|
-
|
|
138
|
-
---
|
|
139
|
-
|
|
140
118
|
### Final Thoughts
|
|
141
119
|
|
|
142
120
|
When evaluating an i18n approach for Flutter:
|
|
@@ -50,7 +50,23 @@ Translating a Svelte application can present several hurdles:
|
|
|
50
50
|
|
|
51
51
|
Svelte doesn’t provide a native, built-in i18n solution (as Angular does), but the community has created a variety of robust libraries and patterns. Below are several popular approaches.
|
|
52
52
|
|
|
53
|
-
### 1.
|
|
53
|
+
### 1. Intlayer
|
|
54
|
+
|
|
55
|
+
> Website: [https://intlayer.org/](https://intlayer.org/)
|
|
56
|
+
|
|
57
|
+
**Overview**
|
|
58
|
+
**Intlayer** is an open-source i18n solution that aims to simplify multi-language support across multiple frameworks, including **Svelte**. It emphasizes a declarative approach, strong typing, and SSR support in other ecosystems, although SSR is not typical in standard Svelte.
|
|
59
|
+
|
|
60
|
+
**Key Features**
|
|
61
|
+
|
|
62
|
+
- **Declarative Translation**: Define translation dictionaries either at the widget level or in a centralized file for a cleaner architecture.
|
|
63
|
+
- **TypeScript & Autocompletion (Web)**: While this feature primarily benefits web frameworks, the typed translation approach can still guide structured code in Svelte.
|
|
64
|
+
- **Asynchronous Loading**: Load translation assets dynamically, potentially reducing the initial bundle size for multi-language apps.
|
|
65
|
+
- **Integration with Svelte**: A basic integration can be set up to leverage the Intlayer approach for structured translations.
|
|
66
|
+
|
|
67
|
+
---
|
|
68
|
+
|
|
69
|
+
### 2. svelte-i18n
|
|
54
70
|
|
|
55
71
|
Repository: [https://github.com/kaisermann/svelte-i18n](https://github.com/kaisermann/svelte-i18n)
|
|
56
72
|
|
|
@@ -72,7 +88,7 @@ Repository: [https://github.com/kaisermann/svelte-i18n](https://github.com/kaise
|
|
|
72
88
|
|
|
73
89
|
---
|
|
74
90
|
|
|
75
|
-
###
|
|
91
|
+
### 3. svelte-intl-precompile
|
|
76
92
|
|
|
77
93
|
Repository: [https://github.com/cibernox/svelte-intl-precompile](https://github.com/cibernox/svelte-intl-precompile)
|
|
78
94
|
|
|
@@ -94,7 +110,7 @@ Repository: [https://github.com/cibernox/svelte-intl-precompile](https://github.
|
|
|
94
110
|
|
|
95
111
|
---
|
|
96
112
|
|
|
97
|
-
###
|
|
113
|
+
### 4. i18next with Svelte / SvelteKit
|
|
98
114
|
|
|
99
115
|
Website: [https://www.i18next.com/](https://www.i18next.com/)
|
|
100
116
|
|
|
@@ -52,7 +52,21 @@ Below are several popular libraries and approaches you can use to incorporate in
|
|
|
52
52
|
|
|
53
53
|
---
|
|
54
54
|
|
|
55
|
-
### 1.
|
|
55
|
+
### 1. Intlayer
|
|
56
|
+
|
|
57
|
+
> Website: [https://intlayer.org/](https://intlayer.org/)
|
|
58
|
+
|
|
59
|
+
**Overview**
|
|
60
|
+
**Intlayer** is an open-source i18n solution that aims to simplify multi-language support across multiple frameworks, including **Vue**. It emphasizes a declarative approach, strong typing, and SSR support in other ecosystems, although SSR is not typical in standard Vue.
|
|
61
|
+
|
|
62
|
+
**Key Features**
|
|
63
|
+
|
|
64
|
+
- **Declarative Translation**: Define translation dictionaries either at the widget level or in a centralized file for a cleaner architecture.
|
|
65
|
+
- **TypeScript & Autocompletion (Web)**: While this feature primarily benefits web frameworks, the typed translation approach can still guide structured code in Vue.
|
|
66
|
+
- **Asynchronous Loading**: Load translation assets dynamically, potentially reducing the initial bundle size for multi-language apps.
|
|
67
|
+
- **Integration with Vue**: A basic integration can be set up to leverage the Intlayer approach for structured translations.
|
|
68
|
+
|
|
69
|
+
### 2. Vue I18n
|
|
56
70
|
|
|
57
71
|
> Website: [https://vue-i18n.intlify.dev/](https://vue-i18n.intlify.dev/)
|
|
58
72
|
|
|
@@ -83,7 +97,7 @@ Below are several popular libraries and approaches you can use to incorporate in
|
|
|
83
97
|
|
|
84
98
|
---
|
|
85
99
|
|
|
86
|
-
###
|
|
100
|
+
### 3. LinguiJS (Vue Integration)
|
|
87
101
|
|
|
88
102
|
> Website: [https://lingui.js.org/](https://lingui.js.org/)
|
|
89
103
|
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: How to internationalise your Next.js application using next-i18next
|
|
5
5
|
description: Set up i18n with next-i18next - best practices and SEO tips for multilingual Next.js apps, covering internationalisation, content organisation, and technical setup.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: How to internationalise your Next.js application using next-intl
|
|
5
5
|
description: Set up i18n with next-intl - best practices and SEO tips for multilingual Next.js apps, covering internationalisation, content organisation, and technical setup.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-10-29
|
|
4
4
|
title: How to automate your next-intl JSON translations using Intlayer
|
|
5
5
|
description: Automate your JSON translations with Intlayer and next-intl for enhanced internationalisation in Next.js applications.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -114,28 +114,6 @@ Repository: [https://pub.dev/packages/flutter_i18n](https://pub.dev/packages/flu
|
|
|
114
114
|
|
|
115
115
|
---
|
|
116
116
|
|
|
117
|
-
### 4. Intlayer
|
|
118
|
-
|
|
119
|
-
Website: [https://intlayer.org/](https://intlayer.org/)
|
|
120
|
-
|
|
121
|
-
**Overview**
|
|
122
|
-
**Intlayer** is an open-source i18n solution aiming to simplify multilingual support across multiple frameworks, including **Flutter**. It emphasises a declarative approach, strong typing, and SSR support in other ecosystems, though SSR is not typical in standard Flutter, you might find synergy if your project uses Flutter web or advanced frameworks.
|
|
123
|
-
|
|
124
|
-
**Key Features**
|
|
125
|
-
|
|
126
|
-
- **Declarative Translation**: Define translation dictionaries either at a widget level or in a centralised file for cleaner architecture.
|
|
127
|
-
- **TypeScript & Autocompletion (Web)**: While this feature mostly benefits web frameworks, the typed translation approach can still guide structured code in Flutter.
|
|
128
|
-
- **Asynchronous Loading**: Load translation assets dynamically, potentially reducing initial bundle size for multi-language apps.
|
|
129
|
-
- **Integration with Flutter**: Basic integration can be set up to leverage the Intlayer approach for structured translations.
|
|
130
|
-
|
|
131
|
-
**Considerations**
|
|
132
|
-
|
|
133
|
-
- **Flutter-Specific Maturity**: While growing, Intlayer’s Flutter community is smaller, so you might find fewer tutorials or code samples than with other libraries.
|
|
134
|
-
- **SSR**: The library strongly supports SSR in web-based contexts, but Flutter’s SSR usage is more specialised (e.g., Flutter web or custom server approaches).
|
|
135
|
-
- **Custom Setup**: Requires initial configuration to fit into Flutter’s `MaterialApp` or `CupertinoApp` flow.
|
|
136
|
-
|
|
137
|
-
---
|
|
138
|
-
|
|
139
117
|
### Final Thoughts
|
|
140
118
|
|
|
141
119
|
When evaluating an i18n approach for Flutter:
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Cómo internacionalizar tu aplicación Next.js usando next-i18next
|
|
5
5
|
description: Configura i18n con next-i18next - mejores prácticas y consejos SEO para aplicaciones Next.js multilingües, cubriendo internacionalización, organización de contenido y configuración técnica.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Cómo internacionalizar tu aplicación Next.js usando next-intl
|
|
5
5
|
description: Configura i18n con next-intl - mejores prácticas y consejos SEO para aplicaciones Next.js multilingües, cubriendo internacionalización, organización de contenido y configuración técnica.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-10-29
|
|
4
4
|
title: Cómo automatizar tus traducciones JSON de next-intl usando Intlayer
|
|
5
5
|
description: Automatiza tus traducciones JSON con Intlayer y next-intl para una internacionalización mejorada en aplicaciones Next.js.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -114,28 +114,6 @@ Repositorio: [https://pub.dev/packages/flutter_i18n](https://pub.dev/packages/fl
|
|
|
114
114
|
|
|
115
115
|
---
|
|
116
116
|
|
|
117
|
-
### 4. Intlayer
|
|
118
|
-
|
|
119
|
-
Sitio web: [https://intlayer.org/](https://intlayer.org/)
|
|
120
|
-
|
|
121
|
-
**Descripción General**
|
|
122
|
-
**Intlayer** es una solución de i18n de código abierto que busca simplificar el soporte multilingüe a través de múltiples frameworks, incluyendo **Flutter**. Enfatiza un enfoque declarativo, fuerte tipado, y soporte SSR en otros ecosistemas, aunque SSR no es típico en Flutter estándar, podrías encontrar sinergias si tu proyecto utiliza Flutter web o frameworks avanzados.
|
|
123
|
-
|
|
124
|
-
**Características Clave**
|
|
125
|
-
|
|
126
|
-
- **Traducción Declarativa**: Define diccionarios de traducción ya sea a nivel de widget o en un archivo centralizado para una arquitectura más limpia.
|
|
127
|
-
- **TypeScript y Autocompletado (Web)**: Aunque esta característica beneficia principalmente a los frameworks web, el enfoque de traducción tipada puede guiar aún un código estructurado en Flutter.
|
|
128
|
-
- **Carga Asincrónica**: Cargar recursos de traducción de forma dinámica, potencialmente reduciendo el tamaño del paquete inicial para aplicaciones multilingües.
|
|
129
|
-
- **Integración con Flutter**: La integración básica puede configurarse para aprovechar el enfoque de Intlayer para traducciones estructuradas.
|
|
130
|
-
|
|
131
|
-
**Consideraciones**
|
|
132
|
-
|
|
133
|
-
- **Madurez Específica de Flutter**: Aunque está creciendo, la comunidad de Intlayer para Flutter es más pequeña, por lo que podrías encontrar menos tutoriales o ejemplos de código que con otras bibliotecas.
|
|
134
|
-
- **SSR**: La biblioteca soporta fuertemente SSR en contextos basados en la web, pero el uso de SSR en Flutter es más especializado (por ejemplo, Flutter web o enfoques de servidor personalizados).
|
|
135
|
-
- **Configuración Personalizada**: Requiere una configuración inicial para encajar en el flujo de `MaterialApp` o `CupertinoApp` de Flutter.
|
|
136
|
-
|
|
137
|
-
---
|
|
138
|
-
|
|
139
117
|
### Reflexiones Finales
|
|
140
118
|
|
|
141
119
|
Al evaluar un enfoque de i18n para Flutter:
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Comment internationaliser votre application Next.js avec next-i18next
|
|
5
5
|
description: Configurez l'i18n avec next-i18next : meilleures pratiques et conseils SEO pour les applications Next.js multilingues, couvrant l'internationalisation, l'organisation du contenu et la configuration technique.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-i18next
|
|
8
|
+
- i18next
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- nextjs-internationalization-using-next-i18next
|
|
@@ -3,6 +3,13 @@ createdAt: 2025-11-01
|
|
|
3
3
|
updatedAt: 2025-11-01
|
|
4
4
|
title: Comment internationaliser votre application Next.js avec next-intl
|
|
5
5
|
description: Configurez l'i18n avec next-intl : meilleures pratiques et conseils SEO pour les applications Next.js multilingues, couvrant l'internationalisation, l'organisation du contenu et la configuration technique.
|
|
6
|
+
keywords:
|
|
7
|
+
- next-intl
|
|
8
|
+
- Internationalization
|
|
9
|
+
- Blog
|
|
10
|
+
- Next.js
|
|
11
|
+
- JavaScript
|
|
12
|
+
- React
|
|
6
13
|
slugs:
|
|
7
14
|
- blog
|
|
8
15
|
- nextjs-internationalization-using-next-intl
|
|
@@ -3,6 +3,14 @@ createdAt: 2025-01-02
|
|
|
3
3
|
updatedAt: 2025-10-29
|
|
4
4
|
title: Comment automatiser vos traductions JSON next-intl avec Intlayer
|
|
5
5
|
description: Automatisez vos traductions JSON avec Intlayer et next-intl pour une internationalisation améliorée dans les applications Next.js.
|
|
6
|
+
keywords:
|
|
7
|
+
- Intlayer
|
|
8
|
+
- next-intl
|
|
9
|
+
- Internationalization
|
|
10
|
+
- Blog
|
|
11
|
+
- Next.js
|
|
12
|
+
- JavaScript
|
|
13
|
+
- React
|
|
6
14
|
slugs:
|
|
7
15
|
- blog
|
|
8
16
|
- intlayer-with-next-intl
|
|
@@ -114,28 +114,6 @@ Dépôt : [https://pub.dev/packages/flutter_i18n](https://pub.dev/packages/flutt
|
|
|
114
114
|
|
|
115
115
|
---
|
|
116
116
|
|
|
117
|
-
### 4. Intlayer
|
|
118
|
-
|
|
119
|
-
Site web : [https://intlayer.org/](https://intlayer.org/)
|
|
120
|
-
|
|
121
|
-
**Aperçu**
|
|
122
|
-
**Intlayer** est une solution i18n open-source visant à simplifier le support multilingue à travers plusieurs frameworks, y compris **Flutter**. Elle met l'accent sur une approche déclarative, un typage fort, et le support SSR dans d'autres écosystèmes, bien que le SSR ne soit pas typique dans Flutter standard, vous pourriez trouver une synergie si votre projet utilise Flutter web ou des frameworks avancés.
|
|
123
|
-
|
|
124
|
-
**Caractéristiques clés**
|
|
125
|
-
|
|
126
|
-
- **Traduction déclarative** : Définissez des dictionnaires de traduction soit à un niveau de widget soit dans un fichier centralisé pour une architecture plus propre.
|
|
127
|
-
- **TypeScript et auto-complétion (Web)** : Bien que cette fonctionnalité bénéficie principalement aux frameworks web, l'approche de traduction typée peut toujours guider un code structuré dans Flutter.
|
|
128
|
-
- **Chargement asynchrone** : Chargez des actifs de traduction dynamiquement, réduisant potentiellement la taille initiale du bundle pour des applications multilingues.
|
|
129
|
-
- **Intégration avec Flutter** : Une intégration de base peut être mise en place pour tirer parti de l'approche Intlayer pour des traductions structurées.
|
|
130
|
-
|
|
131
|
-
**Considérations**
|
|
132
|
-
|
|
133
|
-
- **Maturité spécifique à Flutter** : Bien qu'en croissance, la communauté Flutter d'Intlayer est plus petite, vous pourriez donc trouver moins de tutoriels ou d'exemples de code par rapport à d'autres bibliothèques.
|
|
134
|
-
- **SSR** : La bibliothèque soutient fortement le SSR dans des contextes basés sur le web, mais l'utilisation du SSR dans Flutter est plus spécialisée (par exemple, Flutter web ou des approches serveur personnalisées).
|
|
135
|
-
- **Configuration personnalisée** : Nécessite une initialisation pour s'intégrer au flux de `MaterialApp` ou `CupertinoApp` de Flutter.
|
|
136
|
-
|
|
137
|
-
---
|
|
138
|
-
|
|
139
117
|
### Pensées finales
|
|
140
118
|
|
|
141
119
|
Lorsque vous évaluez une approche d'i18n pour Flutter :
|
|
@@ -2,7 +2,7 @@
|
|
|
2
2
|
createdAt: 2025-11-24
|
|
3
3
|
updatedAt: 2025-11-24
|
|
4
4
|
title: कंपाइलर बनाम घोषणात्मक i18n
|
|
5
|
-
description: "मैजिक" कंपाइलर-आधारित अंतरराष्ट्रीयकरण और स्पष्ट घोषणात्मक सामग्री प्रबंधन के बीच वास्तुशिल्पीय ट्रेड-ऑफ का अन्वेषण।
|
|
5
|
+
description: '"मैजिक" कंपाइलर-आधारित अंतरराष्ट्रीयकरण और स्पष्ट घोषणात्मक सामग्री प्रबंधन के बीच वास्तुशिल्पीय ट्रेड-ऑफ का अन्वेषण।'
|
|
6
6
|
keywords:
|
|
7
7
|
- Intlayer
|
|
8
8
|
- अंतरराष्ट्रीयकरण
|
|
@@ -14,9 +14,8 @@ keywords:
|
|
|
14
14
|
- कंपाइलर
|
|
15
15
|
- घोषणात्मक
|
|
16
16
|
slugs:
|
|
17
|
-
- compiler-vs-declarative-i18n
|
|
18
17
|
- blog
|
|
19
|
-
- i18n
|
|
18
|
+
- compiler-vs-declarative-i18n
|
|
20
19
|
---
|
|
21
20
|
|
|
22
21
|
# कंपाइलर-आधारित i18n के पक्ष और विपक्ष
|