Abstractus Font | (Holloway) Chew, Kean Ho's Creative Visuals

Abstractus is a Latin (ID: *Latn) Display font designed by The Abstractus Project Team. Its design is based on creative, bold, unique glyphs forming a near readable but graphically cryptic text presentation.

This font is ideal for any eye-catching general use like poster title, movie title, movie notice headings, and body headings.

Verifying Content Integrity

To secure the content from unauthorized modification by anyone down to bit-level (0|1), they are cryptographically signed using one or more cryptography tools such as but not limited to:

GnuPG; AND/OR
OpenSSL.

The public key and the associated certificate are attached. Only the main owner keeps and maintains the private keys. To verify the content's integrity:

GnuPG

Install GnuPG software if not present.
Download the target file and its detached signature file (the .asc file with the same filename).
Download the public key file (.gpg).
Place them next to each other in the directory.
Open a terminal and execute the following command:

$ gpg --no-default-keyring --keyring /path/to/public.gpg --verify /path/to/file.asc

OpenSSL

Install OpenSSL software if not present.
Download the target file and its detached signature file (the .sig/.sign file with the same filename).
Download the public certificate file (.pem) containing the public key within.
Place them next to each other in the directory.
Open a terminal and execute the following command:

$ openssl dgst -verify /path/to/pubkey.pem -signature /path/to/file.sig /path/to/file

Artificial Intelligence (A.I.) Decrees

This decree defines the project’s policy on the use of Artificial Intelligence. The following sections list data lifecycle activities and indicate whether A.I. is deployed. Unless explicitly stated otherwise (e.g. deployment with specifics), A.I. is not used for these tasks.

Data Sourcing & Acquisition

Note

Example activities:

Performing enhanced web searches due to search engine pollution by A.I. slop contents.
Performing completely auto-generated media such as but not limited to images, videos, and audios.

Multiple Large Language Model (LLM) A.I.s as the search engine for searching research materials across the Internet due to massive unwanted A.I publication slops.
One or more LLM A.I.s as the grammar and language corrector and enhancer for superpervised improvement against human written content.

Data Processing & Transformation

Note

Example activities:

Performing multi-steps process development.
Performing data sanitization like data cleaning and data deduplication.
Performing data format compatibility conversion.
Constructing and optimizing data processing libraries.
Upscaling an image with neural network not achievable with conventional image manipulation technologies.

No deployment.

Data Storage & Security

Note

Example activities:

Performing security and threat detection.
Performing Data at Rest encryption and health monitoring.
Performing encryption data storage management.
Performing automated data storage house-keeping.
Performing data storage devices health monitoring and mitigation.

No deployment.

Data Analysis & Insight Generation

Note

Example activities:

Performing multi-steps data analytics.
Performing pattern detection and recognition.
Developing predictive modelling.
Developing natural language queries models.
Creating artificial intelligence's neural network models based on data feeds.
Optimizing artificial intelligence's transfer learning, hyperparameter tuning, etc.

No deployment.

Data Quality Validation & Assurances

Note

Example activities:

Performing end-user use case simulated testings.
Performing automated sanity testings.
Performing penetration & security testings.
Performing anomaly detection testings.
Performing schema validations.
Performing automated testing of data pipelines.

No deployment.

Data Visualization & Reporting

Note

Example activities:

Performing data graphical visualization creation based on data feeds.
Performing summarized dashboarding with graphical design and data feeds.
Performing report writing.
Performing prediction projections.

No deployment.

Data Governance & Compliance

Note

Example activities:

Performing personal identifiable information (PII) filtration and removal.
Performing regulatory compliance checks (e.g., data filtration, censorship, removal as required by law).
Performing compliance monitoring and validation.
Performing data lineage tracking and analysis.
Performing data audit trail analysis.

No deployment.

Data Sharing & Publication

Note

Example activities:

Performing document's metadata creation.
Performing document translation.
Processing data publication licensing and management.

No deployment.

Maintainers' Notes

This is a STRICTLY DECENTRALIZED SELF-SUFFICIENT git repository so all critical and maintenance data and info MUST inside this repository. Anyone has this repository can operate without any restrictions or limitations.
Only keep the git repository for font metadata and display purposes.
- Font files are binary objects which are unsuitable for git commits.
- Use git tag and releases version control strategy instead.
DO NOT use git-lfs due to ambiguous and inconsistent storage allocation policies from various git service providers.
- It will disrupt the work pipeline causing unwanted data losses downstream.
- Some actually monetarily charge you for storage space.
All fonts MUST be strictly licensed under Open Font License without ANY private arbitrary terms (e.g. people from country X are prohibited to use; not allowed to re-distribute without payment; trademarked font, etc).
- The goal is for downstream to use the font without fear of anything.
- Some designers modify the license terms without considering its legal concequences into account. Also watch out for hidden modifications (The same license name with different license body).
- When you have even a slightest doubt: DROP & DO NOT commit. There are a lot of fonts in the market to deal with.
To naturally monitor conflicting font families' names and IDs:
- Font Filename - STRICTLY THE SAME as the font family name. If it is funny looking; leave it. It is the creators' responsibilities to sort out proper naming conventions. For any following type descriptor (e.g. Regular or Bold), it is first separated by a dash (-). Descriptor can be anything.
- Product SKU - STRICTLY THE SAME as the font family name only in lowercase basic Latin, number, and dash ([a-z][0-9]-). You MUST replace all spaces to dash (-) and non-compatible characters to their basic Latin counterparts (e.g. & -> and; 天宇 -> tian-yu). The SKU is used across various applications including repository URL construction.
- If any of the above is conflicting with existing registered font(s):
  - Comply to Copyright laws: the oldest (check its license ownership birth time) stays; the new ones get updated. In any case, the default action is dropping the new ones.
  - If you have the resources to drive the upstream changes:
    - Make sure you are prepared to possibly face any legal reprecussion from any socially undesirable creators.
    - Drop the project with a public notice if things go sour.
