Hello [EMAIL PROTECTED]
On 10-Jul-01, you wrote:
> Applications that are aware of this can then use the new API that comes
> along with this new system.
>
> And then, ON TOP of this system would be new versions of the existing
> diskfont.library (and any other 'old style' API libraries). These new
> versions of old libraries would then allow the 'old style' applications to
> work like they used to, allowing both old and new style to be used at the
> same time.
It would certainly be possible to forcibly map all calls to old routines to
a peice of code that forces Latin1 encoding and sends it to a Unicode
routine: but so many people use applications, fonts and methods that
use customized fonts and libraries that THESE would all break.
Supporting older apps in this way effectively means locking everyone
into US English until their apps support the new libraries.
> Unicode-supporting layer using latin1.
Exactly. And what about, for example, the cyrillic language support people
are using on AmigaOS atm by way of a few support libraries and some
whacky fonts?
> But I guess time is the old enemy - it's probably one of those things that
> are easier said than done.
Sure, it will ALWAYS be easier to force people to use a new API :)
Thanks
--
Matt <[EMAIL PROTECTED]>
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
