caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Matías Giovannini" <matias@k-bell.com>
To: Benoit Deboursetty <debourse@email.enst.fr>
Cc: caml-list@inria.fr
Subject: Re: Go for ultimate localization!
Date: Thu, 28 Oct 1999 14:41:37 -0300	[thread overview]
Message-ID: <38188ACC.54FBF398@k-bell.com> (raw)
In-Reply-To: <Pine.GSO.4.02.9910260222280.22949-100000@young.enst.fr>

Uh, I'm going to get flamed by off-topicness, but...

Benoit Deboursetty wrote:
>         So, O'CaML handles Latin-1 characters in the identifiers. This
> allows most Europeans, well at least you and me, to use their own
> language; but to me, it has always seemed a bit strange to write a program
> with keywords in English, and identifiers in French. Indeed, I feel
> it's really bogus when I try to read this out loud:
> 
>         "let élément = String.sub chaîne where chaîne = "...
> 
> Do you take the French accent to read this? an English accent? Do you
> switch accents? How do you say "=", "égal" or "equals"? Do you translate
> every word to your mother tongue on-the-fly?

Symbols and numbers in Spanish, "words" (be them identifiers or
keywords) as they are. Accent varies, but normally is Argentinian
English (I can speak acceptable English, with something of an American
English accent). 
This I do when reading programs aloud, or when doing mathematics.

For instance

"Let x be a real such that x >= 0"

is for me "Let <<equis>> be a real such that <<equis mayor o igual a cero>>"

Evidently, the linguistic structures I use for words and concepts are
separated. And I had never been misunderstood, and I never misunderstood
anybody doing this sort of things.

I think all this is fascinating ;-}

-- 
I got your message. I couldn't read it. It was a cryptogram.
-- Laurie Anderson




  parent reply	other threads:[~1999-10-28 20:32 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-15 13:53 localization, internationalization and Caml Gerard Huet
1999-10-15 20:28 ` Gerd Stolpmann
1999-10-19 18:06   ` skaller
1999-10-20 21:05     ` Gerd Stolpmann
1999-10-21  4:42       ` skaller
1999-10-21 12:05       ` Matías Giovannini
1999-10-21 15:35         ` skaller
1999-10-21 16:27           ` Matías Giovannini
1999-10-21 16:36             ` skaller
1999-10-21 17:21               ` Matías Giovannini
1999-10-23  9:53               ` Benoit Deboursetty
1999-10-25 21:06                 ` Jan Skibinski
1999-10-26 18:02                 ` skaller
1999-10-25  0:54               ` How to format a float? skaller
1999-10-26  0:53                 ` Michel Quercia
1999-10-26  4:36         ` Go for ultimate localization! Benoit Deboursetty
1999-10-28 17:04           ` Pierre Weis
1999-10-28 17:41           ` Matías Giovannini [this message]
1999-10-28 17:59           ` Matías Giovannini
1999-10-29  9:44             ` Francois Pottier
1999-10-28 21:00           ` Gerd Stolpmann
1999-10-29  4:29           ` skaller
1999-10-17 14:29 ` localization, internationalization and Caml Xavier Leroy
1999-10-19 18:36   ` skaller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=38188ACC.54FBF398@k-bell.com \
    --to=matias@k-bell.com \
    --cc=caml-list@inria.fr \
    --cc=debourse@email.enst.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).