Return-Path: X-Original-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-ooo-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 59B9CD247 for ; Sat, 3 Nov 2012 18:26:19 +0000 (UTC) Received: (qmail 17600 invoked by uid 500); 3 Nov 2012 18:26:18 -0000 Delivered-To: apmail-incubator-ooo-dev-archive@incubator.apache.org Received: (qmail 17528 invoked by uid 500); 3 Nov 2012 18:26:18 -0000 Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ooo-dev@incubator.apache.org Delivered-To: mailing list ooo-dev@incubator.apache.org Received: (qmail 17520 invoked by uid 99); 3 Nov 2012 18:26:18 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Nov 2012 18:26:18 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of jancasacondor@gmail.com designates 209.85.214.175 as permitted sender) Received: from [209.85.214.175] (HELO mail-ob0-f175.google.com) (209.85.214.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 03 Nov 2012 18:26:11 +0000 Received: by mail-ob0-f175.google.com with SMTP id eq6so4436744obc.6 for ; Sat, 03 Nov 2012 11:25:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=ut5u6+uJ+5hn7Ymj6V81Hfuo6KugirflSG2N5FjowRs=; b=RfOyJRYJGLEVokIJqm+yp6el+psDz4CHrmHAnKloz1O+O/4nsFh2DClC1hZ4MkB5zw MlXdpDnN2h6Na3Klp3CrXvpaBdfmvwxawmX03d6I3AGagkkqBXxZW9V9i5NSiA0HR8LH fr3zJL4Dw6SOesrYrNYHOSHmdVWIFnlVtoDuEMxQhsEt+CioaiR6B9O0jrQmDo7HglO8 zktJg7bh1zoNTmorYDfbykqdf9KhpDqxXwdEXqervkzyVINKz2hWz1TtyOIqbQ4qreDI um9XuM1tCAvRsyWbTReqOAY5D+FYCx+sOoqqRsIYG6pLmTTqrb0/PCSLK3YyhEIMe6ox R0dQ== MIME-Version: 1.0 Received: by 10.60.24.7 with SMTP id q7mr4094926oef.108.1351967151001; Sat, 03 Nov 2012 11:25:51 -0700 (PDT) Received: by 10.76.91.9 with HTTP; Sat, 3 Nov 2012 11:25:50 -0700 (PDT) In-Reply-To: References: <50954AB7.1070502@apache.org> Date: Sat, 3 Nov 2012 19:25:50 +0100 Message-ID: Subject: Re: [DOCUMENTATION]Wrong use of scientific notation From: jan iversen To: ooo-dev@incubator.apache.org Content-Type: multipart/alternative; boundary=e89a8ff1c4e6c8926204cd9b6144 X-Virus-Checked: Checked by ClamAV on apache.org --e89a8ff1c4e6c8926204cd9b6144 Content-Type: text/plain; charset=ISO-8859-1 When it is in the part that is being translated localizers will take care of "," versus ".". I know the "x10" is a scientific notation and I use it and like it, but since our calc does not accept it, I would prefer the E notation, so people does not get confused. Jan. On 3 November 2012 19:14, RGB ES wrote: > 2012/11/3 jan iversen > > > May I politely as a mathematician point out that there is a major > > difference in the 2 proposals. > > > > Number 1 is a mathematical expression whereas number 2 is a number. > > > > I'm physicist :) > > The first number is the traditional scientific notation (specially if > proper super indexes are used) while the second one is the "E notation" > > http://en.wikipedia.org/wiki/Scientific_notation#E_notation > > > > > > > Now I do not know where it is used, > > > One example > > https://translate.apache.org/es/OOo_34_help/translate.html?unit=6097629 > > Regards > Ricardo > > > > > but if I copy both suggestions into > > Calc, it believes it is text. > > > > Should we not have a format that our own calc accept as a number ?? > > > > I agree with andrea that number 2 is more readable (and then forget it is > > not a number). > > > > rgds > > Jan I. > > > > > > On 3 November 2012 17:47, Andrea Pescetti wrote: > > > > > RGB ES wrote: > > > > > >> On the help files, you find numbers written like > > >> 1.79769313486232 x 10E308 > > >> > > >> This is wrong: it should be either > > >> 1.79769313486232 x 10^308 > > >> or > > >> 1.79769313486232E308 > > >> what do you think? > > >> > > > > > > Yes, it's wrong and your first proposal is correct and more readable > than > > > the second one. Then I wonder how many times we have these kind of > > numbers > > > in our documentation... and probably when they do appear we are more > > > interested in their order of magnitude than in their actual value. > > > > > > Regards, > > > Andrea. > > > > > > --e89a8ff1c4e6c8926204cd9b6144--