waddou / libass

Automatically exported from code.google.com/p/libass
1 stars 0 forks source link

issues with arabic script #111

Open GoogleCodeExporter opened 8 years ago

GoogleCodeExporter commented 8 years ago
Using last VLC 2.1.0 in windows 7

the issue is LTR VS RTL

libass: http://im32.gulfup.com/ICjZZ.png

vsfilter: http://im38.gulfup.com/H57c4.png

Style: AllForToday,Open Sans 
Semibold,54,&H008F19F2,&H000000FF,&H00000000,&H00000000,-1,0,0,0,100,100,0,0,1,0
,0,8,13,13,107,1

Dialogue: 
0,0:00:02.98,0:00:09.29,AllForToday,Text,0,0,0,,{\fad(1288,1)}لدينا 
اليوم {\c&H1C68FF&}ما {\c&H2BC14F&}الى نهاية 
{\c&HC4A422&}وصلنا

Original issue reported on code.google.com by amjadn...@gmail.com on 17 Oct 2013 at 10:55

Attachments:

GoogleCodeExporter commented 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

GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
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

GoogleCodeExporter commented 8 years ago
[deleted comment]
GoogleCodeExporter commented 8 years ago
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