Skip to content

Added: Double-Blocky Font #140

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

Merged
merged 1 commit into from
Nov 23, 2024
Merged

Added: Double-Blocky Font #140

merged 1 commit into from
Nov 23, 2024

Conversation

CatPieLeaf
Copy link
Contributor

@CatPieLeaf CatPieLeaf commented Jul 19, 2024

 ▄▄█ ▄▀▄ █░█ █▄▄ █░ ██▀  ██▄ █░░ █▀█ █▀▀ █░█ █▄█ █
 █▄█ ▀▄▀ ▀▄█ █▄█ █▄ █▄▄  █▄█ █▄▄ █▄█ █▄▄ █▀▄ ░█░ ▄
                                     by CatPieLeaf

A font that uses only TWO rows of unicode blocks!

This PR Adds the Double-Blocky Font! Based in the font "Blocks in two lines" from https://texteditor.com/multiline-text-art/ and the second font from https://fsymbols.com/generators/tarty/. Double blocky contains much more characters than both, some modified and original ones (like M, W, I, l, z), uppercase/lowercase differentiation and all punctuation signs.
it was made by using https://textpaint.com and https://patorjk.com/figlet-editor/#/edit

Preview:

Lowercase:

 ▄▀▄ █▄▄ ▄▀▀ ▄▄█ ██▀ █▀ ▄▀░ ▀ ░░▀ █░▄ █░ ▄▀▄▀▄ ▄▀█ ▄▀▄ █▀▄ █▀█ █▀▄ █▀ ▄█▄ █░█
 █▀█ █▄█ ▀▄▄ █▄█ █▄▄ █▀ ▀▄█ █ ▀▄█ █▀▄ █▄ █░▀░█ █░█ ▀▄▀ █▀░ ▀▀█ █▀▄ ▄█ ░█▄ ▀▄█
abcdefghijklmnopqrstu

 █░█ █░▄░█ █░█ ▀▄▀ ▀█
 ▀▄▀ ▀▄▀▄▀ ▄▀▄ ░█░ █▄
vwxyz

Uppercase:

 ▄▀█ ██▄ █▀▀ █▀▄ █▀▀ █▀▀ █▀▀ ▀█▀ ░░█ █░█ █░░ █▄░▄█ █▄░█ █▀█ █▀█ ▄▀▄ █▀█ ▄▀▀ ▀█▀
 █▀█ █▄█ █▄▄ █▄▀ ██▄ █▀░ █▄█ ▄█▄ █▄█ █▀▄ █▄▄ █░▀░█ █░▀█ █▄█ █▀▀ ▀▄█ █▀▄ ▄██ ░█░
ABCDEFGHIJKLMNOPQRST

 █░█ █░█ █░▄░█ ▀▄▀ █▄█ ▀█▀
 █▄█ ▀▄▀ █▀░▀█ █░█ ░█░ █▄▄
UVWXYZ

Numbers:

 █▀█ ▄█ ▀█ ▀██ █░█ █▀ █▀ ▀▀█ █▄█ ██
 █▄█ ░█ █▄ ▄▄█ ▀▀█ ▄█ ██ ░░█ █▄█ ▄█
0123456789

Punctuation:

 ▄█▄█▀ ▄█▀ ▀░▄▀ ▄▀ ▀▄ █▀ ▀█ ░█▀ ▀█░ █░█ ▀ ░ ░ ░▄ ▄░ ░▀ ▀ ░░▄▀ ▀▄░░ █ ▀▄ ░░░ ▀▀
 ▄█▀█▀ ▄█▀ ▄▀░▄ ▀▄ ▄▀ █▄ ▄█ ▀█▄ ▄█▀ ░░░ ░ █ ▄ ▀▄ ▄▀ ▄█ ▄ ▄▀░░ ░░▀▄ ▄ ▄▀ ▄▄▄ ▀▀
#$%()[]{}´"',.<>;:/\!)_=
                                                                              
 ▀█ ▄▄ ▄█▄ ▀▄▀ ▄▀▄ ██ ░▄░▄
 ░▄ ░░ ░▀░ ▀░▀ ░░░ ██ ▀░▀░
?-+*^|~

That character ß:

 ██▄
 █▄▀
ß

Features:

  • Lowercase and Uppercase differentiation
  • ALL punctuation signs #$%()[]{}´"',.<>;:/\!)_=?-+*^|~, except @ and &
  • It has numbers 3 and 8 (8 is kinda weird..), which were lacking on the second font
  • It has the character ß

@pwaller
Copy link
Owner

pwaller commented Nov 16, 2024

Thanks for contributing this! If you want it to be available in the default install of pyfiglet, it needs to go in fonts-standard.

@peterbrittain
Copy link
Collaborator

Given the origins of this font and lack of clear license from that website, I suggest this is the right folder @pwaller

@pwaller
Copy link
Owner

pwaller commented Nov 22, 2024

I understood the provenance was from the PR contributor, so they could choose. If I am mistaken, then it is fine where it is. @CatPieLeaf any thoughts?

@peterbrittain
Copy link
Collaborator

Sorry, but we need to be careful... The Fedora legal team would say that this needs to be @CatPieLeaf 's own work and have a clear license (e.g. the license for this project) before they would allow it in the default fonts downstream. We need to make that clear in this PR (e.g. a statement from @CatPieLeaf to this effect) before moving.

@CatPieLeaf
Copy link
Contributor Author

CatPieLeaf commented Nov 23, 2024

Well, this is the main reason i didn't try to submit the font to be added into the default fonts.

Since the font used others as pieces to be made plus some original work, and these others don't explicitly show their licenses, i have no idea if i am able to license it. but I believe this falls under the fair use permit.

I'm new on this, and i don't know much about licensing.

@peterbrittain
Copy link
Collaborator

If you've sourced parts from another font, this is the right folder.

@pwaller pwaller merged commit f8c5f35 into pwaller:main Nov 23, 2024
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 this pull request may close these issues.

3 participants