Granbury Airport Shuttle

tag text. Next:

...

We need to translate while preserving tags and any inline markup like → and ↔. Those are HTML entities; they should stay unchanged (they represent arrows). The inner text we translate. Original paragraph: "The straight-line distance from Granbury to Love Field is about 62 miles, but the real driving distance via US-377 → I-20 East → I-30 East → I-35E South runs 70–78 driving miles with a median of 74 miles across our 249 most-recent completed Granbury↔Love Field trips. Door-to-door drive time typically runs 80–115 minutes — closer to 80 minutes off-peak and pre-dawn, closer to 115 minutes during DFW-area rush windows on I-30 or I-35E. Headed to Dallas Love Field from a neighboring Somervell-County town? See our Glen Rose to Love Field shuttle service for direct rides to DAL." We translate to Latin American Spanish, preserving tags. Points: Keep city/airport names unchanged: Granbury, Love Field, Dallas Love Field, Somervell-County, Glen Rose, DFW, I-30, I-35E, etc. Keep codes unchanged (US-377, I-20 East, I-30 East, I-35E South, DFW-area, etc). Keep the tags content unchanged? Actually the content inside is numbers and maybe "driving miles". Should we translate "driving miles"? The requirement: Keep city/airport names and codes unchanged, but other text can be translated. However "driving miles" is not a city name or code; it's part of the measurement. Should we translate? The instruction: "Translate this airport-shuttle landing-page HTML 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." It doesn't say to keep measurement units unchanged. So we can translate "driving miles" to "millas recorridas" or "millas de manejo". But maybe keep "miles" as is? Usually translate to Spanish: "millas". Could keep "millas". The phrase "driving miles" maybe "millas de conducción". We'll translate naturally. Similarly "median of 74 miles" => "mediana de 74 millas" maybe. "Door-to-door drive time typically runs 80–115 minutes" => "El tiempo de viaje puerta a puerta suele ser de 80‑115 minutos". Keep dash as –. "closer to 80 minutes off-peak and pre-dawn" => "más cercano a 80 minutos en horas bajas y antes del amanecer" but natural Latin American: "más cercano a 80 minutos en horas valle y antes del amanecer". Or "más cerca de 80 minutos en horas bajas y antes del amanecer". We'll pick "más cercano a 80 minutos en horas valle y antes del amanecer". "closer to 115 minutes during DFW-area rush windows on I-30 or I-35E." => "más cercano a 115 minutos durante los horarios pico de la zona DFW en la I-30 o la I-35E." Keep DFW-area unchanged? "DFW-area" is a code? It's not a city/airport name but maybe keep as is? It says keep city/airport names and codes unchanged. "DFW-area" includes code DFW; we could keep "DFW-area". We'll keep as is. "Headed to Dallas Love Field from a neighboring Somervell-County town?" => "¿Se dirige al Love Field de Dallas desde una localidad vecina del condado de Somervell?" Keep Somervell-County unchanged? It's a county name; maybe keep as is? It's not a city/airport name; but it's a proper noun. Probably keep "Somervell-County". However translation may adapt: "condado de Somervell". The instruction: Keep city/airport names and codes unchanged. It doesn't forbid translating other proper nouns like county. But to be safe, we could keep "Somervell-County". Might be okay to translate to "condado de Somervell". I'd lean to keep as is because it's a proper name. However "Somervell-County" includes hyphen; it's a proper name. I'd keep unchanged. "See our Glen Rose to Love Field shuttle service for direct rides to DAL." => "Vea nuestro servicio de transporte Glen Rose a Love Field para viajes directos a DAL." Keep title attribute unchanged? It's part of tag; we should keep title unchanged? The instruction: Keep ALL HTML tags exactly as-is. That includes attributes values? Usually yes, we should keep them unchanged. However the title attribute contains English text "Glen Rose to Love Field shuttle". If we keep tags exactly as-is, we must keep the attribute value unchanged. So we must not translate the title. Similarly the href stays same. The link text inside we can translate? The instruction says keep HTML tags exactly as-is; the content inside tags is not a tag, it's text. So we can translate the link text. But the title attribute is part of the tag, so we must keep it unchanged. So we keep title="Glen Rose to Love Field shuttle". The link text we can translate to "Glen Rose a Love Field". However we must be careful not to alter the tag itself: Glen Rose to Love Field shuttle. If we change the inner text, we are not changing the tag; it's still ... . That's allowed. Thus final HTML:

Sobre el tiempo de viaje

La distancia en línea recta entre Granbury y el Love Field es de aproximadamente 62 millas, pero la distancia real de conducción mediante US-377 → I-20 Este → I-30 Este → I-35E Sur abarca 70–78 millas de conducción con una mediana de 74 millas en nuestras 249 recientes completadas Granbury↔Love Field. El tiempo de viaje puerta a puerta suele ser de 80–115 minutos — más cercano a 80 minutos en horas valle y antes del amanecer, y más cercano a 115 minutos durante los horarios pico de la zona DFW en la I-30 o la I-35E. ¿Se dirige al Love Field de Dallas desde una localidad vecina del condado de Somervell? Vea nuestro servicio de transporte Glen Rose a Love Field para viajes directos a DAL.

But need to keep the text "Glen Rose to Love Field shuttle" inside as per translation? I changed to "servicio de transporte Glen Rose a Love Field". That changes the inner text but keeps the tag. However maybe we should keep "Glen Rose to Love Field shuttle" as inner text and just add a service phrase outside? The original phrase: "See our Glen Rose to Love Field shuttle service for direct rides to DAL." So the link text is "Glen Rose to Love Field shuttle". After that, the word "service" is outside the link. If we translate, we might want to keep the link text unchanged? The instruction says keep HTML tags exactly as-is; the content inside is not a tag. So we could translate it. However many translation tasks keep the link text unchanged because it's a brand or specific name. But "Glen Rose

Preguntas frecuentes

¿Cuánto tiempo tarda el viaje desde Granbury hasta Love Field Airport?

