Return-Path: <tiff-bounces@remotesensing.org>
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx005.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j4QJZ03Q022318
        for <joris.at.lebbeke@skynet.be>; Thu, 26 May 2005 21:35:03 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 2DEE725A4360; Thu, 26 May 2005 15:34:44 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from scooby.simplesystems.org (scooby.simplesystems.org
	[65.66.246.67])
	by xserve.flids.com (Postfix) with ESMTP id 4D8AA25A433C
	for <tiff@remotesensing.org>; Thu, 26 May 2005 15:34:42 -0400 (EDT)
Received: from blade.simplesystems.org (blade.simplesystems.org [65.66.246.74])
	by scooby.simplesystems.org (8.12.10+Sun/8.12.10) with ESMTP id
	j4QJYdAi028393; Thu, 26 May 2005 14:34:39 -0500 (CDT)
Date: Thu, 26 May 2005 14:34:39 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@blade.simplesystems.org
To: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] How to Write a tif file with compression =COMPRESSION_JPEG&
	photometric = PHOTOMETRIC_YCBCR ?
In-Reply-To: <p0521060dbebbd3d829b1@[153.32.48.223]>
Message-ID: <Pine.SOC.4.60.0505261431380.12047@blade.simplesystems.org>
References: <42959EB2.000055.32635@m52.126.com>
	<1486734063.20050526142456@culture.gouv.fr>
	<000e01c561f3$537438c0$fda5f651@dfgrrxsknr4e>
	<1698276405.20050526161052@culture.gouv.fr>
	<001a01c5620f$3ccfccd0$a5adf651@dfgrrxsknr4e>
	<Pine.SOC.4.60.0505261147290.12047@blade.simplesystems.org>
	<p0521060dbebbd3d829b1@[153.32.48.223]>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed
Cc: tiff <tiff@remotesensing.org>
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 000000000023ceae.000002a5
X-MSP-STORE: Thu, 26 May 2005 21:35:14 +0200
Status:   

On Thu, 26 May 2005, Chris Cox wrote:
>> 
>> The really annoying "new rule" that seems to have popped up recently is 
>> that 24 bits-per-sample images are supposed to be swapped for endianness. 
>> To me that is still a resounding "huh"? I have yet to encounter a CPU with 
>> a 24-bit processor word.
>
> It doesn't require a certain word size.
>
> Windows prefers everything as BGR, while other OSes prefer RGB.
> Anything that is a multiple of 8 bits is subject to byte order rules (I have 
> yet to see a 96 bit word CPU, either - but extended precision floating point 
> is also subject to byte order).

What does Microsoft Windows have to do with the TIFF specification? 
Could it be that other OSs do not really "prefer" RGB but use the 
arbitrary ordering "RGB" because that is the convention that CIE 
standards use?

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer,    http://www.GraphicsMagick.org/
_______________________________________________
Tiff mailing list: Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
