mikkeli
e45562a9d2
50.52 紅葉山駐車帯 41 m off 夕張市紅葉山 57.08 楓駐車帯 39 m off 夕張市楓 Both signposted and both absent from OpenStreetMap, which carries no parking or rest-area features anywhere on this stretch. One of them is a bay the author had previously recorded as unnamed. Responsible body is 北海道開発局 札幌開発建設部 岩見沢道路事務所 by jurisdiction — R274 is 指定区間 全線 and every adjacent structure registers to that office — but no document names either bay, since parking has no published register. Author's trimming removed 38 rows: the 丁目 grid, all five bus stops, 川端駅, and some civic furniture. That leaves 132 rows with 132 distinct object names, so the planned lyric-to-row index is unambiguous with no special case except モトツ橋/シェルター, which already share coordinates. 274-romaji.py learns ちゅうしゃたい and ていしゃたい so parking bays split as Momijiyama chuushatai rather than one run-on token; --check is clean. CSV and GeoJSON re-propagated from the Markdown. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01S6MpcBisZYhX45oDGRRJoz
Northwich committee of magic researches songs repository
Just a collection of lyrics of songs. Probably will be managed into proper folders. Probably will have LRCs.
Publishing to the wiki
Song pages are auto-published to https://wiki.novoyuuparosk.org by the
songs pipeline in the companion repo novoyuuparosk-auto-wiki (the
"repo next door"). It triggers on push to master.
- Source-file contract (frontmatter fields, body conventions): see
pipelines/songs/SCHEMA.mdinnovoyuuparosk-auto-wiki. - Pipeline overview (branch convention, triggers, categories, LRC, etc.):
pipelines/songs/README.md.
In short: a file is published when its frontmatter has wiki.publish: true
and it isn't under wip/. The title field becomes the wiki page name.
Linking to another song page
Write an ordinary relative Markdown link. There is nothing to declare in the frontmatter:
For more behind-the-scene shenanigans, see [Dev gibberish](pulse_dev.md).
At publish time the .md target is swapped for the target file's own title,
giving a proper wikilink — so renaming a page means editing its title and
nothing else. The link keeps working in Gitea's blob view and in any editor
preview, because it is just a link.
Two things to know:
- The target must be published too (
wiki.publish: true, outsidewip/). Linking to a file does not publish it; an unresolvable link fails the CI run instead of quietly turning into plain text. - Links do not work inside a
```columnsfence — that block is verbatim by design. Put them in ordinary prose.
This replaces the old wiki.siblings frontmatter block and its ALL_CAPS
placeholders, which are gone.
Side-by-side lyrics (columns shorthand)
To lay two (or more) versions of a song next to each other — e.g. an original
and its translation — use a fenced code block tagged columns, with each
column separated by a line containing only ===:
```columns
**原題**
一行目
二行目
===
**Title**
first line
second line
```
Notes:
- Line breaks and blank lines are preserved verbatim (each column is rendered with line breaks intact).
Ncolumns ⇒N − 1===separators.- Use Markdown emphasis inside the block:
*italic*,**bold**,***bold-italic***. (No need for raw HTML.)
This is implemented entirely by the auto-wiki pipeline at publish time; the
authoritative description lives in
SCHEMA.md.
See kairo/kimito_en.md for a real example.