,
Actualizado 2026-11-06
. The content between markers must be translated into Spanish, preserving structure, headings, bullet lists, links (translate link text, keep paths). Must be 900-1400 words in Spanish. Must include eSIM call to action and 1-2 links from allowed list. Also must keep the three markers as literal ASCII text.
We need to translate the entire English article, preserving headings levels (## and ###). The English article has headings: Title (not part of body), description, then body with several sections: "## Why Stockholm's Old Town and Archipelago Pair Perfectly", "## Gamla Stan on Foot: Stortorget, Royal Palace and Mårten Trotzigs Gränd", "## Djurgården Museums Worth Booking Ahead: Vasa Museum and Skansen", "## Stockholm Archipelago Day Trip: Ferries to Vaxholm and Beyond", "## Getting Around: SL Transit Cards, Ferries and Walking Routes", "## Staying Connected: eSIM for Stockholm and Island Day Trips", "## FAQ", then FAQ items.
We need to translate all content, including bullet lists, and internal markdown links. The allowed internal links are given. We need to translate link text, keep paths. For example, Copenhagen neighborhoods walk becomes Caminata por los barrios de Copenhague (Spanish translation of link text). Also Amsterdam canals and Museumplein itinerary -> Canales de Ámsterdam y itinerario de Museumplein. Also Edinburgh Old Town and Arthur's Seat guide -> Guía de la Ciudad Vieja de Edimburgo y Arthur's Seat. Also Europe eSIM guide -> Guía de eSIM para Europa. Also what an eSIM actually is -> qué es un eSIM realmente. Also dual SIM travel tips -> consejos de viaje con dual SIM. Also data needs guide -> guía de necesidades de datos. Also Europe coverage on PingRoam -> Cobertura de Europa en PingRoam. Also iPhone -> iPhone (maybe keep same path but translate text? The link text is "iPhone" maybe keep as is? The instruction: translate link text; keep paths from Allowed list only. So we need to translate the link text, not the path. So "iPhone" stays "iPhone"? It's a language-neutral term; maybe keep "iPhone". But we could translate to "iPhone" (same). Probably keep as is.
Also Android -> Android. Also PingRoam tickets -> entradas PingRoam. Also Europe coverage on PingRoam -> Cobertura de Europa en PingRoam. Also Europe eSIM guide -> Guía de eSIM para Europa. Also what an eSIM actually is -> qué es un eSIM realmente. Also dual SIM travel tips -> consejos de viaje con dual SIM. Also data needs guide -> guía de cuántos datos necesito. Also Europe coverage on PingRoam -> Cobertura de Europa en PingRoam. Also install guides for iPhone -> guías de instalación para iPhone. Also install guides for Android -> guías de instalación para Android.
We also need to include eSIM call to action and 1-2 links from allowed list. Already have eSIM call to action in the article: "Stay connected: Set up a European eSIM before you fly so maps and ferry timetables work from the moment you land; see Europe coverage on PingRoam plus our install guides for iPhone and Android." We'll translate that.
Also "Worth booking: Vasa Museum timed entry, Skansen tickets, Royal Palace apartments, and a guided archipelago boat tour are the Stockholm experiences travelers most often pre-book. Browse options on PingRoam tickets to lock in the busy ones before you arrive." We'll translate and keep link.
We need to ensure total word count 900-1400 Spanish words. Let's approximate. The English article is maybe ~800 words. We need to translate fully, maybe add some extra Spanish phrasing to reach 900-1400. Must be careful not to exceed 1400.
We need to preserve heading levels: The English uses ## for main sections, ### for subsections? Actually the English uses ## for "Why Stockholm's Old Town and Archipelago Pair Perfectly", "Gamla Stan on Foot...", "Djurgården Museums...", "Stockholm Archipelago Day Trip...", "Getting Around...", "Staying Connected...", "FAQ". And ### for FAQ header? Actually the English shows "## FAQ" then "### Do I need to book Vasa Museum tickets in advance?" etc. So we need to keep same hierarchy: ## for main sections, ### for FAQ items.
We need to translate headings accordingly.
Let's outline the Spanish translation:
###TITLE### <localized title> -> "Stockholm Old Town to Archipelago: Paseos por Gamla Stan, Ferrys de Archipiélago, Tarjetas de Tránsito SL y Consejos de eSIM"
But need to translate title exactly? The English title: "Stockholm Old Town to Archipelago: Gamla Stan Walks, Island Ferries, Transit Cards & eSIM Tips". Spanish: "Paseos por el Centro Histórico de Estocolmo hasta el Archipiélago: Caminatas por Gamla Stan, Ferrys de Archipiélago, Tarjetas de Tránsito y Consejos de eSIM". Let's craft: "Paseos por Gamla Stan hasta el Archipiélago: Caminatas, Ferrys de Archipiélago, Tarjetas de Tránsito y Consejos de eSIM". That's okay.
###DESC### <localized meta description, max 160 characters> -> "Recorre las callejuelas empedradas de Gamla Stan, navega por el archipiélago de Estocolmo y prepara tu tarjeta SL y eSIM antes de llegar."
Count characters: Let's count roughly: "Recorre las callejuelas empedradas de Gamla Stan, navega por el archipiélago de Estocolmo y prepara tu tarjeta SL y eSIM antes de llegar." That's about 115 characters, within 160.
