mikkeli
ee4c177233
Field sweep additions, all absent from OpenStreetMap and found by the author on Google Maps: 40.16 滝下八幡神社 栗山町字滝下 43.07 滝下発電所 栗山町字滝下 (北海道企業局) 57.44 登川神社 夕張市楓 66.78 豊進神社 むかわ町穂別稲里 71.86 穂別ダム神社 むかわ町穂別稲里 79.67 福山神社 むかわ町穂別福山 93.58 名石駐車場 占冠村字中央 102.36 日高神社 日高町宮下町 104.52 日高発電所 日高町字千栄 (北海道電力) 106.22 右左府発電所 日高町字日高 Plus 滝ノ上信号場 and 楓信号場, which OSM tags railway=signal / railway=junction with no place tag, so both fell through every filter. Corrections: モトツ橋 moved 86.16 → 87.12. It does not cross パンケモトツ沢川; it is the sheltered span between モトツトンネル and 福山トンネル, roofed by モトツシェルター — the identical 62 m lengths are the same deck. Author also fixed 下福山橋 → 77.05 and オロロップ橋 → 77.55, matching route01's order. Readings: kana is the source of truth. Romaji regenerated from it in wāpuro style, no macrons. Adds 274-romaji.py, which does that deterministically and is idempotent against the current table. Artifact now shows Romaji in the table and kana under each strip mark. CSV and GeoJSON re-propagated. 168 entries, 118 with readings. 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.