When a font is qualified for re-dstribution, please DO HELP the upstream creators to clean up their license file and marketing pitches. This repo uses the unified copyright accreditations licensing pattern. Hence, you should do the following:
- The upstream owns their repository/workspace; we own the re-distributed repository.
- For CREATORS.txt or CONTRIBUTORS.txt:
  1. CREATORS.txt are for the legal entities that are responsible and own the project copyright like authors, principal designers, principal engineers, etc.
  2. CONTRIBUTORS.txt are for any legal entities that contributes to the project but are not owning the project copyright like pull-request contributors, curators, etc.
  3. Each files have their internal guides. Please comply accordingly.
- LICENSE.txt
  1. Update the collective aliases (e.g. The XYZ Project Authors) matching the project correctly. The format is the same as the ones in CREATORS.txt and CONTRIBUTORS.txt.
  2. ENSURE the creators entry is linked correctly with upstream websites.
  3. When re-distributing a font, ENSURE the wording CLEARLY STATES that we ARE NOT the creators but a re-distributor.
  4. There should be 2 EMPTY lines context separator between the copyright entities list and the first line of the first clause.
Please ONLY USE AND SUPPORT the following open source image editing software for securing software supply chain from unwanted threats (e.g. vendor-locked by any expensive or proprietary software):
- Inkscape (https://inkscape.org) - for vector graphics maintenances and exporting SVG plain vector files.
- FontForge (https://fontforge.org) - for assembling and developing font files.
For the thumbnail:
- All known languages are already tabulated accordingly with their ISO3166-Alpha2 (e.g. ZH) and/or ISO15924 language scripts (e.g. Hans/Hant for ZH or entirely ZH-Hans/ZH-Hant).
- If the language is unsupported with blank or tofu, leave it. That's the whole point of demonstrating the font's capabilities.
- The languages'/scripts' elements are labelled and ID-ed with full english identifier using basic latin characters only for programming purposes.
- The principal canvas MUST BE SAVED in inkscape SVG format and retain all legal attributes (license, copyright, etc). The files MUST HAVE inkscape- prefixes to avoid confusion. They are saved inside Pictures/principal-canvas directory.
- The exported svg MUST BE IN Plain SVG format and retain all legal attributes (license, copright, etc). The files MUST NOT HAVE inkscape- prefixes. They are saved inside /Pictures directory.
- The exported svg's texts MUST BE converted into object path data type and then union into a single foreground path object layer. This is to ensure the text remain consistent in the absent of font files (e.g. end-user shopping the font on storefront without owning the font).
For the artificial intelligence (A.I.):
1. Use of A.I. IS ALLOWED INTERNALLY as long as:
  - You as a legal entity (e.g. person|organization) BEARS FULLY LEGAL REPONSIBILITIES for ALL your signed-off commitment.
  - Non-legal entities (e.g. bot|AI account|shadow account|alternate account) ARE STRICTLY PROHIBITED FROM ANY SIGNED-OFF COMMITMENT.
  - Update the A.I Decree section accordingly on any use of any kind of A.I.
2. For any non-supervised or unatteneded automation; or "vibe" commitments, to comply with the previous, please REJECT ALL WITH PREJUDICE AND BLOCK THE ENTITY WHEN NECESSARY.

License

This entire repository is licensed under SIL Open Font License. To ensure better understanding of this license, the following sub-sections will briefly describe how to deploy the content.

For registered non-profit organizations (NGO), you are considered a Commercial Entity the same as any for-profit organization by default. However, you will be eligible for the NGO disbursement grant and receive exception privileges from the creator(s).

Attribution

Attribution is OPTIONAL. Whenever required, you MUST attribute back to the creator(s) as follows:

Title: Abstractus Font
Creators: The Abstractus Project Team
Packaged-By: (Holloway) Chew, Kean Ho
Contact: hello@chewkeanho.com
SKU: chewkeanho-visuals-fonts-abstractus
UUID: 766B2E16-DAC4-4CB3-A716-524B6A6C1C00
License: SIL Open Font License (http://scripts.sil.org/OFL)
Repository Made On: 2026-03-08
Repository Made From: Malaysia, South East Asia
Procure: https://github.com/ChewKeanHo/visuals-fonts-abstractus

Ownership - Personal

Note

This targets any customer wanting to own a copy of the content and then only he/she is using it without sharing with any 3rd-party entity; AND WITHOUT any monetary intention such as but not limited to:

Saving a local copy and then viewing via his/her own mobile device(s); OR
Saving a local copy and then viewing via his/her own personal computer; OR
Saving a local copy for artificial intelligence data training purposes.