Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

lost in translation: Built-in

Open
#588 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Documentation
Clarity
Needs clarification
Activity status
Stale
Tech stack
javascript

Research direction

Search the repository for translations of “built-in” and collect the different forms mentioned in the issue: “incorporado,” “preincorporado,” “integrado,” and “nativo.” Review the existing translation context, then establish the project-wide criterion and update all occurrences consistently. Done means the terminology is agreed and unified throughout the repository.

Written by the indexing model from the issue text.

Description

Traduccion de "built-in"

DEBE eestablecers el criterio y unificar en todo el repo.

Habiamos empezado el repo con ---> "incorporado"
pero es ambiguo, una biblioteca de terceros también "incorpora" cosas
se puede resolver con "preincorporado", suena raro

Algunos usaron "integrado", pero tiene el mismo problema de ambiguedd

Tambien se usó "nativo" que tiene mi voto. Suena extraño, pero es mas preciso.

opiniones? help wanted

Dominant language
HTML
Stars
626
Forks
226
PR merge metrics
No merged PRs in 30d

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.

More from javascript-tutorial/es.javascript.info

All issues in javascript-tutorial/es.javascript.info

Similar issues

More Documentation issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.