2014-04-01, 22:52
Best thing to do now would be confirm that it's a problem in an OpenELEC nightly based on the latest master, and if so open an issue on the OpenELEC github. libass 0.11.1 is the latest stable release however it dates from 19 Feb and there have been a number of commits on the libass github since then so who knows it may already be fixed (I may try including the very latest libass so you can test, but this will only be a one-off as it needs fixing upstream)