Ape tags, includes and portability
wheeler at kde.org
Tue Jul 18 16:39:28 CEST 2006
On Jul 18, 2006, at 4:28 PM, Sebastian Pipping wrote:
> i thought about your recommendations and i now strongly
> prefer the first one, the two-constructors-solution.
> this would save unnecessary conversions on windows and
> also not require two differently compiled versions.
> TagLib::String is not what i want since i mainly work
> with plain-c-"array"-strings.
And on UNIX it's not a matter of "want", really, which is why it uses
const char * in the first place. On UNIX each file system has its
own encoding, but all are 8-bit. So TagLib just passes the file name
on to the OS's fopen() command without paying any attention to it.
Passing it through TagLib::String would corrupt it in many cases
since TagLib::String only understands two 8-bit encodings (UTF-8 and
More information about the taglib-devel