Wed Jul 17, 2019 3:18 pm Post
Wed Jul 17, 2019 4:25 pm Post
Thu Jul 18, 2019 4:10 pm Post
Thu Jul 18, 2019 4:28 pm Post
Thu Jul 18, 2019 5:15 pm Post
I avoid using en-dashes and en-dashes in the editor for this reason – my writing font makes the differences hard to see…. two hyphens become an en-dash and three become an em-dash.
Thu Jul 18, 2019 5:41 pm Post
Thu Jul 18, 2019 5:46 pm Post
Silverdragon wrote:I avoid using en-dashes and en-dashes in the editor for this reason – my writing font makes the differences hard to see. Instead, I turn off "Smart dashes and ellipses", put the ellipsis auto-convert in the Mac keyboard settings, and put replacements in my Compile options – two hyphens become an en-dash and three become an em-dash.
Mon Jul 22, 2019 6:26 am Post
AmberV wrote:I see you’re using the Space+En Dash+Space convention. That’s not something the macOS text engine has any built-in help for. It prefers the Word+Em Dash+Word convention, and its built-in substitution for double-hyphens is how you’d insert those. That’s probably a point of trivia to your question, but it might help identify what is going on here. Your use of the word “dash” is a bit vague, in that there are probably over half a dozen different dash characters, the hyphen (in most cases your keyboard will insert the Hyphen-Minus character rather than a true hyphen, since most software conflates these two dash types) among them. Scrivener distinguishes between all of them and the millions of other Unicode character entries.
Otherwise I have no idea how you ended up with the result you describe. When I type a “hyphen” character, as provided by the key to the left of the [+/=] key, that’s all I get. I don’t get an en dash unless I use the ⌥- combination, and an em dash with ⇧⌥-.
But your keyboard layout may differ from mine. As I say this is all basic macOS technology here, so you should be seeing this behaviour everywhere you type that uses the native Mac text toolkit. One clue, you mention this happens “on compile”. Does that mean the character code is accurate in the editor if you copy and paste it into the search field of the Emoji & Symbols palette—but incorrect when you compile? I presume there is some extra layer in here as well, such as opening the compiled document in some type of software, it might help to know what that is, and what type of file you are creating.
Replacements might be a culprit. That’s the only obvious thing I can think of that would translate characters in that direction, especially if you only ever use a single hyphen in compound words.
Mon Jul 22, 2019 7:28 am Post
Mon Jul 22, 2019 11:14 am Post
Mon Jul 22, 2019 11:38 am Post
Tue Jul 30, 2019 12:57 pm Post
brookter wrote:Minor point: You're right—Word and Scrivener (PCs and Macs in general, in fact), produce an em-dash automatically.
But... if you press opt-minus you'll get an en-dash (–). You need shift-opt-minus for an em-dash (—).
I think it's been mentioned above, but if you're going to have a space around the dash, you need the en-dash (Word – Word); if you don't use a space, you need the em-dash (Word—Word)—at least, that's the usual convention, which Word cheerfully ignores...
Tue Jul 30, 2019 3:16 pm Post
In total there are 3 users online :: 0 registered, 0 hidden and 3 guests (based on users active over the past 5 minutes)
Most users ever online was 1048 on Mon Feb 06, 2012 9:07 pm
Users browsing this forum: No registered users and 3 guests