Hebrew guides: formula code blocks in Latin symbols with a Hebrew key
Hebrew words inside a left-to-right code block are reordered by the bidi
algorithm, so the TAS / density-altitude formulas on Planning-Form-he and
Inspector-he rendered garbled (and `מ.א.מ ÷ √σ` showed as σ√). The blocks now
use PA / T / ISA / DA / ELEV, with a Hebrew line naming each symbol.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016iFU698yss2ToHbRpRJJS8
Wiki sweep (HE): same as the English sweep — menu split into Map + Settings, phone tabs and red Comm fail, edit column, centred questions, SIGMET layer and lists, decoder, movable hazard lists, aerodrome charts, NOTAMs in bubble/leg panels, symbols by zoom, LSA sites and route types
Apply verified GitHub LTR spans across Hebrew guides
Isolate technical inline text left-to-right on Hebrew wiki pages
Update route-check, offline and deployment guides; fix Hebrew direction wrappers
Sweep: the compass card, Add a level, the window, and the question every route door now asks
Keep one exercise download: Herzliya to Rosh Pina
Five exercises, as files the app loads
Herzliya-Rosh Pina, Masada-Herzliya, Atarot-Haifa, Haifa-Atarot and Teyman-Sdom,
built from the question sheets rather than reconstructed: real coordinates, each
exercise's own met table (Atarot's starts at 1,000 ft, Teyman's at 3,000 with
different winds entirely), its own compass card where it differs, and its own
speeds, rates, fuel and field elevations -- Masada 1,200 ft below the sea, Sdom
1,000 below.
Each is also a route the map loads whole, so one Open draws the plan and fills
the form.
The wiki's ISA is two degrees, as the code's is
The page still printed the physical 1.98 in its formula. The form works in 2 --
the exercise's figure, and one a reader can check in their head -- and the page
now says which, where the two part company, and that the in-flight altimetry
correction keeps 1.98 because it is flown against rather than checked by hand.
Say how to save the exercise file, and put it on the page
The raw link is served as text/plain with nosniff, so every browser shows the
JSON instead of downloading it -- and nothing in a wiki page can change that: the
download attribute is ignored cross-origin, and the wiki has no control over
GitHub's headers.
So the page says what to do instead -- right-click, save link as -- and carries
the file itself in a collapsed block to copy. The app reads the text, not the
name.
The exercise itself, to download, and the coordinate search
The Herzliya - Rosh Pina sheet is attached to the planning-form page in both
languages: route with its legs at 6,000 ft, met table, compass card, 4E
variation, the stated climb and descent figures. Open it through Import/Export
and the map and the form both fill in -- and what comes out should match the
published answers cell for cell, which is the point of handing it over rather
than describing it.
Features also documents what the search box now takes: a coordinate, in any of
the forms one actually arrives in, read as one coordinate before the
space-separated route syntax so "N32 30 E035 00" is a place rather than four
waypoints.
Hebrew pages read right to left
The planning form's page was written without the <div dir="rtl"> wrapper every
other Hebrew page here carries, so it rendered left to right: bullets on the
wrong side, tables mirrored against the text, punctuation adrift at the ends of
lines.
Four more were missing it too -- the safety notice, the assistant, extra layers
and the phone layout -- all pages added since the convention was set, which is
how a convention nobody checks goes quiet.
A picture of the planning form, in both languages
Generated by the same spec that makes every other wiki image, with the exercise's
own met table and compass card in it -- an empty form shows the shape but not the
thing it does.
The flight planning form, and what the flight plan deliberately is not
A new page in both languages for the wind-triangle sheet: the 23 columns in the
order the exercise prints them, and the reasoning behind each rule -- why the met
table and the compass card are read at their nearest entry rather than
interpolated, why there is one top of climb and not one per waypoint, why drift
is the opposite sign to the correction, and what the sheet says when a segment
cannot be worked out at all.
The flight plan page now says, at the top, that its table is zero-wind on purpose
and where the wind triangle lives instead. Two documents, and the difference
between them is the whole reason the second one exists.
Local storage gains navaid.navlog -- which holds only what was typed, because
everything else is re-derived -- and navaid.navlogPos.