|
| 1 | +export default { |
| 2 | + langs: { |
| 3 | + 'zh-Hans': { |
| 4 | + name: 'Simplified Chinese', |
| 5 | + // 翻译规则和指南 |
| 6 | + guide: ` |
| 7 | + - For technical terms that should not be fully translated, use the format: "中文翻译 (English term)" |
| 8 | + Example: "服务端渲染 (SSR)" instead of just "SSR" or just "服务端渲染" |
| 9 | + - Add a space between Chinese characters and English words/symbols to improve readability |
| 10 | + - Maintain consistent translations for common terms across the entire document |
| 11 | +`, |
| 12 | + // 常见技术术语翻译词典 |
| 13 | + // 格式: 'English term': '中文翻译' |
| 14 | + terms: {}, |
| 15 | + }, |
| 16 | + 'zh-Hant': { |
| 17 | + name: 'Traditional Chinese', |
| 18 | + // 翻譯規則和指南 |
| 19 | + guide: ` |
| 20 | + - For technical terms that should not be fully translated, use the format: "繁體中文翻譯 (English term)" |
| 21 | + Example: "伺服器渲染 (SSR)" instead of just "SSR" or just "伺服器渲染" |
| 22 | + - Add a space between Chinese characters and English words/symbols to improve readability |
| 23 | + - Maintain consistent translations for common terms across the entire document |
| 24 | +`, |
| 25 | + // 常見技術術語翻譯詞典 |
| 26 | + // 格式: 'English term': '繁體中文翻譯' |
| 27 | + terms: {}, |
| 28 | + }, |
| 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 | + }, |
| 89 | + }, |
| 90 | + docsRoot: 'content/en/', |
| 91 | + outputRoot: 'content/', |
| 92 | + docsContext: `Next.js is a React framework for building full-stack web applications. You use React Components to build user interfaces, and Next.js for additional features and optimizations. |
| 93 | +It also automatically configures lower-level tools like bundlers and compilers. You can instead focus on building your product and shipping quickly. |
| 94 | +Whether you're an individual developer or part of a larger team, Next.js can help you build interactive, dynamic, and fast React applications.`, |
| 95 | + docsPath: ['**/*.mdx'], |
| 96 | + pattern: [], |
| 97 | +}; |
0 commit comments