59 lines
1.3 KiB
Plaintext
59 lines
1.3 KiB
Plaintext
head 1.2;
|
|
access;
|
|
symbols;
|
|
locks; strict;
|
|
comment @# @;
|
|
|
|
|
|
1.2
|
|
date 2010.02.19.16.57.50; author RyanKaldari; state Exp;
|
|
branches;
|
|
next 1.1;
|
|
|
|
1.1
|
|
date 2005.10.18.11.41.31; author BobMorris; state Exp;
|
|
branches;
|
|
next ;
|
|
|
|
|
|
desc
|
|
@none
|
|
@
|
|
|
|
|
|
1.2
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@%META:TOPICINFO{author="RyanKaldari" date="1266598669" format="1.1" version="1.2"}%
|
|
%META:TOPICPARENT{name="WebHome"}%
|
|
* IntroductionToJPEG2000
|
|
* OtherJPEG2000Resources
|
|
|
|
-- Main.BobMorris - 18 Oct 2005
|
|
|
|
Because of uncertainties surrounding the legal status of JPEG2000 (specifically the fear of submarine patents and patent trolling), it's unlikely that we'll see widespread adoption of the format on the web before 2020 (when most of the patents will have expired). After the endless patent litigation that surrounded the original JPEG format (which didn't end until 2008), most web software vendors are understandably wary of adopting new file formats. One area where JPEG2000 might be able to find some traction, however, is for extremely high resolution images (> 50 megapixel), where JPEG isn't as practical.
|
|
|
|
-- Main.RyanKaldari - 19 Feb 2010@
|
|
|
|
|
|
1.1
|
|
log
|
|
@none
|
|
@
|
|
text
|
|
@d1 1
|
|
a1 1
|
|
%META:TOPICINFO{author="BobMorris" date="1129635691" format="1.0" version="1.1"}%
|
|
d3 2
|
|
d6 1
|
|
a6 2
|
|
* IntroductionToJPEG2000
|
|
* OtherJPEG2000Resources
|
|
d8 1
|
|
a8 1
|
|
-- Main.BobMorris - 18 Oct 2005
|
|
d10 1
|
|
@
|