Use `U+2019 right single quotation mark` instead of `U+0027 apostrophe` where appropriate

[dietmarkammerer]

In the English Internationalization file (src/assets/i18n/en.json5), the most commonly used character for apostrophe is U+0027 apostrophe. However, according to the Unicode Standard (v13), the preferred apostrophe should be U+2019 right single quotation mark.

Punctuation Apostrophe. U+2019 right single quotation mark is preferred where the character is to represent a punctuation mark, as for contractions: “We’ve been here before.” In this latter case, U+2019 is also referred to as a punctuation apostrophe.

In a small number of places, U+2019 right single quotation mark is already used in src/assets/i18n/en.json5, e.g. in "admin.access-control.groups.form.alert.workflowGroup": "This group can’t be modified or deleted because it corresponds to …" etc.

Note that U+0027 apostrophe is also used for other purposesin the i18n file, e.g. here:
"comcol-role.edit.create.error.title": "Failed to create a group for the '{{ role }}' role", to denote the variable,
or here:
"item.edit.bitstreams.notifications.discarded.content": "Your changes were discarded. To reinstate your changes click the 'Undo' button", where it is used as quotation marks.

I suggest to replace U+0027 apostrophe with U+2019 right single quotation mark where it is used as punctuation mark,
and with U+2018 Left Single Quotation Mark and U+2019 right single quotation mark respectively, where it is used as quotation marks.

Ressources:
https://en.wikipedia.org/wiki/Quotation_marks_in_English#Typographical_considerations
https://www.unicode.org/versions/Unicode13.0.0/ch06.pdf#page=19

[tdonohue]

@dietmarkammerer : While I understand your desire to better standardize against Unicode guidelines, I worry it will be very difficult to enforce the usage of a right single quotation mark in these files.

For instance, on an English Language Keyboard, there is only a key for apostrophe (U+0027) and no key exists to type a right single quotation mark (U+2019). This is why apostrophes appear more frequently, because on some keyboards there is no inherent support for a left/right single quotation mark. (My own keyboard is an English language keyboard which has this issue...I cannot easily type a left/right single quotation mark in my preferred editor)

While I realize that some editing programs do provide tools to add left/right-single quotation marks, there are many developers/translators who still use basic text editors or IDEs which may not have that support. Developers/translators are also using a variety of tools to edit these files from a variety of operating systems.

So, even if we were to change all apostrophes to left/right-single quotation marks, I feel that this problem will arise again as these files continue to be edited/updated.

[mwoodiupui]

For example: here I can type that character, but I have to remember Shift Right-Control, apostrophe, greater-than, which took me about 5 minutes to find. And Shift Right-Control is my own custom modmap configuration for the X Window "Multi" key that won't necessarily work elsewhere.

In general, translating keystrokes to character codes is a multi-layered mess.

[tdonohue]

Closing, as two Committers are in agreement that this seems too messy to do at this time. We can always reopen later if we find a better way to achieve this.