From owner-freebsd-hackers Fri Jun 12 11:15:01 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA06324 for freebsd-hackers-outgoing; Fri, 12 Jun 1998 11:15:01 -0700 (PDT) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from mrelay.jrc.it (mrelay.jrc.it [139.191.1.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA06298 for ; Fri, 12 Jun 1998 11:14:43 -0700 (PDT) (envelope-from nick.hibma@jrc.it) Received: from elect8 (elect8.jrc.it [139.191.71.152]) by mrelay.jrc.it (LMC5688) with SMTP id UAA28712; Fri, 12 Jun 1998 20:14:33 +0200 (MET DST) Date: Fri, 12 Jun 1998 20:08:30 +0200 (MET DST) From: Nick Hibma X-Sender: n_hibma@elect8 Reply-To: Nick Hibma To: Terry Lambert cc: FreeBSD hackers mailing list Subject: Re: internationalization In-Reply-To: <199806121738.KAA13739@usr02.primenet.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > Could someone translate this into a language called English? Some people > > on this list are non native speakers of English, like myself, and have > > a 'syntax error' or 'decoding error' on the fragment below. > > If you could give a specific fragment, I could "translate" it for > you; the "fragment" you attached was rather large: a whole message. No thanks, my English is well^H^H^H^Hgood enough. :) > A translation would be too large for this list, especially given > the fact that it would be a repost of the same information, and that > the information itself is dangerously close to being off topic, > like this post. 8-). Oh well, let's climb the barricades then. > Discussions of highly technical issues require *precise* language. > This is why all highly technical fields develop their own jargon. Highly technical, as in: ilk, bigotry, premise? :-) Nope, that was an excursion into the land of poetry and was definitely not within the jargon of the topic being discussed. I was referring to 'some ilk' vs. 'some sort' (fancy language) rather than "Why cannot we support _both_ the ISO and Unicode paradigms." (jargon) A small child will have no difficulty with the Dutch phrase 'Save File' to save a file, it is appropriately used 'jargon'. Some people, Microsoft for example make the mistake of translating this into 'Bestand Opslaan', which makes it incomprehensible for me _and_ changes the keyboard shortcut. This change moves the language away from jargon and makes life more difficult (for me). Using jargon improves the readability as you say. > For comparison, consider someone wanting/usr/src/sys/i386/i386/locore.s > be written in C instead of 386 assembly so that more people could > understand it. It could probably be done, with a small number of > inlines, but it would not be very efficient to do it. Another example: writing Apache in C++. But, let's stop the thread before someone finds a way to attach a hammer object that just knows how to hit you to an e-mail. Nick Hibma P.S.: It's Feierabend. I go for a gin&tonic. STA-ISIS, T.P.270, Joint Research Centre, Italy building: 27A tel.: +39 332 78 9549 fax.: +39 332 78 9185 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message