El tiempo típico de viaje puerta a puerta desde Granbury hasta Love Field varía entre 84 y 115 minutos, según las condiciones del tráfico.

¿Me recogerán en mi dirección exacta en Granbury?

Sí, ofrecemos un servicio privado puerta a puerta. Por favor, proporcione su dirección completa al hacer la reserva y nos aseguraremos de que le recojamos justo fuera de su puerta.

¿Qué debo saber sobre el manejo del equipaje?

Estaremos encantados de ayudarle con su equipaje durante el viaje. Indíquenos cuántas piezas tiene y nos aseguraremos de que lleguen de forma segura al Love Field Airport.

Route Specifics: Granbury to Dallas Love Field (DAL)

We need to translate the English paragraph to natural Latin American Spanish, preserving HTML tags exactly as-is. The input is just a

containing text with some strong tags, — etc. We must keep all HTML tags unchanged, i.e., we keep

,

, , — etc. Only translate the textual content inside tags. We must keep city/airport names and codes unchanged: Granbury, Dallas Love Field, US-377, Cresson, Aledo, I-20 East, west Fort Worth, I-30 East, I-35E South, Mockingbird Lane, Cedar Springs Road, Love Field main terminal, 8008 Herb Kelleher Way, ZIP 75235. Also keep phone numbers and URLs unchanged (none present). Keep strong tags. Thus we need to translate sentences to Spanish, preserving the markup. Original:

The real driving distance from a typical Granbury pickup to Dallas Love Field is 70–78 miles — median 74 miles across our 249 most-recent completed Granbury↔Love Field rides — with door-to-door drive time of 80–115 minutes depending on US-377 traffic between Cresson and Aledo, I-20 East congestion through west Fort Worth, and most importantly I-30 East / I-35E South traffic crossing into Dallas. From the historic Granbury square, drivers head northeast on US-377 to pick up I-20 East at the Aledo / Willow Park interchange, run I-30 East (Tom Landry Freeway) through Arlington into Dallas, then drop to I-35E South for a short jog and exit at Mockingbird Lane / Cedar Springs Road for the Love Field main terminal at 8008 Herb Kelleher Way (ZIP 75235).

We need to translate inside

and etc. Keep the strong tags around the numbers. Thus produce:

La distancia real de conducción desde un típico punto de recogida en Granbury hasta el Aeropuerto Love Field de Dallas es 70–78 millas — mediana 74 millas en nuestras 249 últimas rides completadas Granbury↔Love Field — con un tiempo de conducción puerta a puerta de 80–115 minutos, dependiendo del tráfico de la US-377 entre Cresson y Aledo, la congestión de la I-20 Este hacia el oeste de Fort Worth y, lo más importante, el tráfico de la I-30 Este / I-35E Sur al cruzar hacia Dallas. Desde la histórica plaza de Granbury, los conductores toman la US-377 hacia el noreste para incorporarse a la I-20 Este en el intercambio de Aledo / Willow Park, recorren la I-30 Este (Autopista Tom Landry) pasando por Arlington hacia Dallas, luego se incorporan a la I-35E Sur por un corto tramo y salen en Mockingbird Lane / Cedar Springs Road para llegar a la terminal principal del Love Field en 8008 Herb Kelleher Way (ZIP 75235).

We must keep ↔ unchanged? The original had Granbury↔Love Field (HTML entity for left-right arrow). We need to keep that exactly. In translation we used "Granbury↔Love Field". That changes the entity; we must keep the entity as is. So we need to keep "Granbury↔Love Field". So translation should keep that entity unchanged. So inside the sentence we need to keep "Granbury↔Love Field". So we must not replace with Unicode arrow. Keep as is. Thus: "... across our 249 most-recent completed Granbury↔Love Field rides". So translate "most-recent completed" as "últimas completadas" maybe "más recientes completadas". Keep entity. Thus: "... en nuestras 249 rides más recientes completadas Granbury↔Love Field". But we need to keep entity exactly: "Granbury↔Love Field". So phrase: "nas 249 rides más recientes completadas Granbury↔Love Field". However "rides" is English word; we should translate to Spanish "viajes". Keep entity. So "nas 249 viajes más recientes completados Granbury↔Love Field". Or "las 249 viajes más recientes completados Granbury↔Love Field". Need article: " nuestras 249 viajes más recientes completados Granbury↔Love Field". Could be "nuestros 249 viajes más recientes completados Granbury↔Love Field". Since "viajes" is masculine plural, "nuestros". So: "nuestros 249 viajes más recientes completados Granbury↔Love Field". Check original: "across our 249 most-recent completed Granbury↔Love Field rides". So "our 249 most-recent completed Granbury↔Love Field rides". So translation: "nuestros 249 viajes más recientes completados Granbury↔Love Field". That seems fine. Now other translations: "The real driving distance from a typical Granbury pickup to Dallas Love Field is" -> "La distancia real de conducción desde un típico punto de recogida en Granbury hasta el Aeropuerto Love Field de Dallas es". Keep strong tags. We must keep the — entities as they are (they are HTML em dash). Keep them unchanged. Thus after first strong: " — median 74 miles across our 249 most-recent completed Granbury↔Love Field rides — with door-to-door drive time of 80–115 minutes depending on US-377 traffic between Cresson and Aledo, I-20 East congestion through west Fort Worth, and most importantly I-30 East / I-35E South traffic crossing into Dallas." Translate: " — mediana 74 millas en nuestros 249 viajes más recientes completados Granbury↔Love Field — con un tiempo de conducción puerta a puerta de 80–115 minutos, dependiendo del tráfico de la US-377 entre Cresson y Aledo, la congestión de la I-20 Este hacia el oeste de Fort Worth y, lo más importante, el tráfico de la I-30 Este / I-35E Sur al cruzar hacia Dallas." Check: we kept — as " — ". Should keep the entity exactly: " — ". In output we can keep the same entity. So we need to output " — ". We'll keep as is. Now second sentence: "From the historic Granbury square, drivers head northeast on US-377 to pick up I-20 East at the Aledo / Willow Park interchange, run I-30 East (Tom Landry Freeway) through Arlington into Dallas, then drop to I-35E South for a short jog and exit at Mockingbird Lane / Cedar Springs Road for the Love Field main terminal at 8008 Herb Kelleher Way (ZIP 75235)." Translate: "Desde la histórica plaza de Granbury, los conductores se dirigen hacia el noreste por la US-377 para incorporarse a la I-20 Este en el intercambio de Aledo / Willow Park, continúan por la I-30 Este (Autopista Tom Landry) pasando por Arlington hacia Dallas, luego se desvían hacia la I-35E Sur por un corto tramo y salen en Mockingbird Lane / Cedar Springs Road para llegar a la terminal principal del Love Field en 8008 Herb Kelleher Way (ZIP 75235)." Check for keeping slash and spaces: "Aledo / Willow Park". Keep slash and spaces. We must keep "US-377", "I-20 East", "I-30 East", "I-35E South", "Mockingbird Lane", "Cedar Springs Road", "Herb Kelleher Way", "ZIP 75235". Also keep parentheses. Thus final HTML:

