Oleg Oshmyan

> It does talk of how font linking “takes priority over font fallback”, but the way it is described in the next sentence makes me think that perhaps this is...

> Uniscribe proper actually [allows](https://learn.microsoft.com/en-us/windows/win32/api/usp10/nf-usp10-scriptstringanalyse) enabling and disabling both font linking and font fallback Well, further tests suggest that while the API allows this, `SSA_LINK` actually does nothing. So we’re...

FWIW I think it’s good to support files that are non-seekable; and even a seekable file’s size can change mid-read if someone concurrently writes to it. We could, of course,...

(Another non-ISO-C alternative for getting the file size is the `stat` family of functions.)

Good point 😅 But yeah, it shouldn’t hurt and might help in the future, so it’s probably good to have it added while we remember about it.

To render vertical Japanese in ASS, you must do the following: 1. Specify a Japanese font that supports vertical writing. 2. Prefix the font name with an `@` symbol. 3....

I’m not sure which exact symbols you’re trying to use, but yes, some are unfortunately rotated incorrectly in current libass, and I’m afraid you don’t have any solution for this...

The reason I have doubts is because vertical writing support in Windows is _pretty_ old and I couldn’t find clear information on how fonts define it when I first tried...

Oh, someone did archive the Google Code repo on GitHub! That’s good to know. Of course, Google still hosts [its own archive](https://code.google.com/archive/p/libass/issues/95), but it’s anonymized.

I don’t think that’s `ー` in the picture: it’s too long. (Of course, it’s not MS Mincho, either.) Certainly, an exact text sample would help for reproduction purposes.