Carane Ngowahi PDF dadi Gambar Online (JPG, PNG, TIFF) - PDFSub Javanese Translation Example - SEO Optimized for Javanese Search Intent - Max 60 Chars Title - Max 160 Chars Meta Description - Javanese Keywords - Natural Idiomatic Javanese Translation - Professional Yet Approachable Tone - Technical Terms Localized Where Appropriate - All User-Facing Text Translated - Preserve Formatting & Links - Localized Bank Names If Applicable - No Extra Text Outside JSON - Valid JSON Only - PDFSub Brand Name Preserved - Technical Formats & Terms Unchanged - Image Placeholders Preserved - Markdown Headings Preserved - Cultural Adaptation Applied - Accuracy & Quality Paramount - SEO Optimization Critical - What to Translate: ALL Strings - What NOT to Translate: Keys, Brand, Formats, Technical Terms, URLs, Emails, Numbers, Placeholders, Markdown Syntax - Formatting: Preserve HTML/Markdown, Maintain Array Structure, Exact Item Count - Cultural Adaptation: Formality, Idioms, Metaphors - Bank Name Localization: CRITICAL - DO NOT SKIP - Examples: 'Sberbank', 'Tinkoff', 'VTB', 'Alfa-Bank', 'Gazprombank', 'Raiffeisen', 'Rosbank', 'Otkritie', 'HSBC', 'Deutsche Bank', 'BNP Paribas', 'UBS', 'Santander', 'ING', 'ICBC', 'Mizuho Bank', 'State Bank of India', 'Barclays', 'Commonwealth Bank', 'Standard Chartered', 'Citibank' for Russian; 'PKO BP', 'mBank', 'ING', 'Santander', 'BNP Paribas', 'Pekao', 'Alior Bank' for Polish; 'Deutsche Bank', 'Commerzbank', 'Sparkasse', 'ING', 'N26', 'DKB' for German; 'BNP Paribas', 'Société Générale', 'Crédit Agricole', 'LCL', 'Boursorama' for French; Native script for non-Latin: Arabic ('البنك الأهلي', 'الراجحي'), Chinese ('中国工商银行', '中国建设银行'), Japanese ('三菱UFJ', 'みずほ銀行'). The bank list must feel native to Javanese speakers, not like a US-only product. - CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization: CRITICAL - DO NOT SKIP. Examples provided. The list must feel native. CRITICAL RULES: Accuracy & Quality: Native-quality translations, natural idiomatic phrasing, adapt sentence structure, match tone, use industry terminology. SEO Optimization: Javanese search intent, Javanese keywords, character limits, preserve CTAs. What to Translate: ALL strings, headings, descriptions, features, FAQs, CTAs, user-facing text, adapt formats/units. What NOT to Translate: JSON keys, 'PDFSub', technical formats, universal English terms (API, URL, OCR, AI, CTA, SEO, GDPR, SOC 2), 'PDFSub Engine', code-like strings, URLs, emails, identifier numbers, image placeholders, markdown heading syntax. Formatting: Preserve HTML/Markdown, maintain array structure/count, exact item count, ONLY valid JSON. Cultural Adaptation: Formality, idioms, metaphors. Bank Name Localization