search

okamibl / xy-vsfilter

Automatically exported from code.google.com/p/xy-vsfilter
0 stars 0 forks source link

Scrambled text with "Wasco Sans" font on WinXP #122

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. I kept re-installing and the problem persists.
2. I followed other installation steps and the same happens.
3.

What is the expected output? What do you see instead?
http://screenshotcomparison.com/comparison/149775

What version of the product are you using? On what operating system?
3.0.0.65 xy-VSFilter Windows XP

Please provide related subtitle script (if any). And the less characters
the script is, the less effort I have to make to fix the issue, so if you
could make the script as simple as possible, that would be appreciated.

Please provide any additional information below.

Original issue reported on code.google.com by Linkm...@gmail.com on 7 Oct 2012 at 6:47

GoogleCodeExporter commented 8 years ago 
Strange issue that seems to be triggered by using 'Wasco Sans' at a particular 
size range on Windows XP only. Affects all implementations of VSFilter (2.39, 
2.41, MPC-HC ISR, xy-VSFilter).

This could be some sort of bug in WinXP itself.

Original comment by cyber.sp...@gmail.com on 7 Oct 2012 at 10:25

GoogleCodeExporter commented 8 years ago 
I still have the problem.
I really need it fixed... X(

Original comment by Linkm...@gmail.com on 7 Oct 2012 at 8:27

GoogleCodeExporter commented 8 years ago 
[deleted comment]
GoogleCodeExporter commented 8 years ago 
It will be looked into in a couple weeks, but all I'm saying is if WinXP font 
handling or GDI32 itself has a bug with this font, it may not be able to be 
fixed. Overall it's probably best to just avoid this font if targeting WinXP.

Original comment by cyber.sp...@gmail.com on 7 Oct 2012 at 9:43

GoogleCodeExporter commented 8 years ago 
I don't think it's that font. When I checked the muxed files of that video the 
font Wasco Sans'was not part of the fonts that were muxed in there.
It had 'Montara-Bold', 'Montara-BoldItalic', 'Montara-Gothic', 
'OptimaLTStd-DemiBold', 'GOTHICB', 'IwaOMinPro-Hv-En', 'LinLibertine_DR', 
'Montara-Italic', 'QuaySansMdITCTT', and 'wscsnrg'.
Somehow VLC was able to work it correctly so right now I'm at a lost... X(

Original comment by Linkm...@gmail.com on 8 Oct 2012 at 1:27

GoogleCodeExporter commented 8 years ago 
ah nvm... 'wscsnrg' IS 'Wasco Sans (TrueType)'... T~T

Original comment by Linkm...@gmail.com on 8 Oct 2012 at 1:41

GoogleCodeExporter commented 8 years ago 
VSFilter uses GDI32 and other Microsoft Windows built-in functionally as a 
back-end, and is dependent on the OS.

VLC & MPlayer use Libass. Libass uses Freetype and FriBidi/HarfBuzz as a 
back-end, and works independently of the OS.

Something font related working or not working in Libass, has no impact on 
VSFilter or vice versa.

Original comment by cyber.sp...@gmail.com on 8 Oct 2012 at 4:06

GoogleCodeExporter commented 8 years ago 
So I have to wait a couple of weeks before it will be looked into...
I guess I can wait that long. 
Thanks for responding to this problem! =D
Is it possible that it'll be notified later on? Like a fix or something?

Original comment by Linkm...@gmail.com on 9 Oct 2012 at 3:35

GoogleCodeExporter commented 8 years ago 
Any progress? =O

Original comment by Linkm...@gmail.com on 17 Oct 2012 at 4:33

GoogleCodeExporter commented 8 years ago 
There was a change in plans, as our dev decided he wanted our next build to be 
a rather major stable release. What this means is that instead of just this one 
issue, we are now working though a long list of things including feature 
enhancements, code maintenance, and bug fixes which all need to be completed 
before we release our next build. 

As soon as we've either fixed this issue or deemed it unfixable, I'll leave a 
comment here. Otherwise, just assume it's still being worked on, along with the 
other fixes for our next release.

Original comment by cyber.sp...@gmail.com on 17 Oct 2012 at 8:35

GoogleCodeExporter commented 8 years ago 
It was looked into and determined this was a GDI32 bug on WinXP. GDI32 on WinXP 
is giving VSFilter corrupted glyph information for that font for unknown 
reasons.

Closing the issue since we don't believe this is possible to fix.

Original comment by cyber.sp...@gmail.com on 4 Nov 2012 at 1:17

GoogleCodeExporter commented 8 years ago

Original comment by cyber.sp...@gmail.com on 4 Nov 2012 at 1:17

GoogleCodeExporter commented 8 years ago 
Oh... i see... :(

Original comment by Linkm...@gmail.com on 4 Nov 2012 at 4:32

GoogleCodeExporter commented 8 years ago 
If only there was a way to fix that bug... Maybe replace the GDI32.dll?

Original comment by Linkm...@gmail.com on 4 Nov 2012 at 4:35