yeah, i'm using win10 with 4k resolution, 140% system custom scale.

before you change border, still see two button top edge, redownload, after change border, can't see two button, without edge

OK, I just reverted it to a non-fixed border for now. I might eventually move it to WinUI for better scaling

yeah, now can see buttons, also wish could add a cancel converting function, i added several files for test, and want to cancel the convert

@bronan

Hey, Bronan, I just downloaded your latest version of this tool, having recently bought a UHD TV, so that I can convert my .ass with UHD resolution, and I have noticed that in the meantime, between the 0.2c version and the latest 0.91, a problem has been introduced regarding special characters such as accents for us abroad who use accents in our languages : é, à, ù, ê, ç, Ç, À, É, Ê, È, Ô, ô, etc. See capture below, those characters come out as squares. Could you fix this, please?

Sure, I think I know whats causing it. Can you please share your ass for testing purposes?

(2021-04-23, 05:21 PM)bronan Wrote: Sure, I think I know whats causing it. Can you please share your ass for testing purposes?

Thanks. There it is as a MEGA link: https://fanrestore.com/thread-1833-post-...l#pid52295

Any chance you can look at one of my files bronan? I typically use easySUP to process and create subs, because I've noticed that when I use sub2bd, some of the formatting tags are not recognized, or ignored. For instance, if I set a drop shadow using "\xshad" or "\yshad" rather than the standard "\shad", I get subtitles with no drop shadow at all from sub2bd, whereas easySUP renders them correctly.

Any help is appreciated, as your tool is much more efficient to use than easySUP.


https://mega.nz/file/XR91hazb#7LsC9PPntw...Q9Ft6e-T_M

(2021-04-23, 05:25 PM)Beber Wrote:

(2021-04-23, 05:21 PM)bronan Wrote: Sure, I think I know whats causing it. Can you please share your ass for testing purposes?

Thanks. There it is as a MEGA link: https://fanrestore.com/thread-1833-post-...l#pid52295

OK please try 0.92. This is trouble stemming from the temp file creation, I was assuming UTF8 always to fix the problem with Chinese characters, but obviously that wasn't a catch all solution. I've added new code to attempt to detect the file's encoding and use it for the temp file.

(2021-04-23, 06:29 PM)schorman Wrote: Any chance you can look at one of my files bronan? I typically use easySUP to process and create subs, because I've noticed that when I use sub2bd, some of the formatting tags are not recognized, or ignored. For instance, if I set a drop shadow using "\xshad" or "\yshad" rather than the standard "\shad", I get subtitles with no drop shadow at all from sub2bd, whereas easySUP renders them correctly.

Any help is appreciated, as your tool is much more efficient to use than easySUP.


https://mega.nz/file/XR91hazb#7LsC9PPntw...Q9Ft6e-T_M

This is most likely a difference with how VSFilter.dll processes the ASS. Theoretically we could replace it with another subtitling DLL that works with Avisynth. Are you familiar at all with Avisynth? We can confirm all this by testing the ASS directly through it first.