Fix Spanish string-range instructions and rope terminology
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 78/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- markdown, python
Research direction
Review the cited files: wavedoc/es/language/strings.md, es/stdlib/bytes.md, es/reference/string-and-bytes.md, es/reference/standard-library.md, and es/getting-started/overview.md. Compare the revised strings paragraph directly with the Korean source, preserving code, output, and links. Done means the range and NUL-termination meaning is restored, terminology is consistent, and python3 tools/check-doc-translations.py passes.
Written by the indexing model from the issue text.
Description
Problem
The substring explanation says transportar la estufa (“carry the stove”). The source says to retain the range separately or allocate new string storage: moving the starting address does not insert a NUL at the end of the range.
The same paragraph calls text strings cuerdas (ropes). This also occurs in es/stdlib/bytes.md, es/reference/string-and-bytes.md, es/reference/standard-library.md, es/getting-started/overview.md.
Acceptance criteria
- Restore the meaning of the range-management instruction, including the distinction between a byte range and a NUL-terminated string.
- Use Spanish text-string terminology (
cadena/cadena de caracteres) in the five cited locations. - Preserve code, expected output, and link destinations; compare the revised paragraph directly with the Korean source.
- Run
python3 tools/check-doc-translations.py.
- Dominant language
- Go
- Stars
- 1
- Forks
- 7
- Avg merge
- 1h 45m
- Merged PRs (30d)
- 16
Getting set up
We have not checked this project's setup files yet. Start from its README, and see our first-contribution guide for the general steps.
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 wavefnd/wave-platform
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 90/100
wavefnd/wave-platform#140 ·
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
wavefnd/wave-platform#139 ·
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 Half a day Newbie friendliness 88/100
wavefnd/wave-platform#137 ·
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
wavefnd/wave-platform#136 ·
-
bug difficulty: beginner documentation good first issue help wanted localization
Difficulty 1/5 Under an hour Newbie friendliness 94/100
wavefnd/wave-platform#135 ·
All issues in wavefnd/wave-platform
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
rossoctl/context-guru#346 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
prime-radiant-inc/evener#2883 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
gravitational/teleport#69805 ·
Maintainers usually reply within 11 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Under Poisson sampling, the `PLDAccountant` composes the inner event both before and after samplingOpen
Difficulty 2/5 Half a day Newbie friendliness 78/100
google/differential-privacy#496 ·