zlacker

[parent] [thread] 11 comments
1. machin+(OP)[view] [source] 2025-08-30 05:30:20
Easy is almost an understatement; it's Alt+Hyphen. [Edit: My bad that's en-dash, can't tell the difference in this monospaced text field. Em-dash you have to hold shift.]

I guess on Windows it's Alt+0,1,5,1 on a numpad. Or you copy+paste from Character Map.

replies(3): >>e28eta+9 >>notpus+47 >>SAI_Pe+S02
2. e28eta+9[view] [source] 2025-08-30 05:32:29
>>machin+(OP)
To be pedantic: Opt-shift-hyphen for the em dash (longer one). Opt-hyphen only gets you an en dash.
replies(3): >>9dev+91 >>machin+e1 >>saagar+fe
◧◩
3. 9dev+91[view] [source] [discussion] 2025-08-30 05:49:35
>>e28eta+9
…which is the appropriate character for ranges, i.e., page 1–2.

I find it a bit sad that using proper typography is now frowned upon, but it seems that ship has sailed.

replies(1): >>Symbio+ub
◧◩
4. machin+e1[view] [source] [discussion] 2025-08-30 05:50:44
>>e28eta+9
Right, you sniped my edit. I don't know why I gave up my hn delay setting...
5. notpus+47[view] [source] 2025-08-30 07:08:53
>>machin+(OP)
You can install a custom layout on Windows, like the one I made: https://typo.ale.sh/
◧◩◪
6. Symbio+ub[view] [source] [discussion] 2025-08-30 08:02:58
>>9dev+91
From the discussion with our head of communications (whose pedantry I approve of) US usage avoids spaces—like this—and should use an em-dash.

But British usage – instead – uses spaces, so an en-dash or an em-dash is acceptable.

replies(1): >>d1sxey+mG
◧◩
7. saagar+fe[view] [source] [discussion] 2025-08-30 08:36:23
>>e28eta+9
One of the reasons I'm not on that page–I have a policy of using en dashes because I am lazy
◧◩◪◨
8. d1sxey+mG[view] [source] [discussion] 2025-08-30 13:57:33
>>Symbio+ub
Generally spaces around em-dashes is a question of style, not pre- or pro-scribed by any specific typographical rule. One nice middle ground is a hair space ( ), although it’s a pain to insert.
replies(2): >>165944+7E1 >>andrew+cE1
◧◩◪◨⬒
9. 165944+7E1[view] [source] [discussion] 2025-08-30 22:11:48
>>d1sxey+mG
> spaces around em-dashes is a question of style, not pre- or pro-scribed by any specific typographical rule

Writing and publishing style guides like Hart's Rules (Oxford Style Guide) & Chicago manual of style have the 'em' dash use as a parenthetical closed or "no spaces" dash.

In British use – Hart's Rules – writers will choose the 'en' dash with spaces as a parenthetical dash, where US writers/publishers choose the closed 'em' dash for the same thing.

Imo, there is a conflation of 'en' dash and 'em' dash going around due to the ease of smart-dashes auto-correction turning (--) into 'em' dash with the 'en' dash and non-auto-correct 'em' dash needing a key-combo.

Common everyday typing online, I think people will simply use what is convenient and "good enough" -- a single hyphen dash as an 'en' dash or 2-hyphen dashes that may or may not auto correct into an 'em' dash. I prefer mixing spaces with a 2-hyphen dash 'em' dash, but I'm not a published writer so I enjoy doing wild things like that

◧◩◪◨⬒
10. andrew+cE1[view] [source] [discussion] 2025-08-30 22:12:33
>>d1sxey+mG
I configured my Markdown renderer to replace ` -- ` with " — ". Hopefully those narrow spaces make it through HN's rendering — it's much easier when your tooling can do the job for you.

https://github.com/andrewaylett/aylett.co.uk/blob/d338d35a3d...

11. SAI_Pe+S02[view] [source] 2025-08-31 02:36:04
>>machin+(OP)
Or you've had WinCompose installed for years and type Compose+hyphen+hyphen+hyphen. — is easy to type that way. The same works for Linux with a compose key enabled, WinCompose is a program to give Windows a compose key, and comes with default sequences including those found by default in most distro's XCompose list.
replies(1): >>etra0+582
◧◩
12. etra0+582[view] [source] [discussion] 2025-08-31 04:08:49
>>SAI_Pe+S02
Big shout-out to WinCompose, it's the only way I found my keyboard usable while being bilingual :)
[go to top]