diff options
| author | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2011-01-26 16:56:38 +0000 |
|---|---|---|
| committer | giraffedata <giraffedata@9d0c8265-081b-0410-96cb-a4ca84ce46f8> | 2011-01-26 16:56:38 +0000 |
| commit | e9130c54e8a75339fab9e9b14f37bd8877ccbd88 (patch) | |
| tree | 3b631b2710b87ae625832dfc02fd6ce373638040 /pamtojpeg2k.html | |
| parent | a598fb04da86b2d492142e9db626c286cee19e1e (diff) | |
| download | netpbm-mirror-e9130c54e8a75339fab9e9b14f37bd8877ccbd88.tar.gz netpbm-mirror-e9130c54e8a75339fab9e9b14f37bd8877ccbd88.tar.xz netpbm-mirror-e9130c54e8a75339fab9e9b14f37bd8877ccbd88.zip | |
typo fixes from john@johnbradshaw.org
git-svn-id: http://svn.code.sf.net/p/netpbm/code/userguide@1395 9d0c8265-081b-0410-96cb-a4ca84ce46f8
Diffstat (limited to 'pamtojpeg2k.html')
| -rw-r--r-- | pamtojpeg2k.html | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/pamtojpeg2k.html b/pamtojpeg2k.html index 52f0a678..c5e07b24 100644 --- a/pamtojpeg2k.html +++ b/pamtojpeg2k.html @@ -60,8 +60,8 @@ specifically, whereas JPC is a more or less arbitrary array of codes. <B>pamtojpeg2k</B> can't produce a JP2, but the JPC image that <b>pamtojpeg2k</b> produces is very similar to a JP2 if the input is a PBM, PGM, or PPM image or equivalent PAM image. One difference is -that that RGB intensity values in a JP2 are SRGB values, while -<b>pamtojpeg2k</b> produces ITU-R Recommedation BT.709 values. Those +that the RGB intensity values in a JP2 are SRGB values, while +<b>pamtojpeg2k</b> produces ITU-R Recommendation BT.709 values. Those are very similar, but not identical. Another difference is that a JP2 can contain extra information about an image that JPC cannot. |