Case Converter (including Title Case) - now working on MacOS 12.3

[Chris Messina]

19 hours ago, matthewmcvickar said:

@Chris Messina Re: labeling the hotkeys objects; you can right-click the hotkey object and select 'Edit Note' to add a label underneath the object, like in this screenshot:

 

Oh yes, I'm aware — thanks! I was talking more about the layout of the Workflow blocks! 

[Marlouis]

Dear Alfred community,

 

I enjoyed using the Case Converter workflow since last year and it worked like a charm on my Macbook Pro 2019 Monterey 12.3. But since a few weeks, it doesn't work anymore, I don't know if it's related to the 12.3. 

 

The Capitalize function does appear on Alfred (photo 1) but as soon as I try to type or paste a word it goes to google search (which is my default search on Alfred - photo 2). Would you have any advices on how to make it work again ? 

I tried to delete and reinstall the workflow without success.

 

Regards, 

Joseph 

[Vero]

@Marlouis Welcome to the forum

 

This post summarises why you're seeing the change in macOS 12.3; In short, Apple have removed the Python 2 scripting language, which is used behind the scenes by the workflow you're using.

 

https://www.alfredapp.com/blog/guides-and-tutorials/python-2-workflows-on-macos-monterey-12-3/

 

The creator of this workflow has already updated it for Python 3, so take a look at the first post of this thread for details:

 

As @dfay opted for Python 3, you'll need to set this up on your Mac as well. If you're not familiar with the process, I'm sure community members will be able to help you out. 

[dfay]

@Vero is there a process to set up Python 3 in Monterey?  I just used the shebang above & it just worked.

Edited April 6, 2022 by dfay

[vitor]

9 minutes ago, dfay said:

is there a process to set up Python 3 in Monterey?  I just used the shebang above & it just worked.

 

If you’re using /usr/bin/python3, it should just work if the user already has the Developer Tools (DT) installed. If they have Homebrew, they have the DT. If they don’t have the DT, that shebang will trigger macOS to show a GUI prompt to install them in two clicks.

There’s a rare chance that the user will instead get a variant of xcrun: error: invalid active developer path. The cause seems to be a macOS update breaking the previously installed DT. xcode-select --install in the Terminal fixes it.

Edited April 6, 2022 by vitor

[Chris Messina]

On 4/5/2022 at 8:04 AM, Marlouis said:

The Capitalize function does appear on Alfred (photo 1) but as soon as I try to type or paste a word it goes to google search (which is my default search on Alfred - photo 2). Would you have any advices on how to make it work again ? 

 

@dfay there's a bug (typo) in your Workflow:

 

 

[Southgirl]

Installed the newest update for MacOS 12.3, it's working again. Thanks!

[dfay]

On 4/16/2022 at 2:45 PM, Chris Messina said:

 

@dfay there's a bug (typo) in your Workflow:

 

 

 

Thanks - just posted an updated version.

[Marfa]

Hi @Dfay, could you please take a look at this question?

 

[jackk]

I was using another case workflow before, just wondering if this workflow is able to show what's in the clipboard before pasting Example (Photo1)

[dfay]

Yes, see the first post in this thread.

[winterflags]

On 4/24/2022 at 7:39 AM, dfay said:

Yes, see the first post in this thread.

 

Given:

 

//a[contains(@href, "UPPERCASE")][contains(@href, ".pdf")]

 

the script appears to insert backslash characters (\) on four locations below:

 

//a[contains\(@href, "uppercase"\)][contains\(@href, ".pdf"\)]

 

Any way to fix this?

Edited October 18, 2022 by winterflags

[dfay]

I can't replicate it - 

I get the same results launching from hotkeys.

[vitor]

There’s a very small typo in the Title Case Universal Action: it’s TItle Case (uppercase i).

[arielylim]

First, thanks for this workflow. Been a lifesaver for someone who does content. 

 

One request though - can you take a look at the workflow again? I recently upgraded to Ventura (13.0) and it broke again. When I do the cc workflow, it starts off correct

 

but when I try to enter a text, it tries to search for it on the internet.    

 

 

If I remember correctly, this was the same behavior before you made the update in March. But now, it broke again Hope you can make a fix. 

 

[vitor]

@arielylim I suspect you might need to open a terminal and do xcode-select --install. A macOS dialog will guide you through the rest. The upgrade to Ventura would have been the cause.

[dfay]

Thanks @vitor - it's working for me on two Macs both running Ventura so it's hard for me to test here.

[arielylim]

On 10/30/2022 at 5:28 PM, vitor said:

@arielylim I suspect you might need to open a terminal and do xcode-select --install. A macOS dialog will guide you through the rest. The upgrade to Ventura would have been the cause.

I didn't realize my upgrade to Ventura deleted my previous install 🤦‍♂️ This install got it to work again. Thanks! 

[christianmagill]

Very useful!

 

Could you add an option to create safe strings?... like

 

"The Quick Brown Fox" -> "the_quick_brown_fox" 

"The Quick Brown Fox" -> "the-quick-brown-fox" 

 

Useful for programming and urls

Edited December 16, 2022 by christianmagill

[Mindstormer]

First of all, brilliant workflow. Tremendously useful.

 

I think I've come across two bugs:

 

1. Title case conversions do not work correctly when starting with UPPER CASE TEXT.

When I paste in a lower-case line of text, conversion to title case works fine.

When I paste in an upper-case line of text, it only converts the first word to title case, leaving the rest of the sentence capitalized.

 

2. The sentence case doesn't seem to recognize that the pronoun i should be capitalized.

Edited April 12 by Mindstormer

[David H]

When all letters are already capitalized, Title Case in Case Converter doesn't work. (Thanks for the workflow!)

[vitor]

On 4/12/2023 at 10:55 PM, Mindstormer said:

Title case conversions do not work correctly when starting with UPPER CASE TEXT.

 

37 minutes ago, David H said:

When all letters are already capitalized, Title Case in Case Converter doesn't work.

 

That’s a decision, not a bug. It’s quite common for case converters to make that choice, because otherwise acronyms get mangled. A way to work around, if you know your text doesn’t have acronyms, is to lowercase first then title case.

[David H]

19 hours ago, vitor said:

That’s a decision, not a bug. It’s quite common for case converters to make that choice, because otherwise acronyms get mangled. A way to work around, if you know your text doesn’t have acronyms, is to lowercase first then title case.

Oh, I didn't know that. Thanks for your answer. 

[Viming]

The word `with` should be lower-cases in Title Cases. 

[Toffy]

On 5/18/2023 at 9:21 PM, vitor said:

On 5/18/2023 at 8:42 PM, David H said:

When all letters are already capitalized, Title Case in Case Converter doesn't work.

 

That’s a decision, not a bug. It’s quite common for case converters to make that choice, because otherwise acronyms get mangled. A way to work around, if you know your text doesn’t have acronyms, is to lowercase first then title case.

 OMG, thanks for clarifying this. This behaviour was driving me nuts. I kept checking the config, uninstalling and reinstalling the workflow...

I didn't realize this behaviour was specific to all Caps because all Caps is all I use the workflow for.

 

IMHO it makes more sense to let the converter treat acronyms wrong (and the user fixes it manually) rather than not doing anything at all.

 

Or here is a suggestion: If I understand it correctly, workflows doesn't touch words that are all Caps, right? My use case is that I often have the entire text all Caps and I'd say at least for that case it makes sense to make an exception to the exception and apply title case. So: if single words are all Caps, OK, leave them alone. But if the entire text (or, say more than 90 percent) is all caps, then apply titlecase anyway.