Cursor rule

1---
2description: i18n, 翻译, 国际化
3globs:
4alwaysApply: false
5---
6Internationalization (i18n) Guidelines:
7 
8Message Structure:
9- Store all text content in `@/i18n/locales/[locale]/*.json`
10- Use descriptive message keys in SNAKE_CASE
11- Include placeholders with $PLACEHOLDER$ syntax
12- Add descriptions for translators in message files
13- `console.log` don't need add i18n, only for UI text display on screen
14 
15```
16# For server component
17import { createTranslation } from '@/i18n/server';
18const { t } = await createTranslation('home');
19 
20# For client component
21'use client'
22import { useTranslation } from '@/i18n/client';
23const { t } = useTranslation('install');
24```
25 
26Message Format:
27```json
28"footer": {
29    "slogan": "Build something amazing.",
30    "copyright": "© {{year}} Your Company. All rights reserved.",
31    "sections": {
32      "services": "Services",
33      "support": "Support",
34      "aboutus": "About Us",
35      "legal": "Legal"
36    },
37    "navigation": {
38      "services": {},
39      "support": {
40        "pricing": "Pricing",
41        "userManual": "Documentation"
42      },
43      "aboutUs": {
44        "team": "Our Team"
45      },
46      "legal": {
47        "privacy": "Privacy Policy",
48        "terms": "Terms of Service"
49      }
50    }
51  },
52```
53 
54Implementation:
55- Use i18n translation functions for all user-facing text
56- Never hardcode text strings in components
57- Handle RTL languages with appropriate CSS
58- Support fallback locales
59 
60Best Practices:
61- Keep messages concise and clear
62- Use semantic keys (e.g., WELCOME_MESSAGE vs MSG_001)
63- Maintain consistent terminology across translations
64- Handle pluralization properly
65- Consider cultural differences in formatting dates, numbers, and currencies
66- Test UI with different language lengths
67