[Sync EN] Document the missing ValueErrors for chunk_split, str_pad, str_repeat and other string functions (#6004)
Maintainers usually reply within 2 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 85/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- xml
- Domain
- documentation, localization
Research direction
Start from the linked EN commit and PR doc-en/pull/6004 to see exactly which ValueError descriptions were added upstream. Then mirror those changes into the eight listed Spanish XML files under reference/strings/functions/, adapting the wording to Spanish. Done when all eight files match the English revision and the docs still build (configure.xml / PhD render) without errors.
Written by the indexing model from the issue text.
Description
Commit: https://github.com/php/doc-en/commit/25ec27a80ca17bf72bbe7a3ea65b0a1038c15025
PR: https://github.com/php/doc-en/pull/6004
Archivos ES a actualizar
reference/strings/functions/chunk-split.xmlreference/strings/functions/count-chars.xmlreference/strings/functions/str-pad.xmlreference/strings/functions/str-repeat.xmlreference/strings/functions/str-word-count.xmlreference/strings/functions/strpbrk.xmlreference/strings/functions/substr-compare.xmlreference/strings/functions/substr-count.xml
- Dominant language
- XML
- Stars
- 34
- Forks
- 64
- Avg merge
- 3d 1h
- Merged PRs (30d)
- 53
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from php/doc-es
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 75/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 1/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 2 days
-
sync-en
Difficulty 1/5 Under an hour Newbie friendliness 74/100
Maintainers usually reply within 2 days
Similar issues
-
Link Checker ReportOpenautomated issue linkchecker report
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
QuantEcon/lecture-python.myst#1098 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 82/100
OpenShot/openshot-qt#6230 ·
Maintainers usually reply within 1 day
-
area: docs difficulty: easy documentation first-timers-only good first issue help wanted
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
hayagrivai-labs/phantom#123 ·
Maintainers usually reply within 1 day
-
self-driving
Difficulty 1/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
yazi-rs/yazi-rs.github.io#438 ·