We need to translate the English text to natural Latin American Spanish, preserving HTML tags, city/airport names and codes unchanged, phone numbers and URLs unchanged. Keep all tags exactly as is. So we replace only the text content inside tags, leaving tags like , , — etc. We must not alter the tags themselves. Also we need to ensure the translation is natural, not overly literal.
First, let's parse the content:
,
,Azle to DFW Airport Shuttle Service
Translate: "Servicio de traslado en shuttle de Azle al Aeropuerto DFW" but need natural Latin American Spanish. Could be "Servicio de transporte en shuttle de Azle al Aeropuerto DFW". Keep tags. NextBook your Azle to DFW shuttle in 2 minutes — door-to-door, non-stop, 24/7. We pick up from any address in Azle, TX and drop you curbside at your specific Dallas/Fort Worth International Airport (DFW) terminal. Fares start from $85 all-in — no surge pricing, no per-bag fees, no hidden surprises curbside. Saginaw to DFW Airport shuttle
We need to translate the plain text but keep the tags: etc and tags. Inside the tag there is a title attribute; we must keep the attribute unchanged (the value is English). Should we translate the title? The instruction: Keep ALL HTML tags exactly as-is. That includes attributes? Usually attribute values are part of tag; but they said keep tags exactly as-is. I'd interpret that we should not change the attribute values either, as they are part of the tag. So we keep title="Book Azle to DFW Shuttle" unchanged. Similarly rel="noopener". The href URLs unchanged. Now we need to translate the visible text inside the (the link text) and the surrounding text. Inside the : "Book your Azle to DFW shuttle in 2 minutes" => translate: "Reserva tu traslado en shuttle de Azle al DFW en 2 minutos". Latin American Spanish: "Reserva tu traslado en shuttle de Azle al aeropuerto DFW en 2 minutos"? Keep "DFW" unchanged. Could say "Reserva tu shuttle de Azle al DFW en 2 minutos". Let's decide. Then after the we have: " — door-to-door, non-stop, 24/7. We pick up from any address in Azle, TX and drop you curbside at your specific Dallas/Fort Worth International Airport (DFW) terminal. Fares start from $85 all-in — no surge pricing, no per-bag fees, no hidden surprises curbside." Translate: " — servicio puerta a puerta, sin paradas, 24/7. Recogemos en cualquier dirección de Azle, TX y te dejamos en la acera frente a tu terminal específica del Aeropuerto Internacional Dallas/Fort Worth (DFW). Las tarifas comienzan desde $85 todo incluido — sin tarifas dinámicas, sin cargos por equipaje, sin sorpresas ocultas en la acera." Need to keep the em dash (—) as is. Also the $85 stays. Now after that: " Saginaw to DFW Airport shuttle" translate link text: "Traslado en shuttle de Saginaw al aeropuerto DFW". Keep tag. Now nextDistance, Drive Time, and the Azle → DFW Corridor
Translate: "Distancia, tiempo de viaje y el corredor Azle → DFW". Keep → entity unchanged. Could translate to "Distancia, tiempo de viaje y el corredor Azle → DFW". Use same entity. NextHow far is Azle from DFW Airport, and how long is the drive? Heading there from Azle? See our Azle airport transportation page for direct service.
Translate: The strong text: "¿Qué tan lejos está Azle del aeropuerto DFW y cuánto tarda el viaje?" Or "¿A qué distancia está Azle del aeropuerto DFW y cuánto tiempo se tarda en llegar?" Natural Latin American Spanish: "¿Qué distancia hay entre Azle y el aeropuerto DFW, y cuánto tiempo se tarda en llegar?" We'll choose. Then "Heading there from Azle?" => "¿Vas ahí desde Azle?" Could be "¿Vas allá desde Azle?" Better: "¿Vas desde Azle?" Might be "¿Vas hacia allá desde Azle?" I'd go: "¿Vas hacia el aeropuerto DFW desde Azle?" but we need to keep short. Then "See our" => "Consulta nuestra". Actually "See our" could be "Consulta nuestra" or "Mira nuestro". Use "Consulta nuestra". Then tag with title attribute unchanged. The link text: "Azle airport transportation". Translate: "Transporte al aeropuerto de Azle". Keep tag. Then " page for direct service." => " página para servicio directo." Actually after the link we have a space then "page". So we need: " página para servicio directo." Keep the space before page. Now finalAzle sits in northwest Tarrant County (with the western city limits crossing into Parker County), on the south shore of Eagle Mountain Lake, roughly 35–45 miles from DFW Airport depending on which side of town you start from. The door-to-curbside drive is typically 50–75 minutes depending on time of day, pickup ZIP, and which DFW terminal you need. The two routings we run from Azle:
Translate: "Azle se encuentra en el noroeste del condado de Tarrant (con los límites occidentales de la ciudad que se extienden hasta el condado de Parker), en la ribera sur del lago Eagle Mountain, a aproximadamente 35–45 millas del aeropuerto DFW, dependiendo de desde qué parte de la ciudad salgas. El trayecto puerta a acera suele durar 50–75 minutos, según la hora del día, el código postal de recogida y la terminal DFW que necesites. Las dos rutas que operamos desde Azle son:" Check: "door-to-curbside" translate to "puerta a acera". Good. Keep the – entities unchanged. Now ensure we keep all tags exactly. Let's construct final HTML. We'll go line by line. Original:Azle to DFW Airport Shuttle Service
Translated:Servicio de traslado en shuttle de Azle al aeropuerto DFW
But maybe "Servicio de traslado en shuttle de Azle al aeropuerto DFW". Could also be "Servicio de transporte en shuttle de Azle al aeropuerto DFW". Choose first. Now... We need to preserve the tags exactly. Let's write:
Reserva tu traslado en shuttle de Azle al DFW en 2 minutos — servicio puerta a puerta, sin paradas, 24/7. Recogemos en cualquier dirección de Azle, TX y te dejamos en la acera frente a tu terminal específica del Aeropuerto Internacional Dallas/Fort Worth (DFW). Las tarifas comienzan desde $85 todo incluido — sin tarifas dinámicas, sin cargos por equipaje, sin sorpresas ocultas en la acera. Traslado en shuttle de Saginaw al aeropuerto DFW
Check punctuation: original had em dash after the link then text. We kept —. At end we have "curbside." we translated "en la acera". Good. Now...
Distancia, tiempo de viaje y el corredor Azle → DFW
Now... We need to translate the content inside
. Original:
How far is Azle from DFW Airport, and how long is the drive? Heading there from Azle? See our ,
- SH 199 (Jacksboro Highway) southeast to Loop 820 east to SH 183 east to International Parkway — the default fastest path for most Azle pickups. Cuts diagonally ...
- SH 199 southeast to Loop 820 east to SH 121 east to International Parkway — preferred for Terminal D international departures and for late-evening rides when the SH-183 / Airport Freeway section through Hurst and Bedford is congested. Enters DFW from the north toll plaza.
Our drivers run both routings daily and pick the one that fits your pickup ZIP, your DFW terminal, and current traffic. We monitor real-time DFW arrivals and surface-street conditions, especially the 6–9 a.m. southeast SH-199 commute into Fort Worth and the 4–7 p.m. westbound Loop 820 return, both of which add 15–25 minutes during peak.
Pickup Zones in Azle
Where in Azle do you pick up — downtown, lakeside, or the rural Parker County addresses?
Everywhere — we are a true door-to-door service. There is no central meet point and no need to drive to a park-and-ride lot. Common Azle pickup areas:
We need to translate each phrase. Let's translate step by step. First list item: - "SH 199 (Jacksboro Highway) southeast to Loop 820 east to SH 183 east to International Parkway — the default fastest path for most Azle pickups. Cuts diagonally through northwest Fort Worth, joins the I-820 north loop, and enters DFW from the south Bear Creek gate. Best for Terminals A, B, C, and E." We need to translate "the default fastest path for most Azle pickups." to Spanish: "es la ruta más rápida predeterminada para la mayoría de recogidas en Azle." Or "es la ruta más rápida por defecto para la mayoría de recogidas en Azle." Could use "Azle" unchanged. Also "Cuts diagonally through northwest Fort Worth" -> "Corta en diagonal por el noroeste de Fort Worth". "joins the I-820 north loop" -> "se une al boucle norte I-820"? Better: "se une al ramal norte de la I-820". "and enters DFW from the south Bear Creek gate." -> "e ingresa al DFW por la puerta sur de Bear Creek." "Best for Terminals A, B, C, and E." -> "Es la mejor opción para las terminales A, B, C y E." Second list item: - "SH 199 southeast to Loop 820 east to SH 121 east to International Parkway — preferred for Terminal D international departures and for late-evening rides when the SH-183 / Airport Freeway section through Hurst and Bedford is congested. Enters DFW from the north toll plaza." Translate: "SH 199 en dirección sureste hacia Loop 820 este hacia SH 121 este hacia International Parkway — preferida para salidas internacionales de la Terminal D y para viajes al final de la noche cuando el tramo de la SH-183 / Airport Freeway a través de Hurst y Bedford está congestionado. Ingresa al DFW por la plaza de peaje norte." Third paragraph: "Our drivers run both routings daily and pick the one that fits your pickup ZIP, your DFW terminal, and current traffic. We monitor real-time DFW arrivals and surface-street conditions, especially the 6–9 a.m. southeast SH-199 commute into Fort Worth and the 4–7 p.m. westbound Loop 820 return, both of which add 15–25 minutes during peak." Translate: "Nuestros conductores recorren ambas rutas todos los días y eligen la que mejor se ajusta a tu código postal de recogida, tu terminal del DFW y el tráfico actual. Monitoreamos llegadas en tiempo real al DFW y las condiciones del tráfico en las calles superficiales, especialmente el trayecto de la SH-199 en dirección sureste entre las 6 y 9 a.m. hacia Fort Worth y el regreso en dirección oeste por el Loop 820 entre las 4 y 7 p.m., ambos de los cuales pueden agregar entre 15 y 25 minutos durante las horas pico." Note: "pickup ZIP" may be "código postal de recogida" or "código postal de recogida". Keep as is? It's a location code. In Spanish we can say "código postal de recogida". "DFW terminal" may remain "terminal del DFW". "real-time DFW arrivals" -> "llegadas en tiempo real al DFW". "surface-street conditions" -> "condiciones del tráfico en las calles superficiales". "southwest SH-199 commute into Fort Worth" is actually "southeast SH-199 commute into Fort Worth". We'll keep "SH-199 en dirección sureste". "westbound Loop 820 return" -> "regreso en dirección oeste por el Loop 820". "add 15–25 minutes during peak." -> "agregan entre 15 y 25 minutos durante las horas pico." Now heading: "Pickup Zones in Azle
" -> "Zonas de recogida en Azle
" First paragraph under heading: "Where in Azle do you pick up — downtown, lakeside, or the rural Parker County addresses?
" -> "¿Dónde en Azle recojo — en el centro, junto al lago o en las direcciones rurales del Condado de Parker?
" Second paragraph: "Everywhere — we are a true door-to-door service. There is no central meet point and no need to drive to a park-and-ride lot. Common Azle pickup areas:
" -> "En todas partes — somos un verdadero servicio puerta a puerta. No hay un punto de encuentro central y no es necesario conducir hasta un lote de estacionamiento y traslado. Áreas comunes de recogida en Azle:
" We need to keep the line break? It ends with colon. Check tags: The- and
- and etc remain.
Also preserve HTML entities like maybe we can replace with non-breaking spaces as same. The English text uses after "SH" etc. That is fine.
Also keep — unchanged.
We need to ensure all punctuation is correct.
Potential issues: Some abbreviations: "SH" stands for "State Highway". Spanish translation might keep "SH" as is, but could be "SH" unchanged. Keep as is because they said city/airport names and codes unchanged. "SH" is a code; it's okay to keep. Similarly "Loop 820" unchanged. "I-820" is also an abbreviation; maybe keep as "I-820". Should we keep "I-820"? It appears in first list item: "joins the I-820 north loop". It may be the interstate number. Keep "I-820". So we need to translate phrase but keep those codes.
Also "Bear Creek gate" - keep as "Bear Creek gate"? Should we translate "gate"? Possibly keep "gate" in English because it's a proper name; "puerta sur de Bear Creek". So keep "Bear Creek" as is.
Also "north toll plaza" keep as "north toll plaza". In Spanish we can say "la caseta de peaje norte". But "north toll plaza" is a proper name, we could keep as is. However "north toll plaza" maybe considered a location name. Could keep "north toll plaza" unchanged: "la plaza de peaje norte". Let's translate to Spanish but maintain naming: "la caseta de peaje norte". The phrase is "Enters DFW from the north toll plaza." We can say "Ingresa al DFW por la caseta de peaje norte." That's natural
The user wants a translation from English to natural, native Latin American Spanish for travelers. Keep all HTML tags exactly as-is. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return only the translated HTML.
We have an HTML snippet:
- Downtown Azle (ZIP 76020) — the Main Street / Boyd Road corridor, Cross Timbers Road, and the Azle ISD school district neighborhoods.
- Eagle Mountain Lake waterfront (76020) — the Stewart Beach, Cardinal Cove, and Twin Points peninsulas, plus the lakeside neighborhoods along Lakeshore Drive, North Lakeshore Drive, and Cardinal Road.
- Pelican Bay (76020) — the small lakefront city tucked between Azle and the lake's south shore, including the Pelican Cove Marina area.
- South Azle / Reno corridor (76020) — addresses along Reno Road, Silver Creek Road, and the Azle / Lake Worth boundary where SH-199 begins to widen out.
- West Azle / rural Parker County (76020) — addresses along FM 730, FM 1886, and the rural cluster west of Boyd Road heading toward Springtown, where pickup time runs 5–10 minutes longer than central Azle.
- North Azle / Briar (76020) — the Briar area and the neighborhoods along Liberty School Road and Old Springtown Road, where we sometimes route via FM 730 to reach Loop 820.
- Hotels, B&Bs, and short-term rentals — we frequently serve guests staying at the Holiday Inn Express and Best Western along SH-199 in adjacent Lake Worth, plus Airbnb / VRBO units around Eagle Mountain Lake.
- and
- tags.
Now produce Spanish translation: natural Latin American Spanish for travelers. Use appropriate synonyms, avoid overly formal translation. The translation should be done per each bullet point.
Let's translate each bullet:
1. Downtown Azle (ZIP 76020) — the Main Street / Boyd Road corridor, Cross Timbers Road, and the Azle ISD school district neighborhoods.
In Spanish: Centro de Azle (Código postal 76020) — el corredor de Main Street / Boyd Road, Cross Timbers Road y los vecindarios del distrito escolar de Azle ISD.
But we might want to keep the English street names, we could keep them as they are, as they are proper nouns. The phrase "Downtown Azle" might be translated as "Centro de Azle". The user says keep city/airport names unchanged. So we keep "Azle". "Downtown" can be translated as "Centro". However, they might want "Downtown Azle" kept as is? But the instruction says keep city/airport names unchanged. "Downtown Azle" includes "Downtown". This is not a city name. So we can translate "Downtown". Usually we translate "Downtown" to "Centro". That's okay.
Check the other bullet:
2. Eagle Mountain Lake waterfront (76020) — the Stewart Beach, Cardinal Cove, and Twin Points peninsulas, plus the lakeside neighborhoods along Lakeshore Drive, North Lakeshore Drive, and Cardinal Road.
Spanish: Orilla del lago Eagle Mountain Lake (76020) — las penínsulas de Stewart Beach, Cardinal Cove y Twin Points, además de los vecindarios junto al lago a lo largo de Lakeshore Drive, North Lakeshore Drive y Cardinal Road.
But we might say "la orilla del lago Eagle Mountain Lake" or "el frente costero del lago Eagle Mountain Lake". Keep proper names: "Eagle Mountain Lake" unchanged.
3. Pelican Bay (76020) — the small lakefront city tucked between Azle and the lake's south shore, including the Pelican Cove Marina area.
Spanish: Pelican Bay (76020) — la pequeña ciudad frente al lago ubicada entre Azle y la orilla sur del lago, incluyendo el área de la marina Pelican Cove.
4. South Azle / Reno corridor (76020) — addresses along Reno Road, Silver Creek Road, and the Azle / Lake Worth boundary where SH-199 begins to widen out.
Spanish: Corredor South Azle / Reno (76020) — direcciones a lo largo de Reno Road, Silver Creek Road y la línea divisoria entre Azle y Lake Worth donde la SH-199 empieza a ensancharse.
5. West Azle / rural Parker County (76020) — addresses along FM 730, FM 1886, and the rural cluster west of Boyd Road heading toward Springtown, where pickup time runs 5–10 minutes longer than central Azle.
Spanish: West Azle / zona rural de Parker County (76020) — direcciones a lo largo de FM 730, FM 1886 y el grupo rural al oeste de Boyd Road rumbo a Springtown, donde el tiempo de recogida es de 5 a 10 minutos más que en el centro de Azle.
6. North Azle / Briar (76020) — the Briar area and the neighborhoods along Liberty School Road and Old Springtown Road, where we sometimes route via FM 730 to reach Loop 820.
Spanish: North Azle / Briar (76020) — el área de Briar y los vecindarios a lo largo de Liberty School Road y Old Springtown Road, donde a veces routeamos a través de FM 730 para llegar a Loop 820.
7. Hotels, B&Bs, and short-term rentals — we frequently serve guests staying at the Holiday Inn Express and Best Western along SH-199 in adjacent Lake Worth, plus Airbnb / VRBO units around Eagle Mountain Lake.
Spanish: Hoteles, B&Bs y alquileres a corto plazo — frecuentemente atendemos a huéspedes que se hospedan en el Holiday Inn Express y Best Western a lo largo de la SH-199 en la vecina Lake Worth, además de unidades de Airbnb / VRBO en los alrededores del lago Eagle Mountain Lake.
But note: In the original, "short-term rentals" we can translate as "alquileres a corto plazo". "B&Bs" we might keep as "B&B" or "camas y desayuno"? In Spanish we could translate "B&Bs" to "B&B" but maintain the HTML & which is & in HTML. The original includes "B&Bs". We need to keep that same entity. So in translation, we should keep "B&Bs". Actually, the original uses "B&Bs". We need to keep the same string "B&Bs" because it's HTML entity for &. So in Spanish translation we need to preserve "B&Bs". Good.
Also "Hotels" we can keep "Hoteles". In Spanish we can say "Hoteles, B&Bs y alquileres a corto plazo". That matches.
Now we need to ensure that all HTML tags remain exactly as is:
- ,
- , . Also keep — (em dash), (non-breaking space) used inside "FM 730". In translation we may want to preserve the same HTML entities like and – for the dash. Also — is present. In Spanish translation we need to keep those as is. Use for spaces in "FM 730". Ensure – for dash? In bullet 5: "5–10". We preserve that.
Now produce the final HTML with translations.
Potential translation approach: The language should be natural Latin American Spanish. Use "usted" maybe? But for a website, the style might be "nosotros" or "nosotros" for service. The user is a "shuttle landing page". We need to adapt the phrasing. For instance, "the pickup time runs 5–10 minutes longer" can be translated as "el tiempo de recogida es de 5 a 10 minutos más largo". Use "nosotros" maybe? In bullet 7: "we frequently serve guests". We can say "Frecuentemente atendemos a los huéspedes". That is okay.
We need to ensure we keep all HTML tags exactly as is. Ensure no extra spaces that may change semantics. Keep line breaks: It's a single line with
- ...
Tell us your exact street address when you book and the driver will meet you at the curb at your scheduled pickup time. For multi-passenger pickups within Azle (split parties, hotel-plus-residence), note it in the booking comments and we route accordingly at no extra charge.
DFW Terminal Routing — A, B, C, D, or E
DFW Airport has five active terminals, each with its own departures-level curb. We drop at the correct one based on your airline:
- Terminal A — American Airlines (most domestic departures)
- Terminal B — American Eagle regional and select American domestic
- Terminal C — American Airlines (additional domestic)
- Terminal D — international departures (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico, and most foreign carriers)
- Terminal E — non-American carriers: Delta, United, Spirit, Frontier, Southwest (limited), JetBlue, Alaska, Sun Country
Tell us your flight number when you book and we route to the correct terminal automatically — no need to look it up yourself.
Travel Tips for Azle → DFW
We need to translate this into natural Latin American Spanish, for travelers. So the translation should be colloquial but clear, appropriate for travelers, possibly using "tú" forms. Keep HTML tags. Potential translation:Indícanos tu dirección exacta al momento de reservar y el conductor te esperará en la acera a la hora de recogida programada. Para recogidas de varios pasajeros dentro de Azle (grupos divididos, hotel más residencia), anótalo en los comentarios de la reserva y routematics lo direccionaremos sin costo adicional.
But we need to translate "For multi-passenger pickups within Azle (split parties, hotel-plus-residence), note it in the booking comments and we route accordingly at no extra charge." So "Para recogidas de varios pasajeros dentro de Azle (grupos divididos, hotel más residencia), indícalo en los comentarios de la reserva y lo routematics sin cargo extra." But we might avoid using "routematics", that is a brand? It's just "lo encaminhamos". The phrase "we route accordingly" is "lo direccionamos" or "lo gestionamos". "at no extra charge" => "sin costo adicional". Good. NowDFW Terminal Routing — A, B, C, D, or E
=> "DFW Terminal Routing — A, B, C, D, o E". Keep same HTML tag. The term "Routing" maybe "Enrutamiento". So "Enrutamiento de Terminales DFW — A, B, C, D o E". Could keep as "DFW Terminal Routing — A, B, C, D, o E". Let's translate "Routing" to "Enrutamiento". SoEnrutamiento de Terminales DFW — A, B, C, D o E
. But keep the dash as HTML entity. Use —. NowDFW Airport has five active terminals, each with its own departures-level curb. We drop at the correct one based on your airline:
=> "El aeropuerto DFW cuenta con cinco terminales activas, cada una con su propia acera de salida. Te dejamos en la terminal correcta según tu aerolinea:" But maybe "We drop" means "We drop you off". In Spanish: "Los dejamos en la terminal correcta según tu aerolinea". Use "te dejamos" or "los dejamos". Let's go with "Te dejamos". So:El aeropuerto DFW tiene cinco terminales activas, cada una con su propia acera de salidas. Te dejamos en la terminal correcta según tu aerolinea:
Now the list items. We need to translate each but keep the terminal letters and airline names unchanged (airline names are proper nouns; they remain in English). The description after dash: "American Airlines (most domestic departures)" => "American Airlines (la mayoría de los vuelos domésticos)". "American Eagle regional and select American domestic" => "American Eagle regional y algunos vuelos domésticos de American". "American Airlines (additional domestic)" => "American Airlines (vuelos domésticos adicionales)". "international departures (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico, and most foreign carriers)" => "salidas internacionales (American, British Airways, Lufthansa, Emirates, Qatar, JAL, Korean, Aeromexico y la mayoría de las demás aerolíneas extranjeras)". "non-American carriers: Delta, United, Spirit, Frontier, Southwest (limited), JetBlue, Alaska, Sun Country" => "aerolíneas no estadounidenses: Delta, United, Spirit, Frontier, Southwest (limitado), JetBlue, Alaska, Sun Country". We might keep the airline names unchanged. Now the final paragraph: "Tell us your flight number when you book and we route to the correct terminal automatically — no need to look it up yourself." => "Indícanos tu número de vuelo al reservar y te direccionamos automáticamente a la terminal correcta — no necesitas buscarlo tú mismo." Now the finalTravel Tips for Azle → DFW
=> "Consejos de viaje de Azle a DFW". Use arrow as HTML entity: "→". SoConsejos de viaje para Azle → DFW
. Make sure we keep all tags exactly as-is. The HTML includes line breaks? The content provided has...
...
...
- ... list items etc. Keep same structure.
Now ensure translation is natural Latin American Spanish. Use "tú" forms. Use "aeropuerto DFW" not "DFW Airport". Keep "DFW" unchanged.
Check each phrase:
- "Tell us your exact street address when you book" => "Indícanos tu dirección exacta al reservar". Or "Dinos tu dirección exacta al hacer la reserva". Let's choose "Indícanos tu dirección exacta al hacer la reserva". That is natural.
- "and the driver will meet you at the curb at your scheduled pickup time." => "y el conductor te esperará en la acera a la hora de recogida programada."
- "For multi-passenger pickups within Azle (split parties, hotel-plus-residence)" => "Para recogidas de varios pasajeros dentro de Azle (grupos divididos, hotel más residencia)". Or "Para recogidas de varios pasajeros en Azle (fiestas divididas, hotel más residencia)". "Split parties" could be "fiestas divididas" or "grupos separados". "hotel-plus-residence" is "hotel más residencia". So "Para recogidas de varios pasajeros dentro de Azle (grupos divididos, hotel más residencia)".
- "note it in the booking comments and we route accordingly at no extra charge." => "anótalo en los comentarios de la reserva y lo direccionamos sin costo adicional." Or "indícalo en los comentarios de la reserva y lo gestionamos sin cargo extra." Use "sin costo adicional".
Now the heading
- Terminal A — American Airlines (most domestic departures) => "
- Terminal A — American Airlines (la mayoría de los vuelos domésticos) "
- Terminal B — American Eagle regional and select American domestic => "
- Terminal B — American Eagle regional y algunos vuelos domésticos de American "
- Terminal C — American Airlines
We need to translate the HTML content (English) to NATURAL, native Latin American Spanish for travelers. Keep HTML tags unchanged. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return only the translated HTML. The content is a list of bullet items (li) with strong tags and some HTML entities. We need to translate each sentence into natural Latin American Spanish, with proper nuance for travelers. Must preserve HTML tags, keep city/airport names, codes unchanged. Must keep phone numbers and URLs unchanged. No extra text.
We need to be careful about translation: "For 6–9 a.m. departures, the SH-199 southeast commute into Fort Worth and the Loop 820 east loop both back up heavily on weekdays. We pre-set your pickup with that buffer built in — you do not need to ask." That should be translated to something like: "Para salidas entre las 6 y las 9 a.m., la ruta SH-199 hacia el sureste hacia Fort Worth y el Loop 820 este se congestionan mucho los días laborables. Nosotros programamos su recogida con ese margen incluido — no necesita solicitarlo."
Make sure to use natural Latin American Spanish (i.e., no "vosotros", no overly Castilian idioms). Use "usted" forms perhaps. Use common expressions like "para salidas entre las 6 y las 9 a.m.", "se generan embotellamientos", etc.
Second bullet: "For Terminal D international departures, add 15 minutes vs. domestic so you have margin at international security and immigration checkpoints. We default to a 3-hour pre-departure pickup unless you tell us otherwise." In Spanish: "Para salidas internacionales desde la Terminal D, agregue 15 minutos respecto a los vuelos nacionales para tener margen en los puntos de control de seguridad e inmigración. Por defecto, programamos la recogida 3 horas antes de la salida, a menos que nos indique lo contrario."
Third bullet: "For 4–7 p.m. inbound rides (DFW → Azle), expect 70–90 minutes during peak. We factor it into your return ETA so we are not late to your next obligation." Spanish: "Para viajes de regreso entre las 4 y las 7 p.m. (DFW → Azle), espere entre 70 y 90 minutos en horas pico. Lo incluimos en la hora estimada de regreso para no llegar tarde a su siguiente compromiso."
Fourth bullet: "Major events — Cowboys home games (AT&T Stadium in Arlington), Rangers home games (Globe Life Field), and large concerts at Dickies Arena in Fort Worth can ripple traffic across Loop 820 and SH-183. Book a little earlier on event days to lock in your preferred window." Spanish: "Eventos importantes — partidos locales de los Cowboys (AT&T Stadium en Arlington), partidos locales de los Rangers (Globe Life Field) y grandes conciertos en el Dickies Arena en Fort Worth pueden provocar efectos en el tráfico por todo el Loop 820 y la SH-183. Reserve un poco antes en los días de evento para asegurar su franja horaria preferida."
Fifth bullet: "Eagle Mountain Lake weekends — on summer weekends, SH-199 northbound (lake-bound) backs up on Friday evenings and SH-199 southbound (returning) backs up on Sunday afternoons. Sunday-evening DFW arrivals should plan for an extra 15–20 minutes." Spanish: "Fines de semana en Eagle Mountain Lake — los fines de semana de verano, la SH-199 en dirección norte (hacia el lago) se satura los viernes por la tarde y la SH-199 en dirección sur (de regreso) se satura los domingos por la tarde. Los pasajeros que lleguen a DFW el domingo por la noche deben prévoir entre 15 y 20 minutos adicionales."
Note: Use "preveer" or "considerar"? "Deben planificar" or "deben prever". Keep natural Latin American Spanish: "Deben planificar" or "deben contemplar". Use "planificar" maybe.
Also keep HTML tags:
- ...
- items inside. Use tags for the same segments. Make sure to preserve HTML entities like –, —, → as they are. Now we need to output only the translated HTML. Potential translation nuance: Bullet 1: Original:
- For 6–9 a.m. departures, the SH-199 southeast commute into Fort Worth and the Loop 820 east loop both back up heavily on weekdays. We pre-set your pickup with that buffer built in — you do not need to ask. We need to translate. Use "Para las salidas entre las 6 y las 9 a.m." The phrase "the SH-199 southeast commute into Fort Worth and the Loop 820 east loop both back up heavily on weekdays." Could translate as "la circulación por la SH-199 hacia el sureste hacia Fort Worth y el ramal este del Loop 820 se congestionan fuertemente los días laborables." We need to keep "SH-199" and "Fort Worth" unchanged. "Loop 820" unchanged. "Nosotros pre-establecemos su recogida con ese margen incorporado — no necesita pedirlo." Could use "pre-configuramos" but "pre-set" is similar to "preconfigurar". Use "preconfiguramos su recogida con ese margen incorporado — no necesita solicitarlo." Potential translation: "Nosotros preconfiguramos su recogida con ese margen incorporado — no necesita solicitarlo." That is natural. Bullet 2:
- For Terminal D international departures, add 15 minutes vs. domestic so you have margin at international security and immigration checkpoints. We default to a 3-hour pre-departure pickup unless you tell us otherwise. Translate: "Para las salidas internacionales desde la Terminal D, agregue 15 minutos respecto a los vuelos nacionales para tener margen en los puntos de control de seguridad e inmigración. Por defecto, programamos la recogida 3 horas antes de la salida, a menos que nos indique lo contrario." Bullet 3:
- For 4–7 p.m. inbound rides (DFW → Azle), expect 70–90 minutes during peak. We factor it into your return ETA so we are not late to your next obligation. Translate: "Para los viajes de regreso entre las 4 y las 7 p.m. (DFW → Azle), espere entre 70 y 90 minutos en horas pico. Lo incluimos en la hora estimada de regreso para no llegar tarde a su próximo compromiso." Bullet 4:
- Major events — Cowboys home games (AT&T Stadium in Arlington), Rangers home games (Globe Life Field), and large concerts at Dickies Arena in Fort Worth can ripple traffic across Loop 820 and SH-183. Book a little earlier on event days to lock in your preferred window. Translate: "Eventos importantes — partidos locales de los Cowboys (AT&T Stadium en Arlington), partidos locales de los Rangers (Globe Life Field) y grandes conciertos en el Dickies Arena en Fort Worth pueden provocar efectos en el tráfico por todo el Loop 820 y la SH-183. Reserve un poco antes en los días de evento para asegurar su franja horaria preferida." Bullet 5:
- Eagle Mountain Lake weekends — on summer weekends, SH-199 northbound (lake-bound) backs up on Friday evenings and SH-199 southbound (returning) backs up on Sunday afternoons. Sunday-evening DFW arrivals should plan for an extra 15–20 minutes. Translate: "Fines de semana en Eagle Mountain Lake — los fines de semana de verano, la SH-199 en dirección norte (hacia el lago) se satura los viernes por la tarde y la SH-199 en dirección sur (de regreso) se satura los domingos por la tarde. Los pasajeros que lleguen a DFW el domingo por la noche deben planificar entre 15 y 20 minutos adicionales." We need to preserve HTML tags, the tags, the – and — etc. Now check for any missing translations: "We pre-set your pickup with that buffer built in — you do not need to ask." Could also be "Nosotros preconfiguramos su recogida con ese margen incorporado — no necesita pedirlo." That is okay. Check the translation for bullet 4: "Book a little earlier on event days to lock in your preferred window." "Reserve un poco antes en los días de evento para asegurar su franja horaria preferida." Good. Bullet 5: "Sunday-evening DFW arrivals should plan for an extra 15–20 minutes." In Spanish: "Los pasajeros que lleguen a DFW el domingo por la noche deben planificar entre 15 y 20 minutos adicionales." That is fine. Now check if any phone numbers or URLs appear? Not in this snippet. So okay. Now ensure that we preserve all tags. The original has
- items. We need to return only the translated HTML, presumably the entire snippet including
- and
- list, maybe preceded by some content. The user gave:
- For 6–9 a.m. departures, ... ...
- contents, but keep
- tags. The final answer should be the same structure.
Thus
We need to translate the given HTML snippet (including tags) from English to NATURAL, native Latin American Spanish for travelers. Keep all HTML tags exactly as-is. Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. Return ONLY the translated HTML.
The snippet is:
```
- Flight delays — if your inbound flight is delayed or rerouted, your pickup adjusts automatically. You do not need to call. Text or call the dispatcher number on your confirmation when you have your bags and we'll meet you curbside.
Routes Related to Azle
Need a different lane? See our companion route pages: Azle to Dallas Love Field (DAL), Azle to Fort Worth, Azle to Dallas, Fort Worth to DFW, and DFW airport shuttle hub.
Ready to ride? Book your Azle → DFW shuttle online in under two minutes, or call (817) 403-6196 — we answer 8 a.m. to 6 p.m. CST and the booking system is live 24/7.
``` We need to translate the English text into natural Latin American Spanish (for travelers). Keep tags unchanged. Keep city/airport names and codes unchanged (so "Azle", "Dallas Love Field (DAL)", "Fort Worth", "Dallas", "DFW", "DFW airport shuttle hub", etc.) Keep phone numbers unchanged ( (817) 403-6196 ), URLs unchanged. Keep HTML tags and attributes unchanged. Only translate visible text. We need to maintain Spanish naturalness, including appropriate tone for travelers. Avoid overly formal translation; use colloquial but respectful. Potential translations: - "Flight delays" -> "Retrasos de vuelo". Could keep the same as "Flight delays". In Spanish we might say "Retrasos de vuelo". Keep tags. - "if your inbound flight is delayed or rerouted, your pickup adjusts automatically." => "si tu vuelo de llegada se retrasa o es redirigido, tu recogida se ajusta automáticamente." Could also use "si tu vuelo de entrada se retrasa o es reubicado". Keep Spanish. - "You do not need to call." => "No necesitas llamar." or "No es necesario que llames." - "Text or call the dispatcher number on your confirmation when you have your bags and we'll meet you curbside." => "Envía un mensaje o llama al número del despachador en tu confirmación cuando tengas tu equipaje y te esperamos en la acera." Could say "te esperamos en la acera". Good. - Next: "
Routes Related to Azle
" => "Rutas relacionadas con Azle
" - "Need a different lane? See our companion route pages:" => "¿Necesitas una ruta diferente? Consulta nuestras páginas de rutas complementarias:" Or "Necesitas otra ruta? Mira nuestras páginas de rutas complementarias:". - Then a list of links. Keep anchor text unchanged for city/airport names. But we could translate anchor titles? The instructions: Keep city/airport names and codes unchanged. The anchor text includes city/airport names and codes; should remain unchanged. Titles (title attribute) also contain city/airport names; they could be translated but they mention the same names; we can keep them as they are because they are names. - "Ready to ride?" => "¿Listo para viajar?" Or "¿Listo para el recorrido?" Use "¿Listo para viajar?" For a traveler. - "Book your Azle → DFW shuttle online in under two minutes, or call (817) 403-6196 — we answer 8 a.m. to 6 p.m. CST and the booking system is live 24/7." We need to translate "Book your Azle → DFW shuttle online" to Spanish: "Reserva tu shuttle de Azle a DFW en línea". However we must keep the arrow "→". We can replace the English words but keep the arrow. So anchor text: "Reserva tu Azle → DFW shuttle en línea". Or "Reserva tu shuttle Azle → DFW en línea". But we need to keep city/airport names unchanged, so "Azle" and "DFW" unchanged. Keep "shuttle". Could keep "shuttle" as is. The phrase "Book your Azle → DFW shuttle online" becomes "Reserva tu Azle → DFW shuttle en línea". The strong tag includes that phrase. We'll maintain the strong tag. - "in under two minutes" => "en menos de dos minutos". - "or call" => "o llama al". - "we answer 8 a.m. to 6 p.m. CST" => "respondemos de 8 a.m. a 6 p.m. CST". Or "de 8:00 a.m. a 6:00 p.m. CST". Keep as is. - "and the booking system is live 24/7." => "y el sistema de reservas está activo 24/7." Also note the- appears before the
- . It appears that the snippet begins with
- and ends with
- after the
- ? Actually the snippet: `
- Flight delays — ...
Routes Related to Azle
`. So there is a closing - Retrasos de vuelo — si tu vuelo de llegada se retrasa o es redirigido, tu recogida se ajusta automáticamente. No necesitas llamar. Envía un mensaje o llama al número del despachador en tu confirmación cuando tengas tu equipaje y te esperamos en la acera.
- ...` and `
DFW Terminal Routing — A, B, C, D, or E
=> "Enrutamiento de Terminales DFW — A, B, C, D o E". Might also keep "DFW Terminal Routing". But translation: "Enrutamiento de Terminales DFW". The phrase "Terminal Routing" is perhaps "Enrutamiento de Terminales". So final:Enrutamiento de Terminales DFW — A, B, C, D o E
. Now the next paragraph: "DFW Airport has five active terminals, each with its own departures-level curb." => "El aeropuerto DFW tiene cinco terminales activas, cada una con su propia acera de salidas." Could be "acera de salidas". That's fine. - "We drop at the correct one based on your airline:" => "Te dejamos en la terminal correcta según tu aerolinea:". Use "aerolínea" singular. Now the list items:- around the
- earlier not included. We can leave it unchanged.
Thus final translation:
```
Rutas relacionadas con Azle
¿Necesitas una ruta diferente? Consulta nuestras páginas de rutas complementarias: Azle to Dallas Love Field (DAL), Azle to Fort Worth, Azle to Dallas, Fort Worth to DFW, y DFW airport shuttle hub.
¿Listo para viajar? Reserva tu Azle → DFW shuttle en línea en menos de dos minutos, o llama al (817) 403-6196 — respondemos de 8 a.m. a 6 p.m. CST y el sistema de reservas está activo 24/7.
``` Check for any missing spaces, HTML entities: the original uses for phone number (817) 403-6196. Keep that as is. Also in the phrase "8 a.m. to 6 p.m. CST". Keep that. Also keep "CST" unchanged. Also original uses "in under two minutes," with comma. We can maintain punctuation. We need to ensure we keep the- opening? The snippet includes `
- in
- , . Also keep — (em dash), (non-breaking space) used inside "FM 730". In translation we may want to preserve the same HTML entities like and – for the dash. Also — is present. In Spanish translation we need to keep those as is. Use for spaces in "FM 730". Ensure – for dash? In bullet 5: "5–10". We preserve that.
Now produce the final HTML with translations.
Potential translation approach: The language should be natural Latin American Spanish. Use "usted" maybe? But for a website, the style might be "nosotros" or "nosotros" for service. The user is a "shuttle landing page". We need to adapt the phrasing. For instance, "the pickup time runs 5–10 minutes longer" can be translated as "el tiempo de recogida es de 5 a 10 minutos más largo". Use "nosotros" maybe? In bullet 7: "we frequently serve guests". We can say "Frecuentemente atendemos a los huéspedes". That is okay.
We need to ensure we keep all HTML tags exactly as is. Ensure no extra spaces that may change semantics. Keep line breaks: It's a single line with
