This version coming from my experience as web developer.
Often I exchanged colon (:) with semicolon (;) and sometime I had the suspect that L lowercase can be more distinguished using a new design. After this redesign I can work now more sure to avoid misinterpretations.
— Curly slash and backslash in Git tree command line
It’s possible to enable it using Pragmata Pro™ with OpenType Stylistic Set 13 named ‘git tree’.
Every slash and backslash, at specific conditions, will appears with curly terminations even with Italic versions.
From now coders can see a more nice Git tree in their command line editor
— Extended the range of ligatures
Ligatures helps a lot the programmers. Now the help is increased!
— Added Bulgarian and Serbian language support
Cyrillic set now includes also Bulgarian and Serbian characters
— Other improvements:
— Regular: Soft dotted improved and Mathematical Alphanumeric Symbols glyphs can be accented
like other standard letters using Combining Diacritical Marks set
— Regular: improved the design of APL glyphs
— Regular: improved the design of Mathematical Operators
— Regular:BQN programming glyphs like ˜˘•÷׬⎉⚇⍟◶⊘⎊⍎⍕⟨⟩√⋆⌽∊↑∧⊔⊏⊐π←↙⍷⍋⊑⊒⍳⊣⊢⍉↕⊸∘○⟜⋄↩↖⌾⥊↓∨⌊⍒⌈≢≤≥⇐… are improved by design
70 replies to “PragmataPro 0.829: Curly Git tree and new essential glyphs”
Cedrik Dubois
Hi Fabrizio! I really enjoy this font and was very excited to see the addition of git-graph support! You mentioned in your post that the ligature for git tree will trigger based on some conditions, may I know what those conditions are? Do I need to setup a specific formatting in order for them to trigger properly?
For me, most of the time the ligature does not show up, I am using the very basic “git log –graph” command.
Here is a video demonstrating what I mean by they almost never show up: https://watch.screencastify.com/v/1sypfHJLXlCoowfQFij4
Ignoring that one issue, I’ve had absolutely no problem with this font and it’s a joy. The little additions you added in this update made a big difference for me, especially for the lower case L and the ‘; :’.
In the video, I am using the mac terminal emulator called iTerm2. I also use on linux a terminal emulator called WezTerm and on windows I use the terminal emulator called Windows Terminal (not cmd).
I see you have been mentioning IDE a couple of time, are you talking about JetBrains IDEs and Visual Studio Code? I recently switched to using vim and work almost completely in terminals nowadays. WezTerm and iTerm2 have great support for ligatures and as you can see in the video, some of the git ligatures work… But I can’t get something as pretty as your screenshot in this blog.
That’s why I was wondering if you were using a special git command to see that?
I actually tried it in a vim editor, and it worked perfectly. That means the problem is not your font, but something else.
I did some debugging, and I think I found the problem: colors.
Colors in a terminal are escape sequences, and I think the conditions you are using to decide which ligature to use does not take colors in consideration.
This also explains why yours looks perfect: there is no colors.
I have no knowledge of fonts, so I can’t help you any further. If this ends up not being fixable, that’s fine but maybe add it as a note in the screenshot and docs 🙂
Great job Cedrik! I would like to let it know to iTerm2 maintainers so this issue can be fixed definitely
Cedrik Dubois
I wasn’t able to reply to the other comment, so I’m replying here: The issue is not with iTerm2. It’s with any terminal.
On windows, I use the Windows Terminal, it has the exact same issue.
On mac, I use both iTerm2 and WezTerm, they both show the same problem.
On Linux, I use tons of terminal, but mainly Kitty, WezTerm and gnome-terminal.
They all show the same problem: with colors, the ligatures don’t work unless they are both the same color (|/ becomes the ligature if they are both blue, but if “|” is blue and “/” is yellow, they will not do the ligature)
But then, if I turn of colors with “git log –graph –no-color –oneline” then the ligatures work in all of the terminals I mentioned above. (and it’s so beautiful)
So again, the issue is not iTerm2, the issue is that the ligatures do not work when using colors, and I believe it has to do with the conditions you have set.
I got it! It’s a kind of reset everytime the color change: if | is red and \ is purple the ligature |\ is disabled by default. I would like to fix it but of course I can’t
Murugan
Dear Fabrizio,
The download available at myfonts.com as latest update ( released Jun 14, 2021 ) is version 0.828.
Could you please update the release in myfonts.com?
Unfortunately to update the files in MyFonts backend is very complicated. Anyway it’s already updated correctly. Please try to download the files again. Thanks!
I realized I bought Pragmata Pro over 3 years ago now and it has been my default programming font that I use everyday, but I never thanked you for creating such a wonderful font. And you’re keeping on improving it in meaningful ways. I love the new “l’.
It’s not as urgent for me as >= <= ligatures, but having `PATH=/usr/bin/sth:$PATH` rendered as `PATH!=usr/bin/sth:$PATH` is also a bit confusing. :/ Can't wait for the font editor. I'm also a bit surprised `=/` is not rendered as the opposite of `/=`.
As always, compliments to Fabrizio for the great work, the willingness to continue improving the font, and the fantastic customer service!
An example for other font designers to follow. As others have said, I got goosebumps when I saw the email announcing a new version.
One small request: as C languages are very prominent (i.e. Rust, C#, JS, etc..). It would be nice to have ligatures for ‘// TODO’ ‘/* TODO’, ‘///’, ‘/*’. I remember seeing something about this being slow in the Github repo, but not sure if it is still a problem (on why it is).
Thank you Luca for your compliments!
I think the C ligatures you request are a very problem with performance. Unfortunately I’ve been forced to remove the // TODO and # TODO ligature also for the mess created by IDE weird behaviours. Sorry Luca
Ok. If you remeber the weird behavior you experienced, please reach out to me and I can see if anything can be done about it. Thanks anyhow for a fantastic font
I don’t think I’ve been as exited over an email in years. Endless props to you Fabrizio for continuing to support and improve the typeface. As someone who primarily programs in Clojure, I really, really, REALLY like how the new curly-parens stand out against regular ones. It makes such a huge difference when you have stacks like [{( or ))}).
PS: Thank you for filing my request and adding the copyleft sign. GPL users all around the world rejoice!
Whoa! New release, wow! I’m slightly teary 😉
Great changes, you made my day, literally.
With new $ and {} forms my ZSH in terminal vim looks slightly funny, but it’s a subject of eyes habits and using python instead 🙂
$ print — ${(vj:,:)${(P)A}[(I)(${(j:|:)@})]:#0}
Nice idea for having a little dot in “!=” ligature, it’s fresh and intuitive 🙂
I have been using this font for a couple of years already. There is nothing more to say: it is a fantastic font making every day better and just worth every penny! Thank you for yet another update 🙂
As I grow older, I *perceive* that more and more people are doing crappier and crappier work. From bagging groceries to building houses. In the past 10 years my appreciation for fine craftsmanship, like your work Fabrizio, has increased three-fold. I don’t make lots of money, but I am even more willing to pay top dollar for *high quality* products. Your fonts Fabrizio, are more “inexpensive” on a cost/quality ratio than most $25 fonts out there. In terms of items purchased for improving my life as a developer, my purchase of PragmataPro is in the top five. Bravo. And thank you so much for continuing to improve the product over time.
Thanks for the beautiful work!
I also have your minimalistic emojis which I love but I couldn’t get it to work in iTerm the way I want. If I choose it as the non-ascii font then I lose all the nerdfont icons. That’s not a choice anyone should be forced to make!
Do you think you could release a version of the emoji font with nerd fonts or a version of pragmatapro with the emojis?
Just downloaded the update and I have to say I really, really like the changes you have made to the font. The best programming font out there just got even better and that’s no small feat. Thank you very much for all the hard work and considerations you put into improving it, Fabrizio!
My sentiment as well. I did a deep dive into alternatives last year when transitioning to ligatures in my development environment, and every other font got something critically wrong. For example, one font converted [|…|] to indistinguishable rectangles! Adding insult to injury, it treated the || in [||] as a ligature rather than [| and |]. PragmataPro is fantastic, and now it’s even better. I’m especially happy about the l change. Thank you for providing such a finely crafted tool, Fabrizio!
The closing curly brace } is also displaying really strangely, with only its bottom part taking 2px. This is not happening with the opening curly brace {.
Unfortunately my font editor changed a lot in these years and I lost the total control I have in past.
Anyway I’ll fix as soon as possible. Thanks to let me know this
Alright, one more but this may be quirky out of necessity. The pair of letter KT gets merged and I’m not certain why; it seems that the T is shifted one pixel left instead of right. See the last picture at https://imgur.com/a/YOwyxEB (guide added for clarity).
thanks for this new version, I like how it makes glyphs like the $ clearer than the previous versions.
One “regression” I don’t like as much is the disappearance of the greater than or equal sign which is now replaced with a ligature similar to the >>= one. I guess it’s more in-line with <= which becomes an arrow, however the nice thing is that ≥ is symmetric so one could always flip the operands 🙂
Is there any way to get the ≥ ligature back?
Thanks Mark for this precious feedback! ≥ and ≤ ligature is still alive but “hidden”; its Unicode codepoints are EA2A and E9E1.
If you can’t find the way to exchange the ligatures I can relase a PragmataPro version with this feature.
Please let me know. Thanks again!
hi Fabrizio, same for me, the previous (0.828) ligatures for = were a bit clearer to me. Also the != !== etc ligatures show a dot at the bottom of the glyphs, is it desired? The 8.28 version were more polished, in my opinion.
Last, do you have any suggestions on how to enable the “git tree” features in some common terminal? (gnome-terminal, st, kitty, iterm).
The choice to transform => in arrows was a request of many developers. It’s almost impossible to make all happy in situations like this.[1]
The dots at the bottom of the != ligatures are absolutely wanted and I’m sure can helps to distinguish them to /=.[1]
I don’t know how to enable in editors “git tree”, sorry, every editors has its strange behaviour with OpenType features.[1]
[1] At this point there is one only solution: a personal PragmataPro configurator. I’ll work on it asap.
Any suggestions?
I would love it.
Personally, I’m supposedly ready even pay for it separately around $10-15,
as this thing is a totally separate scope from promised font itself, but can alleviate some of my pains (like disabling “#TODO” ligatures before, or having two font copies with different “<=" ligatures now for different terminals with different coding languages).
Nevermind if you want to opensource it 😀
Mark
Hey Fabrizio! Thanks for getting back to me, I missed your response somehow, sorry about that.
The thing is that in my case, a personal configuration wouldn’t even be enough :D. The programming language I use `<=` sometimes means a ⇐ and sometimes it means ≤.
I know there is semantic highlighting in Visual Studio Code (https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide), but I don't think there's a way to trigger specific stylistic sets, although it's probably doable as some sort of plugin.
Maybe in my case I'd just need to disable this particular ligature.
Wow and now scrolling further down I see you've already changed the ligatures back.
You're the best, thank you!
You’ve right Mark: this can be quite a good challenge. Maybe in the personal configuration you’ll be able to disable specific ligatures like that can be enough
Michal Kielbowicz
I’m afraid I can’t see how having >= and <= as \geq and \leq respectively is *less* universal than Haskell's bind cut in half and a right-to-left arrow. :/ This is not a sane default.
Ok you convinced me. I’m generating the >= and <= ligature as before.
Tomorrow will be available the new font files from the download area of your account. Thanks to letting me know the importance of the design of this ligatures
I wonder if this could be configurable as a stylistic set similar to “git tree”? I too would prefer “>=” and “<=" like before, but I understand that not everybody wants that.
Please download the font files again to use PragmataPro 0.829 with the old design enabling stylistic set ss14
cxu
I am so sorry to have bothered you, my comment was made regarding the ligature change. I liked when it was “Haskell’s bind cut in half”.
Tekl
Thanks a lot for making this great font even greater. I use it everywhere I can. Only for writing longer texts or in my RSS Reader I’m using your Sys Font. Especially on small smartphone displays it is one of the best fonts to have large glyphs and not too less letters per line. The readability is astonishing for both of your fonts. Since I’ve found your fonts, I’m settled. I never had the need to try new fonts for some years now. 😉
Tekl’s comment made me have a look at Sys and Sys 2.0.
There seam to be quite a few improvements in 2.0, but as a consequence the price also increased.
The only thing I would miss (for reading/writing on a screen) are Tabular Numbers.
BTW: the preview images for Sys 2.0 do not work in Safari. VP8 encoding is not supported.
PragmataPro 0.829: Curly Git tree and new essential glyphs
This version coming from my experience as web developer.
Often I exchanged colon (:) with semicolon (;) and sometime I had the suspect that L lowercase can be more distinguished using a new design. After this redesign I can work now more sure to avoid misinterpretations.
— Curly slash and backslash in Git tree command line
It’s possible to enable it using Pragmata Pro™ with OpenType Stylistic Set 13 named ‘git tree’.
Every slash and backslash, at specific conditions, will appears with curly terminations even with Italic versions.
From now coders can see a more nice Git tree in their command line editor
— Extended the range of ligatures
Ligatures helps a lot the programmers. Now the help is increased!
— Added Bulgarian and Serbian language support
Cyrillic set now includes also Bulgarian and Serbian characters
— Other improvements:
— Regular: Soft dotted improved and Mathematical Alphanumeric Symbols glyphs can be accented
like other standard letters using Combining Diacritical Marks set
— Regular: improved the design of APL glyphs
— Regular: improved the design of Mathematical Operators
— Regular: BQN programming glyphs like
˜˘•÷׬⎉⚇⍟◶⊘⎊⍎⍕⟨⟩√⋆⌽∊↑∧⊔⊏⊐π←↙⍷⍋⊑⊒⍳⊣⊢⍉↕⊸∘○⟜⋄↩↖⌾⥊↓∨⌊⍒⌈≢≤≥⇐… are improved by design— Regular: added curly arrows ︎↖︎↗ ↙↘︎ ↘︎↙ ↗↖︎ ligature coming from ↘︎ ↖︎ ↗ ↙ diagonal arrows combinations
— Regular: Geometric Shapes set are more distinguished at small sizes
— Regular: added Combining Diacritical Marks Extended and Combining Diacritical Marks Supplemental set
— all weights: checkmarks appears by default from now, no more from Stylistic Set ss12
— all weights: added Creative Commons glyphs and harmonized © copyright sign also
— all weights: added Hellschreiber pause symbol
— all weights: improved design and positioning of Graphics for Legacy Computing symbols
Feel free to contact me directly or notify an issue via Github to improve PragmataPro again and again.
Thank you!
70 replies to “PragmataPro 0.829: Curly Git tree and new essential glyphs”
Cedrik Dubois
Hi Fabrizio! I really enjoy this font and was very excited to see the addition of git-graph support! You mentioned in your post that the ligature for git tree will trigger based on some conditions, may I know what those conditions are? Do I need to setup a specific formatting in order for them to trigger properly?
For me, most of the time the ligature does not show up, I am using the very basic “git log –graph” command.
Here is a video demonstrating what I mean by they almost never show up:
https://watch.screencastify.com/v/1sypfHJLXlCoowfQFij4
Ignoring that one issue, I’ve had absolutely no problem with this font and it’s a joy. The little additions you added in this update made a big difference for me, especially for the lower case L and the ‘; :’.
Many thanks for your work!
Fabrizio Schiavi
Thank you Cedrik for your kind words!
About the issue: which IDE do you used?
Cedrik Dubois
In the video, I am using the mac terminal emulator called iTerm2. I also use on linux a terminal emulator called WezTerm and on windows I use the terminal emulator called Windows Terminal (not cmd).
I see you have been mentioning IDE a couple of time, are you talking about JetBrains IDEs and Visual Studio Code? I recently switched to using vim and work almost completely in terminals nowadays. WezTerm and iTerm2 have great support for ligatures and as you can see in the video, some of the git ligatures work… But I can’t get something as pretty as your screenshot in this blog.
That’s why I was wondering if you were using a special git command to see that?
Again, thanks for your amazing work!
Fabrizio Schiavi
No, I didn’t used any special git command.
I’m almost sure that this is a iTerm2 issue. Could be a good idea to submit it to iTerm2 repo.
This is how it render in Mac OS Terminal:
https://github.com/fabrizioschiavi/pragmatapro/blob/master/showcase/PragmataPro%200.829/PragmataPro%20Git%20tree%20on%20MacOS%20Terminal.png
Thanks again for letting me know it!
Cedrik Dubois
I actually tried it in a vim editor, and it worked perfectly. That means the problem is not your font, but something else.
I did some debugging, and I think I found the problem: colors.
Colors in a terminal are escape sequences, and I think the conditions you are using to decide which ligature to use does not take colors in consideration.
Here is an example of git that I ran using “git log –graph –no-color –oneline”
https://imgur.com/a/jqQ1JtO
And here is an example of that exact same command, but without the “–no-color”
https://imgur.com/a/Ux9My3n
This also explains why yours looks perfect: there is no colors.
I have no knowledge of fonts, so I can’t help you any further. If this ends up not being fixable, that’s fine but maybe add it as a note in the screenshot and docs 🙂
Fabrizio Schiavi
Great job Cedrik! I would like to let it know to iTerm2 maintainers so this issue can be fixed definitely
Cedrik Dubois
I wasn’t able to reply to the other comment, so I’m replying here: The issue is not with iTerm2. It’s with any terminal.
On windows, I use the Windows Terminal, it has the exact same issue.
On mac, I use both iTerm2 and WezTerm, they both show the same problem.
On Linux, I use tons of terminal, but mainly Kitty, WezTerm and gnome-terminal.
They all show the same problem: with colors, the ligatures don’t work unless they are both the same color (|/ becomes the ligature if they are both blue, but if “|” is blue and “/” is yellow, they will not do the ligature)
But then, if I turn of colors with “git log –graph –no-color –oneline” then the ligatures work in all of the terminals I mentioned above. (and it’s so beautiful)
So again, the issue is not iTerm2, the issue is that the ligatures do not work when using colors, and I believe it has to do with the conditions you have set.
Fabrizio Schiavi
I got it! It’s a kind of reset everytime the color change: if
|is red and\is purple the ligature|\is disabled by default. I would like to fix it but of course I can’tMurugan
Dear Fabrizio,
The download available at myfonts.com as latest update ( released Jun 14, 2021 ) is version 0.828.
Could you please update the release in myfonts.com?
Thank you,
Murugan
Fabrizio Schiavi
Unfortunately to update the files in MyFonts backend is very complicated. Anyway it’s already updated correctly. Please try to download the files again. Thanks!
Akshay
I realized I bought Pragmata Pro over 3 years ago now and it has been my default programming font that I use everyday, but I never thanked you for creating such a wonderful font. And you’re keeping on improving it in meaningful ways. I love the new “l’.
Thank you so much, Fabrizio!
Fabrizio Schiavi
Thank you Akshay!
Michal Kielbowicz
It’s not as urgent for me as >= <= ligatures, but having `PATH=/usr/bin/sth:$PATH` rendered as `PATH!=usr/bin/sth:$PATH` is also a bit confusing. :/ Can't wait for the font editor. I'm also a bit surprised `=/` is not rendered as the opposite of `/=`.
Michal Kielbowicz
To be more clear, by != I meant a ligature similar to ≠ which is currently the symbol that =/ defaults to.
Fabrizio Schiavi
Please download the font files again. It was fixed days ago. Thanks!
tomhh
Super excited to check out the new version 😀 Pragmata Pro is still my favourite font of all time 🙂 Thank you for the update!
Fabrizio Schiavi
Thank you!!!
Luca Bolognese
As always, compliments to Fabrizio for the great work, the willingness to continue improving the font, and the fantastic customer service!
An example for other font designers to follow. As others have said, I got goosebumps when I saw the email announcing a new version.
One small request: as C languages are very prominent (i.e. Rust, C#, JS, etc..). It would be nice to have ligatures for ‘// TODO’ ‘/* TODO’, ‘///’, ‘/*’. I remember seeing something about this being slow in the Github repo, but not sure if it is still a problem (on why it is).
Fabrizio Schiavi
Thank you Luca for your compliments!
I think the C ligatures you request are a very problem with performance. Unfortunately I’ve been forced to remove the
// TODOand# TODOligature also for the mess created by IDE weird behaviours. Sorry LucaLuca Bolognese
Ok. If you remeber the weird behavior you experienced, please reach out to me and I can see if anything can be done about it. Thanks anyhow for a fantastic font
Love Lagerkvist
I don’t think I’ve been as exited over an email in years. Endless props to you Fabrizio for continuing to support and improve the typeface. As someone who primarily programs in Clojure, I really, really, REALLY like how the new curly-parens stand out against regular ones. It makes such a huge difference when you have stacks like [{( or ))}).
PS: Thank you for filing my request and adding the copyleft sign. GPL users all around the world rejoice!
Fabrizio Schiavi
Thank you!! I really like too the new design of {[()]} , it’s more functional.
Feel free to suggest me other good features
Vladimir Burdukov
It looks awesome, thank you, Fabrizio!
Could you share any details about “special conditions” to convert a slack to a curly slash, please?
Fabrizio Schiavi
Thank you Vladimir!
It’s necessary to find and IDE that supports OpenType Stilistic Sets and enable ‘ss13’ also named ‘git tree’
Yani I
I am pleasantly surprised to see the support for Bulgarian language. Thank you!
amerlyq
Whoa! New release, wow! I’m slightly teary 😉
Great changes, you made my day, literally.
With new $ and {} forms my ZSH in terminal vim looks slightly funny, but it’s a subject of eyes habits and using python instead 🙂
$ print — ${(vj:,:)${(P)A}[(I)(${(j:|:)@})]:#0}
Nice idea for having a little dot in “!=” ligature, it’s fresh and intuitive 🙂
Marcin Ziabek
I have been using this font for a couple of years already. There is nothing more to say: it is a fantastic font making every day better and just worth every penny! Thank you for yet another update 🙂
Fabrizio Schiavi
Thank you Marcin!!!
CodeAlchemist
Hi Fabrizio!
Thank you very much for your work and for continuously improving the font. I really like the update!
Fabrizio Schiavi
Thank you! Thank you!
Tinjaw
As I grow older, I *perceive* that more and more people are doing crappier and crappier work. From bagging groceries to building houses. In the past 10 years my appreciation for fine craftsmanship, like your work Fabrizio, has increased three-fold. I don’t make lots of money, but I am even more willing to pay top dollar for *high quality* products. Your fonts Fabrizio, are more “inexpensive” on a cost/quality ratio than most $25 fonts out there. In terms of items purchased for improving my life as a developer, my purchase of PragmataPro is in the top five. Bravo. And thank you so much for continuing to improve the product over time.
Fabrizio Schiavi
Thank you very very much for these unforgettable words!
Shay Bergmann
Hey Fabrizio!
Thanks for the beautiful work!
I also have your minimalistic emojis which I love but I couldn’t get it to work in iTerm the way I want. If I choose it as the non-ascii font then I lose all the nerdfont icons. That’s not a choice anyone should be forced to make!
Do you think you could release a version of the emoji font with nerd fonts or a version of pragmatapro with the emojis?
Fabrizio Schiavi
Yes, I’ll work on it. Thank you for your good suggestion!
Shay Bergmann
omg thank you!!
Tom Mornini
Thank you for continuing to make a great font even better!
Fabrizio Schiavi
Thank you Tom!!
clayman
Just downloaded the update and I have to say I really, really like the changes you have made to the font. The best programming font out there just got even better and that’s no small feat. Thank you very much for all the hard work and considerations you put into improving it, Fabrizio!
Fabrizio Schiavi
Comments like this are fuel to continue to do my best in this project. Thank you very much!
Jason Evans
My sentiment as well. I did a deep dive into alternatives last year when transitioning to ligatures in my development environment, and every other font got something critically wrong. For example, one font converted [|…|] to indistinguishable rectangles! Adding insult to injury, it treated the || in [||] as a ligature rather than [| and |]. PragmataPro is fantastic, and now it’s even better. I’m especially happy about the l change. Thank you for providing such a finely crafted tool, Fabrizio!
Fabrizio Schiavi
Thank you Jason!!
Michael Cadilhac
Hi there Fabrizio,
Thanks so much for your great work! I’m having a few problems with the “l” and with the ligatures not appearing; did I miss something?
https://imgur.com/a/YOwyxEB
Thanks!
Michael Cadilhac
The closing curly brace } is also displaying really strangely, with only its bottom part taking 2px. This is not happening with the opening curly brace {.
Fabrizio Schiavi
Unfortunately my font editor changed a lot in these years and I lost the total control I have in past.
Anyway I’ll fix as soon as possible. Thanks to let me know this
Michaël
Cheers! I also added the 3 to the list of oddities on imgur: it appears slightly slanted.
Fabrizio Schiavi
Thanks Michaël but I have already fixed all this mess.
Please download and install the font files again
Michaël
Fantastico! Thanks a lot, everything looks buttery smoothly nice now!
Michaël Cadilhac
Alright, one more but this may be quirky out of necessity. The pair of letter KT gets merged and I’m not certain why; it seems that the T is shifted one pixel left instead of right. See the last picture at https://imgur.com/a/YOwyxEB (guide added for clarity).
Cheers!
Mark
Hey Fabrizio,
thanks for this new version, I like how it makes glyphs like the $ clearer than the previous versions.
One “regression” I don’t like as much is the disappearance of the greater than or equal sign which is now replaced with a ligature similar to the >>= one. I guess it’s more in-line with <= which becomes an arrow, however the nice thing is that ≥ is symmetric so one could always flip the operands 🙂
Is there any way to get the ≥ ligature back?
Fabrizio Schiavi
Thanks Mark for this precious feedback!
≥and≤ligature is still alive but “hidden”; its Unicode codepoints areEA2AandE9E1.If you can’t find the way to exchange the ligatures I can relase a PragmataPro version with this feature.
Please let me know. Thanks again!
Matteoeghirotta
hi Fabrizio, same for me, the previous (0.828) ligatures for = were a bit clearer to me. Also the != !== etc ligatures show a dot at the bottom of the glyphs, is it desired? The 8.28 version were more polished, in my opinion.
Last, do you have any suggestions on how to enable the “git tree” features in some common terminal? (gnome-terminal, st, kitty, iterm).
Fabrizio Schiavi
The choice to transform
=>in arrows was a request of many developers. It’s almost impossible to make all happy in situations like this.[1]The dots at the bottom of the
!=ligatures are absolutely wanted and I’m sure can helps to distinguish them to/=.[1]I don’t know how to enable in editors “git tree”, sorry, every editors has its strange behaviour with OpenType features.[1]
[1] At this point there is one only solution: a personal PragmataPro configurator. I’ll work on it asap.
Any suggestions?
amerlyq
> a personal PragmataPro configurator
I would love it.
Personally, I’m supposedly ready even pay for it separately around $10-15,
as this thing is a totally separate scope from promised font itself, but can alleviate some of my pains (like disabling “#TODO” ligatures before, or having two font copies with different “<=" ligatures now for different terminals with different coding languages).
Nevermind if you want to opensource it 😀
Mark
Hey Fabrizio! Thanks for getting back to me, I missed your response somehow, sorry about that.
The thing is that in my case, a personal configuration wouldn’t even be enough :D. The programming language I use `<=` sometimes means a ⇐ and sometimes it means ≤.
I know there is semantic highlighting in Visual Studio Code (https://code.visualstudio.com/api/language-extensions/semantic-highlight-guide), but I don't think there's a way to trigger specific stylistic sets, although it's probably doable as some sort of plugin.
Maybe in my case I'd just need to disable this particular ligature.
Wow and now scrolling further down I see you've already changed the ligatures back.
You're the best, thank you!
Fabrizio Schiavi
You’ve right Mark: this can be quite a good challenge. Maybe in the personal configuration you’ll be able to disable specific ligatures like that can be enough
Michal Kielbowicz
I’m afraid I can’t see how having >= and <= as \geq and \leq respectively is *less* universal than Haskell's bind cut in half and a right-to-left arrow. :/ This is not a sane default.
Fabrizio Schiavi
Ok you convinced me. I’m generating the >= and <= ligature as before. Tomorrow will be available the new font files from the download area of your account. Thanks to letting me know the importance of the design of this ligatures
Dmytro Sadovnychyi
I wonder if this could be configurable as a stylistic set similar to “git tree”? I too would prefer “>=” and “<=" like before, but I understand that not everybody wants that.
Fabrizio Schiavi
Good idea! I’ll do it. As default
=> <=will be as before.Please re-download the font files tomorrow. Thanks!
Michal Kielbowicz
This is the best customer support I’ve ever experienced! 😀
Fabrizio Schiavi
I just replaced the PragmataPro 0.829 font files with the required ligatures. Feel free to download again. Thanks!
Aaron Madlon-Kay
Thank you very much for the quick fix. I rarely have a use for the previous new ligature, but I use greater-than and less-than all the time!
cxu
Is it possible for me to have the “old” way through a stylistic set?
Fabrizio Schiavi
Yes, I can add it. Good idea! Keep in touch
Fabrizio Schiavi
Please download the font files again to use PragmataPro 0.829 with the old design enabling stylistic set
ss14cxu
I am so sorry to have bothered you, my comment was made regarding the ligature change. I liked when it was “Haskell’s bind cut in half”.
Tekl
Thanks a lot for making this great font even greater. I use it everywhere I can. Only for writing longer texts or in my RSS Reader I’m using your Sys Font. Especially on small smartphone displays it is one of the best fonts to have large glyphs and not too less letters per line. The readability is astonishing for both of your fonts. Since I’ve found your fonts, I’m settled. I never had the need to try new fonts for some years now. 😉
Fabrizio Schiavi
Thank you very very much for this comment!
Götz
Tekl’s comment made me have a look at Sys and Sys 2.0.
There seam to be quite a few improvements in 2.0, but as a consequence the price also increased.
The only thing I would miss (for reading/writing on a screen) are Tabular Numbers.
BTW: the preview images for Sys 2.0 do not work in Safari. VP8 encoding is not supported.
cemm_wayfinding_sys.jpg: RIFF (little-endian) data, Web/P image, VP8 encoding, 1500×1000, Scaling: [none]x[none], YUV color, decoders should clamp
Fabrizio Schiavi
Thanks to letting me know it