.github/ISSUE_TEMPLATE/bug_report.yaml

@@ -0,0 +1,55 @@
+name: "Bug report 🐛"
+description: Report rendering issues or unexpected behavior
+body:
+- type: markdown
+  attributes:
+    value: |
+      Please make sure to [search for existing issues](https://github.com/mishamyrt/Lilex/issues) before filing a new one!
+
+- type: input
+  id: version
+  attributes:
+    label: Lilex font version
+    placeholder: "2.530, 2.500"
+  validations:
+    required: true
+
+- type: dropdown
+  id: format
+  attributes:
+    label: Font file format(s)
+    multiple: true
+    options:
+      - .ttf (variable)
+      - .ttf (static)
+      - I don't know
+  validations:
+    required: true
+
+- type: input
+  id: platform
+  attributes:
+    label: Platform
+    placeholder: "macOS 14.5; Linux (freetype 2.13.2); Windows 11"
+  validations:
+    required: true
+
+- type: textarea
+  id: software
+  attributes:
+    label: Other Software
+    description: If you're reporting a bug about Lilex's interaction with other software, what software? What versions?
+    placeholder: |
+      iTerm2
+      VS Code
+      Windows Terminal
+  validations:
+    required: false
+
+- type: textarea
+  id: what-happened
+  attributes:
+    label: What happened?
+    placeholder: Tell what's happening. Include some screenshots! Does it happen only at a certain font size or a certain pixel density?
+  validations:
+    required: true

.github/ISSUE_TEMPLATE/feature_request.md

@@ -0,0 +1,34 @@
+---
+name: Feature Request/Idea 🚀
+about: Suggest a new feature or improvement (this does not mean you have to implement it)
+title: "Feature Request"
+labels: enhancement
+assignees: ''
+
+---
+
+<!-- 
+🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨
+
+I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
+1. If I delete this entire template and go my own path, maintainers may close my issue without further explanation or engagement.
+2. If I list multiple bugs/concerns in this one issue, maintainers may close my issue without further explanation or engagement.
+3. If I write an issue that has many duplicates, maintainers may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
+4. If I leave the title incomplete when filing the issue, maintainers may close my issue without further explanation or engagement.
+5. If I file something completely blank in the body, maintainers may close my issue without further explanation or engagement.
+
+All good? Then proceed!
+-->
+
+# Description of the new feature/enhancement (with images if possible)
+
+<!-- 
+A clear and concise description of what the problem is that the new feature would solve.
+Describe why and how a user would use this new functionality (if applicable).
+-->
+
+# Proposed technical implementation details (optional)
+
+<!-- 
+A clear and concise description of what you want to happen.
+-->

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,17 @@
+<!-- Enter a brief description/summary of your PR here. What character(s) are you changing/creating and how was it tested (even manually, if necessary)? Did you hint the entire font or only the modified character(s)? -->
+## Summary of the Pull Request
+
+<!-- Other than the issue solved, is this relevant to any other issues/existing PRs? -->
+## References
+
+<!-- Please review the items on the PR checklist before submitting-->
+## PR Checklist
+* [ ] Closes #xxx
+* [ ] Requires CHANGELOG.md to be updated
+* [ ] Requires [/images/](/mishamyrt/Lilex/images/) to be updated
+
+<!-- Provide a more detailed description of the PR, other things fixed or any additional comments/features here -->
+## Detailed Description of the Pull Request / Additional comments
+
+<!-- Provide images of the character(s) that are being modified/created at different screen sizes. Clearly identifying specific code points is heavily recommended. -->
+## Before (if applicable) and After Images of the Character(s)

.github/workflows/build.yaml

@@ -1,6 +1,9 @@
 on:
   workflow_call:
     inputs:
+      download_url:
+        default: false
+        type: boolean
       check:
         default: false
         type: boolean
@@ -56,6 +59,7 @@ jobs:
       run: make build-preview
 
     - name: Upload build
+      id: build-upload-step
       uses: actions/upload-artifact@v4
       with:
         name: Lilex
@@ -74,3 +78,14 @@ jobs:
       with:
         name: Preview
         path: preview/dist
+
+    - name: Output download URL
+      if: inputs.download_url
+      run: echo "${{ steps.build-upload-step.outputs.artifact-url }}" > download_url.txt
+
+    - name: Upload URL
+      if: inputs.download_url
+      uses: actions/upload-artifact@v4
+      with:
+        name: URL
+        path: download_url.txt

.github/workflows/release.yaml

@@ -48,7 +48,9 @@ jobs:
     - name: Generate sources with new version
       run: |
         . venv/bin/activate
-        python scripts/lilex.py generate --version "${{ inputs.version }}"
+        python scripts/font.py --config "sources/family_config.yaml" \
+          generate --version \
+          "${{ inputs.version }}"
         python scripts/changelog.py notes Next > notes.md
         python scripts/changelog.py release "${{ inputs.version }}"
 
@@ -60,6 +62,7 @@ jobs:
     - name: Create git commit and tag
       run: |
         git add sources/Lilex.glyphs
+        git add sources/Lilex-Italic.glyphs
         git add CHANGELOG.md
         git add fonts
         git status

.gitignore

@@ -2,8 +2,8 @@
 /build/
 /venv/
 /.vscode
-/Lilex (Autosaved).glyphs
+* (Autosaved).glyphs
+*.glyphspackage
 __pycache__
 .ruff_cache
 reports/
-bundle/

CHANGELOG.md

@@ -1,6 +1,31 @@
 # Changelog
 All notable changes to this project will be documented in this file.
 
+## [2.600] — September 25, 2024
+
+### Added
+
+* Italic variant.
+* Cyrillic yus (`ѫ`, `Ѫ`).
+* Spaces. (enspace, emspace, enquad, emquad, threeperemspace, fourperemspace, sixperemspace, figurespace, thinspace, mediumspace-math)
+* Replacement glyph. (`�`)
+* Cedi glyph. (`₵`)
+* Guarani glyph. (`₲`)
+
+### Fixed
+
+* Bar-hyphen alignment. (`||-`)
+
+## [2.530] — July 27, 2024
+
+### Added
+
+* Circles. (`●`, `○◯`, `◐◑◒◓`, `◖◗`, `◔`, `◜◝◟◞`)
+
+### Changed
+
+* Replaced the `ß` glyph, the previous version is available under the `cv12` variant.
+
 ## [2.520] — July 19, 2024
 
 ### Fixed
@@ -219,3 +244,7 @@ IBM Plex Mono version: 3.000
 [2.510]: https://github.com/mishamyrt/Lilex/releases/tag/2.510
 
 [2.520]: https://github.com/mishamyrt/Lilex/releases/tag/2.520
+
+[2.530]: https://github.com/mishamyrt/Lilex/releases/tag/2.530
+
+[2.600]: https://github.com/mishamyrt/Lilex/releases/tag/2.600

CODE_OF_CONDUCT.md

@@ -0,0 +1 @@
+Be awesome for each other

CONTRIBUTING.md

@@ -0,0 +1,90 @@
+# Contributing to Lilex
+
+Thank you for your interest in improving Lilex.
+
+## Contribute an issue
+
+In most cases, submitting an issue is the first step to contributing to Lilex. Check existing issues and see if your issue has not already been described. Then use one of the templates to ask a question, report an issue or suggest an improvement.
+
+## Pull Request
+
+Here are the basic requirements to consider when requesting a pull request:
+
+- Make sure your PR does not duplicate another PR
+- The request is directed to the correct branch
+- All changes have been checked, nothing unnecessary has been added to the PR.
+- Affected issues and linked PRs are linked
+- Commits are named according to the rules
+
+## Project repository usage
+
+All of the active development work for the next release will take place in the `master` branch. 
+
+Here is how to contribute back some code, documentation or design:
+
+- Fork repo
+- Create a feature branch off of the `master` branch
+- Make some useful change
+- Lint code with `make lint`
+- Make sure the fonts tests still pass with `make build && make check`
+- Submit a pull request against the dev branch.
+- Be kind
+
+Please rebase (not merge) from the `master` branch if your PR needs to incorporate changes that occurred after your feature branch was created.
+
+## Build
+
+### Setup
+
+At the moment building is possible on Ubuntu and macOS. First, install the system dependencies.
+
+#### macOS
+
+```sh
+brew install cairo freetype harfbuzz pkg-config
+```
+
+#### Ubuntu
+
+```sh
+sudo apt install python3-setuptools ttfautohint build-essential libffi-dev libgit2-dev
+```
+
+#### Common
+
+Clone the repository and navigate to the project folder:
+
+```
+git clone https://github.com/mishamyrt/Lilex
+cd Lilex
+```
+
+And then setup python virtual environment:
+
+```sh
+make configure
+```
+
+### Compile
+
+Now run the command to build Lilex.
+
+```sh
+make build
+```
+
+or
+
+```sh
+./scripts/font.py build
+```
+
+### Forced feature activation
+
+The builder gives you the ability to forcibly enable any font features. This works by moving their code to the calt. If the ligatures work, the selected features will also work.
+
+To do this, build the binaries from the source file with the features:
+
+```sh
+./scripts/font.py --features 'ss01,zero' build
+```

Makefile

@@ -1,17 +1,21 @@
-# Project paths
-# BUNDLE_DIR = bundle
-BUILD_DIR = build
-REPORTS_DIR = reports
-SCRIPTS_DIR = scripts
-GLYPHS_FILE = sources/Lilex.glyphs
+# Project directories
+BUILD_DIR := build
+REPORTS_DIR := reports
+SCRIPTS_DIR := scripts
+SOURCES_DIR := sources
+
+# Font sources
+LILEX_ROMAN_SOURCE = $(SOURCES_DIR)/Lilex.glyphs
+LILEX_ITALIC_SOURCE = $(SOURCES_DIR)/Lilex-Italic.glyphs
 
 # Internal build variables
 OS := $(shell uname)
 VENV_DIR = ./venv
 VENV = . $(VENV_DIR)/bin/activate;
 
 define build-font
-	@$(VENV) python $(SCRIPTS_DIR)/lilex.py build $(1)
+	@$(VENV) python $(SCRIPTS_DIR)/font.py \
+		build $(1)
 endef
 
 define check-font
@@ -70,7 +74,7 @@ check-sequential: clean-reports ## check each font file quality
 
 .PHONY: lint
 lint: ## check code quality
-	$(VENV) ruff $(SCRIPTS_DIR)/
+	$(VENV) ruff check $(SCRIPTS_DIR)/
 	$(VENV) pylint $(SCRIPTS_DIR)/
 	cd preview; pnpm eslint 'src/**/*.{svlete,ts}'
 
@@ -80,7 +84,9 @@ preview: ## show CLI special symbols preview
 
 .PHONY: generate
 generate: ## regenerate the font sources with classes and features
-	@$(VENV) python $(SCRIPTS_DIR)/lilex.py generate
+	@$(VENV) python $(SCRIPTS_DIR)/font.py \
+		--config "sources/family_config.yaml" \
+		generate
 
 .PHONY: build
 build: ## build the font
@@ -95,22 +101,6 @@ build-preview: ## build the preview
 run-preview: ## run the preview
 	cd preview; pnpm run dev
 
-# .PHONY: pack-bundle
-# pack-bundle: ## pack the bundle
-# 	rm -rf "$(BUNDLE_DIR)"
-# 	mkdir "$(BUNDLE_DIR)"
-# # Copy fonts
-# 	cp -r "$(BUILD_DIR)/"* "$(BUNDLE_DIR)/"
-# # Copy reports
-# 	cp "$(REPORTS_DIR)/"* "$(BUNDLE_DIR)/"
-# 	cd "$(BUNDLE_DIR)"; zip -r Lilex.zip ./*
-
-# .PHONY: bundle
-# bundle: ## build the bundle
-# 	@make build
-# 	@make check
-# 	@make pack-bundle
-
 .PHONY: release 
 release:
 	@make build