26 April 2001 Unicode and Visual Basi c, IUC 18 (Hong Kong) Unicode and Visual Unicode and Visual Basic: Basic: A Case Study A Case Study Michael S. Kaplan Software Design Engineer Trigeminal Software, Inc. http://www.trigeminal.c om http://www.i18nWithVB.co
21
Embed
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong) Unicode and Visual Basic: A Case Study Michael S. Kaplan Software Design Engineer Trigeminal.
This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Transcript
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
Unicode and Visual Basic: Unicode and Visual Basic: A Case StudyA Case Study
Michael S. KaplanSoftware Design EngineerTrigeminal Software, Inc.http://www.trigeminal.com
http://www.i18nWithVB.com/
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
The purpose of Visual BasicThe purpose of Visual Basic
Making Windows development easierPromote the Windows platform through
ISVs who use itThe "apple in Bill's eye"
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
International support in the International support in the early versionsearly versions
Very limited!Multiple versions of the product codebaseBugs found in one language version often
not fixed elsewhereCertainly NO Unicode support
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
VB 4.0 - a time for choicesVB 4.0 - a time for choices
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
Keep VB in 16 bit, and take Keep VB in 16 bit, and take advantage of the support for advantage of the support for
Win16 applicationsWin16 applications
Easy for VB to doUseless for the Win32 platform itselfNo international support at all
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
Move VB to Win32 entirely, Move VB to Win32 entirely, leveraging the emerging NT leveraging the emerging NT
platform's full support of Unicode platform's full support of Unicode through its "W" APIs.through its "W" APIs.
Great international solutionPoor solution for Windows 95
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
Move VB to Win32 but still with a Move VB to Win32 but still with a code page model rather than a code page model rather than a
Unicode one, using the "A" APIs.Unicode one, using the "A" APIs.
Easiest to doLess multilingual support
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
A hybrid technique ("A" APIs A hybrid technique ("A" APIs on Win9x, "W" APIs on NT)on Win9x, "W" APIs on NT)
Most complicated to doBest international supportGood leveraging of the best features of each
platform
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
What the VB team actually didWhat the VB team actually did
Using COMPorting the original VBWorking with the volume platform
(Windows 95)
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
Where COM fits inWhere COM fits in
Benfits to VB by using COMBenefits to COM by VB being a client
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
The birth of "UniMess"The birth of "UniMess"
An attempt to keep the conversion from VB3 to VB4 simple
From simplicity comes confusion
26 April 2001 Unicode and Visual Basic, IUC 18 (Hong Kong)
The cousin of UniMess:The cousin of UniMess:Using LCIDs for code pagesUsing LCIDs for code pages