Vertical (') and slanted (’) apostrophes
DiscussionsBug Collectors
Rejoignez LibraryThing pour poster.
1Cynfelyn
This is either a bug or a recommended site improvement, depending on whether it was intentional in the first place.
Predictive text in CK seems to differentiate between a vertical apostrophe (') and a slanted apostrophe (’). You can only type a vertical (Unicode?) one into LT, so I'm guessing the slanty ones have been copied and pasted in (perhaps from Microsoft smart quotes?).
I was typing in "Chetham's Library was founded in 1653 in accordance ..." (www.librarything.com/work/25838875), and the predictive text came up with "Chetham’s Library was founded at a time when ..." until I typed the apostrophe, when it disappeared. I don't suppose my "Chetham's ..." has been in the system long enough to crop up as predictive text yet, if anyone wants to repeat the experiment.
It would be tidier if apostrophes (and quotation marks etc.?) were standardised to Unicode when content is saved.
Predictive text in CK seems to differentiate between a vertical apostrophe (') and a slanted apostrophe (’). You can only type a vertical (Unicode?) one into LT, so I'm guessing the slanty ones have been copied and pasted in (perhaps from Microsoft smart quotes?).
I was typing in "Chetham's Library was founded in 1653 in accordance ..." (www.librarything.com/work/25838875), and the predictive text came up with "Chetham’s Library was founded at a time when ..." until I typed the apostrophe, when it disappeared. I don't suppose my "Chetham's ..." has been in the system long enough to crop up as predictive text yet, if anyone wants to repeat the experiment.
It would be tidier if apostrophes (and quotation marks etc.?) were standardised to Unicode when content is saved.
2thorold
>1 Cynfelyn: You can only type a vertical (Unicode?) one into LT
It depends on what sort of keyboard you are using: on a desktop computer you generally have to jump through hoops to get anything other than straight quotes, but iPads and iPhones like to turn everything you type into smart quotes, which can be frustrating when you are trying to enter something like an image link, where only straight quotes will work. In a lot of ways it would be good if LT straightened the quotes by default, but I'm sure you'd also get people who care about the appearance of their talk posts moaning that all their lovely smart quotes have disappeared...
It depends on what sort of keyboard you are using: on a desktop computer you generally have to jump through hoops to get anything other than straight quotes, but iPads and iPhones like to turn everything you type into smart quotes, which can be frustrating when you are trying to enter something like an image link, where only straight quotes will work. In a lot of ways it would be good if LT straightened the quotes by default, but I'm sure you'd also get people who care about the appearance of their talk posts moaning that all their lovely smart quotes have disappeared...
3MarthaJeanne
>2 thorold: Luckily you can turn those stupid smart quotes off.
4conceptDawg
Fixed for CK data.
I am not touching double quotes though. So people can still use fancy double quotes. Just apostrophes are changed to a standard Unicode style.
I am not touching double quotes though. So people can still use fancy double quotes. Just apostrophes are changed to a standard Unicode style.
5Cynfelyn
>4 conceptDawg: Thank you.
6Cynfelyn
Sorry to come back to this, but I've just come across an example of apostrophes that escaped the fix.
Cause of death = Parkinson's disease currently returns seven autocomplete suggestions, all starting "Parkinson's disease", while Cause of death = Parkinson’s disease currently returns four suggestions, all starting "Parkinson’s disease".
Many thanks.
Cause of death = Parkinson's disease currently returns seven autocomplete suggestions, all starting "Parkinson's disease", while Cause of death = Parkinson’s disease currently returns four suggestions, all starting "Parkinson’s disease".
Many thanks.
7kristilabrie
I reopened this but after talking with conceptDawg I'm closing it back up. I've been told this is likely old data still hanging around, and once the other "incorrect" entries are fixed those will go away from the autocomplete options.
