 |
 | Home | Contact Us | FAQ | Search & Site Map | Link to Us |
 | Sign In | Join | Other 45 Sites in Network |
Mac Forum / Applications / Word / May 2008Default formatting of pasted text
As revealed in the Paste options button, formatting of pasted text defaults to "Keep Source Formatting". The other two options available to those willing to use the intrusive, time-consuming Paste options button are "Match Destination Formatting" and "Keep Text Only". In Word 2004, I used a lifesaver of a one-line macro that instructed the Paste command to default to text only. But as we know and regret, support for macros has been stripped from Word 2008. Question: Under Word 2008, is there any way to set the default formatting of pasted text to anything other than "Keep Source Formatting"? That seems to me like an eminently obvious candidate for an overall preference you change once. I can't imagine the current fix- as-you-go approach as the only option, but I have been unable to find how to change it. As someone who pastes into Word from other sources all the time, having to fix unwanted formatting at every turn is truly a deal- breaker. Patricio Mason Santiago, Chile It doesn't change the default setting, but you can assign cmd-v to use the script to paste unformatted. Various options here: http://word.mvps.org/mac/Scripts/PasteTextAS.html You might be one to prefer the Tidbits variant, linked from there, otherwise the cursor flips back to the beginning of the paste. Send Feedback to request a preference. Considering the demand for this, I think it must be more complicated to implement than we imagine. > As revealed in the Paste options button, formatting of pasted text > defaults to "Keep Source Formatting". The other two options available [quoted text clipped - 18 lines] > Patricio Mason > Santiago, Chile On May 21, 3:27 pm, Daiya Mitchell <daiyaNOS...@mvps.org.INVALID> wrote: > You might be one to prefer the Tidbits variant, linked from there, > otherwise the cursor flips back to the beginning of the paste. Great stuff; that'll do for now. > Send Feedback to request a preference. Sure will. Thanks! On May 21, 3:27 pm, Daiya Mitchell <daiyaNOS...@mvps.org.INVALID> wrote: > It doesn't change the default setting, but you can assign cmd-v to use > the script to paste unformatted. Various options here:http://word.mvps.org/mac/Scripts/PasteTextAS.html > > You might be one to prefer the Tidbits variant, linked from there, > otherwise the cursor flips back to the beginning of the paste. Well, trouble in paradise. Neither script works in Preference windows. I tried to paste a term into the AutoCorrect panel and the scripts just won't work. Instead, they keep pasting into the (now inactive) document window. "Paste from Scrapbook" (Command-Shift-V) works, for some reason. However, neither script will do smart pasting, i.e. add spaces as needed. Smart pasting prevents words from bunching together ("takentogether", for example) and will correctly add a space to produce "taken together". The scripts won't do this, unfortunately. MacBU, please make this a preference ASAP. > Well, trouble in paradise. Neither script works in Preference windows. > I tried to paste a term into the AutoCorrect panel and the scripts > just won't work. Instead, they keep pasting into the (now inactive) > document window. "Paste from Scrapbook" (Command-Shift-V) works, for > some reason. > Interesting, but I suspect an inherent limitation of AppleScript. But, why would you need a Paste *Unformatted* into the AutoCorrect window? Your problem here sounds to be that you will have to learn to use at least two different commands for pasting, so assigning cmd-V to the script may not work for you. > However, neither script will do smart pasting, i.e. add spaces as > needed. Smart pasting prevents words from bunching together > ("takentogether", for example) and will correctly add a space to > produce "taken together". > Smart pasting should only affect the space right before and right after the paste--which, honestly, you ought to be able to handle yourself. Are you seeing something different? That is, if you copy "takentogether", you will still get "takentogether". If you reliably never enter the space after "taken" before pasting "together", I suppose you could hard-code it in. I doubt there's any way to force the script to invoke Word's smart cut and paste, although a better AppleScripter than me might be able to finesse something that checks for an existing space and changes the script's action depending on it. > MacBU, please make this a > preference ASAP. > You aren't talking to MacBU here, as you know. But you should be sure to explain to them the reasons why the script workaround does not meet your needs, as I suspect issues without a feasible workaround move up the priority list. On May 21, 8:59 pm, Daiya Mitchell <daiyaNOS...@mvps.org.INVALID> wrote: > But, why would you need a Paste *Unformatted* into the AutoCorrect window? I don't, of course. It's simply a matter of having assigned Command-V to the script and expecting it to, well, paste stuff. > Smart pasting should only affect the space right before and right after > the paste--which, honestly, you ought to be able to handle yourself. Since AppleScripts are advertised as the replacement for macro support, I guess I was expecting the script to work the same way as the macro I use in Word 2004. No such luck. > Are you seeing something different? That is, if you copy "takentogether", > you will still get "takentogether". Obviously. What I meant is that if I paste the word "together" right after "taken" without a space, said space gets added by smart pasting. > > MacBU, please make this a > > preference ASAP. > > You aren't talking to MacBU here, as you know. Rhetorical lament only. By now I have the MacBU feedback page bookmarked. > But you should be sure to explain to them the reasons why the script workaround does not meet > your needs, as I suspect issues without a feasible workaround move up the priority list. Interesting take. I'll use it. > Since AppleScripts are advertised as the replacement for macro > support, I guess I was expecting the script to work the same way as > the macro I use in Word 2004. No such luck. > Marketing spin.... No such luck. Macros are internal, scripts are external. A number of issues arise from that. >> But you should be sure to explain to them the reasons why the script workaround does not meet >> your needs, as I suspect issues without a feasible workaround move up the priority list. >> > > Interesting take. I'll use it. > well--in this particular case, I doubt anything will make a difference, since VBA is coming back. But a developer talks about triaging bugs here, and workarounds do make a difference, so it's a good idea to give them the data that the workaround is not sufficient. http://www.schwieb.com/blog/2008/05/13/mac-office-2008-sp1/ |
Reply to this Message |
 Sign In
 Join
 My Latest Posts My Monitored Threads My Blog My Photo Gallery My Profile My Homepage Start New Thread Enable EMail Alerts Rate this Thread
|
©2008 Advenet LLC Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.