Opened 10 years ago

Last modified 9 years ago

#1857 open enhancement

PNG iTXt textual information chunk

Reported by: Elon Musk 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 Elon Musk 9 years ago.
iTXt_uncompressed.png (33.6 KB ) - added by Elon Musk 9 years ago.

Download all attachments as: .zip

Change History (9)

comment:1 by Nicolas George, 10 years ago

Status: newopen

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 by Carl Eugen Hoyos, 10 years ago

Keywords: png added

comment:3 by Nicolas George, 10 years ago

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 by Elon Musk, 10 years ago

Summary: PNG textual information chunksPNG iTXt textual information chunk

by Elon Musk, 9 years ago

Attachment: iTXt_compressed.png added

by Elon Musk, 9 years ago

Attachment: iTXt_uncompressed.png added

comment:5 by Elon Musk, 9 years ago

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

I'm also interested in iTXt support in encoder.

comment:6 by Nicolas George, 9 years ago

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 by Elon Musk, 9 years ago

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.