We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When I was preparing to explain to the translator of grep about how terrible it is to use unbalanced spacing between CJK and western text, I decided to take a screenshot using Inziu Iosevka and found that the uppercase letters are almost aligned, or even taller the top of those CJK chars.
grep
This is not desirable in most cases. A changelog check shows that similar behavior in Iosevka has been fixed since 0.1.15.
Example Text:
‘egrep’即‘grep -E’。‘fgrep’即‘grep -F’。 直接使用‘egrep’或是‘fgrep’均已不可行了。 若FILE 为 -,将读取标准输入。不带FILE,读取当前目录,除非命令行中指定了-r 选项。 如果少于两个FILE 参数,就要默认使用-h 参数。 如果有任意行被匹配,那退出状态为 0,否则为 1; 如果有错误产生,且未指定 -q 参数,那退出状态为 2。 他不知道为什么GNU 很高兴。
The text was updated successfully, but these errors were encountered:
P.S. It will also be great if you can put your build script somewhere so lazy guys like me can run them without thinking…
Sorry, something went wrong.
No branches or pull requests
When I was preparing to explain to the translator of
grep
about how terrible it is to use unbalanced spacing between CJK and western text, I decided to take a screenshot using Inziu Iosevka and found that the uppercase letters are almost aligned, or even taller the top of those CJK chars.This is not desirable in most cases. A changelog check shows that similar behavior in Iosevka has been fixed since 0.1.15.
Example Text:
The text was updated successfully, but these errors were encountered: