Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsVB SyntaxEnterprise DevelopmentDatabase AccessControlsCOMWin APICrystal ReportDeploymentGeneralGeneral 2
Related Topics
VB.NET / ASP.NETMS SQL ServerMS AccessOther Database ProductsMore Topics ...

VB Forum / COM / March 2005



Tip: Looking for answers? Try searching our database.

Internationalization in Visual basic application

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
rama - 28 Mar 2005 10:44 GMT
Hi,

I developed an application using Visual Basic 6.0. Now I have to support
internationalization and localization.
Is anybody implemented the internationalization in VB6.0? If so, please
provide information on how to implement and tools used?
Your help will be appritiated.

Thanks & Regards,
Rama
Phil - 28 Mar 2005 11:47 GMT
How about using a resource file using stringtables, one per language?

Use the default RES editor from VB6 to create a stringtable, say for the
English US, use the resourceID's to label your strings and refer to
these in your code by using LoadResString(ResID)...

I do this almost daily to make my apps switch from French to English
based on the Windows version.

Phil

rama a écrit :
> Hi,
>
[quoted text clipped - 6 lines]
> Thanks & Regards,
> Rama
rama - 28 Mar 2005 14:27 GMT
Phil,

Thank you. This appraoch will help to handle the text only.
What about the numbers, date,currentcy etc.
What other things to be considered while localization?
Are there any tools to find out all the strings in the application and to
translate to a specified language?

Thanks & Regards,
Rama
> How about using a resource file using stringtables, one per language?
>
[quoted text clipped - 18 lines]
>> Thanks & Regards,
>> Rama
Ralph - 28 Mar 2005 16:29 GMT
>-----Original Message-----
>Phil,
[quoted text clipped - 29 lines]
>>> Thanks & Regards,
>>> Rama

A good place to start.
http://www.i18ngurus.com/
http://www.i18ngurus.com/docs/985072550.html

IMHO: The first step is to religiously separate the front-
end (presentation) from the backend.
Design the data store and stick with it. (ie, don't start
making 'exceptions' depending on locale.)
In most cases you will be better off designing separate
language-specific dialogs and forms for each language and
swapping them out than you will be trying to
build 'dynamic' forms that change shape, font, and size
on the 'fly'.

But that is only my opinion - your mileage may vary.

hth
-ralph
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.