Ryan L McIntyre
Ryan L McIntyre
Short term solution would seem to be not overwrite codepoints used for ligatures. Long term would be moving codepoints 🤔
I think this is definitely confusing. Yes @wimstefan is right the goal is to create a separate repo for the patcher (and its required files) and I believe that would...
@reportaman it's still a WIP. the org is setup but i want to copy things over so commit and contribution history is not lost
There will be some readme adjustments but the font patcher is now going to be archived with the necessary source files each release, should no longer be a need to...
@Finii > You never explain the why. Who and why wants the patched fonts in the repo :-D Sure I'll try to clarify. I see 2 main reasons to commit...
There have been some updates to the patcher. if you are able to, could you try repatching yourselves? If not i'll follow up with changes in the release candidate 2.2
> We could also pull #717 (which does not change anything if users do not use --parser). That's actually not a bad idea. I was thinking #717 would go with...
I would like to merge this soon. > Generate Caskaydia Cove with --parser for this PR (secretly, without telling anyone). I think maybe that is the most reasonable way forward...
Could you implement your flag idea (i.e. do some special logic with Cascadia only) so this will work okay with the release action? 🙇🏻 now that the fonts are rebuilding...
I forgot to mention, and I'm not sure if it was because of a change I made to get it to run but.. there was strange script output for Cascadia:...