IPB

Welcome Guest ( Log In | Register )

libopusfile and Unicode names., Unicode
thinktink
post Jul 16 2013, 16:39
Post #1





Group: Members
Posts: 12
Joined: 14-November 12
Member No.: 104501



I'm in a bit of a bind at the moment. I've developed a Winamp input plugin to play .opus files but I had to do it by converting long file names to the 8dot3 short names so that I could pass them on to the libopusfile library functions that do not support unicode file names. Little did I know however that people can actually disable 8dot3 file name support.

Apparently, once 8dot3 file name support is disabled on a volume it is impossible for unicode incompatible functions to reference a unicode named file with international characters in the file name.

Or is there an alternative, or if not, who do I contact to get the libopusfile libraries updated to support unicode files?

tia.
Go to the top of the page
+Quote Post
 
Start new topic
Replies
thinktink
post Jul 16 2013, 19:40
Post #2





Group: Members
Posts: 12
Joined: 14-November 12
Member No.: 104501



I thought I set a subscription for instant e-mail notification?! mad.gif

Anyways, thanks, I'll look at the callback functions later on. Although I think the original reason why I didn't use them was because they didn't support multichannel re-multiplexing. I'll look again.
Go to the top of the page
+Quote Post
derf_
post Jul 31 2013, 12:36
Post #3





Group: Developer
Posts: 9
Joined: 5-December 12
Member No.: 104986



QUOTE (thinktink @ Jul 16 2013, 19:40) *
Anyways, thanks, I'll look at the callback functions later on. Although I think the original reason why I didn't use them was because they didn't support multichannel re-multiplexing. I'll look again.


Normal place for opusfile discussion is the mailing list: <http://lists.xiph.org/mailman/listinfo/opus>.

All of the other I/O backends are implemented via the callbacks API, so it supports all the same things.

What needs to be done to add unicode support for Windows?
Go to the top of the page
+Quote Post
Peter Harris
post Jul 31 2013, 16:31
Post #4





Group: Members
Posts: 93
Joined: 17-October 01
Member No.: 310



QUOTE (derf_ @ Jul 31 2013, 07:36) *
What needs to be done to add unicode support for Windows?


It's a pain.

Windows prefers to operate in UTF16, so a parallel API that takes wchar_t (and calls _wfopen instead of fopen) would be the Windows thing to do, although it messes up the API.

The other alternative is to keep everything in UTF8 and do all the conversions at the last second.

See https://trac.xiph.org/ticket/268 for the vorbisenc patch set.

I suspect "provide an I/O callback interface and let the caller deal with it" is about the best a cross-platform C library can do.
Go to the top of the page
+Quote Post
derf_
post Jul 31 2013, 17:40
Post #5





Group: Developer
Posts: 9
Joined: 5-December 12
Member No.: 104986



QUOTE (Peter Harris @ Jul 31 2013, 16:31) *
The other alternative is to keep everything in UTF8 and do all the conversions at the last second.

See https://trac.xiph.org/ticket/268 for the vorbisenc patch set.


Thanks for the pointer. Keeping things in UTF-8 would be my preference, as that is, you know, what a sane API would do. Not sure when I'll get to this, but you're right, callbacks would certainly work in the mean time.
Go to the top of the page
+Quote Post

Posts in this topic


Reply to this topicStart new topic
1 User(s) are reading this topic (1 Guests and 0 Anonymous Users)
0 Members:

 



RSS Lo-Fi Version Time is now: 22nd August 2014 - 05:00