> On Dec 28, 2020, at 9:33 PM, Carl Zwanzig <c...@tuunq.com> wrote: > > On 12/28/2020 5:44 PM, Carl Zwanzig wrote: >> (If I have a chance later tonight, I might look into the filter's source >> code.) > > I took an admittedly quick look at vf_drawtext.c and the helper routines. It > looks like the only string quoting needed would be for '\' and '%', so not > for a comma. I did not dive further into character processing. It does look > like there's a substitution made for characters that can't be found in the > font so it could be that the font is faulty or that the comma isn't really a > comma (see prev. email).
Hi Carl, Thanks for the research. I think the culprit is the font 🤦‍♂️ (If that last glyph doesn’t render properly in the mailing list, it’s a facepalm) I switched from Keyboard.ttf to Helvetica.ttc, and now the commas render properly. So sorry to everyone for the colossal waste of time and bandwidth. I’ll post the final results of my experiment tomorrow as atonement. _______________________________________________ ffmpeg-user mailing list ffmpeg-user@ffmpeg.org https://ffmpeg.org/mailman/listinfo/ffmpeg-user To unsubscribe, visit link above, or email ffmpeg-user-requ...@ffmpeg.org with subject "unsubscribe".
