From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Original-To: caml-list@yquem.inria.fr Delivered-To: caml-list@yquem.inria.fr Received: from mail4-relais-sop.national.inria.fr (mail4-relais-sop.national.inria.fr [192.134.164.105]) by yquem.inria.fr (Postfix) with ESMTP id C1DEFBBAF for ; Thu, 11 Mar 2010 15:54:41 +0100 (CET) X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AncBANaSmEvRVdvikGdsb2JhbACDC5dOCBUBAQEBCQkMBxMDH6xrgheFL4h4AQEDBYEtgl9qBIwi X-IronPort-AV: E=Sophos;i="4.49,620,1262559600"; d="scan'208";a="58572610" Received: from mail-ew0-f226.google.com ([209.85.219.226]) by mail4-smtp-sop.national.inria.fr with ESMTP; 11 Mar 2010 15:54:41 +0100 Received: by ewy26 with SMTP id 26so42726ewy.3 for ; Thu, 11 Mar 2010 06:54:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to:cc :content-type; bh=MMXywYXOfVgrrxzKfRh1hgxwaOUQ/U/stxA+RipS2Aw=; b=Lk5uIbI0ZioL41Lz4/B52R/BWQWhspQ1w6EFl5gVtTDwERmqfQVct3AN+1bZRvr8VA m+5LSflIYhzjy8yGH9xVajlo2u+2a4qIMbwekQjbDKQfYVFZbyPdMFWzcfb8XVuQP5YC OJJIdpWMVFZtDrwfnvYzJ7pDIZaQ51eHdbcqk= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; b=EX3+ktNbGX6Y1teO1za5znTQuRgQiKNuMiuek/OOh+d3u8OR0ODChP2U5P3PQMPuQy J/DdGLIJqGFKR3RhcHCKZii9aFSyw0I2mahWKVYKgvUn0er2+ooX5wdkK4iqC+YyTXxw wDsXhoLex2zJliqQgoc10vkVEBzjEpZhh3vak= MIME-Version: 1.0 Sender: daniel.c.buenzli@gmail.com Received: by 10.213.96.7 with SMTP id f7mr6510095ebn.7.1268319280918; Thu, 11 Mar 2010 06:54:40 -0800 (PST) In-Reply-To: <594748.67259.qm@web111501.mail.gq1.yahoo.com> References: <91a3da521003101309n5eadf89dt7e6e157e3dd14a3@mail.gmail.com> <594748.67259.qm@web111501.mail.gq1.yahoo.com> Date: Thu, 11 Mar 2010 15:54:40 +0100 X-Google-Sender-Auth: 85124e9c48450f1e Message-ID: <91a3da521003110654x37d8a551u948c39889b64fdba@mail.gmail.com> Subject: Re: [Caml-list] [ANN] CCSS 1.0 From: =?UTF-8?Q?Daniel_B=C3=BCnzli?= To: Dario Teixeira Cc: caml-list@yquem.inria.fr Content-Type: text/plain; charset=UTF-8 X-Spam: no; 0.00; buenzli:01 bug:01 real-world:01 1.0:98 height:98 photographic:98 height:98 readable:01 caml-list:01 font:97 font:97 data:02 objects:02 tagged:02 unit:03 > I understand why you may see this as a bug, but for me it's a feature. > Personal experience tells me that mixing units -- even if they belong > to the same system, as cm and mm -- is asking for trouble (never mind > mixing units from metric and imperial -- ask NASA). Well you're not in a NASA case since all the data is tagged correctly. > But anyway, if you really think unit conversion is a must-have feature, > I can add it to the next release (it's actually simple to implement). > However, personally I remain sceptical about its real-world usefulness. For the web I anyway use more relative lengths than absolute ones. I don't know if it's a must have feature however I can see that being annoying if you have to do an absolute layout (e.g. for print). The problem is that different kind of objects naturally use different kind of units. A font size or line height for example is usually expressed in pts and a standard paper or photographic print size will be in cms (or inches). Having to use a calculator to add them just feels wrong and makes the resulting stylesheet less readable : if I see 210mm x 297mm I recognize quite easily A4, however if I see 595.275591pt x 841.889764pt, well, no. Conversely a value in pt for a line height or font size will give me a better idea of the typographical result than a value in mm. Best, Daniel P.S. I know about metric typographic units [1] but somehow they didn't catch and most people still think in pts in typography. [1] http://www.cl.cam.ac.uk/~mgk25/metric-typo/