docs: updates and corrections for Spanish translation - #5307
Conversation
jackestar
changed the title
|
for every: By default, if there's no title, it displays the English title. Ideally, this could be configured in Now, this could be translated as a "patch" in other i8n versions, BUT first, I don't feel it's the right decision, and second, I'm not going to make that decision arbitrarily. I'm not looking for a purist Spanish translation either, just consistency with the english version.... |
|
Since there are no visible links to |
|
Is |
|
Yes, 'path' is better translated as 'ruta' in this context, I've actually used both..., later I'll review it to make it more consistent and only use 'ruta'. |
Change the Spanish translation of "Last Updated Timestamp" from "Sello temporal de actualización" to "Última actualización". The original translation doesn't make sense. "Última actualización" is the most general and natural, though "Actualizado por última vez el" or "Fecha de última actualización" might be more appropriate depending on the exact context.
Change the Spanish translation of "Markdown to beautiful docs in minutes" from "Markdown para obtener lindos documentos en minutos" to "Markdown en documentación atractiva en minutos". VitePress is focused on creating documentation, not documents (right?), so translating "docs" to "documentación" is more accurate. Additionally, replace "lindo" with "atractiva" as the former sounds too informal. Include minor orthographic corrections.
- Change "path" translation to "directorio". - Add the missing tip from the English version - Capitalize headings to match the English version (e.g., "El directorio público"). - Use "ubicación" instead of "localización" to avoid semantic ambiguity. - Fix markdown formatting for the `withBase` helper link. - Correct various spelling and syntax
replaced `Presente` to `Renderice`
Update the Spanish translation of the custom theme guide to align with the English version and correct grammatical errors. - Change the `useData()` explanation to clarify that the data is used to "conditionally" render layouts, matching the English context. - Add the missing documentation section for router event listeners (`onBeforeRouteChange`, `onAfterRouteChange`). - Update code block filenames (e.g., changing `.vitepress/theme/config.ts` to `.vitepress/config.ts`). - Fix various spelling and accentuation errors throughout the document (e.g., "raíz", "presencia", "definido", "fácil").
- Fix missing accents on words like "Compilación", "artículos", "extraído", and "implícitamente". - Improve translation naturalness by changing phrases like "apenas en el tiempo" to "solo en el tiempo" and "actualizaciones rápidas" to "actualizaciones en caliente". - Correct terminology mistakes, such as translating "timestamps" to "marca de tiempo" instead of "sellos se datos". - Update code block comments to use proper Spanish interrogative punctuation (adding "¡" and "¿").
Update the Spanish translation of the deployment guide to improve terminology, fix grammatical errors, and sync with the upstream English version. - Update GitLab interface references to use their Spanish equivalents (e.g., "Usar dominio único") since the GitLab UI, unlike GitHub, is natively available in Spanish. - Replace inaccurate translations like "implantar" and "build" with standard terminology like "desplegar" and "compilación". - Sync the GitHub Actions workflow with the English version (adding the VitePress cache step and updating Node.js versions). - Fix various typographical and grammatical errors (e.g., changing "em" to "en", "removera" to "removerá", "ou" to "o") (from PT translation maybe?).
…icial azure spanish documentation
…h translation Update the Spanish translation of the extending default theme guide to correct minor typos and update code examples. - Capitalize "Defecto" in the main heading. - Correct missing accents in words like "asegúrese", "raíz", "automáticamente", and "Aquí". - Fix typos, such as changing "componetes" to "componentes" and removing the incorrect accent on "substituidas". - Add the proper Spanish opening exclamation mark to "¡atención!". - Update the custom component import path to correctly point to `./theme/components/CustomNavBar.vue` in the overriding components example.
- Update the JSON frontmatter example translation from "Creando blog como un hacker" to "Blogueando como un hacker" for a more natural phrasing.
Update the Spanish getting started guide to sync with the English version and correct various grammatical issues. Specific changes include: - Add the Deno installation command snippet to the package managers list. - Add `vue` to the Yarn installation command snippet. - Update the ESM warning note to refer to "contextos de CJS asíncronos" instead of "JavaScript asíncronos". - Correct missing accents and misspellings (e.g., "Estructura", "raíz", "línea", "asegúrese", "explícitamente"). - Improve translation (e.g., changing "embutido" to "incluye", "build" to "compilación", "paths" to "rutas").
- Portuguese phrasing in the text ("documentação" to "documentación").
- translation of "merge" in a technical programming context by replacing "mezclar" with "fusionar" (e.g., "se fusionará", "fusionarlos").
…anslation - Fix incorrect code block syntax (e.g., mismatched backticks ````md) so the examples render correctly. - Add missing documentation sections for custom container attributes (`markdown-it-attrs`), VS Code regions, and header anchors. - Improve terminology by using "encabezado" (instead of "Header"), "anclaje" (instead of "anchor"), and "carga diferida" (instead of "lazy loading"). - Fix Markdown table alignment and spacing issues. - Sync code snippet examples to include line numbers (`md:line-numbers`) as in the English version. - Correct minor typos and orthographic errors.
Specific changes include: - Remove the unnecessary accent on "incluido". - Fix a mistranslation by changing "modelo de lenguaje" (language model) to "lenguaje de plantillas" (templating language). - Replace "Nungun manipulador de eventos será embutido" with the more accurate "No se adjuntarán controladores de eventos".
- Add missing documentation sections for `defineRoutes` type-safe loaders and watching template/data files. - Update file names in code block examples to match the Spanish translation (e.g., `getting-started.md` to `comenzar.md` and `guide/` to `guia/`).
from commit e558af6 PR vuejs#5315 from commit e21ffab PR vuejs#4758
…own.md in spanish docs
…translation
Specific changes include:
- Remove the `defineConfig` wrapper from the configuration examples to match the latest upstream conventions.
- Add the missing `{transformitems-hook}` anchor to the `transformItems` heading.
- Translate domain placeholders in the code blocks (e.g., `example.com` to `ejemplo.com`).
… with the upstream English documentation structure.
| --- | ||
|
|
||
| # Layout {#layout} | ||
| # Layout |
There was a problem hiding this comment.
keep hash if not removed at english version
There was a problem hiding this comment.
I don't understand... in the English version there are practically no anchors in any header; I removed it because it generates the same anchor. In that case, there are instances like docs/es/guide/deploy.md and docs/es/guide/frontmatter.md where the custom anchor isn't used for that reason, or is there a criterion I'm not taking into account?
There was a problem hiding this comment.
The english version doesn't have explicit anchors, but the translations need those ids explicitly in most cases. Better to be consistent through out the document IMO.
There was a problem hiding this comment.
🟡 Not ready to approve
Several updated Spanish docs examples/strings contain objective issues (invalid // [!!code ...] markers, mixed-language sentence fragments, and inconsistent default-label wording) that should be corrected before approval.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Review details
Comments suppressed due to low confidence (10)
docs/es/guide/markdown.md:452
- En este ejemplo de entrada se usa
// [!!code highlight], pero la sintaxis soportada por VitePress es// [!code highlight](un solo!). Con!!no se aplicará el resaltado.
msg: '¡Destacado!' // [!!code highlight]
docs/es/guide/markdown.md:484
- En este ejemplo de entrada se usa
// [!!code focus], pero la sintaxis soportada por VitePress es// [!code focus](un solo!).
msg: '¡Enfocado!' // [!!code focus]
docs/es/reference/default-theme-config.md:137
- Esta frase mezcla idiomas ("The configuración" / "menu item"). Debería estar completamente en español para evitar confusión.
The configuración del elemento del menu item. Más detalles en [Tema por defecto: Barra lateral](./default-theme-sidebar).
docs/es/guide/routing.md:18
- En los ejemplos de estructura de archivos se usan
guia/comenzar.mdy por extensión rutas/guia/.... En el resto de la documentación (incluyendo otras traducciones comodocs/pt/guide/routing.md:14) se mantieneguide/getting-started.md, lo que evita sugerir que VitePress requiere rutas localizadas especiales y mantiene consistencia entre locales.
├─ guia
│ ├─ comenzar.md
│ └─ index.md
├─ index.md
└─ prologo.md
docs/es/guide/routing.md:27
- Este bloque de salida HTML está basado en el ejemplo anterior con
/guia/...; si el ejemplo se mantiene consistente conguide/getting-started.md, también deberían actualizarse estas rutas para que coincidan.
index.md --> /index.html (accesible por /)
prologo.md --> /prologo.html
guia/index.md --> /guia/index.html (accesible por /guia/)
guia/comenzar.md --> /guia/comenzar.html
docs/es/guide/routing.md:93
- Los ejemplos de enlaces usan
./comenzary../guia/comenzar. Si se mantiene el ejemplo estándar de la guía (congetting-startedbajoguide/), estos enlaces deberían apuntar a./getting-startedy../guide/getting-started.
[Comenzar](./comenzar)
[Comenzar](../guia/comenzar)
<!-- No hacer -->
[Comenzar](./comenzar.md)
docs/es/guide/markdown.md:547
- En este ejemplo de entrada se usan
// [!!code error]y// [!!code warning], pero la sintaxis válida es con un solo!:// [!code error]/// [!code warning].
msg: 'Error', // [!!code error]
msg: 'Advertencia' // [!!code warning]
docs/es/reference/default-theme-edit-link.md:43
- Aquí se indica que el texto por defecto del enlace es "Edit this page" (inglés), pero en la UI en español y en el propio ejemplo se usa "Editar esta página". Conviene mantener la frase coherente con la localización.
De forma predeterminada, esto agregará el enlace con el texto "Edit this page" al final de la página de documentación. Puedes personalizar este texto configurando la opción `text`.
docs/es/reference/default-theme-home-page.md:120
- En este bloque YAML de ejemplo quedaron dos títulos en inglés ("Simple and minimal, always" / "Another cool feature") dentro de la documentación en español. Si la intención es mantener los placeholders traducidos, deberían estar en español como el resto del ejemplo.
title: Simple and minimal, always
details: Lorem ipsum...
- icon:
src: /icono-de-caracteristica-genial.svg
title: Another cool feature
docs/es/reference/cli.md:5
- En español, "Línea" lleva tilde. Para mantener la ortografía correcta en el encabezado principal, debería ser "Interfaz de Línea de Comando".
# Interfaz de Linea de Comando {#command-line-interface}
- Files reviewed: 26/26 changed files
- Comments generated: 0 new
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
|
github broke something in copilot review in today's release. expand "Review details" in the above comment to see if it flagged anything relevant. also the PR is showing merge conflicts for some reason even when there are none 🫠 |
- Add the missing accent to "línea" in `markdown.md` and `cli.md`.
- Translate a lingering English word ("The" to "La") in `default-theme-config.md`.
- Translate remaining English placeholder texts in `default-theme-home-page.md` and sync the hero text with the actual `config.ts` translation.
- change "tu" to "su" in `default-theme-last-updated.md`.
- Update the pagination terminology from "próximo" to "Siguiente" in `default-theme-layout.md`.
There was a problem hiding this comment.
🟡 Not ready to approve
It introduces a few concrete documentation correctness issues (notably broken internal links and contradictory footer licensing/copyright examples) that should be fixed before merging.
Once you've addressed the issues Copilot identified, you can request another Copilot review.
This review doesn't count toward merge requirements. Sign up for the private preview to control whether Copilot approvals count.
Review details
Suppressed comments (9)
docs/es/guide/routing.md:90
- Estos enlaces del ejemplo apuntan a rutas que no existen en la documentación en español (no hay
comenzar.mdni un directorioguia). Como el archivo real esgetting-started.mdbajodocs/es/guide/, el ejemplo debería enlazar a./getting-startedy../guide/getting-started.
[Comenzar](./comenzar)
[Comenzar](../guia/comenzar)
docs/es/reference/default-theme-config.md:137
- Esta frase mezcla idiomas ("menu item"). Sería mejor mantener la terminología completamente en español para evitar confusión.
La configuración del elemento del menu item. Más detalles en [Tema por defecto: Barra lateral](./default-theme-sidebar).
docs/es/guide/routing.md:94
- En el bloque "No hacer", las rutas de ejemplo también usan
comenzar/guia, que no existen. Para que el ejemplo sea coherente y navegable, deberían apuntar agetting-started.md/getting-started.html.
[Comenzar](./comenzar.md)
[Comenzar](./comenzar.html)
docs/es/guide/using-vue.md:202
- Concordancia: el sujeto es plural ("tokens"), pero el verbo está en singular ("se resalte").
Observe que esto puede impedir que ciertos tokens se resalte la sintaxis correctamente.
docs/es/reference/default-theme-footer.md:14
- El ejemplo mezcla "Liberado bajo la licencia MIT" con "Todos los derechos reservados", lo cual es contradictorio y difiere del ejemplo en inglés. Conviene mantener el texto equivalente a "Copyright © 2019-present" para evitar confusión legal/licenciamiento.
message: 'Liberado bajo la licencia MIT',
copyright: 'Todos los derechos reservados © 2019-PRESENTE Evan You'
docs/es/reference/default-theme-footer.md:37
- En el ejemplo con HTML ocurre la misma contradicción de licencia/copyright ("MIT" vs "Todos los derechos reservados"). Sería mejor conservar el mismo sentido que el ejemplo original ("Copyright © 2019-present").
message: 'Liberado bajo <a href="https://github.com/vuejs/vitepress/blob/main/LICENSE">Licencia MIT</a>.',
copyright: 'Todos los derechos reservados © 2019-PRESENTE <a href="https://github.com/yyx990803">Evan You</a>'
docs/es/reference/default-theme-home-page.md:138
- Error de concordancia: "de la características" debería ser singular (o plural coherente) en este comentario.
// Detalles de la características.
docs/es/reference/default-theme-config.md:213
- Concordancia de género/número: debería ser "todos los viewports".
Si desea deshabilitarlo para todas los viewports, debe usar `outline: false` en su lugar.
docs/es/reference/default-theme-config.md:390
- El placeholder de
placementestá traducido como "vinculación", que no refleja el sentido de "placement" (ubicación/colocación) en Carbon Ads; puede inducir a error al copiar el ejemplo.
placement: 'tu-vinculación-carbon',
- Files reviewed: 26/26 changed files
- Comments generated: 0 new
- Review effort level: Lite
We're testing this review assessment. Please use 👍 or 👎 to tell us if it's correct.
|
Okay, there are several instances where example directory structures are explained ( vitepress/docs/es/guide/routing.md Lines 12 to 19 in 0c7b85b vitepress/docs/en/guide/routing.md Lines 12 to 19 in 0c7b85b For example, "prologue" and "guide" are translated; naturally, i don't translate directories like "docs" or files like "index." vitepress/docs/es/guide/using-vue.md Lines 54 to 58 in 0c7b85b On the one hand, it makes it easier to read in Spanish, but at the end of the day, directory/file/variable names, etc., are conventionally in English... What I mean is that I need a clearer criterion for these "examples" cases, since I find both in the current version. |
|
/cc @userquin what do you think? IMO variables should remain in English, any inline comment should be translated. Regarding file names, I think the translations are fine if they are consistent throughout the page. Fixed names like index.md or config.ts are not translatable, though. |
- Add the missing "Componentes Personalizados" section - Fix Portuguese remnants - Correct spelling errors and missing accents .
- Update main title to "Enlaces anterior y siguiente" - Improve natural phrasing and readability in descriptions - Translate example strings and URL paths to Spanish - Correct grammar in the next section
- Fix spelling of "búsqueda" and improve phrasing - Add missing community search plugins to the list - Add clarification for `suggestedQuestions` in Ask AI - Refine translations for Algolia and Local Search
…tion - Add missing "Prefijo de Ruta" section - Translate URL paths and code examples to Spanish - Correct minor typos and improve grammar
- Fix Portuguese remnants in member titles - Update phrasing to use the formal "usted" tone - Revert improperly translated prop value to "medium" - Change "Amigos" to "Socios" in the partners section - Fix formatting for technical terms like "slots" - Correct spelling errors
- Add missing isHome section and outline example - Change header "descripción" to "description"
- Add missing `hash` and `onAfterPageLoad` properties - Add clarification for `page.headers` behavior - Add router event assignment code example - Fix Portuguese remnants - Correct technical terminology (e.g., "rebajas" to "Markdown")
- Fix Portuguese remnants and refine terminology - Translate new sections for page and directory-level overrides - Add missing `appearance` and `markdown` configuration options - Update build hooks examples and descriptions
…ig.ts`, `index.md` and `site-config.md`. And lang examples in `markdown.md`
- Add task lists, footnotes, and custom container nesting sections. - Add missing section for including code files - Update custom container attributes and GitHub-flavored alerts - Translate code examples, placeholders, and file paths to Spanish - Refine phrasing and correct minor translation errors
There was a problem hiding this comment.
this file can be deleted, it's not indexed.
Description
The main objective of this PR is to provide a complete, accurate, Spanish translation for the VitePress documentation.
Upon reviewing the current state of the translations, it became evident that practically every file required either corrections or significant updates to align with the latest English docs. Instead of opening ~38 separate PRs—which would be unproductive and difficult to manage for both reviewers and contributors—I have consolidated the translation updates into this single PR.
To ensure the review process remains manageable and to maintain a clean history, each modified file has its own separate commit.
Translation Terminology & Decisions
Following the precedent and discussions from PR #4352, I have established consistent criteria for handling technical terms to preserve context while ensuring natural readability in Spanish:
buildandpath. Additionally,helperhas been translated to auxiliar andhandlerto manejador, as they are perfectly understood in the Spanish development ecosystem.frontmatterand remain in English, as translating them often creates confusion and keeping the original terminology preserves better technical context.I'm still in the process of translating and updating (I'm not going to launch a PR with 38 modified files and >40 commits all at once, there needs to be feedback naturally)
Type of change
Please delete options that are not relevant.
Checklist
docs(es): ...).