Comment 13 for bug 369861

1) The attached new patch should suppress the warning

2) I was converting the files through command line, so I didn't see this message but I got broken SVG, and the 'test2.pdf' is supposed to be OK.

3) That is right, may main problem was the same as #605872 (I think I just found the wrong bug report), but even so the two bugs, AFAIK, are manifestations of the same underlying issue. As said in my previous comment, the current UTF-16 to UTF-8 conversion is buggy, it does not handle surrogate pairs correctly (my and #605872, and possibly this one), nor it validates the resulting UTF-8 which in either case means broken SVG that can't be reopened.