Well, I looked at (what seems to be) the specification fpr ISDB text. This is going to be very difficult to implement (and outright impossible for someone like me who cannot read Kanjis). As Rémi said, for non-Japanese speakers, it's too difficult. And for me, too :( . But I'll send my patch for su...
Old versions VLC used libiconv built by VLC. Current versions use the system libiconv in the /usr/lib. If you use the system libiconv, the problem will be solved. % otool -L /Applications/VLC.app/Contents/MacOS/lib/libvlccore.dylib /Applications/VLC.app/Contents/MacOS/lib/libvlccore.dylib: @loader_p...
I think your patch, reintroducing fontconfig to Windows, will be rejected.
And it's known issue. See ticket 6350.
I attached a patch on the ticket, but the patch has performance problem...
I don't have time for it.
Patch welcome!
I tested tamil word "அது" by making SRT subtitles and ASS subtitles. SRT: 1 00:00:00,000 --> 00:03:03,000 அது ASS: [Script Info] ; Script generated by Aegisub 2.1.8 ; http://www.aegisub.org/ Title: Default Aegisub file ScriptType: v4.00+ WrapStyle: 0 PlayResX: 640 PlayResY: 480 ScaledBorde...
I think there are 2 patterns using embedded fonts: - Attachment in the MKV. - Embedded in ASS script. You can check the attachments in the MKV file using mkvinfo. mkvinfo foobar.mkv |+ Attachments | + Attached | + File name: foobar.ttf | + Mime type: application/x-truetype-font | + File data, size: ...
If you want to know what fonts are selected, you can see the log of libass outputed to stderr. If you use Windows, launch VLC like: "c:\Program Files (x86)\VideoLAN\VLC\vlc.exe" --extraintf=logger and logger window will appear. If libass(fontconfig) cannot find the exact font in the ASS sc...
@quequotion As you said, current VLC has a problem. I have a patch for this problem and some patches (subtitles, now playing, etc) for ISDB. Patches for vlc-2.0.git and vlc.git are here . If you want to fix only audio issue, use 0025-fix-for-aac-channel-transition.patch (in the full-patch-vlc-2.0-*....
configure:6670: checking for i686-w64-mingw32-g++ configure:6700: result: no This is an answer. If your system has i686-w64-mingw32-g++, config.log looks like the following: configure:6680: checking for i686-w64-mingw32-g++ configure:6696: found /Users/nkoriyama/mingw/mingw-w64/bin/i686-w64-mingw32...
I tried to add the gdi32 to libass in the configure.ac file: if test "${SYS}" = "mingw32"; then VLC_ADD_LIBS([libass],[-lgdi32]) fi On Ubuntu, I confirm that libass plugin cannot be built. gdi32 and usp10 are required. And these libraries must be placed after harfbuzz in modules...
The compile problem of HARFBUZZ is only with the git version. With stable version 2.0.3, this compile problem does not occurs, nor the -H option crash, nor the sound problem. Because HarfBuzz doesn't exist on vlc-2.0.git. Anyway I will see if the compilation fail will occur on Ubuntu. At the moment...
@noah buddy Can you provide sample patterns/files that describe this issue? Maybe we can easily understand your issue if there are samples. On VLC 2.0.3 or later, subtitles encoding GB18030 seems to work when "Universal, Chinese (GB18030)" is selected at Default Encoding in Subtitles &...
Thanks for the log. But I wrongly told you how to take a log. Because the log of libass doesn't appear in the Messages window. Can you take a log with the following steps: 1. Launch the terminal.app. 2. Launch VLC by typing the following command in the terminal window: /Applications/VLC.app/Contents...