[1639] in java-interest
More on Javier (Java Version Idioma Espa^ol)
daemon@ATHENA.MIT.EDU (Ing. Carlos A. Osuna Roffe)
Tue Sep 12 04:29:26 1995
Date: Mon, 11 Sep 1995 23:21:37 GMT
To: java-interest@java.sun.com
From: cosuna@giga.com (Ing. Carlos A. Osuna Roffe)
I've noticed that some of you didn't quite catched what I meant on the
translation...(maybe something was lost after those words got past my
internal Spanish-to-English compiler)...
Transalting software and its docs isn't new. You just get the original
source or negatives and just replace what's in English (menus, buttons,
forms, etc.) and replace it in Spanish...something like this goes on when
you have installed a localized version of Windows and all dialog boxes seem
a little confused: with English question and Spanish answers--sort like:
Do you wish to save xxx.yyy?
<Aceptar> <Cancelar>
Most of the time this translations are just a waste of time, cuz people tend
to prefer the original version versus the 'patch'...Sometimes you even find
conflicts with one over the other implementation...Things don't quite work
the same with the 'International' version...
Some of you suggested a lookup table...others thought we would be better off
learning the whole thing in English, and so participate on the community as
a whole...not just this strange experiment called Javier...
This made me thoughtthat you might have missed the point...
We're not looking into a whole new programming environment, nor are we
interested in a dubbed Java using lookup tables...
What we're interested in is a _down-compatible_ system...not an
interoperable environment...
Why? To create Spanish-safe Internet apps (similar to mail, tin and mosaic)
that'll cohabitate (not cooperate) along side Java (English) apps and
applets...just like CBS and NBC live right next to Univision and Telemundo...
To avoid a dual system, all core systems will interoperate in English or
Spanish...alas, all instance variable types and methods are equivalent, that is:
main() {
....
}
would be equal to
principal() {
....
}
down to the 'bytecode' level.
Also
int UnEntero;
may be equal to:
entero UnEntero
Of course, variables and methods are considered a-lingual, since a method
called: ImageMoveRight can't be equal to MueveImagenAlaDerecha...
Any intrenal relationship will be done thru an explicit extension to the
Traduce class...which will convert instance variables and methods to and
from different language classes...
The main thing is that we're specifing language specific Classes via an
specific method called Idioma() equal to Language(), which would return
"Java" for normal programs and "Javier" for spanish equivalents...
I tried to give some Conceptual examples, since Javier hasn't begun as yet
to be developed...Most things here are proyects and not real parts of the
implementation...
I urge you to visit our new Home Page at:
http://www.xmission.com/~cc/javier/
where you will learn more about this new initiative...
Of course, we're still in the process of translating the site, so please
wait a week or two if you don't speak english...please...
Saludos y muchas gracias...
THIS MESSAGE BROUGHT TO YOU BY:
....................................................
Carlos A. Osuna Roffe <cosuna@raza.giga.com>
"We make other BIG SIGNATURES look like one liners"
.............................................and by:
Correo_Clave <cc@xmission.com>
"You don't even need know how to drive to be
on the INFORMATION SUPERHIGHWAY"
......................please visit our HOME PAGE at:
http://www.xmission.com/~cc/
====================================================
MADE WITH CARE AND WITH QUALCOMM'S EUDORA LITE 1.4
-
Note to Sun employees: this is an EXTERNAL mailing list!
Info: send 'help' to java-interest-request@java.sun.com
