[vorbis] vorbiscomment and multi line comments
John Morton
jwm at eslnz.co.nz
Thu Oct 2 13:42:30 PDT 2003
On Friday 03 October 2003 08:01, you wrote:
> John Morton wrote on 2003-10-02:
> > On Thursday 02 October 2003 23:29, you wrote:
> > > On Thu, Oct 02, 2003 at 11:09:17PM +1200, John Morton wrote:
> > > No, we've not implemented any more sophisticated input format for
> > > vorbis comment. As you say, -t "foo=bar" works fine up to the
> > > length-limit of the commandline. I have run into the problem
> > > occasionally, but in those few cases I just used that as a
> > > work-around.
> >
> > Fair enough. I'll indent multi-line comments in my text serializing
> > scheme with '~', seeing as ascii 0x7E appears to be outside the range
> > allowed for field names.
>
> The issue with this approach is that multi-line comments won't be
> easily processible with scripts, because they will still span mulitple
> lines. Grep and friends won't work well with them. Therefore I
> believe that ``\n`` or something like that would be better.
>
> I've once written__ a patch__ for reading/writing this style, also
> supporting ``\0``. (It was somewhat overengineered, also supporting a
> different style abusing 254 and 255 which can't appear in UTF-8; I now
> think that's quite useless and if more than one styles should be
> supported a human-readable one, like your ``~`` idea would be better).
>
> __ http://www.xiph.org/archives/vorbis/200211/0128.html
> __ http://bugs.xiph.org/show_bug.cgi?id=273
Having a mode that escapes the newline is probably the most useful trick, so
long as the default behaviour is still the 'human-readable'.
John
--- >8 ----
List archives: http://www.xiph.org/archives/
Ogg project homepage: http://www.xiph.org/ogg/
To unsubscribe from this list, send a message to 'vorbis-request at xiph.org'
containing only the word 'unsubscribe' in the body. No subject is needed.
Unsubscribe messages sent to the list will be ignored/filtered.
More information about the Vorbis
mailing list