La distancia real de conducción desde un típico punto de recogida en Granbury hasta el Aeropuerto Love Field de Dallas es 70–78 millas — mediana 74 millas en nuestros 249 viajes más recientes completados Granbury↔Love Field — con un tiempo de conducción puerta a puerta de 80–115 minutos, dependiendo del tráfico de la US-377 entre Cresson y Aledo, la congestión de la I-20 Este hacia el oeste de Fort Worth y, We need to translate the given HTML content to natural, native Latin American Spanish for travelers, preserving HTML tags, city/airport names and codes unchanged, phone numbers and URLs unchanged. There are no phone numbers or URLs in the snippet. We need to translate the text content. We need to keep all HTML tags exactly as-is. So we need to output the same tags but with translated text inside. Keep any HTML markup like

, , — etc. We must not change city/airport names and codes: Granbury, Love Field, DFW, etc. Keep them as they are (English). Also keep "DAL" code? That's an airport code for Love Field. Keep unchanged. Also "DFW". Keep unchanged. Also any other proper nouns like "Southwest Airlines", "Delta Air Lines", "Alaska Airlines". Those are brand names, keep unchanged? The instruction says keep city/airport names and codes unchanged. It doesn't explicitly say keep airline names unchanged, but likely they should stay as is because they are proper nouns. However, we could translate them? The instruction: "Keep city/airport names and codes unchanged." It doesn't say to keep airline names unchanged. But natural translation might keep airline names as they are (they are proper nouns). Usually you keep brand names unchanged. So we will keep them as is. We need to translate the rest: "We pick up at every Granbury-area address — ZIPs 76048 (Granbury proper, the historic square, Pecan Plantation, Decordova Bend, the east side of Lake Granbury, Acton, Mambrino) and 76049 (Hudson Oaks, the I-20 service-road corridor, Tolar direction, Cresson edge). We also serve Acton, Cresson, Lipan, Mambrino, Pecan Plantation, Rainbow, Stockton Bend, Tolar, and the broader Hood County and Lake Granbury area on the same flat rate — just enter your exact pickup address at booking. The corridor is well balanced: about 49% of our trips go Granbury→Love Field (outbound) and 48% go Love Field→Granbury (returning home), so we run the route in both directions all week." Second paragraph: "Airlines and gate clusters at Love Field (single main terminal, gates 1–20): Southwest Airlines — gates 1–15 (DAL is Southwest's main Dallas base; if you're flying Southwest out of the Dallas area, you're flying out of Love Field, not DFW). Delta Air Lines — gates 16–17. Alaska Airlines — gates 18–19. There is no separate international terminal at Love Field — international travelers connect through DFW instead. Tell us your airline at booking and we'll drop curbside at the door closest to your gate cluster, so you skip a 5-minute terminal walk with luggage." We need to translate to Latin American Spanish. Use natural phrasing. Let's translate sentence by sentence, preserving tags. First

: Original:

We pick up at every Granbury-area address — ZIPs 76048 (Granbury proper, the historic square, Pecan Plantation, Decordova Bend, the east side of Lake Granbury, Acton, Mambrino) and 76049 (Hudson Oaks, the I-20 service-road corridor, Tolar direction, Cresson edge). We also serve Acton, Cresson, Lipan, Mambrino, Pecan Plantation, Rainbow, Stockton Bend, Tolar, and the broader Hood County and Lake Granbury area on the same flat rate — just enter your exact pickup address at booking. The corridor is well balanced: about 49% of our trips go Granbury→Love Field (outbound) and 48% go Love Field→Granbury (returning home), so we run the route in both directions all week.

We need to keep tags:

,

, etc. Also keep — and → as they are HTML entities. We should keep them unchanged. Also keep parentheses and punctuation. We'll translate the text inside. "Ponemos a su disposición" or "Recogemos". Natural Latin American Spanish: "Recogemos en cualquier dirección de Granbury" maybe. Let's think. "We pick up at every Granbury-area address — ZIPs 76048 (Granbury proper, the historic square, Pecan Plantation, Decordova Bend, the east side of Lake Granbury, Acton, Mambrino) and 76049 (Hudson Oaks, the I-20 service-road corridor, Tolar direction, Cresson edge)." Could be "Recogemos en cualquier dirección de Granbury — códigos ZIP 76048 (Granbury propiamente dicha, la plaza histórica, Pecan Plantation, Decordova Bend, el lado este del lago Granbury, Acton, Mambrino) y 76049 (Hudson Oaks, el corredor de la carretera de servicio I-20, dirección Tolar, límite de Cresson)." But we need to keep "ZIPs" maybe translate as "códigos ZIP". However, the instruction says keep city/airport names and codes unchanged. It didn't say to keep "ZIPs" unchanged. But "ZIP" is a US postal code term; translating to "códigos ZIP" might be okay. However, they might expect to keep "ZIPs" as is because it's part of the address format. The instruction only mentions city/airport names and codes unchanged. So we can translate "ZIPs" to "códigos ZIP". But we need to be careful: The original text: "ZIPs 76048 (Granbury proper, the historic square, Pecan Plantation, Decordova Bend, the east side of Lake Granbury, Acton, Mambrino) and 76049 (Hudson Oaks, the I-20 service-road corridor, Tolar direction, Cresson edge)." If we translate "ZIPs" to "códigos ZIP", we need to keep the HTML tags around the numbers. So we would have: "códigos ZIP 76048 (Granbury proper, ... ) y 76049 (Hudson Oaks, ...)". However, the original had "ZIPs" plural. In Spanish, we could say "códigos ZIP". That seems natural. But maybe better to keep "ZIPs" as is, because it's a term used in US addresses and many Spanish speakers understand it. However, the instruction didn't require keeping it unchanged. I'd lean to keep "ZIPs" unchanged to avoid altering something that might be considered a code? But it's not a city/airport code. It's a postal code label. The instruction only mentions city/airport names and codes unchanged. So we can translate it. But we need to ensure natural Latin American Spanish. Many Latin American countries use "código postal". Using "ZIP" is understandable but might be less natural. I think "códigos ZIP" is okay. Let's decide: We'll translate "ZIPs" to "códigos ZIP". Keep the strong tags around numbers. Now "We also serve Acton, Cresson, Lipan, Mambrino, Pecan Plantation, Rainbow, Stockton Bend, Tolar, and the broader Hood County and Lake Granbury area on the same flat rate — just enter your exact pickup address at booking." Translate: "También atendemos Acton, Cresson, Lipan, Mambrino, Pecan Plantation, Rainbow, Stockton Bend, Tolar y el área más amplia del condado de Hood y del lago Granbury con la misma tarifa plana — solo ingrese su dirección exacta de recogida al hacer la reserva." Need to keep "the broader Hood County and Lake Granbury area". Could translate as "el área más amplia del condado de Hood y del lago Granbury". Keep "Hood County" maybe translate as "condado de Hood". Keep "Lake Granbury" as "lago Granbury". The area: "el área más amplia del condado de Hood y del lago Granbury". Or "el área más amplia del condado de Hood y del lago Granbury". Good. Now "The corridor is well balanced: about 49% of our trips go Granbury→Love Field (outbound) and 48% go Love Field→Granbury (returning home), so we run the route in both directions all week." Translate: "El corredor está bien equilibrado: aproximadamente el 49% de nuestros viajes van de Granbury a Love Field

Contexto de precios: Tarifas del shuttle Granbury a Love Field

El precio es tarifa fija puerta a puerta: el precio que ves al reservar es el total, sin recargos, sin cargos por minuto de tráfico, sin tarifa de acceso al aeropuerto agregada al final. Según nuestros 249 viajes más recientes completados entre Granbury↔Love Field:

• Sedán de cuatro puertas (1–3 pasajeros) — alrededor del 97% de las reservas en este corredor. Las tarifas reales de ida del sedán han variado entre $86 y $223, normalmente entre $149 y We need to translate the HTML content into natural Latin American Spanish for travelers, preserving HTML tags, city/airport names, codes, phone numbers, URLs unchanged. Return only translated HTML. We have a snippet:
• Shuttle van (7–14 passengers) — typically $310–$540 one-way depending on group size and luggage. Most common for Lake Granbury wedding parties heading to DAL, Southwest Companion Pass families flying together, corporate retreats, and large family vacations using Southwest as the outbound carrier.

The quoted fare includes the Love Field curbside access, tolls, fuel, standard driver gratuity, luggage handling, child seats when requested at booking, and meet-and-greet on the return leg. There is no surge pricing during Southwest's peak Friday-evening and Sunday-return banks, holiday weekends, lake weekends, or weather events — a 3:30 AM Granbury pickup costs the same as a 3:30 PM Granbury pickup. Booking the return at the same time as the outbound triggers a 10% round-trip discount using promo code ONLINE at checkout, which is meaningful on this corridor because the round-trip pattern is so common.

Travel Tips: Granbury to Love Field (DAL)

• Plan 90 minutes before a Southwest domestic departure. Love Field TSA lines are usually shorter than DFW (the terminal is smaller and the passenger volume lower), but Southwest's Friday-afternoon and Sunday-evening banks fill the security checkpoint and bag-drop quickly. Allow 2 hours during summer leisure peaks. We dispatch drivers to arrive 15 minutes early as standard.
We need to translate to Latin American Spanish (natural). Keep HTML tags unchanged, but translate text inside tags and any plain text. We must preserve entities like – and — etc. Should keep them unchanged as they are part of HTML. Also preserve apostrophe escaped: Southwest's -> keep. We need to translate phrases like "Shuttle van (7–14 passengers)" -> "Van shuttle (7–14 pasajeros)"? Actually "Shuttle van" is a type; natural Spanish could be "Van de transporte" or "Van shuttle". Usually "Van de transporte (7–14 pasajeros)" or "Van de traslado (7–14 pasajeros)". Keep the parentheses and numbers. "typically $310–$540 one-way depending on group size and luggage." -> "por lo general $310–$540 ida, dependiendo del tamaño del grupo y el equipaje." "Most common for Lake Granbury wedding parties heading to DAL, Southwest Companion Pass families flying together, corporate retreats, and large family vacations using Southwest as the outbound carrier." -> "Lo utilizan con frecuencia las bodas en el Lago Granbury que van al aeropuerto DAL, familias con el Companion Pass de Southwest que vuelan juntas, retiros corporativos y grandes vacaciones familiares que usan Southwest como aerolínea de ida." But keep "Lake Granbury", "DAL", "Southwest Companion Pass", etc unchanged. Need to keep the dash entity — etc. We'll produce translation preserving HTML tags. Check each piece. Original snippet:
• Shuttle van (7–14 passengers) — typically $310–$540 one-way depending on group size and luggage. Most common for Lake Granbury wedding parties heading to DAL, Southwest Companion Pass families flying together, corporate retreats, and large family vacations using Southwest as the outbound carrier.

