Open GoogleCodeExporter opened 8 years ago
this issue in any ass code (tag), like:-
!{\i1}(ثعلب الماء){\i0} راكّو
in vsfilter:-
!(راكّو (ثعلب الماء
in libass will be (like) this:-
!(ثعلب الماء) راكّو
Original comment by amjadn...@gmail.com
on 23 Oct 2013 at 10:54
From what I heard from Greg, it's because vsfilter layouts text in a broken,
non-standard way. It first splits the text in rather arbitrary chunks
(according to formatting), and then runs shaping on the chunks. libass on the
other hand does something that's closer to what everyone else does.
So, this sounded like this is a WONTFIX to me.
Maybe an improvement is possible when Chortos really goes and implements
rendering text by chunks instead of by glyphs?
Original comment by nfxjfg@googlemail.com
on 9 Nov 2013 at 2:12
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
[deleted comment]
This is not a problem. You have specified libass to render your text in RTL (by
indicating Arabic encoding), but you wrote the text in the LTR to accommodate
VSFilter.
To solve the problem, remove the Arabic encoding option from the style, and you
are good to go.
Original comment by ghassan...@gmail.com
on 21 Dec 2013 at 3:13
[deleted comment]
if you mean Encoding, it's already 1 not 178, look above (The last value of
Style)
Original comment by real.fin...@gmail.com
on 17 Mar 2014 at 8:22
Original issue reported on code.google.com by
amjadn...@gmail.com
on 17 Oct 2013 at 10:55Attachments: