Skip to content

Split the map screen paragraph of README.md - #38

Merged
eyunya11 merged 1 commit into
mainfrom
docs/split-readme-en-map-paragraph
Nov 9, 2026
Merged

eyunya11 merged 1 commit into
mainfrom
docs/split-readme-en-map-paragraph

Conversation

@eyunya11

@eyunya11 eyunya11 commented Nov 9, 2026

Copy link
Copy Markdown
Owner

The English README's "The map screen" section was one paragraph of about 1,900 characters, with a long sentence that held the screen's settings in nested parentheses and semicolons. This splits it the same way #37 split README.ja.md:

  • placing the block (the sentence about the dimension moves up here);
  • the settings, now a list of five items;
  • the track tags;
  • the station and signal marks;
  • the speed-limit signs;
  • the placement of marks and names;
  • what the server sends.

The wording is unchanged apart from the sentences that were joined by semicolons now standing on their own, and the tags sentence starting with its own subject ("It shows the track tags as the editor's map does"). A word-by-word diff of the section shows nothing else added or dropped.

Documentation only; no build or tests were run.

🤖 Generated with Claude Code

The section was one paragraph of about 1,900 characters, with a sentence
that held the screen's settings in nested parentheses and semicolons. Split
it as README.ja.md was split: placing the block, the settings (now a list),
the tags, the station and signal marks, the speed-limit signs, the placement
of marks, and what the server sends. The wording is unchanged except that
the sentences joined by semicolons now stand on their own, the tags sentence
starts with its own subject, and the sentence about the dimension moves up
beside the placement.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@eyunya11
eyunya11 merged commit f73cc1e into main Nov 9, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant