search for: g_ogg

I'm not sure if this falls within the scope of tag data, somewhere else, or if there's any provision for it at all: I have a lot of songs whose native titles are in Japanese. For example, I have a song titled "螟". The filename for this song would be "02 - yume [Dream].ogg" (or even "02 - 螟 (yume) [Dream].ogg".) To automatically name this file, I'd need

Background link for those unfamiliar: http://www.debian.or.jp/~kubota/unicode-symbols.html W3's suggestions for within XML: http://www.w3.org/TR/japanese-xml/ The nice thing about this document is it gives data for a bunch of different translation tables, and enumerates their differences. (This is only about Japanese encodings. I believe similar problems may exist for Chinese and Korean;

I'm seeing some inconsistency in returned timestamps using vorbisfile. I open a file, read some data (grabbing timestamps with ov_pcm_tell), then seek back with ov_pcm_seek(vf, 0) and read it again. The seek lands back on 0, but on the second read through, there's a gap in the timestamps: they jumps up by 2112 frames. This causes my vorbisfile code to insert silence to maintain sync (as

Well, my last question about this was in the middle of other stuff, but it's a basic one: why put tag info in the comment field at all? Why not use the XML field that's already there? It gives the flexibility needed to do things like translated tags easily, and keeps tag info in the same format as other data--potentially simplifying editors which read other types of metadata. The only

I've found a much better solution; it's standard (in Unicode itself), simple and more flexible: Unicode language tagging. It was made for just this purpose, in fact. A technical description is at http://www.unicode.org/unicode/reports/tr27/#tag which, like all specs, makes it sound a bit more complicated than it really is. It comes down to this: mark the language of text with U+E0001