Cursor rule

1---
2description: i18n, 国际化, 翻译, tanslation, chinese, english
3globs: locales/**/*.json
4alwaysApply: false
5---
6Internationalization (i18n) Guidelines:
7 
8Message Structure:
9- Store all text content in `/locales/[locale]/messages.json`
10- Use descriptive message keys in camelCase: `errorImportingContent`
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 
15Message Format:
16```json
17"extensionDisplayName": {
18  "message": "MultiPost",
19  "description": "Multipost Extension"
20},
21```
22 
23Implementation:
24- Use `chrome.i18n.getMessage('extensionDisplayName')` for all user-facing text
25- Never hardcode text strings in UI components
26- Handle RTL languages with appropriate CSS
27- Set default_locale in manifest.json
28- Support fallback locales
29 
30Best Practices:
31- Keep messages concise and clear
32- Use semantic keys (e.g., WELCOME_MESSAGE vs MSG_001)
33- Maintain consistent terminology across translations
34- Handle pluralization properly
35- Consider cultural differences in formatting dates, numbers, and currencies
36- Test UI with different language lengths
37 
38Code Examples:
39```typescript
40// Component usage
41const message = chrome.i18n.getMessage("WELCOME_MESSAGE", [username]);
42 
43// Manifest configuration
44{
45  "default_locale": "en",
46  "name": "__MSG_extension_name__",
47  "description": "__MSG_extension_description__"
48}
49```
50