diff options
Diffstat (limited to 'README.imagemagick')
| -rw-r--r-- | README.imagemagick | 49 |
1 files changed, 12 insertions, 37 deletions
diff --git a/README.imagemagick b/README.imagemagick index e9d6a4166ea..80c665e0cef 100644 --- a/README.imagemagick +++ b/README.imagemagick | |||
| @@ -27,11 +27,21 @@ jpegs. | |||
| 27 | the bundle. This feature is not the primary usecase for the | 27 | the bundle. This feature is not the primary usecase for the |
| 28 | imagemagick patch though. | 28 | imagemagick patch though. |
| 29 | 29 | ||
| 30 | - optimize number of pages calculation for bundles as suggested by | ||
| 31 | imagemagick forum: "set the density to something low like 2 and use | ||
| 32 | MagickPingImage()" | ||
| 33 | |||
| 30 | - zooming the image like what is done for fonts in face-remap.el would | 34 | - zooming the image like what is done for fonts in face-remap.el would |
| 31 | be a useful and demo friendly addition. | 35 | be a useful and demo friendly addition. Some work has been done on |
| 36 | image-mode.el to acihieve this. | ||
| 32 | 37 | ||
| 33 | - figure out what to do with the experimental features noted below. | 38 | - look for optimizations for handling images with low depth |
| 39 | |||
| 40 | - it would be neat if the graphicsmagick fork of imagemagick could | ||
| 41 | optionaly be used. | ||
| 34 | 42 | ||
| 43 | |||
| 44 | |||
| 35 | * TODO | 45 | * TODO |
| 36 | #B _ complete documentation drafts below | 46 | #B _ complete documentation drafts below |
| 37 | 47 | ||
| @@ -120,41 +130,6 @@ as TIFF or DJVM, to view. | |||
| 120 | The image-metadata function can be used to retrieve the total number | 130 | The image-metadata function can be used to retrieve the total number |
| 121 | of images in an image bundle. This is simmilar to how GIF files work. | 131 | of images in an image bundle. This is simmilar to how GIF files work. |
| 122 | 132 | ||
| 123 | * experimental | ||
| 124 | |||
| 125 | - :crop is used to specify a croping area: (width height x y). This | ||
| 126 | is similar to the slice image specification, but has a different | ||
| 127 | purpose. :crop removes the croped areas from memory, so its memory | ||
| 128 | efficient if you only need to view a certain part of the image. The | ||
| 129 | slice specification can be used to pick diferent parts of the same | ||
| 130 | image, so its more disk and display efficient. :crop works well, but | ||
| 131 | it would still be better to find a way to have :splice do the same | ||
| 132 | thing. | ||
| 133 | |||
| 134 | - :geometry takes a geometry string as defined by ImageMagick: | ||
| 135 | |||
| 136 | scale% | ||
| 137 | scale-x%xscale-y% | ||
| 138 | width | ||
| 139 | xheight | ||
| 140 | widthxheight | ||
| 141 | widthxheight^ | ||
| 142 | widthxheight! | ||
| 143 | widthxheight> | ||
| 144 | widthxheight< | ||
| 145 | area@ | ||
| 146 | {size}{offset} | ||
| 147 | {size}{+-}x{+-}y | ||
| 148 | |||
| 149 | See the ImageMagick manual for more information. | ||
| 150 | |||
| 151 | - :crop is used to specify a croping area, with the "{size}{offset}" syntax. | ||
| 152 | |||
| 153 | :geometry and :crop with a string argument, are both particular to | ||
| 154 | ImageMagick, whereas the lisp interface is more general. Currently it | ||
| 155 | seems like the lisp interface is good enough, so the string argument | ||
| 156 | interface will probably be removed. | ||
| 157 | |||
| 158 | * Changelog entry | 133 | * Changelog entry |
| 159 | 2010-06-12 Joakim Verona <joakim@verona.se> | 134 | 2010-06-12 Joakim Verona <joakim@verona.se> |
| 160 | * image.c: Add support for ImageMagick. When HAVE_IMAGEMAGICK is | 135 | * image.c: Add support for ImageMagick. When HAVE_IMAGEMAGICK is |