I discovered this by writing in Italian, but I think it is the same on any language.
By default, autocorrect makes sure that any phrase starts with caps, changing
But if the first word contains an apostrophe like
l'importanza di questo periodo
autocorrect fails, which is not desired. It should change the phrase into
L'importanza di questo periodo
On Windows 8.1 Enterprise 64-bit en-US with
Version: 22.214.171.124 (x64)
Build ID: f99d75f39f1c57ebdd7ffc5f42867c12031db97a
CPU Threads: 8; OS Version: Windows 6.29; UI Render: GL;
Locale: en-US (en_US)
New default profile.
If the Autocorrect Options dialog Localized options tab "Single Quotes" is checked active--the capitalization of a word with "apostrophe" does not occur.
But with "Single Quotes" unchecked in auto-correct options, also seeing some weirdness in the auto-correct when the paragraph is not the first of the document.
Typing these lines and observing which words with apostrophe receive capitalization.
"it's my party, i'll cry if i want to"
"it's my party. i'll cry if i want to"
"i'll cry if i want to. i'll cry if i want to. it's my party"
something is wrong in edit engine--and the "Single Quotes" substitution is also having an affect.
Confirmed all V Stuart Foote's points on Windows 10, LO 126.96.36.199.
bug still present in LibO 188.8.131.52.alpha0+
Build ID: 4c70a1a6666a079872b8f1966bd398e924dc1d1a
CPU Threads: 4; OS Version: Windows 6.29; UI Render: default;
TinderBox: Win-x86@42, Branch:master, Time: 2016-09-22_06:54:24
Locale: it-IT (it_IT); Calc: group
Yep, still happening with latest version (184.108.40.206).
Fix: Type document with ' straight single quote, then use 'Search and Replace' to place ’ symbol. The only problem is that you can't then use single quotes for dialogue, as the end quote will be facing the wrong way. This is a problem for some publications' style guides, as they prefer singles. I guess the workaround /then/ is to use double quotes (still selected to 'smart'), and use Search and Replace to change them to single quotes.
@ Jon Pienaar
thanks for confirming issue with 220.127.116.11 but please do not mess bug fields if you don't know hoe it works...
I reverted all the wrong changes you made (status, hardware, version)
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Problem still present in 18.104.22.168 and 22.214.171.124
*** This bug has been marked as a duplicate of bug 106164 ***