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
[quoted text, click to view] Thomas Due wrote:
> 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?
>
> --
> Thomas Due
> Posted with XanaNews version 1.18.1.0
>
> "Only sick music makes money today."
> -- Friedrich Nietzsche
