🚀 go-pugleaf

Andy wrote:
> I had actually considered calling the babelfish soap service [snip]
> 
> Andrue Cope <not.a.valid@email.address.sorry> wrote:
> >> Is there a standard approach to this problem?
> >
> >If you're talking about comment text then the only solutions are to
> >ignore it or translate it. The latter can be done (with varying
> >degrees of success) by machine.

You could develop a mechanism to identify the language stored in the
field/record with, say, a language field.  'course, that opens all other
sortsa worms to deal with ie. are you allowed to mix languages on a
single stored record ie. each field gets a language code?  Do you let a
French client update a German record/field?  In which language?  Do you
let the French client *see* the German information?  I think a lot of
this depends mightily on your application environment and will require
you to do some major thinking.  

We're a bilingual university so the (mainframe) applications development
group always has two fields for comment type stuff;  English & French. 
Standardized/fixed fields are always codes that have look-ups and
descriptions in both languages.  Fortunately, our programming software
vendor, being multi-national, had thought ahead and provide an
environment-type variable that can be set/queried/changed
programmatically such that, for example, the local paradigm has PF5 key
set to allow the client to switch between the local language values.
---------->  signature = 5 lines follows <--------------
Neil Duffee, Joe Systems Guy, U d'Ottawa, Ottawa, Ont, Canada
telephone:1 613 562 5800 x4585             fax:1 613 562 5161
mailto:NDuffee at uottawa.ca    http://aix1.uottawa.ca/~nduffee
"How *do* you plan for something like that?" Guardian Bob, Reboot
"For every action, there is an equal and opposite criticism."