From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: weis Received: (from weis@localhost) by pauillac.inria.fr (8.7.6/8.7.3) id WAA14237 for caml-redistribution; Thu, 28 Oct 1999 22:33:10 +0200 (MET DST) Received: from nez-perce.inria.fr (nez-perce.inria.fr [192.93.2.78]) by pauillac.inria.fr (8.7.6/8.7.3) with ESMTP id UAA07787 for ; Thu, 28 Oct 1999 20:01:14 +0200 (MET DST) Received: from mail.nap.com.ar (mail-in.nap.com.ar [200.49.40.90]) by nez-perce.inria.fr (8.8.7/8.8.7) with SMTP id TAA12000 for ; Thu, 28 Oct 1999 19:59:35 +0200 (MET DST) Received: from [200.41.180.76] (HELO k-bell.com) by mail.nap.com.ar (Stalker SMTP Server 1.8b3) with ESMTP id S.0003856602; Thu, 28 Oct 1999 14:59:26 -0300 Message-ID: <38188EFB.80C29974@k-bell.com> Date: Thu, 28 Oct 1999 14:59:29 -0300 From: =?iso-8859-1?Q?Mat=EDas?= Giovannini Reply-To: matias@k-bell.com Organization: Script S.A. X-Mailer: Mozilla 4.7 (Macintosh; I; PPC) X-Accept-Language: en,es-AR,es MIME-Version: 1.0 To: Benoit Deboursetty CC: caml-list@inria.fr Subject: Re: Go for ultimate localization! References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: weis I should have read all before letting my fingers twitch, but... ObCaml now :-) Benoit Deboursetty wrote: > All this may be very difficult to implement, I don't know, I am > telling things from the user's point of view. This may also be a project > completely different from what O'CaML wants to focus on. But couldn't the > camlp4 "PreProcessorPrettyPrinter" by D. de Rauglaurde be the beginning of > a solution, at least for parser localization? It would even provide > translations between different localizations of the parser by > pretty-printing, wouldn't it? Localizing the language is not that difficult, but it would involve exposing the abstract syntax to the localizer, and the localizer would have the difficult task of rewriting the parser. This is not as bad as it sounds for indoeuropean languages (the most difficult problem I can think of is the use of cases vs. prepositions, but I can't think of the equivalent of a prepositional phrase in a computer language), but for object-subject-verb languages like Japanese it could be nightmarish. Localizing the libraries can be done the right way, or the easy way. The easy way is to have a dictionary of external-vs-internal names, with the language using only internal names. It could be easy if initially the internal names are the names used by the developer, and external names are added as the localization proceeds. Somehow, this seems wrong to me (because it seems too easy), so I think there must be a "right" way to do it that is absolutely non-trivial. > PPS: Pour "to match sthg against a pattern", existe-t-il une traduction > "officielle" ? Que pensez-vous de "plaquer qqch sur un motif" ? Um, you know, I think that this is pressing things too far. It's the same attitude the Spanish have, trying to find a Spanish word for every technical word out there. The result is doubly bad: on one hand, you're restricting yourself to *translating* instead of *generating* technical language (as is done in the Social Sciences, for instance), and you're letting out people who have no problem with direct imports (we speak routinely of *matchear*, and I have yet to find someone, techical or non, who doesn't "get me"). I'm not afraid of jargon, and I think we in Argentina are used to jargon (we speak dialect anyway, in Buenos Aires). The literal Spanish to your French would be "pegar algo sobre un patrón" (paste sthg over a pattern) but it sounds backwards. Better would be "aplicar un patrón sobre algo" (apply a pattern on sthg), but while it now sounds right it *is* exactly backwards. The best compromise is "matchear algo contra un pattern", and it only translates the normal "part-of-speech" words, leaving order and technical words intact. -- I got your message. I couldn't read it. It was a cryptogram. -- Laurie Anderson