Escape handling different from VSFilter

[GoogleCodeExporter]

The sequence "c\{o\}m" is rendered as "c\m" in VSFilter, but "c{o}m" in libass. 
VSFilter also renders "c{o\}m" as "cm". So it appears "\{" is actually not a 
valid escape.

The Aegisub manual doesn't list them as valid escapes either: 
http://docs.aegisub.org/manual/ASS_Tags

This makes me wonder just how you can put a "{" character on the screen with 
ASS. (This fix will break mplayer2 OSD display of any strings that contains "{" 
and "}".)

Original issue reported on code.google.com by nfxjfg@googlemail.com on 23 Mar 2013 at 11:17

Attachments:

• 0001-Remove-and-escape-sequences.patch

[GoogleCodeExporter]

As far as I know, there is no way to escape anything or to display "{" in 
VSFilter. That's exactly why it was added to libass. Does it break anything in 
practice? If not, why should this functionality be removed?

Original comment by g...@chown.ath.cx on 29 Mar 2013 at 1:01

[GoogleCodeExporter]

I just thought it was an escape handling bug. It also means there's no way of 
having a \ followed by an override tag. (mplayer2 handles this by inserting an 
invisible space after "\".)

>That's exactly why it was added to libass.

If that is so, I withdraw the patch.

Original comment by nfxjfg@googlemail.com on 29 Mar 2013 at 12:16

[GoogleCodeExporter]

Also see discussion at 
https://code.google.com/p/xy-vsfilter/issues/detail?id=149

Original comment by nfxjfg@googlemail.com on 23 Jun 2013 at 1:13