@Zanna Hi -- sorry I didn't see these messages before today; I would've submitted an edit sooner to address the misconception expressed in the comments. Please feel free to roll back or otherwise re-edit if you don't agree with the way the information is presented.

Aww thanks so much for the edit. That's awesome. Makes my answer so much better :) :)

@Zanna Stéphane Chazelas removed the comments (and replied) shortly thereafter, even though I had not yet pinged him, so I think much of the confusion has been alleviated. (I only say "much of" because the old comment had some upvotes on it, as I recall. I think some other people may also have been misled by the name of the name "right single quotation mark" into assuming that the normative content of the standard indicated that it was to be used only for closing quotations.)

Btw I changed the output of your command slightly (and the command even more slighly, adding a "." to compensate). I don't know if there's any better example, since the context is aliasing, and aliases in Bourne-style shells don't support suppressing arguments. I didn't mention that change in the edit summary because I wanted to clearly express the rationale for the major change (summarizing and quoting from Unicode 10.0), and that took pretty much all the space in the edit summary.

TIL about this nice tool for converting PDF to Markdown:

github.com/jzillmann/pdf-to-markdown

(Huh, I thought GitHub project pages were eligible for oneboxing in SE chat.)

Anyway, I used that to convert the excerpt from Unicode 10.0 into Markdown, then made changes to accommodate SE's style sheets (which don't render #### headings in a way that make them recognizable as headings) and simulate small caps badly with subscripted superscripted strong ("bold") capitalized text, which seemed like a bad but least bad way to represent them compared to other methods.

@EliahKagan not sure how I lost that part...

@EliahKagan neat!

In that post, what do you mean about how the locale might affect the appearance of the ’ character?

@Zanna If everybody's copy of the Unicode standard had fallen to the bottom of the sea -- this possibility crossed my mind -- then diving down to get it might be justifiable, but only if you have the necessary training and PPE! :)

I don't know if it's affected by locale. Someone once corrected a post I wrote about writing a special character by typing Ctrl+Shift+uXXXX to say it depended on the locale. AFAIK, it depends on the font haha

Oh. So...is the idea that the way the terminal interprets that is affected by locale?

@EliahKagan yes, all that effort would be worth rescuing :)

@EliahKagan that's what I thought...

@Zanna Do you happen to know what post? It might be good to ask about this. I am not familiar with differing terminal behavior based on locale.

I imagine that some terminal emulators do behave differently based on locale, but my impression from what you're saying is that someone said it is affected in a way that is predictable from the locale, rather than in a way that is not predictable at all because it's dependent on idiosyncrasies of specific terminal emulators (rather than, like, terminal types) that might happen to be influenced by locale.

@EliahKagan here it is

Different terminal emulators do display the same text differently, as evidenced by your experiences with only some terminal emulators being suitable for Tamil. But I don't think that's affected by your locale settings, is it?

Does the way your terminal displays the same text -- as opposed to the way programs you are running in the terminal display it -- vary when the locale is changed (it would have to be changed in the environment of the terminal emulator itself, rather than the shell you're running in it, right?) with no other changes.

@Zanna Thanks. ...I'm relieved it's not me who edited it, since I cannot think of a reason this would be so. :)

haha if it had been you, I would have mentioned that in the first place

thinking aloud you don't have to press enter though... the character appears when you release the mod keys...

I've commented.

@Zanna So is the answer wrong?

@EliahKagan thanks for commenting :)

No problem.

@EliahKagan yes. I've fixed that part of it though

Ah, I see. It's the other part, holding down the correct keys, that is what helped the OP and other readers.