Autodesk GIS Design Server

[#1]

Hi,

I'm trying to translate the Generic Application VBasic components to
Spanish, so I'm following the detailed instructions in
localization_guide.pdf.

It seems to be very easy to do:

- download and unzip GenApplNls8000.zip

- translate the resource files in the extraction directory

- create new Nls.LCID_ localizer components in DLLs,
following the sample code that is left in the extraction directory

- register the DLLs

Since it has'nt worked, I have simplified the problem by performing a
MsgBox("...") inside each method in the localizer, so the translation and
resource access is not necessary to ensure the problem correctness. It is
now supposed to appear a message if the localized was ever loaded and used,
but no message has ever appeared.

I have avoided debugging since there are many COM objects implicated and the
source code for the globalizer is not fully available.

To avoid problems with the LCIDs, I have created a class for 40A (for
Spanish), 0 (which is the code that some test applications have returned in
my system), 409 (for English), ...

It is still not working.

May I have forgotten something?

The globalizer is supposed to be codified to always success, even if the
localizer cannot be found. I have seen that every call to
Globalizer.LocalizeString() returns the default_string parameter. Something
is going wrong, but what? There is no error message!

Has anybody experienced similar problems?

What am I doing wrong?



Thank-you in advance,



Antoni Mena.

[#2]

Hi Antoni


The new that you want to implement is obtained internally within the
GenApp application from the Windows API call GetUserDefaultLCID().

Have you tried to set your user locale from Control Panel ,Regional Settings
to corresponds to ?


Lee Chye
Enterprise Support Engineer
Autodesk Professional Services


"Antoni Mena" wrote in message
news:0347D525A6C951A7E2534AC0C2A05A5C@in.WebX.maYIadrTaRb...
> Hi,
>
> I'm trying to translate the Generic Application VBasic components to
> Spanish, so I'm following the detailed instructions in
> localization_guide.pdf.
>
> It seems to be very easy to do:
>
> - download and unzip GenApplNls8000.zip
>
> - translate the resource files in the extraction directory
>
> - create new Nls.LCID_ localizer components in DLLs,
> following the sample code that is left in the extraction directory
>
> - register the DLLs
>
> Since it has'nt worked, I have simplified the problem by performing a
> MsgBox("...") inside each method in the localizer, so the translation and
> resource access is not necessary to ensure the problem correctness. It is
> now supposed to appear a message if the localized was ever loaded and
used,
> but no message has ever appeared.
>
> I have avoided debugging since there are many COM objects implicated and
the
> source code for the globalizer is not fully available.
>
> To avoid problems with the LCIDs, I have created a class for 40A (for
> Spanish), 0 (which is the code that some test applications have returned
in
> my system), 409 (for English), ...
>
> It is still not working.
>
> May I have forgotten something?
>
> The globalizer is supposed to be codified to always success, even if the
> localizer cannot be found. I have seen that every call to
> Globalizer.LocalizeString() returns the default_string parameter.
Something
> is going wrong, but what? There is no error message!
>
> Has anybody experienced similar problems?
>
> What am I doing wrong?
>
>
>
> Thank-you in advance,
>
>
>
> Antoni Mena.
>
>
>

[#3]

I have run that API call within a Visual C++ application and the result
has been "C0A" in hex.
I have already implemented the class "AeScVisualPrjMgrNls.LCID_c0a"
(that is the name taken from the Windows registry) and it is still not
working. The component is not translated and there is no message box
displayed.

What could I do to find where the problem is?
Is all the Globalizer source code available? Where?

Thank-you!!


"Heng Lee Chye" escribió en el mensaje
news:F0BA8B4EC0D07F75412F10E28D9ABC78@in.WebX.maYIadrTaRb...
> Hi Antoni
>
>
> The new that you want to implement is obtained internally within
the
> GenApp application from the Windows API call GetUserDefaultLCID().
>
> Have you tried to set your user locale from Control Panel ,Regional
Settings
> to corresponds to ?
>
>
> Lee Chye
> Enterprise Support Engineer
> Autodesk Professional Services
>
>
> "Antoni Mena" wrote in message
> news:0347D525A6C951A7E2534AC0C2A05A5C@in.WebX.maYIadrTaRb...
> > Hi,
> >
> > I'm trying to translate the Generic Application VBasic components to
> > Spanish, so I'm following the detailed instructions in
> > localization_guide.pdf.
> >
> > It seems to be very easy to do:
> >
> > - download and unzip GenApplNls8000.zip
> >
> > - translate the resource files in the extraction directory
> >
> > - create new Nls.LCID_ localizer components in DLLs,
> > following the sample code that is left in the extraction directory
> >
> > - register the DLLs
> >
> > Since it has'nt worked, I have simplified the problem by performing a
> > MsgBox("...") inside each method in the localizer, so the translation
and
> > resource access is not necessary to ensure the problem correctness. It
is
> > now supposed to appear a message if the localized was ever loaded and
> used,
> > but no message has ever appeared.
> >
> > I have avoided debugging since there are many COM objects implicated and

> the
> > source code for the globalizer is not fully available.
> >
> > To avoid problems with the LCIDs, I have created a class for 40A (for
> > Spanish), 0 (which is the code that some test applications have returned
> in
> > my system), 409 (for English), ...
> >
> > It is still not working.
> >
> > May I have forgotten something?
> >
> > The globalizer is supposed to be codified to always success, even if the
> > localizer cannot be found. I have seen that every call to
> > Globalizer.LocalizeString() returns the default_string parameter.
> Something
> > is going wrong, but what? There is no error message!
> >
> > Has anybody experienced similar problems?
> >
> > What am I doing wrong?
> >
> >
> >
> > Thank-you in advance,
> >
> >
> >
> > Antoni Mena.
> >
> >
> >
>
>