The halant key (्) and how to build any conjunct

Conjuncts in InScript are simple: type the first consonant, press the halant key (्), type the second consonant. The InScript text engine handles the visual ligature automatically. क + ् + ष = क्ष.

This is dramatically simpler than Kruti Dev, where conjuncts have non-obvious key sequences. InScript was designed with conjunct production in mind, and the design shows.

Lesson 5 drills the five workhorse conjuncts plus a few rarer but exam-relevant ones: क्ष, ज्ञ, श्र, त्र, द्व, द्ध, प्र, प्य, स्व, द्य.

The halant marker in Mangal Inscript works identically to Kruti Dev — it suppresses the inherent vowel from a consonant, allowing the consonant to combine with another consonant into a conjunct. The keystroke sequence is: consonant 1, halant key, consonant 2. The renderer composes the visible conjunct (क्ष, त्र, ज्ञ, etc.) from this three-keystroke sequence. Conjuncts account for 30-40% of keystrokes in formal Hindi text.

Conjunct errors on Mangal: (1) typing the conjunct as separate consonants (forgetting the halant) — produces wrong word; (2) double-halant from over-pressed key; (3) confusing visually-similar conjuncts; (4) speed-induced wrong-consonant selection inside the conjunct. These are the same error patterns as Kruti Dev because the conjunct construction logic is the same — only the key positions differ.

30 minutes daily, five days. Day 1: halant key in isolation, then halant followed by each consonant. Day 2: simple two-consonant conjuncts in isolation. Day 3: simple conjuncts in three-syllable words. Day 4: complex multi-consonant conjuncts. Day 5: paragraph practice featuring conjuncts at moderate speed. Conjunct fluency is the largest single contributor to the 25-to-35 WPM jump on Hindi typing.

Looking ahead: Lesson 6 covers numbers and Hindi punctuation in the Mangal layout.

The definition of mastery is consistency, not peak performance. A single best-ever run does not mean the skill is consolidated. The check: three runs of the final drill across three different days, all at or above the lesson's target speed, with accuracy sustained at 96%+. Fall short on any one run and the lesson is not yet mastered.

Faster mastery is allowed. If the three-run check passes in three or four days, move to the next lesson — the curriculum is sequenced so each lesson builds on the previous one, and consolidating the prior lesson is what makes the next lesson learnable rather than frustrating.

Each lesson in the curriculum has a specific place in the learning arc. The sequence reflects how typing skills actually build on each other — finger-position before bigram, bigram before word, word before sentence, sentence before passage. Trying to compress this order into fewer steps almost always slows progress rather than speeding it up.

The 10-lesson curriculum maps to 8-10 weeks for most candidates, with the final week reserved for mock-test consolidation. Faster paths (5-6 weeks) work for candidates with prior typing experience; slower paths (12 weeks) work for first-time typists. The per-lesson mastery check matters more than the total timeline.

Pitfall: typing the conjunct as two separate syllables. Forgetting the halant produces 'का्म' instead of 'कम' (visible to the reader, scored as wrong). Recovery: pre-drill the halant key in isolation until it's automatic, before practising compound conjuncts.

Pitfall: double-halant from over-pressed key. Pressing the halant twice produces 'क्' followed by 'क्' producing 'क्क्' which is not a valid Hindi compound. Recovery: light-touch halant key drills; consciously release the key after one press for the first three practice sessions.

Pitfall: confusing visually-similar conjuncts. क्ष and क्र look alike at speed, as do ज्ञ and ज्य. Recovery: drill each confused pair in isolation in week 1 of this lesson; the brain learns to distinguish them with focused exposure faster than with mixed-context exposure.

Pitfall: speed-induced wrong-consonant inside the conjunct. Typing क्त when क्थ was intended. The single-consonant substitution is invisible to the typist mid-flow but counts as a full error in scoring. Recovery: slow the conjunct drilling pace by 30% from the rest of the lesson; conjunct-specific accuracy matters more than conjunct-specific speed.

Keyboard. Use a full-size wired USB keyboard for the final two weeks of any lesson plan. The actuation feel of a mechanical or membrane keyboard with proper key travel is different from laptop chiclet keys, and the difference shows up as 5-8 WPM loss on test day. A budget keyboard works fine — the goal is the form factor, not premium build.

Body position. Three things matter: forearms parallel to the floor, wrists straight (not flexed up or down), and the screen at roughly an arm's length. The combination removes the late-window forearm tension that collapses accuracy in the final minutes. Poor posture is the silent reason many candidates' mock scores never match their drill scores.

Practice environment. The centre is quiet and distraction-free; mock conditions should match. Phone out of the room (not just face-down), no music with vocals, and a stable working temperature. These small environmental controls add up to noticeable focus improvement across a full lesson week.

Time of day. For the closing two weeks before the test, schedule practice at the same time of day as the assigned examination slot. The 30-60 minute cognitive variation across the day matters more than candidates expect; matching practice timing to the centre slot tightens the mock-to-test correlation.

Conjuncts are the rate-limiting step in Hindi typing speed. A candidate who is fluent on simple letters but stumbles on conjuncts loses 4-6 WPM on real exam passages. Lesson 5 closes this gap directly.

Notice that the InScript conjunct rule is just three keys per conjunct, in the order they read. Compare with Kruti Dev where each conjunct can have an idiosyncratic key sequence. The InScript design wins on consistency and that consistency is what speeds up your typing.