Opened 7 years ago

Last modified 6 years ago

#1857 open enhancement

PNG iTXt textual information chunk

Reported by: richardpl Owned by:
Priority: wish Component: avcodec
Version: git-master Keywords: png
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Attachments (2)

iTXt_compressed.png (33.5 KB) - added by richardpl 6 years ago.
iTXt_uncompressed.png (33.6 KB) - added by richardpl 6 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 Changed 7 years ago by Cigaes

  • Status changed from new to open

I had old patches implementing that, I just updated them and submitted them to the mailing-list.
http://ffmpeg.org/pipermail/ffmpeg-devel/2012-October/133165.html

I do not have samples with iTXt chunks. Do you have any, or can you suggest a tool to produce some?

comment:2 Changed 7 years ago by cehoyos

  • Keywords png added

comment:3 Changed 7 years ago by Cigaes

tEXt and zTXt decoding implemented and pushed. iTXt still waiting for a sample.

Is there anything else you want? The details on your ticket are rather sparse.

comment:4 Changed 6 years ago by richardpl

  • Summary changed from PNG textual information chunks to PNG iTXt textual information chunk

Changed 6 years ago by richardpl

Changed 6 years ago by richardpl

comment:5 Changed 6 years ago by richardpl

I attached iTXt files i managed to create by hacking gif2png.

I'm also interested in iTXt support in encoder.

comment:6 Changed 6 years ago by Cigaes

Do you have actual use cases for iTXt? If the files are so hard to generate, that probably means it is not very useful.
As for me, I can say I do not see how to get it to fit the API.

comment:7 Changed 6 years ago by richardpl

They are not so hard to generate at all.
Speaking about API, the parts that can not be exported could just be ignored, as they are not very important.

Why iTHt? This is the only standard png chunk that allows utf8.

Note: See TracTickets for help on using tickets.