Insert/replace Scripture reference in Word on a Mac no longer working

Page 2 of 2 (29 items) < Previous 1 2
This post has 28 Replies | 6 Followers

Posts 18987
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Sun, Jan 3 2021 3:45 PM

Donnie Gullion:
That change in a MS Word shortcut doesn't sound encouraging.  One would think MS would be highly unlikely to change a shortcut on their side.

Possibility is recent Word update stopped sending COMMAND+Shift+E to macOS services (since keyboard shortcut was handled by Word).

Microsoft support has Keyboard shortcuts in Word (with operating system selector) that includes macOS:

  • Turn change tracking on or off. COMMAND+Shift+E

Appears COMMAND+Shift+U and some more key combinations do not conflict with Word for Microsoft 365 on macOS

Keep Smiling Smile

Posts 9
Donnie Gullion | Forum Activity | Replied: Mon, Jan 4 2021 6:10 AM

Thanks!  When I get some time I'll update to the current Word and see if I can change shortcuts.  Assuming I understood you correctly.

Posts 485
Jonathan Bradley | Forum Activity | Replied: Mon, Jan 4 2021 7:00 AM

Keep Smiling,

So did you get it to work on Word?

Posts 18987
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Mon, Jan 4 2021 7:41 AM

Jonathan Bradley:

Keep Smiling,

So did you get it to work on Word?

Apologies for me not having Word 365 (free alternatives are adequate for me).

Keep Smiling Smile

Posts 3
Travis Ulrich | Forum Activity | Replied: Sat, Jan 16 2021 11:20 AM

The problem here is not a conflict in shortcut keys, it's a problem with how Microsoft Word is interacting with the OS services. To test where the problem is, I changed the Text service from "Replace with Passage" to "TextEdit Window Containing Selection" to see what is actually being passed from Word. The result of that was an error from TextEdit stating:

Service failed. Couldn’t open the selection. There might be an internal error or a performance problem, or the source application may be providing text of invalid type in the service request. Please try the operation a second time. If that doesn’t work, copy/paste the selection into TextEdit.

If Logos doesn't receive something it can parse as a passage reference, it doesn't do anything (I believe that's why you could never use "Replace with Passage" in when the reference is the first characters of a bulleted list), so it just appears like the Text Service isn't working in Logos. In reality, the problem is on Microsoft's side, and if they're not sending the correct payload to the service, I doubt that there's anything Logos can do to fix it (other than inform Microsoft of the problem).

OS: 10.15.7
Word: 16.45
Logos: 8.17.0.0022

Posts 97
Christopher Powell | Forum Activity | Replied: Sat, Jan 16 2021 11:34 AM

Thanks Travis - this is I believe the correct diagnosis.  I have temporarily switched to Apple's Pages where it still works.  

Perhaps since the two companies are so geographically close together, some of the Logos developers can chat with their friends at Microsoft to help accomplish this bug fix.  Or so we can dream :-) 

Posts 9
Donnie Gullion | Forum Activity | Replied: Sat, Jan 16 2021 5:25 PM

Travis Ulrich:

The problem here is not a conflict in shortcut keys, it's a problem with how Microsoft Word is interacting with the OS services. To test where the problem is, I changed the Text service from "Replace with Passage" to "TextEdit Window Containing Selection" to see what is actually being passed from Word. The result of that was an error from TextEdit stating:

Service failed. Couldn’t open the selection. There might be an internal error or a performance problem, or the source application may be providing text of invalid type in the service request. Please try the operation a second time. If that doesn’t work, copy/paste the selection into TextEdit.

If Logos doesn't receive something it can parse as a passage reference, it doesn't do anything (I believe that's why you could never use "Replace with Passage" in when the reference is the first characters of a bulleted list), so it just appears like the Text Service isn't working in Logos. In reality, the problem is on Microsoft's side, and if they're not sending the correct payload to the service, I doubt that there's anything Logos can do to fix it (other than inform Microsoft of the problem).

OS: 10.15.7
Word: 16.45
Logos: 8.17.0.0022

Thanks for looking into this.  Seems as though you found the problem.  Unfortunately getting MS to "fix" for Logos that may unfix something they want seems to be hoping for a lot.  But we can and must!

As stated before, I'm just refusing to update to the current Word version since the one I'm using does what I want.

Posts 3
Travis Ulrich | Forum Activity | Replied: Sat, Jan 16 2021 7:46 PM

Donnie Gullion:

Unfortunately getting MS to "fix" for Logos that may unfix something they want seems to be hoping for a lot.

The upside of this issue is that this is not just broken for Logos, but for all Mac OS services that receive "text" as an input. So maybe since it's a broader issue it might make it on their radar. We can hope!

Posts 3
Travis Ulrich | Forum Activity | Replied: Sat, Jan 16 2021 8:01 PM

UserVoice issue linked here: https://word.uservoice.com/forums/304942-word-for-mac/suggestions/42328090-possibly-an-issue-caused-by-the-update-to-big-sur

Vote and or comment to get this issue some exposure.

Page 2 of 2 (29 items) < Previous 1 2 | RSS