Aldo Donetti [MS] wrote:
> Hi Brent, if I have not misunderstood I believe your application is doing
> everything via code and you are not relying on any Delphi-specific
> mechanism. If so, you can do just the same in .Net and probably with code
> which is similar to what you currently have.
> If the data in your table is dynamic and/or can be updated without touching
> the App's code, then I think it's one of many correct approaches but I
> cannot tell you if it's the best or not. Otherwise I would suggest adding
> those strings in resources because they are faster to load.
>
> Aldo
> -- This posting is provided "AS IS" with no warranties, and confers no
> rights.
>
>
> --------------------
>
> | I have a Delphi App that I am rewriting in .net
> |
> | This application manages different species of animals, so many labels
> | are different depending on the species. eg:
> |
> | species offspring
> | =============== ===========
> | horse foal
> | cow calf
> | llama cria
> |
> |
> | in addition, there are translations to each different language.
> |
> | eg: French for the same
> |
> | species offspring
> | =============== ============
> | cheval poulain
> | vache veau
> | lama cria
> |
> | to complicate matters even more, we also had labels change depend on the
> | sex of the animal eg, horse offspring are filly and colt for female/male.
> |
> | In our old app we had a table like this:
> | form, object, property, language, species, sex, text
> |
> | So any specific label is determined from the language->species->sex
> |
> | Can internationalization as implemented in .net deal with this type of
> | situation? Any .net excepted way? Pointers?
> |