Skip to content

Commit 2d3e014

Browse files
xiaoyu2erxiaoyu2er
committed
feat: update translate config
1 parent deaa5e1 commit 2d3e014

File tree

1 file changed

+60
-60
lines changed

1 file changed

+60
-60
lines changed

‎apps/docs/translation.config.mjs‎

Lines changed: 60 additions & 60 deletions
Original file line numberDiff line numberDiff line change
@@ -26,66 +26,66 @@ export default {
2626
// 格式: 'English term': '繁體中文翻譯'
2727
terms: {},
2828
},
29-
// ja: {
30-
// name: 'Japanese',
31-
// guide: `
32-
// - For technical terms that should not be fully translated, use the format: "日本語訳 (English term)"
33-
// Example: "サーバーサイドレンダリング (SSR)" instead of just "SSR" or just "サーバーサイドレンダリング"
34-
// - Maintain consistent translations for common terms across the entire document
35-
// - Use katakana for foreign technical terms where appropriate
36-
// `,
37-
// terms: {},
38-
// },
39-
// es: {
40-
// name: 'Spanish',
41-
// guide: `
42-
// - For technical terms that should not be fully translated, use the format: "Traducción en español (English term)"
43-
// Example: "Renderizado del lado del servidor (SSR)" instead of just "SSR" or just "Renderizado del lado del servidor"
44-
// - Maintain consistent translations for common terms across the entire document
45-
// - Use formal "usted" form instead of informal "tú" for instructions
46-
// `,
47-
// terms: {},
48-
// },
49-
// de: {
50-
// name: 'German',
51-
// guide: `
52-
// - For technical terms that should not be fully translated, use the format: "Deutsche Übersetzung (English term)"
53-
// Example: "Server-seitiges Rendering (SSR)" instead of just "SSR" or just "Server-seitiges Rendering"
54-
// - Maintain consistent translations for common terms across the entire document
55-
// - Follow German capitalization rules for nouns
56-
// `,
57-
// terms: {},
58-
// },
59-
// fr: {
60-
// name: 'French',
61-
// guide: `
62-
// - For technical terms that should not be fully translated, use the format: "Traduction française (English term)"
63-
// Example: "Rendu côté serveur (SSR)" instead of just "SSR" or just "Rendu côté serveur"
64-
// - Maintain consistent translations for common terms across the entire document
65-
// - Use proper French punctuation with spaces before certain punctuation marks
66-
// `,
67-
// terms: {},
68-
// },
69-
// ru: {
70-
// name: 'Russian',
71-
// guide: `
72-
// - For technical terms that should not be fully translated, use the format: "Русский перевод (English term)"
73-
// Example: "Рендеринг на стороне сервера (SSR)" instead of just "SSR" or just "Рендеринг на стороне сервера"
74-
// - Maintain consistent translations for common terms across the entire document
75-
// - Use proper Russian cases for technical terms where appropriate
76-
// `,
77-
// terms: {},
78-
// },
79-
// ar: {
80-
// name: 'Arabic',
81-
// guide: `
82-
// - For technical terms that should not be fully translated, use the format: "الترجمة العربية (English term)"
83-
// Example: "العرض من جانب الخادم (SSR)" instead of just "SSR" or just "العرض من جانب الخادم"
84-
// - Maintain consistent translations for common terms across the entire document
85-
// - Arabic text should flow right-to-left, but keep code examples and technical terms left-to-right
86-
// `,
87-
// terms: {},
88-
// },
29+
ja: {
30+
name: 'Japanese',
31+
guide: `
32+
- For technical terms that should not be fully translated, use the format: "日本語訳 (English term)"
33+
Example: "サーバーサイドレンダリング (SSR)" instead of just "SSR" or just "サーバーサイドレンダリング"
34+
- Maintain consistent translations for common terms across the entire document
35+
- Use katakana for foreign technical terms where appropriate
36+
`,
37+
terms: {},
38+
},
39+
es: {
40+
name: 'Spanish',
41+
guide: `
42+
- For technical terms that should not be fully translated, use the format: "Traducción en español (English term)"
43+
Example: "Renderizado del lado del servidor (SSR)" instead of just "SSR" or just "Renderizado del lado del servidor"
44+
- Maintain consistent translations for common terms across the entire document
45+
- Use formal "usted" form instead of informal "tú" for instructions
46+
`,
47+
terms: {},
48+
},
49+
de: {
50+
name: 'German',
51+
guide: `
52+
- For technical terms that should not be fully translated, use the format: "Deutsche Übersetzung (English term)"
53+
Example: "Server-seitiges Rendering (SSR)" instead of just "SSR" or just "Server-seitiges Rendering"
54+
- Maintain consistent translations for common terms across the entire document
55+
- Follow German capitalization rules for nouns
56+
`,
57+
terms: {},
58+
},
59+
fr: {
60+
name: 'French',
61+
guide: `
62+
- For technical terms that should not be fully translated, use the format: "Traduction française (English term)"
63+
Example: "Rendu côté serveur (SSR)" instead of just "SSR" or just "Rendu côté serveur"
64+
- Maintain consistent translations for common terms across the entire document
65+
- Use proper French punctuation with spaces before certain punctuation marks
66+
`,
67+
terms: {},
68+
},
69+
ru: {
70+
name: 'Russian',
71+
guide: `
72+
- For technical terms that should not be fully translated, use the format: "Русский перевод (English term)"
73+
Example: "Рендеринг на стороне сервера (SSR)" instead of just "SSR" or just "Рендеринг на стороне сервера"
74+
- Maintain consistent translations for common terms across the entire document
75+
- Use proper Russian cases for technical terms where appropriate
76+
`,
77+
terms: {},
78+
},
79+
ar: {
80+
name: 'Arabic',
81+
guide: `
82+
- For technical terms that should not be fully translated, use the format: "الترجمة العربية (English term)"
83+
Example: "العرض من جانب الخادم (SSR)" instead of just "SSR" or just "العرض من جانب الخادم"
84+
- Maintain consistent translations for common terms across the entire document
85+
- Arabic text should flow right-to-left, but keep code examples and technical terms left-to-right
86+
`,
87+
terms: {},
88+
},
8989
},
9090
docsRoot: 'content/en/',
9191
outputRoot: 'content/',

0 commit comments

Comments
 (0)