Repository navigation
Does Jpeg format need comment marker support? #2061
|
Current jpeg implementation lacks of COM marker support, does it need to support it? Should be easy to implement as this marker is just an array of bytes - itu spec leaves 'interpretation to the application', decoding API should not try to decode it as it can be anything from literal byte array to some weird text encoding. So it can be a 'good first issue' or I can work on it a bit later. |
Replies: 2 comments 5 replies
|
@br3aker I think it would be nice to have support for decoding COM markers and a "good first issue". Don't you think it would make sense to add a default interpretation of the data as ASCII, which would make it a bit more useful? Would there be any harm in doing so? I would be also fine with just providing it as a byte array and the user should take care of it, but I just think a optional default interpretation would be a bit ore convenient. |
|
@br3aker Did you get a chance to work on this? I was looking for a similar functionality? if not, can you share some api design/implementation notes and I can probably have a look. |
@br3aker I think it would be nice to have support for decoding COM markers and a "good first issue".
Don't you think it would make sense to add a default interpretation of the data as ASCII, which would make it a bit more useful? Would there be any harm in doing so? I would be also fine with just providing it as a byte array and the user should take care of it, but I just think a optional default interpretation would be a bit ore convenient.