From owner-freebsd-questions@FreeBSD.ORG Sat Oct 17 20:07:23 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 29A2B106566B for ; Sat, 17 Oct 2009 20:07:23 +0000 (UTC) (envelope-from af.gourmet@videotron.ca) Received: from relais.videotron.ca (relais.videotron.ca [24.201.245.36]) by mx1.freebsd.org (Postfix) with ESMTP id F33678FC0C for ; Sat, 17 Oct 2009 20:07:22 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=UTF-8 Received: from [192.168.0.51] ([96.21.103.185]) by VL-MO-MR002.ip.videotron.ca (Sun Java(tm) System Messaging Server 6.3-4.01 (built Aug 3 2007; 32bit)) with ESMTP id <0KRO00G3TD894E50@VL-MO-MR002.ip.videotron.ca> for freebsd-questions@freebsd.org; Sat, 17 Oct 2009 16:07:22 -0400 (EDT) Message-id: <4ADA23FD.8020003@videotron.ca> Date: Sat, 17 Oct 2009 16:07:25 -0400 From: PJ User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) To: Polytropon References: <4AD8EB8F.9010900@videotron.ca> <20091017010758.088b8b8c.freebsd@edvax.de> <4AD9016E.20302@videotron.ca> <4AD90946.4020204@ibctech.ca> <4AD91DE0.3030701@videotron.ca> <20091017042443.dbc693c8.freebsd@edvax.de> In-reply-to: <20091017042443.dbc693c8.freebsd@edvax.de> Cc: Steve Bertrand , "freebsd-questions@freebsd.org" Subject: Re: I hate to bitch but bitch I must X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 17 Oct 2009 20:07:23 -0000 Polytropon wrote: > On Fri, 16 Oct 2009 21:29:04 -0400, PJ wrote: > >> It is simple to understand Emglish but not so simple what was meant by >> whoever wrote it...I cannot correct something that I do not uderstand... >> come on, man, that should be easy to understand. >> > > As English is not my native language, I *now* understand the > meaning of "it should"; in this case, it seems to mean something > like "basically, it is supposed to, but in this case, it does > not", regarding the desired action. > To be as precise as possible, it means normally it should work so go ahead; then the question is - what do you mean by normally. In our case above, the instructions were to do the operation with the disk not in use and the os in SUM. That's very clear. Now, I f they wanted to point out a bug, the bug means that there is an anomaly under certain circumstances - and in this case there really is no bug as it is very clear as to how the instructions should be used. If they consider the operation under a live files system a bug, then they should just make a warning and say something along the lines of "do not use on live system as that may destroy data" or something to that effect. > > > >> I am afraid that with all the globalization people still do not >> understand that translations should be left to experts... an by that I >> mean the final version should always, and I mean always, be by a native >> speaking person. >> > > It's still possible that non-native speakers misunderstand. > Of course... but what you need is cooperation between the two - and both should have some understanding of the particular area of expertise they are dealing with. Just a note: I find it strange that nobody looked into the problem of the confusion... I thought I had pointed out where the co;nfusion arises... and no one seems to have either understood the inconsistencies or bothere to read the explanation... oh well... let's keep on blundering away... ;-)