[Ham-Mac] OS X development environ Q

[Jerko Golubovic]

>I can't see the purpose of developing a Cocoa app at this point, you're
>ignoring the vast majority of Mac users who don't yet have OSX. Indeed, it
>is still prudent to develop both Carbon and Classic builds of your app if
>possible, since some folks aren't running 8.6 or later.

Classic or Carbon stands for same where Locale support comes in game.
In Roman locale this is not an issue but in others it is.

Classic is script-oriented and there is no way to use Unicode (UTF-8) for 
example. There are problems regarding Microsoft Office nad Croatian 
diacritical signs. Office uses Unicode, I can translate it to MacRoman 
manually, but Office itself does not know how to display special Unicode 
characters.

I downloaded Text.pdf from http://developer.apple.com/ which is 
addressing this problem and what I found inside tells me that even if I 
force system correctly displaying Unicode characters there is no warranty 
of any kind that written text will be properly translated into Unicode by 
Office (since system cannot do that).

It is general mess regarding office documents anyway: older ones use 
Windows EE, newer ones use Unicode.

>From what I heard OS X has Unicode. 

If somebody is interested:
Microsoft Explorer 5 for Mac has available codepage translation tables. 
Just open it with ResEdit and find ISOM resource. Tables are 2-byte, do 
not know if you can add them more but you can certanly modify existing 
ones. 
I did not tested (yet) how it behaves but I will.


Jerko Golubovic
9A6JGJ

APPLE - Think different