The task is to translate the given HTML page from English to Chinese, preserving all HTML tags, attributes, CSS, JS, etc. Only translate visible text content.
Key guidelines:
1. Translate all visible text: titles, headings, nav, buttons, placeholders, continent/country names, stats, UI text.
2. Do not translate: HTML attributes, JS code, CSS, URLs, links, image alt text with country/flag names, technical strings.
3. Country names: Use official Chinese translations. For Oman, it's "阿曼".
4. Continent names: Asia is "亚洲".
5. Natural translation for travel context.
6. Update header.html and footer.html to /zh/header.html and /zh/footer.html.
7. Update language attributes: , canonical to /zh/..., alternate links with /zh/, x-default to English.
8. Update all internal links to include /zh/ prefix, but don't translate the link text.
9. Definitely translate all country names.
10. Translate sponsors descriptions – but in this page, it's the buy coffee section.
The input is a page about Oman Culture & Travel Tips, not a destinations page, but the instruction says "destinations page", probably a generic instruction.
Output only the complete translated HTML.
First, change to .
Update title: "Oman Culture & Travel Tips 2025: Food, Safety & Insider Secrets | Atlas Guide" to Chinese.
Oman is 阿曼.
Translate to: "2025 阿曼文化与旅行提示：美食、安全与内部秘诀 | Atlas Guide"
Keep "Atlas Guide" as is, probably.
Meta tags: translate title, description, keywords, etc.
Keywords: translate to Chinese equivalents.
But keywords might be kept in English? No, guideline says translate all visible text, but keywords are meta, but to be safe, translate them.
Actually, meta keywords are for SEO, perhaps keep English, but instruction says translate ALL visible text, but meta is not visible, but probably translate for consistency.
No, guideline: Translate ALL visible text content. Meta is not visible, so perhaps leave as is? But title is visible in tab.
Title is both and meta name="title".
To be precise, translate the content inside.
Canonical: change to https://www.atlas-guide.com/zh/asia/oman-guide/culture
Hreflang: update the zh one to hreflang="zh", and others accordingly, but the zh link is already /zh/, x-default is English without prefix.
The provided has /zh/ for zh-CN, but change to zh.
For alternate links, update the href for zh to the new one, but since it's the page itself, it's fine.
All internal links: like <a href="/">Home</a> to <a href="/zh/">首页</a> no, don't translate link text? Guideline: Translate ALL visible text, so translate "Home" to "首页".
But "DONT translate internal links!" – wait, that means don't translate the href, but translate the text.
Yes: "update all internal links to the correct language directory links. IMPORTANT for the country links, don't translate the links but use the correct language directory fo them. DONT translate internal links!"
It's a bit confusing. "DONT translate internal links!" probably means don't change the href text, but update the path to /zh/.
And translate the anchor text.
Yes.
For header and footer: in JS, fetch('/header.html') to fetch('/zh/header.html')
In the script: change fetch('/header.html') to fetch('/zh/header.html'), same for footer.
Breadcrumb links: update href to /zh/, /zh/destinations, /zh/asia/oman, and translate texts: Home to 首页, Destinations to 目的地, Oman to 阿曼, Culture to 文化.
Oman is country name, translate to 阿曼.
In related guides: update href to /zh/asia/oman-guide/planning etc., translate texts.
Buy coffee: translate the texts.
Phrases: translate the section, but the phrases themselves are in English and Arabic, probably keep as is, translate the labels.
The phrases are examples, so keep the foreign words, translate the English parts if needed, but since it's "Useful Phrases", translate headings.
For country names in text: all to 阿曼.
Continent: Asia to 亚洲, but in paths keep /asia/, as don't translate URL paths.
Paths remain /asia/oman-guide/, but with /zh/ prefix.
In hreflang, the paths have /asia/, keep as is.
Now, translate all headings and paragraphs.
For example, <h1>Oman Culture & Travel Tips</h1> to <h1>阿曼文化与旅行提示</h1>
<p>Immerse Yourself in Omani Life, Food & Traditions</p> to <p>沉浸在阿曼人的生活、美食与传统中</p>
And so on.
Currency: OMR keep as is.
Names like Shuwa, Majboos keep as is, they are proper names.
Places like Dhofar to 佐法尔? But guideline: for country names official, but subplaces? Probably keep English or transliterate if standard.
In Chinese travel sites, they use transliterations: Dhofar is 佐法尔省, but to keep simple, since instruction says for country names, and others are visible text, but proper names often transliterated.
I need to use standard Chinese transliterations for places.
For example:
Oman: 阿曼
Muscat: 马斯喀特
Dhofar: 佐法尔
Nizwa: 尼兹瓦
Salalah: 萨拉拉
Suhar: 苏哈尔
Wahiba Sands: 瓦希巴沙滩
Etc.
I should look up standard translations.
For food: Shuwa keep as 舒瓦, but often keep English with Chinese explanation.
But since it's translation, translate descriptions, keep dish names in English or transliterate.
Guideline: translate visible text, but proper names like dish names probably transliterate or keep.
To be safe, I'll transliterate where standard.
But for simplicity, since it's a lot, keep dish names as is, translate descriptions.
No, instruction: Translate ALL visible text, but for names, use official.
For dishes, they are not countries, so translate the sentences.
Now, for the meta: translate content.
Title: "2025 阿曼文化与旅行提示：美食、安全与内部秘诀 | Atlas Guide"
Description: "掌握阿曼文化：必试美食、文化礼仪、安全指南、内部旅行提示，以及隐藏宝石，获得真实的阿曼体验。"
Keywords: "阿曼文化, 阿曼美食, 阿曼安全, 阿曼旅行提示, 阿曼礼仪, 阿曼隐藏宝石, 阿曼菜肴"
OG and Twitter: similar.
In schema: translate headline and description.
For JS: don't translate code.
In fetch: change to /zh/header.html and /zh/footer.html
In the script at the end, it's fetch('/header.html'), yes.
Also, there's <div id="included-header"></div> , but no change.
For breadcrumb: translate and update links.
<a href="/">首页</a> <span>›</span> <a href="/zh/destinations">目的地</a> <span>›</span> <a href="/zh/asia/oman">阿曼</a> <span>›</span> <span>文化</span>
Culture is the current page, so no link.
For related: <a href="/zh/asia/oman-guide/planning" ... >规划与实用</a> etc.
Translate "Planning & Practical" to "规划与实用"
"Destinations & Activities" to "目的地与活动"
"Transport & Logistics" to "交通与后勤"
Buy coffee: "支持 Atlas Guide" , "创建这些详细的旅行指南需要数小时的研究和热情。如果这个指南帮助您规划冒险
<!-- Google tag (gtag.js) -->
<script async src="https://www.googletagmanager.com/gtag/js?id=G-RSEFM62P3Q"></script>
<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}
gtag('js', new Date());
gtag('config', 'G-RSEFM62P3Q');
</script>
<div id="included-footer"></div>