Custom localization using an ExtenderProvider

Custom localization using an ExtenderProvider - some hurdles

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Thomas Due - 20 Mar 2006 11:21 GMT

I have decided upon my own localization scheme for my .NET 2.0
applications. The main reason for this, is that I do not want to use
satellite assemblies. There are several reasons for this, which I don't
want to go into now.

The design I have in mind is as follows:

In a separate assembly I have a ExtenderProvider. This provider will be
placed on all forms which should be localized.

Each text is saved into a database designed for this purpose with the
following fields:

Project, Form, Control, Property, TextValue.

An external tool then be used to translate all text values in separate
tables in this database.

Retrieving the name of the form and control is of course not really an
issue. However it turns out that it is quite an issue retrieving the
name of the project assembly at designtime.

I can easily get the name of the assembly in which the extenderprovider
is placed, but what I need is the name of the project which USES the
extenderprovider.

Now how do I get this at designtime?

Signature

Thomas Due
Posted with XanaNews version 1.18.1.0

"Only sick music makes money today."
-- Friedrich Nietzsche

Reply to this Message

rrichardwest@gmail.com - 31 Mar 2006 13:04 GMT

hi
try using StringDB. Very flexible, no need to recompile source for
string changes.

supports x86, ARM, Sparc, MIPS, x51, SuperH
supports Windows CE, Linux, VxWorks, Symbian
supports delphi borlandc++builder .net c# vb .net cf and any platform
that supports c/c++

url: http://www.swbox.com

Once you have used StringDB in your application, 'anyone' can change
the languages and strings with our PC tool. This means you do not need
a software guy for modifications.

Advantages:
- supports ALL languages in the world (ASCII, UNICODE, UTF-8)
- uses MS Excel files for translation
- You can change language and strings without recompiling the software
- Non-technical people can prepare new language releases
- Is being used by embedded devices and also PC software

> I have decided upon my own localization scheme for my .NET 2.0
> applications. The main reason for this, is that I do not want to use
[quoted text clipped - 30 lines]
> "Only sick music makes money today."
> -- Friedrich Nietzsche

Reply to this Message

Thomas Due - 03 Apr 2006 09:22 GMT

>try using StringDB. Very flexible, no need to recompile source for
>string changes.

I appreciate the response, but it isn't really what I was asking about.

I was asking about how I retrieve the project name at design time, not
what localization products are available.

Signature

Thomas Due
Posted with XanaNews version 1.18.1.2

"The advantage of a bad memory is that one enjoys several times the
same good things for the first time."
-- Friedrich Nietzsche

Reply to this Message

Custom localization using an ExtenderProvider - some hurdles

Free Magazines