Spell Check incorrectly catches (TYP.) when a MText Object

[ccowgill]

When I spell check (TYP.) as a dtext object, it says it is spelled correctly, but when it is part of an mtext object, it gets nailed by the spell check, I have several other words that are in my custom dictionary that were over looked as they should have been in 05, but they are getting caught up in 07, even though they should be overlooked. Does any one else seem to have this problem?

Thanks,

[Opie]

When I spell check (TYP.) as a dtext object, it says it is spelled correctly, but when it is part of an mtext object, it gets nailed by the spell check, I have several other words that are in my custom dictionary that were over looked as they should have been in 05, but they are getting caught up in 07, even though they should be overlooked. Does any one else seem to have this problem?

Thanks,
Are you using the same custom dictionary? You can check the DCTCUST (custom dictionary) system variable to find out where it is located.

[ccowgill]

To test my issue, I created a piece of dtext, ran spell check and it said spell check complete, then I used the express tool txt2mtxt and converted it to mtext, and ran spell check again and it came up as a misspelled word.

To answer your question, I havent changed custom dictionaries. It is kind of annoying because I added these words to our dictionary in 05 because they kept comming up, and now that we updated to 07, even though they are still in the dictionary, it is as though the () and . are being ignored in the mtext object

[Opie]

I've tested this on my end and the Spell Checker works correctly. I used a plain TEXT object, an original MTEXT object, and a converted TEXT to MTEXT object (via TXT2MTXT). All objects ran through the spell checker with no problems. The sample text used was (TYP.)

Do you have the latest Service Packs?

[ccowgill]

I've tested this on my end and the Spell Checker works correctly. I used a plain TEXT object, an original MTEXT object, and a converted TEXT to MTEXT object (via TXT2MTXT). All objects ran through the spell checker with no problems. The sample text used was (TYP.)

Do you have the latest Service Packs?

we are running English SP1, and the spell check doesn't seem to work correctly here, is there a spell check hot fix for 2007?

Is it possible that your version for ACDB17.dll is 17.0.116.50? if so, that could be the problem, you have the hot fix for text regeneration installed and we don't, they might have also fixed some issues with the spell check, as it is the same file that back in 05 we needed to replace to fix the spell check issues. Let me know, if that is the case, I will talk to our IT and hopefully she will install the hot fix.

[.T.]

When I spell check (TYP.) as a dtext object, it says it is spelled correctly, but when it is part of an mtext object, it gets nailed by the spell check, I have several other words that are in my custom dictionary that were over looked as they should have been in 05, but they are getting caught up in 07, even though they should be overlooked. Does any one else seem to have this problem?

Thanks,

Do you have TYP. (without parentheses) in your custom dictionary? Mine wouldn't catch it after adding (TYP.) either until I added TYP. without the parentheses, then it worked fine.

HTH

[ccowgill]

In my custom dictionary it is TYP. with no () but it doesn't work fine, what is the version number on your /program files/AutoCAD 2007/acdb17.dll?

[.T.]

In my custom dictionary it is TYP. with no () but it doesn't work fine, what is the version number on your /program files/AutoCAD 2007/acdb17.dll?

17.0.54.110 No service packs yet ( I don't use 2007 in production yet).

[ccowgill]

That is what I figured, .54 means it is pre-service pack1 but if it is 116.50, it has had an additional hot fix installed, that may fix the problem that I am having

[ccowgill]

The additional hotfix did not solve my problem, I guess when all else fails, contact AutoDesk Tech Support, I suppose that is why we are on subscription.

[ccowgill]

Autodesk is aware of the problem. They, however, do not yet have a solution at this time.

[Opie]

Autodesk is aware of the problem. They, however, do not yet have a solution at this time.
It appears that we have a HotFix for this issue. Thanks to Brenda for posting the link.

[ccowgill]

It appears that we have a HotFix for this issue. Thanks to Brenda for posting the link.
Actually, that is a hotfix for 2005, the program that would be part of the hotfix for 07 would have a 17, not a 16 in it.

[Opie]

Actually, that is a hotfix for 2005, the program that would be part of the hotfix for 07 would have a 17, not a 16 in it.
:Oops: Sorry. I should have read the entire page. :?

[ccowgill]

That's alright, the posted date says yesterday, which makes no sense why they would still be putting out hot fixes for 05 (I thought they already fixed the spell check issue in 05 a long time ago), when they are having the same types of issues for 07