TROWSERS

[Anand <akiyer vsnl com>]

Hello friends, list members and contacts

Some time back I made a small browser SCADA. This was a demonstration of
how the browser can itself act as a SCADA or DAS.

I also made a real time trend, but due to some time constraints I couldn't
add finishing touches to it and put it on my website.

I wanted to make my website multilingual. As most websites do, they duplicate
the information in various folders like en for english, fr for french and
so on.
Some information is absent in one language and others in others.
this vast duplication of data makes very little sense.

then I hit upon the idea of putting three new HTML tags 
<langcode> closed by </langcode>
<nolangcode alt=" " native=" "> closed by </nolangcode>
<langnumber> closed by </langnumber>

The translating browser can be called TROWSER to change it from existing
browser specs.

With these new tags people from across the globe can communicate and the
language barrier is broken to microscopic pieces.

Imagine the ability of your company website which can now not be read by
the billions who do not know english,
being able to read the translation in thier language.

Makes good business sense.

---

   The new tag <langcode> will give a twelve digit alphanumeric code. 
 It will be closed by </langcode>

   When there is no equivalent <nolangcode alt="123456789abc" native="french"> 
 which will mean that there is no langcode for this text. the nearest equivalent 
 code is given and the native language or the language in which the text which
 has no langcode was written. this can be closed by </nolangcode>

numbers inside the texts could be written by <langnumber> closed by
 </langnumber>

   Say the alarm tag is "Converter Temperature High 175.25".

In french it may be "Temperature du converter haut (or grand) 175,25" {Note 
 that since i could not get the accent signs in My linux m/c, the text is 
basically incorrect in french, but does convey the message}

And somewhat different in German, spanish, Arabic, Hindi, Marathi and the 
 thousands of languages across the globe.

   Now suppose the server or WEB PLC gives a message indicating the langcode 
 say for example

   <langcode> abc123456789 <langnumber>175.25</langnumber></langcode>

   The browser could have the related messages for the codes stored in the
 language used in the particular PC and the message could be displayed in
the relevant language.

Detailed explaination of the working:
   A standards committee like say the W3C or a new body which is open and
interested makes the langcodes. 
The body establishes  a comprehensive list of codes for common sentences
in every language.
   The table has the following columns:
   A langcode column as a primary key,
   The language which represents the exact meaning for this langcode,
   The languages columns which store the meaning for the langcode in that 
language,  like englist(us), english(uk),french, german, hindi,arabic, persian 
and so  on.

   the browser stores the langcode in the machine. The webtraffic is limited 
 to transmitting langcodes. The browser interpretes the langcode in the native 
 language. The user sees the text in users own native language.

   There are of course limitations that not every phrase could be covered,
 but such messages can be written with code <nolangcode alt="abc213456789" 
 native="english"> No bhai there is no anglais code for this</langcode>
   Where the user sees the message in english "No bhai there is no anglais
 code for this" 
   followed by "nearest Equivalent: There is no English equivalent" in native 
 language.

The browser now has to play a critical role, of converting whatever the  user
types to equivalent codes for transmitting. And on reciept to reconvert  the
messages back to text.

Anand

--

---

Visit www.smbd.org for
Free Tutorials, Source Codes and Other stuff.

---