Ads keep us online. Without them, we wouldn't exist. We don't have
paywalls or sell mods - we never will. But every month we have large bills
and running ads is our only way to cover them. Please consider unblocking us. Thank you from GameBanana <3
Allow JPG 2000, and other more efficent compression file type screenshots
- A Site Idea.
The old JPEG file system is a bit outdated, among other things.
So, for as long as I care to remember, GB, and possibly even FPSB has only allowed JPEG ingame screenshots, this would be okay, if it were not for jpegs destructive nature and the fact there are newer vesions of it and file types that do it better. For example, although not just exclusively, JPEG 2000.
Wikipedia sez
------------------
JPEG 2000 is an image compression standard and coding system. It was created by the Joint Photographic Experts Group committee in 2000 with the intention of superseding their original discrete cosine transform-based JPEG standard (created in 1992) with a newly designed, wavelet-based method. The standardized filename extension is .jp2 for ISO/IEC 15444-1 conforming files and .jpx for the extended part-2 specifications, published as ISO/IEC 15444-2. The registered MIME types are defined in RFC 3745. For ISO/IEC 15444-1 it is image/jp2.
If anything, at least allow .png and single frame .gif formats, both of which have **lossless compression abilities** (Apart from .gif which makes everything spotty)
> **Posted by MC rex**
> > **Posted by Logan Dougall**
>
> > What I mean is browsers don't display jpeg2000 images natively; same for tga, pnga, and many other image formats -- adoption to browsers is rather slow. I remember firefox devs marking the suggestion for adding jpeg2000 compatibility as a "won't fix".
>
> I've never seen someone complain "My browser can't render that image!" before. I understand why every browser would support JPEG, the damn thing is 20 years old, but its a bit surprising that they don't support even the most common ones that aren't jpeg, like png.
Jpeg2000 is not the same as jpeg. Same as pnga is not the same as png. Like I said, newer formats are not adopted instantly because they're not widely used when perfectly good ones still exist.
> **Posted by Logan Dougall**
> What I mean is browsers don't display jpeg2000 images natively; same for tga, pnga, and many other image formats -- adoption to browsers is rather slow. I remember firefox devs marking the suggestion for adding jpeg2000 compatibility as a "won't fix".
I've never seen someone complain "My browser can't render that image!" before. I understand why every browser would support JPEG, the damn thing is 20 years old, but its a bit surprising that they don't support even the most common ones that aren't jpeg, like png.
What I mean is browsers don't display jpeg2000 images natively; same for tga, pnga, and many other image formats -- adoption to browsers is rather slow. I remember firefox devs marking the suggestion for adding jpeg2000 compatibility as a "won't fix".
> **Posted by Logan Dougall**
> Last I checked, JPEG2000 doesn't render natively in browsers, we'd have to convert each and every one still.
So, what does that mean?
Also, JPEG2000 was a suggestion, just to get the ideas rolling. Whatever the developers of the site would see fit should probably do.