Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Human readable tag transport/editing format #15

Open
GoogleCodeExporter opened this issue Oct 6, 2015 · 1 comment
Open

Human readable tag transport/editing format #15

GoogleCodeExporter opened this issue Oct 6, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

We need a human readable format for easy editing of tags.

A lightweight format such as RFC822 or JSON would work best.  XML would be 
much too verbose for this purpose.

Original issue reported on code.google.com by Karoly.Lorentey on 21 Jun 2009 at 12:27

@GoogleCodeExporter
Copy link
Author

Binary data are a problem -- such data should not be included in the format (it 
would 
easily overwhelm all text data, and would also make it harder to edit the tag 
dump).

Long data of binary frames (>100 bytes) should be elided from the text format.  
However, the user should be able to set such data by specifying the name of the 
file 
containing the desired data.  There must be a user command (separate from the 
one 
producing the editable text format) for saving the contents of a binary field 
in a 
file.

$ stagger --get track01.mp3
TIT2: Foobar baz
APIC[Cover]: "Cover art" <254353 bytes of JPEG data>
$ stagger --set track01.mp3
TIT2: Fred Foo
APIC[Cover]: "Cover art" read("cover.jpg")
^D
$ stagger --save APIC cover2.jpg
$ stagger --save APIC[Cover] cover2.jpg
etc.

Original comment by Karoly.Lorentey on 24 Jun 2009 at 11:38

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants