unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Juri Linkov <juri@jurta.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: joakim@verona.se, Emacs development discussions <emacs-devel@gnu.org>
Subject: Image metadata (was: imagemmagick patch 5)
Date: Tue, 30 Mar 2010 19:12:31 +0300	[thread overview]
Message-ID: <874ojxhpqg.fsf_-_@mail.jurta.org> (raw)
In-Reply-To: <jwv6357ltc2.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Sun, 07 Mar 2010 16:23:57 -0500")

>>>> it returns a raw representation of the extension data of a given (sub)image.
>>> Again, what is meant by "extension" here?
>> It seems the term "extension" is GIF-specific.  The GIF specification says
>> that extension blocks "extend" the 87a definition to allow extensions like
>> the Graphic Control Extension that specifies the animation delay time, etc.
>
>> The parameter `count' is used in animation, but unrelated to "extension".
>> Perhaps a more common term for `count' would be "metadata".
>
> Then we should rename image-extension-data to image-metadata, I think.

The problem is that one part of the current `image-extension-data'
is metadata, and another part is extension data.  For instance, in

  (count 44
   255 "NETSCAPE2.0"
     0 "^A^@^@"
   249 "^D^M^@\377"
  )

`count 44' is metadata, and the rest (with non-descriptive numeric keys)
is extension data.

Maybe the list returned by the new function `image-metadata' should be like:

  (count 44
   extension-data (255 "NETSCAPE2.0"
                     0 "^A^@^@"
                   249 "^D^M^@\377")
  )

-- 
Juri Linkov
http://www.jurta.org/emacs/




  parent reply	other threads:[~2010-03-30 16:12 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-03  7:39 imagemmagick patch 5 joakim
2010-03-03 19:34 ` Juri Linkov
2010-03-03 20:03   ` joakim
2010-03-06 17:59     ` Juri Linkov
2010-03-06 20:16       ` Stefan Monnier
2010-03-06 21:05         ` Juri Linkov
2010-03-07 14:37           ` Stefan Monnier
2010-03-07 19:08             ` Juri Linkov
2010-03-07 21:23               ` Stefan Monnier
2010-03-13 17:44                 ` Kim F. Storm
2010-03-30 16:12                 ` Juri Linkov [this message]
2010-03-30 20:36                   ` Image metadata Stefan Monnier
2010-03-30 22:38                     ` Juri Linkov
2010-03-31  1:22                       ` Stefan Monnier
2010-04-02 21:51                       ` joakim
2010-04-02 22:38                         ` Juri Linkov
2010-03-04  2:41 ` imagemmagick patch 5 Stefan Monnier
2010-03-05 22:06   ` joakim
2010-03-05 22:30     ` Stefan Monnier
2010-03-05 23:56       ` Jan Djärv
2010-03-06  6:02       ` Stephen J. Turnbull
2010-04-15  9:34     ` joakim
2010-04-15 10:55       ` joakim
2010-04-16 20:45         ` Juri Linkov
2010-04-17  6:09           ` joakim

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ojxhpqg.fsf_-_@mail.jurta.org \
    --to=juri@jurta.org \
    --cc=emacs-devel@gnu.org \
    --cc=joakim@verona.se \
    --cc=monnier@iro.umontreal.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).