Re: Diacritic accents not displaying properly

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

Thanks. It's a pretty complex mechanism :-)

Unicode is a very powerful tool, but with great power comes an even greater
ability to get into almost all the trouble there is. Unicode works
brilliantly for those folks who "just type". Those of us who need to get a
bit more adventurous can benefit from spending a bit of time understanding
the mechanism :-)

In Preferences>Compatibility, there's a box "Check documents for
compatibility". If you uncheck that, you will see the compatibility report
only if you ask for it.

Hope this helps

On 7/02/08 8:47 AM, in article ee8be51.16@xxxxxxxxxxxxxxxxxxxxxxx,
"alientango@xxxxxxxxxxxxxxxx" <alientango@xxxxxxxxxxxxxxxx> wrote:

wow john, that's a fantastic explanation, thanks! helps a lot with
understanding how it works.

speaking of unicode, could i just ask if anyone knows how to get rid of the
compatibility check? every time i type a unicode character, Word automatically
checks and the blinking red icon annoys the heck out of me. is there any way
to turn it off, now that i know that "the document contains characters that
might not display correctly in earlier versions of Microsoft Office for
Macintosh"? i mean, i do not care if it isn't compatible, i pdf all my docs to
print or to send anyway.

i'm asking since i once tried to click on the "never show again" button and
the doc just refused to display all my characters, so i had to reset the
compatibility check. plus, i don't want to do anything silly and end up having
to troubleshoot it in the end. grateful for any help!

thanks again!

--
Don't wait for your answer, click here: http://www.word.mvps.org/

Please reply in the group. Please do NOT email me unless I ask you to.

John McGhie, Consultant Technical Writer
McGhie Information Engineering Pty Ltd
http://jgmcghie.fastmail.com.au/
Nhulunbuy, Northern Territory, Australia
+61 4 1209 1410, mailto:john@xxxxxxxxxxx

.

Relevant Pages

  • Re: Locales and CString::MakeUpper() and CString::CollateNoCase()
    ... Why else would we have C compatibility in the C++ language? ... And nothing about Unicode. ... No changes in the API to deprecate operations per character. ... Unicode is not the only encoding. ...
    (microsoft.public.vc.mfc)
  • Re: Linux Unicode Passwords
    ... Apart from the previouly mentioned troubles, using Unicode for passwords ... eight characters out of the ASCII alphabet ... what a lot of trouble only about 7 special characters are (in my country ...
    (comp.os.linux.development.system)
  • Re: Unicode in Delphi/VCL (yet again)
    ... Backward compatibility cost us so much money over the years. ... we intend to produce a Unicode VCL. ... > I think D7 should be shipped from now on with all future Delphi SKUs. ...
    (borland.public.delphi.non-technical)
  • Re: Nick, heal the pain of the loyal Delphi community
    ... Here comes the refcounting in, which would require another string type, incompatible with Windows BSTR's. ... There are several unicode components for delphi already, I'm sure they work someway with the current compiler. ... The same change, to managed WideStrings for Win32, would break the ActiveX compatibility. ...
    (borland.public.delphi.non-technical)
  • Re: Locales and CString::MakeUpper() and CString::CollateNoCase()
    ... Why else would we have C compatibility in the C++ language? ... And nothing about Unicode. ... 8, 16, and 32 bit characters. ... I have asked about improving international support. ...
    (microsoft.public.vc.mfc)