parent
a86268a070
commit
1e077e7af6
3 changed files with 11 additions and 11 deletions
|
|
@ -2,13 +2,6 @@
|
|||
How do I...?
|
||||
------------
|
||||
|
||||
Get the code?
|
||||
=============
|
||||
Go to either of
|
||||
|
||||
* http://github.com/quintusdias/glymur (bleeding edge)
|
||||
* https://pypi.python.org/pypi/Glymur/ (stable releases)
|
||||
|
||||
|
||||
Display metadata?
|
||||
=================
|
||||
|
|
|
|||
|
|
@ -142,8 +142,13 @@ From this point forward, python3 will be referred to as just "python".
|
|||
Installation
|
||||
============
|
||||
|
||||
First, get the code by going to either of
|
||||
|
||||
* https://pypi.python.org/pypi/Glymur/ (stable releases)
|
||||
* http://github.com/quintusdias/glymur (bleeding edge)
|
||||
|
||||
In addition to merely installing glymur, you should adjust your **$PATH**
|
||||
environment variable in order to be able to use the **jp2dump** script from
|
||||
environment variable in order to be able to use the *jp2dump* script from
|
||||
the unix command line.
|
||||
|
||||
::
|
||||
|
|
|
|||
|
|
@ -4,7 +4,9 @@ Roadmap
|
|||
|
||||
Here's an incomplete list of what I'd like to focus on in the near future.
|
||||
|
||||
* continue to monitor upstream changes in the **openjp2** library
|
||||
* investigate using CFFI or cython instead of ctypes to wrap **openjp2**
|
||||
* add read support for ICC profiles
|
||||
* continue to monitor upstream changes in the openjp2 library
|
||||
* investigate using CFFI or cython instead of ctypes to wrap openjp2
|
||||
* eventually expose the openjp2 API
|
||||
* add metadata support for ICC profiles
|
||||
* investigate JPIP
|
||||
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue