CoreText on Mac broken, crashes on files with Unicode names

[King InuYasha]

Hello,

I just grabbed the 64-bit Mac version of VLC 1.1.0-pre1, and I tested it with a couple of videos on Mac OS X Snow Leopard 10.6.2 on MacBook Pro Intel 64-bit.

First, thanks for fixing styled subtitles on Mac OS X! It sucks when the subtitles spread all over the screen because it ignores styling data.

Now, I noticed that the CoreText module for onscreen text doesn't seem to be working. Even when I select it as default, it seems to use the FreeType2 module.
I could tell because the FreeType2 module renders text that is jagged and not surrounded with a text shadow. Nor does it match the rendering style of the rest of the OS. When CoreText worked in VLC 1.0.x, the rendering of the text matched the rest of the OS (text outer glow shadow, smooth text, rendering style the same as OS X).

Playing videos with softsubs resulted in videos hiccuping throughout playback, jittery video (frame dropping) and audio skips all over.

Also, when I attempted to open a file containing a Unicode filename (consisting of Korean characters), VLC opened it up and played for a few seconds. It showed question marks in place of the korean characters, in both the title of the window and the on-screen title thingy that shows up for a couple of seconds after the video starts playing.

Then... it crashed...

[Rémi Denis-Courmont]

It's no big news that VLC on MacOS is mostly unmaintained due to lack of developers.

[Jean-Baptiste Kempf]

Administrator ! You Do not delete posts! OK?

We do as we want to remove spam.

[Jean-Baptiste Kempf]

Hello,

I just grabbed the 64-bit Mac version of VLC 1.1.0-pre1, and I tested it with a couple of videos on Mac OS X Snow Leopard 10.6.2 on MacBook Pro Intel 64-bit.

First, thanks for fixing styled subtitles on Mac OS X! It sucks when the subtitles spread all over the screen because it ignores styling data.

Now, I noticed that the CoreText module for onscreen text doesn't seem to be working. Even when I select it as default, it seems to use the FreeType2 module.
I could tell because the FreeType2 module renders text that is jagged and not surrounded with a text shadow. Nor does it match the rendering style of the rest of the OS. When CoreText worked in VLC 1.0.x, the rendering of the text matched the rest of the OS (text outer glow shadow, smooth text, rendering style the same as OS X).

Playing videos with softsubs resulted in videos hiccuping throughout playback, jittery video (frame dropping) and audio skips all over.

Also, when I attempted to open a file containing a Unicode filename (consisting of Korean characters), VLC opened it up and played for a few seconds. It showed question marks in place of the korean characters, in both the title of the window and the on-screen title thingy that shows up for a couple of seconds after the video starts playing.

Then... it crashed...

Could you file a bug, please?