Autocorrection two capital letters in words

Hi, I am typing quite fast and often it happens that the first two letters of a word are capitalized (Writing in German this is really annoying since a lot of words are capitalized). While all other editors correct this automatically, I would like to know whether the feature exists now. THe problem occurs on IOS as well as on windows.

I’d love such autocorrect option as well.

macOS used to have this as standard. I turned it off because my academic qualifications which have deliberate two capital letters. As it was so long ago (maybe around the time that original MacBookPro was first launched) that I forget where the option was and subsequent updates/upgrades of macOS have moved stuff around (detrimentally in my opinion) that I would have to hunt for it.

You could use Regular Expressions to Find two capital letters and Replace them with one…
With the RegEx option selected, Search for:

([A-Z])[A-Z]

Replace with:

$1 or \1 depending on you RegEx-version.

Hope this helps

Thanks all, I just noticed that IOS is doing this correction now. I don’t know when it was introduced.
For Windows the Workaround might do the job.

Hello,
unfortunately this only erases the second letter.
Like
ā€œTHis is my test for CApital LEttersā€ into ā€œTis is my test for Cpital Lttersā€

You’re right. It replaces the second Capital letter with nothing… I’ll look for a better solution.

You can try te Replacement: $1\L$2\E
But it’s unclear if that works in Scrivener.

I’m no RegEx expert, but I do know that the ICU flavor of RegEx that Apple provides does not recognise the Upper and Lower case ( U and L ) switches which Oniguruma RegEx uses. Am I right in thinking that Qt provides PCRE RegEx, which I presume does recognise those switches. If so, an expression can be constructed to turn the second instance lower case.

But I’m a Mac-user so can’t test it out.

:slight_smile:
Mark

I’d like to throw in that to work properly in German you will have to add the Umlauts and the ß to the RegEx concoction.

And isn’t case sensitivity in RegEx the default that has to be switched off if not wanted? Anyhow, how about searching for this: (?-i)[[:upper:]]{2} If it works at all it will cover all uppercase letters like in ā€œICh habe einen BƄrenhungerā€.

Can’t test it out either because I’m on Mac too (and for Mac I’d suggest Typinator to handle stuff like that.)

1 Like

Finding works, but Replacing?

Correct, but it doesn’t.

I really don’t believe that expecting an end user to jump through the programming hoops is a correct way to handle this, honestly. Personally, I don’t even understand what you all are talking about, what this Regex thing is and how does a person access it. :slight_smile:

Having a simple switch/checkbox somewhere in the settings that would make the second capital letter lowercase, like Word does, would be nice. It’s a text processing software, after all.

I agree. The best way to address this problem is to improve the user’s typing technique. Everything else is a band-aid at best.

1 Like

Tee hee! Just wait 'til you get older and your nervous system has odd ideas. . . . :upside_down_face:

That said, I just had a lot of fun finding out what’s possible with Regex in this case. Regex, for those who are mystified, is an immensely powerful, arcane pattern recognition engine. When your browser boops at you when you mess up the phone number, that’s probably Regex behind the scenes saying you missed a number or two. It’s intimidating at first, but once you get the idea that you can do things like switch ā€˜a’ and ā€˜e’ to ā€˜e’ and ā€˜a’ throughout your 100,000 word text you get a little excited. There are great resources across the web to help you get started but if ā€˜\b[A-Z]{-2}’ looks like way too much to fathom, well, that’s OK. Just soldier on.

First, it would, indeed, be better if it were a simple switch to find double-uppercase typos and apparently that’s been done already though now lost as mentioned above. Second, if I’m not mistaken Scrivener is using Apple’s implementation of Regex which does not yet support changing case in replacement strings. So you’re out of luck using it to fix your occasional coffee-induced palsies until Apple restores this useful substitution. :grinning:

Dave

2 Likes

Your response feels like a rather rude trolling. Which it probably is.

1 Like

If one types so fast that a magic intervention is required to correct all the typos, it’s probably ā€œtoo fastā€.

This used to be basic knowledge when people still took typing classes and got a ā€œtime penaltyā€ for every mistake. Not sure what’s offensive about it.

I had this problem. Took quite some relearning to fix it. Slow is smooth, and smooth is fast. The most portable solution I could find.

1 Like