My suggestion

Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic

   Hello,

So many multilanguage issues in the forum!

A step by step procedure for creating  multilangauge supported application would be really helpfull.

Just my idea. Thanks.

Raver

Author	Message Topic Search Topic Options Post Reply Create New Topic Printable Version Translate Topic
Raver Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 13 June 2007 Status: Offline Points: 7	Post Options Post Reply Quote Raver Report Post Thanks(0) Quote Reply Topic: My suggestion Posted: 07 July 2007 at 12:43am
	Hello, So many multilanguage issues in the forum! A step by step procedure for creating multilangauge supported application would be really helpfull. Just my idea. Thanks. Raver

Kenneth Members Profile Send Private Message Find Members Posts Add to Buddy List Senior Member Joined: 23 May 2004 Location: United States Status: Offline Points: 256	Post Options Post Reply Quote Kenneth Report Post Thanks(0) Quote Reply Posted: 07 July 2007 at 12:19pm
	I agree, however the problem is there are several competing thoughts on how to add multi-lingual support and how the Codejock toolkit is used (dll or static linked). If using MFC, is it static linked? Some of these questions depend upon what has to be supported. For example, if you must support unicode on all systems (such as Windows 98/ME) then everything has to be static linked. Should a base language be included in the executable and all other languages contained within resource (satelite) dll's, or should all languages be in resource (satelite) dll's and none in the .exe? An application can have large resource requirements! Will be translation itself be done from the .exe and or resource dll's or should the resource.rc be used. A lot of assumtions is being made in the toolkit multi-language samples which I think is causing some of the confusion. Most companies I am aware of in general use static linking of the toolkit and all language dependent stuff is put in resource dll's. No language dependent stuff is in the .exe itself. In the past, we have always translated from the resource.rc files. However the author of appTranslator http://www.apptranslator.com has almost convinced me it is best to translate from the .exe or resource dll's. So I would also really like to see a step by step procedure, with consideration for the various competing methods.

shobits1 Members Profile Send Private Message Find Members Posts Add to Buddy List Newbie Joined: 18 June 2007 Location: Algeria Status: Offline Points: 16	Post Options Post Reply Quote shobits1 Report Post Thanks(0) Quote Reply Posted: 08 July 2007 at 9:21am
	It is good idea, And I think it saves time and reduce question for all members.