Operator Mono) I believe this is the best one I have ever found and the price is quite fair. I was wondering if it would be a lot of work for you to create a different variation that only contains a few groups of glyphs? For example as a developer who works with C#, JS, HTML, CSS, Markdown, Swift and a few more languages I would only need English language and also some groups (e.g.
#Essential pragmata pro pro#
#Essential pragmata pro codeīox drawing) that don’t have a direct use in writing code are just nice to have. This way you might be able to make it more approachable for more developers. Dank Mono has an interesting price tag, but it only contains a fraction of what you have done (and not as beautiful).
I have another suggestion too(based on Dank Mono’s again).
I think it would be very useful if you could create a page in your website to let people type in their favorite language and see the syntax highlighting and ligatures in action before buying.
#Essential pragmata pro windows#
For example, an application with pretty minimal font settings (you can select font name and size) started to render “PragmataPro” in italic instead of regular, etc.įurther investigation showed that every Regular version has some of its properties tuned in 0.828 comparing to 0.827.īesides some older errors (such as Unique Identifier stated ‘Liga’ for non-ligature variants) these four regular versions now have set “Is Monospaced = Yes”, “Family Style = Monospaced”, “Proportion = Monospaced” and vice versa - even non-Mono versions of PragmataPro Regular! Just installed PragmataPro v0.828 (on Windows 7) and noticed that a lot of apps began to render it improperly. I guess there is a little bug it’s appropriate for “Mono” variants but not for regular ones.
Having set “Monospaced” flag on Regular, but not on Italic, Bold and Bold Italic among one family looks strange. Footmarksġ: The Monospace font demonstrated in this email is Fira Code.As I remember, the intention for a separate “Mono” family was that some apps doesn’t recognize modular-spaced fonts and require a “true” monospaced font. This will also obviously allow people who have Monospace fonts with ligatures have an option for them to not be used if undesired for whatever reason. This will ensure the ligatures of their non-monospace typeface creating undesirable results to their existing iTerm2 experience.
Therefore, ligatures being rendered only makes sense for fixed-width (monospace) fonts to not “confuse” everything accordingly, it makes sense for it to be configurable for it to be active or not for users who’ve decided to eccentrically use a non-monospace typeface with their instances of iTerm.** In the spirit of the existing configurability already available, this may be desired to be toggled on & off in the text section of options since this only makes sense to be active for monospace (fixed-width) Typefaces.Īs noted by George Nachman himself with my brief interaction with him about this that lead to this issue being worthwhile to be filed, “ligature needs to be as wide as the original chars or everything gets confused”. Here’s a figure of a Monospace font w/ Ligatures when ligatures are active: Here’s a figure of a Monospace font 1 w/ Ligatures when ligatures are disabled: Now that mainstream Monospace Typefaces have support for ligatures-typefaces such as Pragmata Pro, Hasklig, & Fira Code-it now seems worthwhile to add Ligature support to iTerm2 when previously that probably couldn’t be justiable.
0 kommentar(er)