The quoted fare includes the Love Field curbside access, tolls, fuel, standard driver gratuity, luggage handling, child seats when requested at booking, and meet-and-greet on the return leg. There is no surge pricing during Southwest's peak Friday-evening and Sunday-return banks, holiday weekends, lake weekends, or weather events — a 3:30 AM Granbury pickup costs the same as a 3:30 PM Granbury pickup. Booking the return at the same time as the outbound triggers a 10% round-trip discount using promo code ONLINE at checkout, which is meaningful on this corridor because the round-trip pattern is so common.

Travel Tips: Granbury to Love Field (DAL)

• Plan 90 minutes before a Southwest domestic departure. Love Field TSA lines are usually shorter than DFW (the terminal is smaller and the passenger volume lower), but Southwest's Friday-afternoon and Sunday-evening banks fill the security checkpoint and bag-drop quickly. Allow 2 hours during summer leisure peaks. We dispatch drivers to arrive 15 minutes early as standard.
We need to keep tags:
• ,
,

,

,

,

,

,

,
• ,
, etc. Inside tags we need to translate the content but keep the tags. Also inside ONLINE keep ONLINE unchanged. Let's translate piece by piece. First
• Shuttle van (7–14 passengers) — typically $310–$540 one-way depending on group size and luggage. Most common for Lake Granbury wedding parties heading to DAL, Southwest Companion Pass families flying together, corporate retreats, and large family vacations using Southwest as the outbound carrier.
Translate: Shuttle van (7–14 passengers) -> Van de traslado (7–14 pasajeros) or "Van shuttle". Let's use "Van de traslado". Keep parentheses and –. Then after we have — (em dash). Keep. Then "typically $310–$540 one-way depending on group size and luggage." -> translate: "por lo general $310–$540 ida, dependiendo del tamaño del grupo y el equipaje." Make sure to keep the $ signs and numbers. Then space then "Most common for Lake Granbury wedding parties heading to DAL, Southwest Companion Pass families flying together, corporate retreats, and large family vacations using Southwest as the outbound carrier." -> translate: "Lo utilizan con frecuencia las bodas en el Lago Granbury que van al aeropuerto DAL, familias con el Companion Pass de Southwest que vuelan juntas, retiros corporativos y grandes vacaciones familiares que usan Southwest como aerolínea de ida." Check: "Lake Granbury" unchanged; "DAL" unchanged; "Southwest Companion Pass" unchanged; "Southwest" unchanged. Now after we have

...

Travel Tips: Granbury to Love Field (DAL)

etc. We need to translate the

content. Original

The quoted fare includes the Love Field curbside access, tolls, fuel, standard driver gratuity, luggage handling, child seats when requested at booking, and meet-and-greet on the return leg. There is no surge pricing during Southwest's peak Friday-evening and Sunday-return banks, holiday weekends, lake weekends, or weather events — a 3:30 AM Granbury pickup costs the same as a 3:30 PM Granbury pickup. Booking the return at the same time as the outbound triggers a 10% round-trip discount using promo code ONLINE at checkout, which is meaningful on this corridor because the round-trip pattern is so common.

Translate: "The quoted fare includes the Love Field curbside access, tolls, fuel, standard driver gratuity, luggage handling, child seats when requested at booking, and meet-and-greet on the return leg." -> "La tarifa incluida incluye el acceso en la acera de Love Field, peajes, combustible, propina estándar al conductor, manejo de equipaje, asientos para niños cuando se solicitan al reservar, y el servicio de recibimiento y acompañamiento en el tramo de regreso." Check: "Love Field curbside access" -> "acceso en la acera de Love Field". Could also be "acceso desde la acera de Love Field". Keep "Love Field". Keep "curbside". Use "acceso en la acera". "tolls" -> "peajes". "fuel" -> "combustible". "standard driver gratuity" -> "propina estándar al conductor". "luggage handling" -> "manejo de equipaje". "child seats when requested at booking" -> "asientos para niños cuando se solicitan al reservar". "meet-and-greet on the return leg" -> "servicio de recibimiento y acompañamiento en el tramo de regreso". Might be "servicio de encuentro y saludo". "meet-and-greet" commonly translates as "servicio de recibimiento". We'll keep natural. Next sentence: "There is no surge pricing during We need to translate the given HTML from English to natural, native Latin American Spanish, preserving all HTML tags exactly. The input is a series of
• elements with content including strong tags, etc. We must translate the textual content, but keep tags unchanged. Keep city/airport names and codes unchanged, phone numbers and URLs unchanged (none in the snippet). Must output only the translated HTML. We need to ensure proper Spanish for Latin America, natural tone. Keep tags:
• , , ↔ maybe it's an entity? Should remain unchanged. Let's translate each piece: First
• : Original:
• This is an overwhelmingly morning corridor. Across our 249 completed Granbury↔Love Field trips, 61% of pickups are between 3 AM and 9 AM (Southwest's morning bank out of DAL) and another 25% are midday 10 AM–3 PM — about 78% before 10 AM. We've handled zero pickups after 4 PM on this corridor in the recent dataset, which means very early-morning rides are common and we're sized for them.
Translate: "This is an overwhelmingly morning corridor." -> "Este es un corredor predominantemente matutino." Natural Latin American Spanish: maybe "Este es un corredor fuertemente matutino." Could also say "Este corredor es muy matutino." Keep strong tag. "Across our 249 completed Granbury↔Love Field trips" -> "En nuestras 249 trips completadas Granbury↔Love Field". Need to keep entity ↔ as is. So: "En nuestras 249 viajes completados Granbury↔Love Field". Better: "En nuestras 249 viajes completados Granbury↔Love Field". Could say "En nuestras 249 viajes completados Granbury↔Love Field". Or "En nuestras 249 viajes completados Granbury↔Love Field". Keep the entity. "61% of pickups are between 3 AM and 9 AM" -> "61% de los recogidas son entre las 3 a.m. y las 9 a.m." In Latin America, "recogidas" maybe "pickups". Better: "el 61% de las recogidas ocurre entre las 3 a.m. y las 9 a.m." Or "61% de los pickups son entre 3 a.m. y 9 a.m." Keep strong. "(Southwest's morning bank out of DAL)" -> "(el banco matutino de Southwest saliendo de DAL)". Keep apostrophe entity ' as is. So "(el banco matutino de Southwest's out of DAL)"? Actually the entity ' is inside the phrase: Southwest's. Must keep that exactly. So we keep "Southwest's". So translation: "(el banco matutino de Southwest's saliendo de DAL)". Could keep parentheses. "and another 25% are midday 10 AM–3 PM" -> "y otro 25% son al mediodía de 10 a.m. a 3 p.m.". Keep – entity. So: "y otro 25% son al mediodía 10 AM–3 PM". But we need to translate AM/PM? Usually keep as is? The instruction says keep city/airport names and codes unchanged, phone numbers and URLs unchanged. It doesn't say to keep time format unchanged, but we can translate to Spanish style: "10 a.m. y 3 p.m." Might keep the AM/PM as is? For natural Latin American Spanish, we would say "de 10 a.m. a 3 p.m." Keep the – entity. So: "y otro 25% son al mediodía de 10 a.m.–3 p.m.". "about 78% before 10 AM." -> "aproximadamente 78% antes de las 10 a.m.." "We've handled zero pickups after 4 PM on this corridor in the recent dataset, which means very early-morning rides are common and we're sized for them." -> "No hemos tenido ninguna recogida después de las 4 p.m. en este corredor en el conjunto de datos reciente, lo que significa que los viajes muy tempranos son comunes y estamos preparados para ellos." Keep ' entity inside We've? Actually "We've" includes '. Must keep that exactly. So we need to keep "We've". So we cannot change that to "No hemos". Because the tag includes the entity. So we must keep "We've" unchanged. So we need to translate the rest but keep "We've". So: "We've tenido cero pickups después de las 4 p.m. en este corredor en el conjunto de datos reciente, lo que significa que los viajes muy temprano son comunes y estamos dimensionados para ellos." But we need to keep the entity ' exactly as is. So we keep "We've". The rest can be translated. Thus final first
• :
• Este es un corredor predominantemente matutino. En nuestras 249 viajes completados Granbury↔Love Field, 61% de las recogidas son entre las 3 a.m. y las 9 a.m. (el banco matutino de Southwest's saliendo de DAL) y otro 25% son al mediodía de 10 a.m.–3 p.m. — aproximadamente 78% antes de las 10 a.m.. We've tenido cero pickups después de las 4 p.m. en este corredor en el conjunto de datos reciente, lo que significa que los viajes muy temprano son comunes y estamos dimensionados para ellos.
Check punctuation: We kept em dash as — original had — after 3 PM — about. In Spanish we used " — " but we should keep the entity — unchanged. So we need to keep — exactly. So replace the dash with —. So: "...3 p.m.—aproximadamente 78% antes de las 10 a.m.." Keep the entity. Thus: "y otro 25% son al mediodía de 10 a.m.–3 p.m.—aproximadamente 78% antes de las 10 a.m.." Now second
• : Original:
• Friday is the busiest day. 44 of our 249 corridor trips (18%) ran on a Friday, with Monday and Wednesday close behind. Saturday is the lightest day (24 trips, 10%). Booking a Friday pre-dawn pickup more than 24 hours in advance is strongly recommended — lake-weekend leisure traffic out of Granbury fills capacity quickly.
Translate: "Friday is the busiest day." -> "El viernes es el día más ocupado." "44 of our 249 corridor trips (18%) ran on a Friday, with Monday and Wednesday close behind." -> "44 de nuestros 249 viajes del corredor (18%) ocurrieron un viernes, con lunes y miércoles cerca detrás." Could say "lunes y miércoles le siguen de cerca." Natural Latin American Spanish: "lunes y miércoles le siguen de cerca." Keep parentheses. "Saturday is the lightest day (24 trips, 10%)." -> "El sábado es el día menos activo (24 viajes, 10%)." "Booking a Friday pre-dawn pickup more than 24 hours in advance is strongly recommended — lake-weekend leisure traffic out of Granbury fills capacity quickly." -> "Se recomienda encarecidamente reservar una recogida previa al amanecer los viernes con más de 24 horas de antelación — el tráfico de ocio de fin de semana alrededor del lago saliendo de Granbury llena rápidamente la capacidad." Need to keep — entity. Also keep "lake-weekend" maybe translate as "finde de semana del lago"? The phrase "lake-weekend leisure traffic out of Granbury" maybe "tráfico de ocio de fin de semana del lago fuera de Granbury". Keep as natural. Thus second
• :
• El viernes es el día más ocupado. 44 de nuestros 249 viajes del corredor (18%) ocurrieron un viernes, con lunes y miércoles le siguen de cerca. El sábado es el día menos activo ( We need to translate the given HTML content from English to natural Latin American Spanish for travelers. Must 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 must translate the visible text inside tags, but not modify any tags themselves (like
• , , tags etc). Also keep URLs unchanged: Granbury to DFW shuttle. Title attribute text also should be translated? The instruction says keep URLs unchanged; does not explicitly say to keep title attribute unchanged. The title attribute is part of HTML; we likely need to keep it unchanged? The title attribute is part of the HTML, not a URL. However they said "Keep ALL HTML tags exactly as-is." That means the tags themselves, including attribute names and values? The title attribute's value is part of the tag. The instruction "Keep ALL HTML tags exactly as-is." Means we cannot modify any part of the tag, including attributes and their values? Typically, when they say keep HTML tags exactly as-is, they mean you should not alter the tags themselves, but you can translate the content inside tags (text nodes). However attributes like href and title are part of the tag; modifying them would change the tag. To be safe, we should leave the entire tag unchanged, i.e., not modify any characters inside <...>. That includes href and title values. So we should not translate the title attribute; we keep it exactly as given. Thus we need to translate the text content inside each
• element, but not inside tags. Let's examine each
• . First
• :
• Southwest Boarding Position A check-in. If you're flying Southwest and want an A-group boarding position without paying for EarlyBird, check in exactly 24 hours before your departure — set a phone alarm before your pickup. We can drop at the gate cluster (Concourse gates 1–15) closest to your boarding door once you know it.
We need to translate the text outside of and other tags. Inside we have "Southwest Boarding Position A check-in." That's inside tags, so we must not translate that? According to "Keep ALL HTML tags exactly as-is." The tag is a tag, but its content is text inside the tag. Does "tags exactly as-is" include the content? Usually they mean you should not alter the tags themselves, but you can translate the text content. However they might also consider the content as part of the tag? The phrase "Keep ALL HTML tags exactly as-is." could be interpreted as you should not change any part of the markup, i.e., the tags themselves, but you can change the text between tags. However they also said "Keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged." They didn't mention to keep other proper nouns unchanged. So we should translate the content, including inside , unless it's a city/airport name or code. "Southwest Boarding Position A check-in." is not a city/airport name/code, it's a phrase describing a service; we likely need to translate it. But if we translate inside , we would be altering the content of a tag, but the tag itself (...) remains unchanged except its inner text. That's allowed per typical instruction. So we should translate the inner text. Thus we need to translate the visible text, preserving entities like ' (apostrophe) and — (em dash) and – (en dash). Those are HTML entities; we should keep them unchanged as they are part of the text. We'll translate the surrounding words but keep the entities. Let's translate each sentence to natural Latin American Spanish. First
• content: Original: Southwest Boarding Position A check-in. If you're flying Southwest and want an A-group boarding position without paying for EarlyBird, check in exactly 24 hours before your departure — set a phone alarm before your pickup. We can drop at the gate cluster (Concourse gates 1–15) closest to your boarding door once you know it. We need to translate to Spanish, preserving entities. Let's break down. - Southwest Boarding Position A check-in. => translate to something like "Registro de posición de embarque A de Southwest." But we need natural Latin American Spanish. "Check-in" could be "registro de llegada" or "facturación". In context of boarding position, maybe "registro de posición de embarque A". Another option: "Posición de embarque A de Southwest: registro." But we need to keep the meaning: "Southwest Boarding Position A check-in." I'd translate as "Registro de posición de embarque A de Southwest." That sounds okay. But maybe "Southwest Boarding Position A check-in." is a heading. Could be "Registro de facturación para posición de embarque A de Southwest." Hmm. Let's think: The service is about checking in to get an A boarding position without paying for EarlyBird. So "Southwest Boarding Position A check-in." could be interpreted as "Registro para obtener la posición de embarque A de Southwest." I'd go with "Registro para posición de embarque A de Southwest." That is concise. Now the rest: "If you're flying Southwest and want an A-group boarding position without paying for EarlyBird, check in exactly 24 hours before your departure — set a phone alarm before your pickup." Translate: "Si vuelas con Southwest y deseas una posición de embarque del grupo A sin pagar por EarlyBird, factura exactamente 24 horas antes de tu salida — configura una alarma en tu teléfono antes del recogido." But need natural Latin American Spanish. Use "facturar" for check-in (airline). Could also be "hacer el check-in". In Latin America, "facturar" is used for checking bags, but check-in for flight is often "hacer el check-in" or "registrarse". However "check-in" as a verb is often used as "hacer el check-in". I'd use "hacer el check-in". But we need to keep the entity ' which is apostrophe in "you're". We'll keep that as is. So "Si vuelas con Southwest y quieres una posición de embarque del grupo A sin pagar por EarlyBird, haz el check-in exactamente 24 horas antes de tu salida — pon una alarma en tu teléfono antes del recogido." But "pickup" refers to the shuttle pickup. Could be "antes de tu recogida". Use "recogida". So "antes de tu recogida." Now next sentence: "We can drop at the gate cluster (Concourse gates 1–15) closest to your boarding door once you know it." Translate: "Podemos dejarte en el grupo de puertas (puertas del concurso 1–15) más cercano a tu puerta de embarque una vez que sepas cuál es." But "gate cluster" maybe "conjunto de puertas". "Concourse gates 1–15" is a proper name? It's a designation; we should keep the numbers and the dash entity. The phrase "Concourse gates 1–15" maybe we should keep as is? The instruction says keep city/airport names and codes unchanged; this is not a city/airport name/code, but it's a specific gate designation. Might be okay to translate "Concourse gates" to "puertas del concourse". However "Concourse" is a term used in airports; maybe keep as "Concourse". Safer to keep the phrase exactly as is? The instruction: "Keep ALL HTML tags exactly as-is." Not about translating terms inside text. They didn't say to keep terms like "Concourse gates". So we can translate. But to be safe, we could keep "Concourse gates 1–15" unchanged because it's a specific label. However they said keep city/airport names and codes unchanged; this is not that. I'd translate to natural Spanish: "el grupo de puertas (puertas del concourse 1–15)". But "Concourse" maybe keep as is because it's a proper term; but we can translate "concourse" to "muelle" or "pasillo". In Latin American Spanish, "concourse" is often used as "concourse" or "muelle". I'd keep "Concourse gates 1–15" unchanged to avoid altering proper naming. However they didn't explicitly require that. But I'd lean to keep it unchanged because it's a specific designation like a gate number range. Let's check the original: "(Concourse gates 1–15)". If we translate to "(puertas del concourse 1–15)" we changed "Concourse gates" to "puertas del concourse". That's a translation but still retains the entity. Might We need to translate English text to natural Latin American Spanish, preserving HTML tags exactly, preserving city/airport names and codes (like Weatherford, Granbury, Love Field, DAL, Mid-Cities, Dallas, Texas, etc.). Also preserve phone numbers and URLs unchanged. We need to output only the translated HTML. Let's parse the source:
• Coming from a different city in the area? If your pickup is in Weatherford instead of Granbury, see our Weatherford to Love Field shuttle page. If you're in the Mid-Cities or Dallas, browse our full Dallas Love Field shuttle hub for all corridor-specific pages.
Then second
• :
• Round-trip vs one-way. Because the Granbury↔Love Field round-trip pattern is so common (Southwest weekend leisure travel home from DAL Sunday night), the 10% promo code ONLINE round-trip discount typically more than covers the airport tip on the outbound leg.

Book Your Ride Today

To ensure a smooth and comfortable journey, please book your shuttle service in advance by calling (817) 403-6196 or booking online. Use promo code ONLINE for a 10% discount on round trips!

We need to translate only the text content inside tags, leaving tags and attributes unchanged. Also need to translate the inner text of , tags? Keep the link text inside but it should be translated as well, as it's text content. Keep the href and title unchanged. Also note the ' entity in "you're" – we need to preserve it as is? The instruction: Keep HTML tags exactly as-is; they didn't say to preserve entities, but it's part of the content. Probably we should keep ' as is, but we could translate "you're" to "eres" or "estás". The entity ' is just an apostrophe; we can translate the word and keep the apostrophe as a regular character, but we need to preserve the entity? Safer to keep the entity as is; but if we translate the word, we will need to replace "you're" with something like "estás" (without apostrophe) but the entity would be gone. The instruction: "Keep ALL HTML tags exactly as-is." The entity is not a tag, it's an HTML entity. It might be considered part of the text. Not explicitly said to preserve. I'd keep it as is but translate the surrounding text? Might be safer to keep the entity and translate the word around it? Actually "you're" is "you're". If we translate to "estás", we would lose the apostrophe. Could we keep the entity and just translate "you" part? Not needed. I think we can replace the whole "you're" with "estás" and keep the apostrophe as a regular apostrophe ('). But that changes the entity. However, the entity is just a way to encode apostrophe; using a regular apostrophe is fine in HTML. Probably acceptable. The instruction didn't forbid changing entities. I'd just translate naturally. Now translate each sentence. First

content: Coming from a different city in the area? If your pickup is in Weatherford instead of Granbury, see our Weatherford to Love Field shuttle page. If you're in the Mid-Cities or Dallas, browse our full Dallas Love Field shuttle hub for all corridor-specific pages. Translate to Latin American Spanish natural for travelers. "Coming from a different city in the area?" => "¿Vienes de otra ciudad de la zona?" or "¿Vienes de otra ciudad cercana?" Natural: "¿Vienes de otra ciudad de la zona?" Keep the strong tags. "If your pickup is in Weatherford instead of Granbury, see our ..." => "Si tu recogida es en Weatherford en lugar de Granbury, consulta nuestra..." Use "recogida" or "servicio de traslado". For shuttle pickup maybe "si tu servicio de traslado es en Weatherford en lugar de Granbury". But "pickup" is location where you get picked up. Could say "Si tu punto de recogida está en Weatherford en lugar de Granbury". Use "puntode recogida". Keep "Weatherford" and "Granbury" unchanged. "see our Weatherford to Love Field shuttle page." => "mira nuestra página del traslado Weatherford a Love Field." Keep the link text translated: "Weatherford to Love Field shuttle" => "traslado de Weatherford a Love Field". But maybe "traslado Weatherford a Love Field". Keep natural. "If you're in the Mid-Cities or Dallas, browse our full Dallas Love Field shuttle hub for all corridor-specific pages." => "Si estás en el área de Mid-Cities o Dallas, explora nuestro centro completo del traslado Dallas Love Field para todas las páginas específicas del corredor." Use "área de Mid-Cities". Could be "si estás en Mid-Cities o Dallas". Keep "Mid-Cities". Use "explora" or "navega". "browse our full ... hub" => "explora nuestro completo centro". Keep translation. Second

: Round-trip vs one-way. Because the Granbury↔Love Field round-trip pattern is so common (Southwest weekend leisure travel home from DAL Sunday night), the 10% promo code ONLINE round-trip discount typically more than covers the airport tip on the outbound leg. Translate: "Round-trip vs one-way." => "Ida y vuelta vs. solo ida." Or "Round-trip versus ida sola." Natural: "Ida y vuelta vs. solo ida." "Because the Granbury↔Love Field round-trip pattern is so common (Southwest weekend leisure travel home from DAL Sunday night), the 10% promo code ONLINE round-trip discount typically more than covers the airport tip on the outbound leg." We need to keep the entity ↔ (which is a double-headed arrow?). It's an HTML entity representing a left-right arrow? We'll keep it as is. Translate: "Debido a que el patrón de ida y vuelta Granbury↔Love Field es tan común (viajes de fin de semana de Southwest para regresar a casa desde DAL domingo por la noche), el descuento de ida y vuelta del código promocional ONLINE del 10% generalmente cubre más que la propina del aeropuerto en el tramo de ida." Make sure to keep "DAL" unchanged. "Southwest" maybe keep as is (airline name). Could translate "viajes de fin de semana de Southwest". Keep "Southwest". Good. Now after

we keep comment unchanged. Then

Book Your Ride Today

=> translate to "

Reserva tu viaje hoy

" or "

Reserva tu traslado hoy

" Since "Ride" could be "viaje". For shuttle service maybe "Reserva tu traslado hoy". Use "Reserva tu viaje hoy". Natural.

To ensure a smooth and comfortable journey, please book your shuttle service in advance by calling (817) 403-6196 or booking online. Use promo code ONLINE for a 10% discount on round trips!

Translate: "Para asegurar un viaje tranquilo y cómodo, reserva tu servicio de traslado con antelación llamando al (817) 403-6196 o reservando en línea. Usa el código promocional ONLINE para obtener un 10% de descuento en viajes de ida y vuelta." Check keep phone number unchanged inside . Keep the parentheses. Now ensure we keep HTML tags exactly. Need to preserve original tag names and attributes. Let's construct final HTML:

¿Vienes de otra ciudad de la zona? Si tu punto de recogida está en Weatherford en lugar de Granbury, consulta nuestra traslado de Weatherford a Love Field página. Si estás en