- Add the missing "Contenido Markdown" section
- Standardize the "Get Started" button translation from "Iniciar" to "Comenzar".
- Fix terminology by replacing incorrect translations like "funciones" with "características" and adding missing accents.
- Translate example image paths in the frontmatter code block (e.g., `/icono-de-caracteristica-genial.svg`).
- Fix Portuguese remnants (changing "ou" to "o" in the comments).
- Improve technical phrasing (e.g., using "sobrescribiendo" instead of "anulando").
- Update code examples to match current configurations in `docs/es/config.ts` and `default-theme-carbon-ads.md`
- Add missing properties to TypeScript interfaces
- Add missing documentation sections for the `skipToContentLabel` option and the `useLayout` composable.
- Fix incorrect vocabulary and Portuguese remnants
- Translate the term "Badge" to "Insignia".
- Translate English placeholder text in the code blocks and examples (e.g., "Title" to "Título", "default" to "predeterminado", "custom element" to "elemento personalizado").
- Fix grammatical errors and improve natural phrasing (e.g., changing "anulando" to "sobrescribiendo", and fixing the capitalization of "Los siguientes").
- Capitalize "Hijos" in the "Personalizar Hijos" heading.
- Clarify "propiedades" by appending "(props)"
- Add the missing accent to "Pública" in the "Ruta Base Pública" heading and its corresponding reference link.
- Correct the capitalization of "Github" to the official "GitHub".
- Translate the lingering English phrase "Follow the" to "Siga la" in the Azure deployment instructions.
- Translate the word "Output" to "Salida" in multiple sections. and "link" to "enlace"
- Fix the rendered output code blocks for highlighting and focusing by changing `// [!!code ...]` to `// [!code ...]`, accurately reflecting how the parsed syntax should look in the final output.
- Fix "title:" keyword
Change the Spanish translation of "Getting Started" from "Iniciando" to "Comenzar" in the sidebar configuration and document heading.
also, it maintains consistency in the rest of the translated documentation.
- Fix the broken Markdown link syntax for `srcDir` by adding the missing square brackets.
- Add the missing `#` to the `{#type-safe-loader-with-defineroutes}` heading anchor so the link resolves correctly.
- Translate directory structure examples and file names to match the Spanish version (e.g., `guide` to `guia`, `pure.html` to `puro.html`).
- Translate remaining English link texts (e.g., "Link to" to "Enlace para").
- Update Wikipedia links to point to the Spanish Wikipedia (`es.wikipedia.org`).
- Improve technical terminology by changing "Desempeño" to "Rendimiento" and "destaque" to "resaltado".
- Fix a spelling error by changing "móbiles" to "móviles".
- Refine phrasing for better natural readability (e.g., "durante la compilación", "impulsa esta página").
- Add missing heading anchors (`{#script-and-style}` and `{#vs-code-intellisense-support}`).
- changing "exibido" to "mostrará", "hífen" to "guion", "embutido" to "integrado", "tags" to "etiquetas" and others
- Translate code block example variables(e.g., `count` to `contador`).
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`).
- 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/`).
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".
- 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.
- 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").
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").
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 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?).
- 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 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").
- 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
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 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.
jackestar
Divyansh Singh