🚀 go-pugleaf

Andrue Cope [TeamB] wrote:

> The ITE in BCB6 is completely broken for most people. See:
> 
> http://qc.borland.com/wc/qcmain.aspx?d=1124
> 
> I suggest using the TsiLang components from SiComponents:
> 
> http://www.sicomponents.com/tsilang1.html

Unfortunately, I'm doing this as part of a free software project, so I'm
not really looking to spend a few hundred dollars on a third party
translation tool.

For those that might need the info, I've actually figured out a
workaround for most of the issues.  Getting all the forms to show up in
the project manager can be done by editing the project file manually.
For example:

 <FILE FILENAME="GPGeeConfigure.dfm" FORMNAME="formGPGeeConfigure"
  UNITNAME="formGPGeeConfigure" CONTAINERID="" DESIGNCLASS=""
  LOCALCOMMAND=""/>

When you first add a new language, the single form that will show up in
the project manager will have a FORMNAME of simply "form".  Change that
to something else - I use the form's name property.  You can then add
lines for as many forms as you have.  Do this when the project is NOT
loaded (ie: not through the ide via "Edit Option Source").

You can get the form designer to work by simply copying the .cpp and .h
file for the form into the relevent language module's directory.  The
form designer needs them in order to display the file.  If you change
the .cpp or .h files then you need to recopy them (ie: add components,
etc).  Since I am using Windows XP, I created NTFS hard links as shown:

 [projectdir]\DEU> fsutil hardlink create GPGeeConfigure.cpp
                    ..\GPGeeConfigure.cpp

Do that for each form's .cpp and .h file - for those who aren't
familliar with hardlinks, this creates a second directory entry that
points to the same file.  This makes it so the form editor always is
accessing the original .cpp/.h files and no copying is required.  You
have to be VERY careful, though.  When you are using the form designer
on a language module's form, you MUST NOT add, delete, or rename
components.  That is, you cannot do anything that would cause the form
designer to change the .cpp or .h file.  If you do this then the .cpp/.h
file in your main project will be modified.  Other than this
restriction, the workaround seems to work perfectly.  Double clicking on
the form in a language module still causes the .dfm file too appear as
text in the code editor, but you can now right click and select "View as
form".  Changing text in the form designer also causes the same text to
change in the Translation Manager.

As a last note, I'm sure most people know but I thought I'd mention
here, if you have added a resource source (.rc) file with a string table
to your project, the translation manager will pick up on that and
include it but the actual language module's project file won't have it.
 So make sure you add the .rc files you need to each language's subproject.

Hope this helps - I know it was driving me batty trying to get it to
work for me.

	Kurt Fitzner