Hi Kevin:
It is "certain" that string operations in the Visual Basic for Applications
are NOT Unicode-enabled. It's not the editor that's the problem, it's VBA
itself: it can't manipulate double-byte strings natively.
The really bad news is that this is because Microsoft wants VBA to go away
(as does a lot of the industry). VBA was designed when people were nice and
computers were not connected to the Internet. In today's toxic
virus-infested network soup, VBA cannot be made sufficiently secure, due to
the way it was designed.
Microsoft is attempting to replace VBA with VB dot-Net. I won't go into it
here except to say that it's a "much better idea". It is secure by design,
and much richer and more powerful than VBA was.
Now, the really really bad news is that Microsoft has "no plans" to migrate
..Net to its Office:Mac platform. And what that really means is they
actually have detailed plans, including costings, and they are waiting for
there to be sufficient interest in .Net solutions development on the Mac to
warrant the cost of the transition.
Given that the cost involved would probably exceed the cost of building
Office for the Mac, I think .Net on the Mac is unlikely in the foreseeable
future.
However, if you ask Paul Berkowitz, who inhabits this newsgroup, he would
tell you all about AppleScript. AppleScript is here now and Office-wide on
the Mac. I am sure the AppleScript compiler is Unicode-enabled. Paul will
tell us whether it will (easily) do Unicode operations in Word.
AppleScript in MS Office Mac is a little bit of a "work in progress". Most
of it is there, but there are some limitations where the AppleScript is
effectively calling in to the Word executable using the same API as VBA
uses, so things that are not possible in VBA are not necessarily possible in
AppleScript.
Hi
I have a macro that changes one group of weird characters to another.
Now that there is unicode, I want to edit the macro so that the 2nd
set of weird characters is a set of unicode characters.
But when I paste or otherwise try and input a unicode character, I get
"?". Is it possible that MS hasn't made the macro editor unicode
aware? If so, amazing, and, what do I do?
Thanks
Kevin
--
Please reply to the newsgroup to maintain the thread. Please do not email
me unless I ask you to.
John McGhie <
[email protected]>
Consultant Technical Writer
Sydney, Australia +61 4 1209 1410