Merci pour votre ré ponse,

A lot of people believe that what I am talking about is just the ability to display in various languages. So I have changed the name to TROWSERS which stands for translating browsers.

Till date all our effort in multilingualism has been concentrated on keyboard mapping for different characters and display of different characters on screen (like different fonts).

For the applications where your company provided multilingual support to operators, I am sure that the HMI application had two sets of display text messages and if language = this then message= this
type of support.


In a short while, a large number of PLC's would become web PLC's and so a large number of Browser SCADA's will come about. So we can expect Linux PLC in a few years to support data transport to the web server area, where an apache server could authenticate and enable exchange of data over the web and browser SCADA can read the data. Now if we try to support multilingualism through conventional means, then we are talking about wastage of a large amount of resources. All that is needed is that the PLC send a code and the browser interprets the code in the language that the user is conversant with.

Now let me elaborate further, Suppose that we have six friends:
An English speaking person,
A German friend
un ami francais
An Hindi indian and
a Chinese

If we were to facilitate communication between these people, then we need five different keyboard maps, five interpreters and oh so much more!!!

But suppose you wrote How are you? in english and your web-server/ or browser converts this to
code 123456789098 and there is a HTML tag called <langcode> 123456789098 </langcode>
And the user browsers read this code and translate it to Comment Allez vous? in the french browser Aap kaise hain? in devanagari script for the hindi person and in chinese and german in their respective browsers.

And when the respective persons type in their language, then the same gets translated to english and you are able to read it.

What I mean is not just key mapping or making characters available on display, but entire phrases and messages translated in languages using codes.

Plus this also provides the benefit of reduced web traffic. Had this already been in place then the LINUX PLC documentation need only have been writen in one language and there would have been automatic translation to all others.

I hope i am able to clarify what I wanted to say in the original message.

Anand


--
------------------------------------------------------------------------
Visit www.smbd.org <http://www.smbd.org> for
Free Tutorials, Source Codes and Other stuff.
------------------------------------------------------------------------



_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc

 

Anand:
> What I mean is not just key mapping or making characters available on
> display, but entire phrases and messages translated in languages using
> codes.

> Plus this also provides the benefit of reduced web traffic. Had this
> already been in place then the LINUX PLC documentation need only have
> been writen in one language and there would have been automatic
> translation to all others.

Try babelfish.

If language translation was that simple, everybody would be doing it. It isn't, especially for short messages like that. You need a lot of context to translate short messages.

When I get around to kicking t-mail into working, you'll see what I mean.


Jiri
--
Jiri Baum <[email protected]> http://www.csse.monash.edu.au/~jirib
MAT LinuxPLC project --- http://mat.sf.net --- Machine Automation Tools
tlhIngan Hol jatlhlaHchugh ghollI' Hov leng ngoDHommey'e' not yISuD
Never bet on Star Trek trivia if your opponent speaks Klingon. --Kung Foole

_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc

 

It is even worse because in most cases you are talking about technical translation.

There are also a lot of application specific translations. How many times have you used a good (human) technical translator only to have the customer change a load of these translations at the last minute because as good as they are they aren't quite what is required ?

And that's assuming a good translator, I'm sure that every body has their own favorite miss translations (try Hydraulic Ram == Water Goat, or the translation of 'Well Head' to something that meant the opposite of a sick head).

Regards
Mark Hutton


_______________________________________________
LinuxPLC mailing list
[email protected]
http://linuxplc.org/mailman/listinfo/linuxplc