Haz una reserva en línea 24/7
Airport Shuttle of Phoenix se creó en 2015 y ahora es una LLC con más de 100,000 clientes. Nuestra oficina principal está a 5 minutos del Aeropuerto Internacional Sky Harbor (PHX). Somos la única empresa de traslados que brinda servicio puerta a puerta a todo Arizona 24/7. Contamos con muchos conductores que viven en ciudades de todo el estado y con vehículos de la empresa.
Tanto la empresa como los conductores pasan por rigurosas verificaciones de antecedentes y requisitos de seguro para recoger a las personas en el aeropuerto. Disponemos de shuttles Mercedes para grupos grandes, SUV Lincoln Navigator y una variedad de sedanes de 4 puertas como el Lexus ES 300 Hybrid y los Lincoln MKZ Hybrid. Actualmente somos la segunda o tercera compañía de transporte aeroportuario más grande del Estado de Arizona.
Oficina principal
4600 E Washington St Suite 300
Phoenix, AZ 85034
Ganador del premio Travel and Hospitality 2018-2023
Testimonios y reseñas
We need to translate the visible text content (strings) from English to natural Latin American Spanish, preserving HTML tags exactly, leaving city/airport names, codes, phone numbers, URLs unchanged. We need to output only the translated HTML, no extra text.
The input HTML includes JavaScript and some text. We need to translate the user-visible strings: e.g., the content inside attributes like title, placeholder text, alt? Let's parse.
We have:
```
"yes" : "no",
n = screen.availHeight - 90,
r = 940;
return window.innerWidth < 1400 && (r = 620),
window.open(this.href, "shopperapproved", "location=" + e + ",scrollbars=yes,width=" + r + ",height=" + n + ",menubar=no,toolbar=no"),
o.stopPropagation && o.stopPropagation(),
!1;
```
The strings: "shopperapproved" is a window name; it's okay to keep unchanged as it's likely a variable. The phrase "location=" + e + ",scrollbars=yes,width=" + r + ",height=" + n + ",menubar=no,toolbar=no" includes "scrollbars=yes". "yes" inside might be considered part of the feature string; we should probably not translate. The instructions: keep city/airport names and codes unchanged. Keep phone numbers and URLs unchanged. For other text, we should translate. However, JavaScript strings like "shopperapproved" might be considered part of code; better to keep unchanged. Also "yes" inside scrollbars=yes is a feature flag; we should keep unchanged as it's part of the spec.
Later:
```
!function() {
for (var o = document.getElementsByClassName("shopperlink"), e = 0, n = o.length; e < n; e++)
o[e].onclick = openshopperapproved;
}();
```
Here class name "shopperlink" and function name openshopperapproved; keep unchanged.
Then:
```
var link = document.createElement('link');
link.rel = 'stylesheet';
link.type = 'text/css';
link.href = "//www.shopperapproved.com/seal/default.css";
document.getElementsByTagName('head')[0].appendChild(link);
```
URL unchanged.
Then after script closing:
```
Click here to read lots of excellent reviews by real customers.
``` We need to translate visible text: In the with title="Airport Shuttle of Phoenix Reviews": keep city name unchanged? It says "Airport Shuttle of Phoenix". Phoenix is a city name; keep unchanged. The title attribute: "Airport Shuttle of Phoenix Reviews". Should we translate? The instruction: Keep city/airport names and codes unchanged. It doesn't say to keep brand names unchanged. The phrase "Airport Shuttle of Phoenix Reviews" maybe we could translate to Spanish? It's a title attribute for the link; it's visible as tooltip. Usually we translate UI text. The instruction says keep city/airport names and codes unchanged; doesn't forbid translating other words. So we should translate "Reviews" to "Reseñas". Keep "Airport Shuttle of Phoenix" unchanged? Actually "Airport Shuttle of Phoenix" is a proper name maybe brand; but it's not a city/airport code; but it's a proper noun (brand). Safer to keep unchanged? The instruction only mentions city/airport names and codes unchanged, phone numbers and URLs unchanged. It doesn't explicitly say to keep brand names unchanged. However typical translation tasks keep proper nouns unchanged unless instructed otherwise. "Airport Shuttle of Phoenix" could be considered a brand name; I'd keep it unchanged to avoid altering a proper name. But "Reviews" is generic; we can translate. Thus title becomes "Airport Shuttle of Phoenix Reseñas". But maybe better to translate whole phrase: "Reseñas de Airport Shuttle de Phoenix". However we need to keep city name unchanged: Phoenix. So we could do "Reseñas de Airport Shuttle de Phoenix". That translates "Reviews" to "Reseñas" and "of" to "de". However "Airport Shuttle" might be brand; keep unchanged. So final title: "Reseñas de Airport Shuttle de Phoenix". We'll see. The link text: "Click here to read lots of excellent reviews by real customers." We need to translate "Click here" to "Haz clic aquí" (Latin American). The rest: " to read lots of excellent reviews by real customers." translate: " para leer muchas excelentes reseñas de clientes reales." Let's craft natural: "Haz clic aquí para leer muchas excelentes reseñas de clientes reales." We need to keep the with style color #000000 wrapping " to read lots of excellent reviews by real customers." We'll translate inside the span accordingly, but need to keep the span tags. So inside span we put the translated text (including leading space? The original had a space before "to". In HTML: Click here to read lots of excellent reviews by real customers.. So there is a space before "to". We'll replicate: after "Click here" we have the span with a leading space then translated text. So final: "Haz clic aquí para leer muchas excelentes reseñas de clientes reales." Now the form: We need to translate the link text "Check Rates" to Latin American Spanish: "Ver tarifas" or "Consultar tarifas". Common: "Ver tarifas". Title attribute: "Check Airport Shuttle Rates". Keep city/airport names unchanged? No city here. Could translate to "Consultar tarifas de Airport Shuttle". Keep "Airport Shuttle" unchanged as brand. So title: "Consultar tarifas de Airport Shuttle". Or "Ver tarifas de Airport Shuttle". We'll go with "Consultar tarifas de Airport Shuttle". Keep URL unchanged. Now any other visible text: The script may contain strings like "shopperapproved" as window name; we keep unchanged. Also "openshopperapproved" function name; unchanged. Potential other text: The string "location=" + e + ",scrollbars=yes,width=" + r + ",height=" + n + ",menubar=no,toolbar=no". The "yes" and "no" are feature flags; we should keep unchanged. The string "shopperapproved" as window name; keep unchanged. Also there is a string "shopperlink" class name; keep unchanged. The script also contains "location=" + e + ",scrollbars=yes,width=" + r + ",height=" + n + ",menubar=no,toolbar=no". We'll keep. Now also there is a string "yes" : "no", in the earlier code: It appears as part of a JSON-like object? Actually: ``` "yes" : "no", ``` We see? It appears at top: ``` "yes" : "no", n = screen.availHeight - 90, ``` That seems like part of some code; but it's likely a variable mapping? It's not visible to user; but it's a string literal "yes" and "no". Should we translate? Probably not; it's code. Safer to keep unchanged. Thus final HTML will have translation only in visible text: title attribute of first link, link text and inner span, and second link text and title attribute. Now ensure we keep all HTML tags exactly as-is. Let's rewrite the snippet with translations. Original snippet: ``` "yes" : "no", n = screen.availHeight - 90, r = 940; return window.innerWidth < 1400 && (r = 620), window.open(this.href, "shopperapproved", "location=" + e + ",scrollbars=yes,width=" + r + ",height=" + n + ",menubar=no,toolbar=no"), o.stopPropagation && o.stopPropagation(), !1; } !function() { for (var o = document.getElementsByClassName("shopperlink"), e = 0, n = o.length; e < n; e
