Jump to content
Software FX Community

Localization of the .Net Client Component


User (Legacy)

Recommended Posts

Posted

We are starting to internationalize our web-based app and I'm looking into 

doing that for the third-party controls we license. I saw in another post a

claim that Internet Explorer doesn't support localization of hosted .Net

controls. Therefore the ChartFx control doesn't isn't localizable.

First off is this true? Shouldn't it be possible to set a property on the

server side and have it load the right strings on the client even if this

means the client download is bigger. Perhaps strings can be set to

softwareFx and compiled into the DLL.

If not does SoftwareFx have a strategy for translating the client compenent.

This is a big deal for us and my force to investigate alt components.

Posted

> I saw in another post a claim that Internet Explorer doesn't support 

> localization of hosted .Net controls.

> First off is this true?

The way localization works in .NET is pretty much transparent for component

vendors (there is almost no code written in our control). The .NET framework

handles loading the satellite assemblies depending on the current thread

culture. We also expose a property to force a specific language but

everything is else is taken care of by the .NET framework.

We have tried to apply the same approach to .NET controls hosted in IE and

have been unable to get even a request to the server to donwload any

satellite assemblies.

> Shouldn't it be possible to set a property on the server side and have it

> load the right strings on the client even if this means the client

> download is bigger.

We are not worried about client download size as we could download the

localized assemblies on demand as we do our extensions. The issue would be

that currently the code that loads strings/dialogs does not have to do

anything special to use a localized assembly. We will research again this

issue to see if we can provide a workaround

> Perhaps strings can be set to softwareFx and compiled into the DLL.

> If not does SoftwareFx have a strategy for translating the client

> compenent.

We provide localized versions for Japanese, Korean, Spanish, German,

Italian, French, Portuguese and Simplified Chinese (check our site for

updates to this list).

If you need to localize in a different language we can provide a set of DLLs

so that you can test your localization, after you do this you will have to

send us the resources as satellite assemblies need to have the same strong

name as the original assembly.

--

Regards,

JC

Software FX Support

"Brad Patton" <fred@flintstone.com> wrote in message

news:nW7XJnxqEHA.3984@webserver3.softwarefx.com...

> We are starting to internationalize our web-based app and I'm looking into

> doing that for the third-party controls we license. I saw in another post

> a claim that Internet Explorer doesn't support localization of hosted .Net

> controls. Therefore the ChartFx control doesn't isn't localizable.

>

> First off is this true? Shouldn't it be possible to set a property on the

> server side and have it load the right strings on the client even if this

> means the client download is bigger. Perhaps strings can be set to

> softwareFx and compiled into the DLL.

>

> If not does SoftwareFx have a strategy for translating the client

> compenent. This is a big deal for us and my force to investigate alt

> components.

>

>

Archived

This topic is now archived and is closed to further replies.

×
×
  • Create New...