zlacker

[parent] [thread] 6 comments
1. LeoPan+(OP)[view] [source] 2025-08-30 04:04:54
Feature request: Sort by em-dashes per comment.

Feature request 2: Em-dash regular-dash ratio.

replies(2): >>qrios+y >>dragon+ga
2. qrios+y[view] [source] 2025-08-30 04:13:44
>>LeoPan+(OP)
Feature request 3: …
3. dragon+ga[view] [source] 2025-08-30 06:53:17
>>LeoPan+(OP)
> Feature request 2: Em-dash regular-dash ratio.

What's a “regular dash”?

Hyphen-minus (which isn't even a dash at all)? En-dash? Figure dash?

replies(1): >>LeoPan+Db
◧◩
4. LeoPan+Db[view] [source] [discussion] 2025-08-30 07:11:00
>>dragon+ga
Hyphen minus, yes. The one on your keyboard.
replies(1): >>layer8+pD
◧◩◪
5. layer8+pD[view] [source] [discussion] 2025-08-30 13:02:35
>>LeoPan+Db
Keys on the keyboard aren’t characters.
replies(1): >>LeoPan+zd1
◧◩◪◨
6. LeoPan+zd1[view] [source] [discussion] 2025-08-30 17:40:10
>>layer8+pD
Pointless bickering. The minus sign on your keyboard is what 99% of people will hit when they want a dash.
replies(1): >>layer8+Fq1
◧◩◪◨⬒
7. layer8+Fq1[view] [source] [discussion] 2025-08-30 19:31:23
>>LeoPan+zd1
My point is there’s a whole software stack that determines what character is actually output when you hit that key, based on locale and IME, and also depending on the application. You meant to indicate a specific character, but specifying a key is a bad way to do that. Keyboard controllers don’t work in terms of characters. I could easily configure my OS to output U+2010 HYPHEN for that key by default, for example, and might actually do that for a typesetting application.
[go to top]