php / php/doc-es

Formato y consistencia en la traducción / Format and consistency in translation

Open
#493 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

question
Dominant language
XML
Stars
33
Forks
63
Avg merge
1d 8h
Merged PRs (30d)
148

Description

Hola,

Quería abrir una conversación sobre dos puntos que he notado al revisar la documentación en español:

  • El formato no siempre está alineado con la versión en inglés (estructura, entidades, referencias, etc.)
  • El lenguaje usado no siempre es neutral ni consistente entre archivos

Esto hace que la revisión, comparación y mantenimiento a largo plazo se vuelvan más complicados de lo necesario.

Más que señalar casos específicos, creo que sería bueno ponernos de acuerdo en un criterio común:

  • qué tan estrictamente debemos seguir el formato del original en inglés
  • qué lineamientos usar para mantener un español neutral y consistente

¿Les parece si definimos algunas pautas simples para esto?

Quedo atento a sus opiniones.


Hello,

I’d like to start a discussion around two things I’ve noticed while reviewing the Spanish documentation:

  • The format is not always aligned with the English version (structure, entities, references, etc.)
  • The language used is not always neutral or consistent across files

This makes reviewing, comparing, and maintaining the documentation more difficult than it should be.

Rather than pointing out specific cases, I think it would be useful to agree on some shared criteria:

  • how strictly we should follow the original English format
  • what guidelines to use to keep the Spanish neutral and consistent

Would it make sense to define some simple guidelines for this?

Looking forward to your thoughts.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reviewing the Spanish documentation alongside its English source and collect concrete formatting and terminology examples; done means agreed, documented guidelines for structure, references, and neutral, consistent Spanish.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
documentation, internationalization, localization
Issue type
Documentation
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.