fabrizioschiavi / pragmatapro Goto Github PK

Hello,

I'm stacking U+2555 on top of U+2502 and it looks good at ≥18pt but a little off on smaller sizes. Is this something that can be fixed in the font... or are Windows users just stuck 🙂

18pt looks good:

16pt looks like it's off a bit:

14pt:

12pt:

Fabrizio,

PragmataPro and PragamataPro Mono are scaling and rendering differently in Windows since 0.822 update:

PragmataPro (gets bolder as of 14px):

PragmataPro Mono scales until 16px

I've been implementing ligature display for Emacs using prettify-symbols-mode, and working off the table in All_chars.txt. A few characters seem to have shifted locations since when this chart was produced (or perhaps it was erroneous before; I'm not sure).

In particular, the U+800 line is off by one: it should give the ligatures for the following sequences (presented as an elisp association list out of convenience):

             ("<~>"  . #xE800)
             ("<**>" . #xE801)
             ("<<^"  . #xE802)
             ("<!"   . #xE803)
             ("<@"   . #xE804)
             ("<#"   . #xE805)
             ("<%"   . #xE806)
             ("<^"   . #xE807)
             ("<&"   . #xE808)
             ("<?"   . #xE809)
             ("<."   . #xE80A)
             ("</"   . #xE80B)
             ("<\\"  . #xE80C)
             ("<\""  . #xE80D)
             ("<:"   . #xE80E)
             ("<->"  . #xE80F)

And then, we should have a (currently missing) line U+810, with these mappings:

             ("<!--" . #xE810)
             ("<--"  . #xE811)

Since these are different, I suspect that there may be other ligatures which have now been added which I haven't yet found, and which I'd definitely like to add if they exist.

Once I've completed this Emacs compatibility layer, I'll certainly publish it, and you can feel free to point people in that direction if they want ligatures in their Emacs. :)

I don't know if I am missing a setting in Atom, but I find zero and capital O are perhaps not as easy to distinguish as I would have liked. This shows PragmataPro on the left and Envy Code R on the right:

Thanks @fabrizioschiavi for my favorite font! I'm a programmer-turned-graphic-designer-turned-programmer and really appreciate the thought and detail that went into PragmataPro. I bought Essential PragmataPro Regular about a week ago and love it. Is it possible to upgrade to the all weights+ligatures version for the difference in cost?

Thank you!

I saw the following issue with emacs' mac port, which occurs with other ligature programming fonts:
https://github.com/railwaycat/emacs-mac-port/issues/96

I believe that people building editors have to be careful to not disrupt layout of lines when ligatures are present. Wouldn't this automatically work itself out if => was rendered as a single glyph that had double width, with the arrow glyphs centered perfectly? Is this how pragmatapro works right now? Should it?

This screenshot compares my terminal window using PragmataPro Mono 0.821 vs. 0.822:

It looks like the new version is roughly one pixel higher, making the lines feel a little cramped.

I have a problem with rendering some ligatures in Intellij IDEA like */ and >> or <<
But only in "no antialiasing mode". Also, the problem is solved by turning off the ligatures, but it kills the whole point.

Examples below:

No antialiasing, ligatures enabled

No antialiasing, ligatures disabled

Greyscale, ligatures enabled

• How does this other project have a copy of PragmataPro free for download?
  https://github.com/ryanoasis/nerd-filetype-glyphs-fonts-patcher
• Why doesn't that version have the ligatures for functional languages?
• If that isn't supposed to be available for free, how can I try the version with ligatures to make sure it actually works in my editor?
• If not open sourced, how can people modify it to include all the new file icons in nerd-filetype-glyphs project?

This is the best font ever! The only thing that I miss is the support for accented characters like the ones used in the image attached:

@fabrizioschiavi
I find that the font size increases a lot when going from size 10 to size 11 on Windows. Size 11 looks too big compared to size 10. I'll add screenshots when I'm back in front of my windows machine.

This jump reflects itself at other sizes in my java applications. Wish the size transitions were a little more moderate.

Along the lines of the ligatures for <==, ==>, and <=>, could we get one for <==>? This symbol shows up in several contexts, including the Dafny language and several pieces of Haskell code I've seen.

Thanks for all your hard work!

Period should be the lower left corner instead of the center

The dash character is positioned so it does not align with the middle of greater than and equal. This means thinks like -> and -= look a bit odd (at least to me). Here is a screenshot:

And for comparison, here is a screenshot where I moved the dashes down one pixel:

In computations it does not align vertically with + either. I can see that the * is positioned similar to the dash though.

I was just wondering if there is a reason for the position of the dash?

I use PragmataPro with no antialiasing at 10pt size (sometimes 11pt). I find it good in general. However, the hinting for some symbols seems to have gotten worse in recent versions (at least from my point of view). Here are some issues at 10pt size:

• The x looks asymmetric (the top right arm looks abit crooked)
• The heads of the "Arrows" also look asymmetric. The diagonals of many arrows look a bit crooked.
• Many mathematical operators look a bit crooked also: ≤ ≥ ≦ ≧ ≨ ≩ ≪ ≫ ≬ ≭ ≮ ≯ ≰ ≱ ≲ ≳ ≴ ≵ ≶ ≷ ≸ ≹ ≺ ≻ ≼ ≽ ≾ ≿ ⊀ ⊁ ⊂ ⊃ ⊄ ⊅ ⊆ ⊇ ⊈ ⊉ ⊊ ⊋ ⊌ ⊍ ⊎ ⊏
• The ∀ symbol is not symmetric either. The differential symbol ∂ is a bit too thick on some areas.
• The stem of the inverted question mark ¿ is shorter than its non-inverted counterpart. This is not a failure by itself, but I would intuitively expect one symbol to be an exact rotation+translation of the other.
• Some of the dots are not rendered as squares, but as a three-pixel shape. For example, see the ellipsis (…).

Hash and screenshots

ab32f7fb838819ad10df3f3b51152977  PragmataPro.ttf

10pt, aliased:

Some of the same issues also appear in the 11pt version:

Popular process viewer htop introduced graphs using braille glyphs to increase terminal resolution.

PP has helper lines for braille that do not serve a clear purpose. Side effect is that HTOP (and elsewhere) braille "dot matrix display" looks odd.

Looks like gliphs render with wrong baseline

I'm wondering whether Pragmata Pro could have an exact half-width variant (which means that all glyphs are 1/2 em wide) to make it compatible to CJK characters (including 中文 and にほんご). The current width of characters is 1060/2048 em which is a bit wider than 1/2em.

I also left a comment on fsd.it but thought I would mention it here, too. I am considering purchasing your font primarily for use with Agda/Haskell but don't see support for one of the most common symbols, namely ℕ. It's actually used in the Agda standard library, so it should be included.

I believe the newest pre-release renders single -> arrows strangely. I don't recall the vertical leg of the triangle being thinner than the other portions of the triangle. Is this unintentional? It makes the arrows feel a little less "sturdy".

Would it be possible to add a ligature for ##? It's used quite a bit in some OCaml code. Here's an example.

PragmataPro currently missing Beamed Notes:

• ♫ http://www.fileformat.info/info/unicode/char/266b/index.htm
• ♬ http://www.fileformat.info/info/unicode/char/266c/index.htm

Just bought your fonts, amazing work! Thank you.

I've noticed that there's no ligature for :<:, would it be hard to add one? I'm using it in various projects, e.g there's an alias defined in a library, but i't would be awesome to see it in the font

Hello,

I don't know if this is a problem with the font itself or IDEA, so I'm posting here with the hope it could lead to a solution.

The problem is that PragmataPro is rendered as bold, always. Whereas PragmataPro Mono has the correct rendering. Here a video demonstrating the problem:

In the video, I first show that when using PragmataPro (not Mono), the font is rendered as bold the bold option does not matter. Then I switch to PragmataPro Mono, where it behaves as it should.

Could it possibly be a difference in the way fonts are built that would cause this rendering issue?

Thanks,
Cam

Hi!

First, thanks for the great font!

My only issue is that some Powerline symbols are slightly misaligned at size 12 on OS X Mavericks (see screenshots attached), which forces me to play with the vertical character spacing property of the font to obtain a perfect rendering of those glyphs.

This is far from critical, but with such a nice font, the slightest visual glitch can bother.

Ideally, I would not have to play with this setting (vertical character spacing). In particular since it messes up box drawing.

Without custom vertical spacing:

With custom vertical spacing:

This is a strange one. -> doesn't work, but other ligatures like => do.

I think it's probably VS's fault, not the font's, but I'm posting here in case someone knows how to fix it...

A lot of programming languages (Scala, Haskell ...) use this symbol, it would be nice to have this one.
http://www.fileformat.info/info/unicode/char/21d2/index.htm. Thanks.

Hi,

Is it possible to have a full set (i.e. a through z) of subscripts to ease mathematical input in PragmataPro? So far, only a subset if available.

Thanks!

As a reminder, Pragmata Pro doesn't have these glyphs:

• ⚑ http://www.fileformat.info/info/unicode/char/2691/index.htm
• ⚐ http://www.fileformat.info/info/unicode/char/2690/index.htm

Hi there,

Recently the IntelliJ line of editors is able to use ligatures as well.
Examples are the Hasklig and FiraCode font.

Due to a bug in the JDK there is a small patch required to make this work until the editors are ready to use Java 9.

As far as I can find out they are talking about "replacing 'DFLT' tag with 'zyyy' tag in GSUB subtable,.
The full tread can be found here : https://youtrack.jetbrains.com/issue/IDEA-127539

Looking forward to use this font (with ligatures) in IntelliJ :D

Gerard

Any idea what settings might have to change? 0.822

Pragmata Pro 0.822

Windows 8.1
Sublime Text 3
Font-size: 16px
Resolution: 1600x900

Tilde is fine in 15px:

Tilde is too close in 16px:

This command should print the word 'Hello" underlined.

echo -e '\033[4mHello'

However, as you can see below, this doesn't work.

I'd assume this is a terminal bug, but it works fine with other fonts.

PragmataPro doesn't render all ligatures one would expect.

Fira Code

https://github.com/tonsky/FiraCode

.= .- := =:=
== != === !== =/=

<<- <-- <- <-> -> --> ->>
<=< <<= <==    <=> => ==> =>> >=>
>>= >>- >-     -< -<< =<<
<~~ <~ ~~~ ~> ~~>

<<< << <= <>  >= >> >>>
 <| <|> |>

 <$ <$> $>
 <+ <+> +>
 <* <*> *>

\\ \\\ {- -} // ///
/* /** **/ */ 
</ <!-- www  --> />
0xF  9:45  m-x *ptr

;; ;;; :: ::: !! !!!
?? ??? %% %%% && &&& 
|| ||| .. ... ..< []
-- --- ++ +++ ** ***

~= ~- -~ =~ ~@
^= ?= /= /== |= ||=
## ### ####
#{ #[ #( #? #_ #_(


a*b a*A B*b A*B *a *A a* A*
a-b a-A B-b A-B -a -A a- A-
a+b a+A B+b A+B +a +A a+ A+
a:b a:A B:b A:B :a :A a: A:

Hasklig

https://github.com/i-tu/Hasklig

***
+++
-<<
...
<$>
<*>
<+>
<<<
<|>
=<<
===
==>
>>-
>>=
>>>
|||

!!
&&
*>
++
-<
->
..
/=
::
<$
<*
<-
<<
<=
<>
<|
==
=>
>-
>=
>>
\\
|>
||

I bought PragmataPro a while ago from FontShop.com. The latest version I have is 0.812. What is the process to get a newer version?

I'm using this new Pull Request for Macvim which adds ligature support. Haskelig and Fira Code both work fine, but then Pragmata Pro has these issues where standard words like "back" are turned into back arrows.

The following line is supposed to say "callback"

Kind of bummed I had to buy it just to learn it doesn't work like the other ligature fonts.

I use Pragmata Pro as font in my shell (gnome-shell). Since updating to the very recent version, it seems lots of stuff gets "ligaturized" which at least some false positives.

For example, in hg log I get strange ligatures for email addresses in the format "Firstname Lastname [email protected]".

Oh, it seems it'll produce that with all <something> things. For example, you'll also get garbled output when grepping XML/HTML files.

Oh, wait. I can see that effect just by typing <test> in my terminal.

From https://redlegion.org/2014/04/30/An-open-letter-to-fabrizio-schiavi/

"Mr. Schiavi,

I’ve read your EULA for WOFF/EOT format fonts. Ridiculous. If this is a standard practice, it’s disgusting. This EULA glorifies prostitution. It makes mopping semen at an adult book store seem like a venerable career. I suppose you might’ve garnered that I’m anti-DMCA.

Dropping $26 on a font is borderline acceptable if you enjoy the font enough. To be honest with you, I’m considering dumping your font from my site out of principle. Paying per page-view for a font license is pretty unreasonable.

Honestly, you’re worse than Metallica. If someone sees code on my site and enjoys the font it’s presented in, they can seek you out and pay you. It’s free advertising. Here you are extorting people into advertising for you, and the more advertising they do for you the more you expect them to pay. Does that seem unreasonable to you when presented honestly?

I’ll give you your $26 for your font for personal use, but I won’t give you any more free advertising and I’ll be replacing your font with something that doesn’t use a license that involves exchanging infant souls for currency.

Sincerely,

Red Legion"

Dear Fabrizio,
Where could mere users like me download Pragmata Pro (TTF) for free on New Year’s eve?

Loving the new [INFO] ligatures, but it seems they don't always seem to fire. Apache Maven (3.4-SNAPSHOT shown here ) recently introduced coloured output arround the [INFO] [ERROR] blocks, which don't seem to like the ligature support.

Is this something that can be solved in the font itself?

One of the few things that I like less about this font is the bold version. I think it is perhaps a bit too bold to be easy to read. I guess part of the reason is so it matches the aliased look.

As an example, here are screenshots from Total Commander using a NC color theme. To me, the regular version is a bit too "thin" for this color combination. The bold is so bold that it is a bit hard to read. The last screenshot is Consolas Bold for comparison, I think it looks good here:

I don't know how hard it would be to add a semi-bold version? just for anti-aliased use of course.

Ciao, Fabrizio:

I was wondering if you could add the ISO/IEC/IEEE power symbols (standby, on, off…) which have been encoded in this year’s Unicode version (9.0)?
I find the symbols useful for translating some command-line programs, due to the added length of Spanish words, but I think that there are other use cases for these symbols (such as technical documentation and manuals) that will make these additions useful for other people.

Proposal
Unicode 9.0’s “Miscellaneous Technical” block

POWER SYMBOL         U+23FB  ⏻
POWER ON-OFF SYMBOL  U+23FC  ⏼
POWER ON SYMBOL      U+23FD  ⏽
HEAVY CIRCLE         U+2B58  ⭘
POWER SLEEP SYMBOL   U+23FE  ⏾

TIA for your consideration! :)

The ligatures in PragmaPro look great but there's a serious issue when trying to edit text that was rendered as a ligature. It's impossible to place the cursor inside a multi-part ligature and moving the cursor over a ligature has very unexpected results.

For example, when the cursor is to the right of the != ligature, moving one position left doesn't do anything. The cursor is "virtually" positioned after the ! character but it's not visible. This makes editing text that was rendered as a ligature very difficult. Fira Code works as expected in all editors so it's not a problem with the editor

This occurs in all editors that support ligatures.

PragmataPro 0.822:

Other fonts, like FiraCode, they works:

I noticed that since 0.822, PragmataPro no longer listed as "Fixed" fonts under OS X FontBook, but PragmataPro Mono is; while in 0.821, both PragmataPro and PragmataPro Mono are listed as "Fixed".

I'm really sorry but there is no any differences on latest update about #18 issue.

Can glyph generation for '<=' (and '=>') be turned off?

I'd like to try this ligature font for SystemVerilog(SV). The issue is that SV used <= both as "smaller than or equal to" and as an assignment operator depending on context. I don't think editors will be smart enough to be able to hint the difference.

Is there any chance there is an option to turn off the generation of glyphs for these symbols? (or render them more like an arrow and not the math sign)?

I've been trying your prerelease and I noticed that >> is rendered as the same arrow that => renders as. I believe this is unintentional.

PragmataPro --> Pragmata Pro Regular
PragmataPro Mono --> Pragmata Pro Mono Regular

previous work config，show Regular,Bold,Italic correctly

set guifont=PragmataPro\ Mono:h9:cDEFAULT

current work config，show Regular correctly，but can not show Bold,Italic

set guifont=Pragmata\ Pro\ Mono\ Regular:h9:cDEFAULT

this config do not work

set guifont=Pragmata\ Pro\ Mono:h9:cDEFAULT

i am using version 0.823.

As far as I'm concerned, the only missing one is powerline (glyph) supports for shell, any plans?