Mirror of Github repository
Go to file
Riesi 75feae0f0d
preparations for sticker bot update (#69)
* preparations for sticker bot update

* remove file ending

* fix some emoji mapping

* fix some review nits from Miepee

* Delete root.txt

* fix more nits

* bow to our all mighty Miepee overlord!
2023-11-23 19:35:35 +01:00
.github/workflows Actions: use external script 2022-03-01 14:55:26 +01:00
png [png] generate PNGs 2023-10-23 20:19:57 +02:00
svg [frog] stay away from my Vodka! 2023-10-28 18:14:37 +02:00
telegram_packs preparations for sticker bot update (#69) 2023-11-23 19:35:35 +01:00
.gitattributes add PNGs to LFS 2023-09-28 23:00:49 +02:00
LICENSE general LICENSE file (#26) 2022-04-19 17:24:02 +02:00
LICENSE-CODE Clean readme+make code license clearer (#25) 2022-04-19 15:24:06 +02:00
LICENSE-GRAPHICS [meta] improve README, use correct grahpics license and include a proper code license 2022-01-03 20:35:31 +01:00
README.md [meta] fix typo in README 2023-05-12 19:26:46 +02:00
checkEmojis.sh make script executable 2022-05-19 09:07:30 +02:00
gen_png.py [tools] add tag message and small refactor (#49) 2022-11-30 15:26:04 +01:00
telegram_definitions.txt make file 120 entries long 2022-05-31 17:49:34 +02:00

README.md

Most of theses frogs are based on the SVGs of Twemoji by Twitter, Inc and other contributors (CC-BY 4.0). Others are unique designs with other inspirations in mind.

Here is a website showing all frog images in the current repository:
https://riesi.github.io/frog_emojis/

Have fun using them! 🐸

License

By contributing you agree to license your contribution under the terms of the GPLv3 (for code) and CC-BY 4.0 (for graphics) licenses. The corresponding license can be found in the LICENCE-CODE and LICENSE-GRAPHICS file respectively. The following links also reference the licenses:

GPLv3: https://github.com/Riesi/frog_emojis/blob/master/LICENSE-CODE

CC-BY 4.0: https://github.com/Riesi/frog_emojis/blob/master/LICENSE-GRAPHICS

Contributing

When submitting PRs keep the following in mind please:

  • only submit SVGs. PNGs will be automatically generated by a maintainer after a merged PR.
  • use the following naming scheme: verb/adjective+Frog+Object+Differential with camelCase. For example, sleepyFrogFamilyTkg for an emoji with a sleepy frog family, which is differentiated from a sleepy frog family, by including Tkg.
    • should you submit an emoji that has a clear emoji mapping to it, please prefix it with U[unicodeChracter]-. For example, U1f35e-frogBread.
    • should you be on Windows and case sensitivity seems to commit wrong, run the following command in the git repo: git config core.ignorecase false
  • only submit SVGs with the file ending .svg. Not .SVG or .sVg

In addition to the following guidelines for the SVG's:

  • file name should not contain spaces
  • the SVG should be a square
  • the SVG should not be all on one line.

If you have Bash and Unix core utilities installed, you can execute the checkEmojis.sh script to locally check if your SVGs fulfill the requirements.

Generating PNGs

If you want to locally generate PNGs from the SVGs, you can use the gen_png.py script.

Dependencies

  • Python 3.9 - To run the script.
  • Inkscape - Used to generate the PNGs. Needs to be located in PATH.
  • (Optional) git - Can be used to automatically add a new commit with the generated PNGs.

Usage

gen_png.py [OPTION]

-h, --help                      Shows this help message.
-a, --all                       Generate PNGs of all SVGs.
-s, --specific S [S ...]        Generate PNGs for each S in the "svg" folder. The '.svg' suffix is optional.
-r, --resolution R [R ...]      Custom resolutions that will be generated instead of the defaults (72, 512, 1024).
-g, --git                       Generates PNGs of SVGs that changed since last auto tag and creates a git commit with them. Requires 'git' to be installed and located in PATH.