You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of verifying whether a muxed script (or a list of fonts) is complete, it would be better to automate the collection of fonts to mux in the first place.
I imagine this as a different subcommand next to the current verify. Name suggestions for the tool include "assfont" and "fontcheck".
As for the operation, of the list or collect command, I would like to either receive a list of fonts on stdout I can parse or have the matched fonts copied into a specified target folder. Font matching could be performed using system fonts (which would probably require using fontconfig directly or some form of emulation on Linux and idk about Windows) or from a list of specified paths like ~/.fonts, which should already be possible for the verify task.
The text was updated successfully, but these errors were encountered:
Funami580
added a commit
to Funami580/Myaamori-Aegisub-Scripts
that referenced
this issue
Jul 13, 2021
Instead of verifying whether a muxed script (or a list of fonts) is complete, it would be better to automate the collection of fonts to mux in the first place.
I imagine this as a different subcommand next to the current
verify
. Name suggestions for the tool include "assfont" and "fontcheck".As for the operation, of the
list
orcollect
command, I would like to either receive a list of fonts on stdout I can parse or have the matched fonts copied into a specified target folder. Font matching could be performed using system fonts (which would probably require using fontconfig directly or some form of emulation on Linux and idk about Windows) or from a list of specified paths like~/.fonts
, which should already be possible for the verify task.The text was updated successfully, but these errors were encountered: