Skip to content
New issue

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

Font is not listed in cmd / mobaxterm #10

Closed
anilkumar150886 opened this issue Aug 28, 2023 · 12 comments · Fixed by #13
Closed

Font is not listed in cmd / mobaxterm #10

anilkumar150886 opened this issue Aug 28, 2023 · 12 comments · Fixed by #13

Comments

@anilkumar150886
Copy link

anilkumar150886 commented Aug 28, 2023

0xProto is not visible in windows command prompt !! I have installed from .ttf file, but still not able to see it.!!
Not sure in mac though..!!

image

@matype
Copy link
Member

matype commented Aug 29, 2023

@anilkumar150886 Thank you for using 0xProto.

I recently tested 0xProto on the Windows 11 command prompt and it worked perfectly.

I have a couple of questions for you:

  1. Which version of Windows are you currently using?
  2. Is it possible to use 0xProto in applications other than the command prompt? (Were you able to successfully install the fonts?)"

@anilkumar150886
Copy link
Author

anilkumar150886 commented Aug 31, 2023

I'm using windows 10.. I'm using App such as VSCode, Visual Studio, Notepad++, for which I'm able to use.. But not in Cmd..

In MobaXterm, i'm able to see the fonts, but the spacing is too wide..

image

I think cmd / terminals / consoles recognizes only monospace font family. .!!

@matype
Copy link
Member

matype commented Sep 1, 2023

@anilkumar150886 Hmm... What version of 0xProto are you using? If you are using v1.000, it may not be recognized as a monospaced font. I fixed that bug in #2 and it should work in v1.001 or later.

If you are already using v1.001 or later, if you have time, please try .otf files instead of .ttf.

@anilkumar150886
Copy link
Author

Tried both *.ttf and *.otf.. with no Luck!!

image

@matype
Copy link
Member

matype commented Sep 2, 2023

Thanks for checking!
I will keep this in mind. Perhaps there are other flags, etc. to indicate that it is a monospace font.

@anilkumar150886
Copy link
Author

Thank you..
I see, your font is going to be selected as one of the favorite coding languages, for sure..
It just needs more improvisation, if you starting addressing issues and introduce more font family weights..!!

@matype
Copy link
Member

matype commented Sep 2, 2023

Thank you!
I have no plans to add font family weights. Please see #12 .
Well, please wait a bit as I will do my own research on this issue you have discovered.

@matype
Copy link
Member

matype commented Sep 2, 2023

@anilkumar150886 Hi. The following zip file contains font files with changes that attempt to resolve this issue.
If you have time, could you install this font file and check again?

0xProto_1.101_beta.zip

I set a flag called panose in the OpenType OS/2 table.
I heard that panose is a flag that is not used much now, but it seems that Windows 10 cannot recognize monospace unless it is enabled.
https://learn.microsoft.com/en-us/typography/opentype/spec/os2#panose

@anilkumar150886
Copy link
Author

anilkumar150886 commented Sep 3, 2023

@masaakim Thanks!!. I was able to test and now the font is recognized in cmd.. it looks good.. but in mobaxterm, the fonts are very wide..

image

Mobaxterm needs fixing on width spacing..!!

image

@matype
Copy link
Member

matype commented Sep 3, 2023

@anilkumar150886 Thanks for checking! I'm glad you can now reference fonts in Command Prompt in Windows 10.
(FYI: #13 is the PR to solve this problem. )

@matype
Copy link
Member

matype commented Sep 3, 2023

Mobaxterm needs fixing on width spacing..!!

Thanks for the feedback. I will try to fix this issue next.
I don't want to deal with multiple issues on one issue, so I created a new separate issue. #14

@anilkumar150886
Copy link
Author

So, One real feedback which you might very often from everyone , is on different "Weights".
You might have to rethink on your decision and give more options to users as per their choice... Cheers,..!!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants