Style probs: not answered by FAQs

[triley]

HA. I'm way ahead of you. I went into the Customize Keybs control
panel, enter CTL-OPT-RTN, and IT ISN'T ASSIGNED TO ANYTHING... weird
huh? Sure has been working as a great hack for this prob all afternoon,
though. I'm wondering about setting up a simple macro for my RTN key to
simply rope in those other modifiers in Word... would something like
that mess up other stuff...? On the MacWord New link, I added .html to
it and it works fine now... Tim

 

[Daiya Mitchell]

Damn. Mine was unassigned too.

How does it work as a hack? Cntl-opt-return executes a command that unlinks
them (do you have to select first?), or you hit cntl-opt-return as an
alternative to the return key?

Aha, another idea. Just after hitting control-opt-return, pull down the
Undo list from the undo icon on the toolbar, and see if it gives a name to
what just happened, other than "typing."

Control-opt-return did not do anything on the doc you sent me, on my
machine.

Daiya

 

[triley]

good idea: the Undo list says "Undo typing." I've double-checked that
add-ons page and I don't have any of those programs. I could send you a
list of Apps and Utils I guess for you to pick over exactly what's on
this machine... Does Word present weirdly on OSX.3.8 or something?

 

[Daiya Mitchell]

I'm running Word 2004 on X.3.8, no problems like this, and so are a lot of
other people.

The other question we didn't ask--has this been happening ever since you
first installed Word 2004? If not, did you install anything a short time
before you began to see the problem?

And we also forgot to say--create a new user and see if the problem
persists--that might narrow it down some.

It's not uncommon for text created in other programs to freak out like this
when imported to Word, but I've not heard of it happening in Word itself. I
would suggest that somehow the existing para in your Normal template got
changed to imported text, but you tried a new Normal, so that's not it.

I don't know enough about Apps and Utils to flag a potential problem just
because it is also installed, so sending the list to me would not be a good
idea, and I doubt posting it here would yield much (maybe, who
knows)--though you might try turning off TypeIt4Me, or anything else that is
either set in your user Startup or that is stored in Word's startup folder.
The new user should be equivalent to testing the user Startup items, but not
the Word startup items.

By the way:

Find & Replace
^p for paragraph mark does not find these
^l for manual line break does not find these
But ^13 which is an alternate code for paragraph mark does find these--but
F&R ^13 with nothing merged all the text into one line, so I don't think
that's a fix.
Don't know what to do with that info--I got the idea because someone said
that's often the case with imported text, so that's consistent.

 

[triley]

Eureka! I rebooted as a different user, and Word worked FINE, no
problem. So I went back in and singled out all my startup items under
my regular sign-in, and found the culprit: TypeitForMe. Turns out, it
likes to know exactly which programs to hook up with, and I had
FORGOTTEN to unhitch the PREVIOUS edition of Word I'd been using...
once I fixed that, it worked like a charm.

Can't thank you ENOUGH for all the great help you've given me here.
This has been annoying me for weeks now, and it feels GREAT to finally
get on top of it.

PS: Why were you telling me about Find & Replace...?

THANK YOU THANK YOU THANK YOU THANK!!!!!!

 

[Daiya Mitchell]

PS: Why were you telling me about Find & Replace...?

Just randomly commenting.

THANK YOU THANK YOU THANK YOU THANK!!!!!!

Glad you got it solved.

I'll just take as a lesson that I probably should've thought of that a lot
earlier.

Daiya

 

[Daiya Mitchell]

the culprit: TypeitForMe. Turns out, it

likes to know exactly which programs to hook up with, and I had
FORGOTTEN to unhitch the PREVIOUS edition of Word I'd been using...

Ohhh...and I was thinking TypeItForMe was unlikely because I know lots of
people use that and no one else had reported this. Good to know.

DM