LyonsType's Gutbust (`LT Gutbust`) Font | (Holloway) Chew, Kean Ho's Creative Visuals

LyonsType's Gutbust (LT Gutbust) is a Latin (ID: *Latn) with Cyrillic (ID: *Cyrl) Serif font designed by The LyonsType's Gutbust Project Team. Its design is based on standard serif with a slide fun and funky tweak on certain character making the entire typeface not boring to read especially long text paragraphs.

This font is ideal for general use like poster title, poster text, poster footer text, movie title, movie notice headings, movie notice text, body headings, body text, and body footer text.

Verifying Content Integrity

To secure the content from unauthorized modification by anyone down to 0-1 bit level, all documents and text 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 I keep and maintain 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

Caution

Note to Maintainers: Update each sub-section here matching the project’s specifications from time-to-time especially between releases.

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.
One or more Transformer-based Diffusion Model A.I.s for generative image creation.

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.

One or more Convolutional Neural Network (CNN) A.I.s used for upscaling one or more images for proper editing.

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

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 requires you to pay 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, trademarking font, etc).
- The goal is for downstream to use the font without fear of anything.
- Some designers modify the license terms without taking its legal concequences into account.
- When you have a slightest doubt, DO NOT commit.
To naturally monitor conflicting names and IDs between any font families:
- Font Filename - STRICTLY THE SAME as the font family name. If it is funny looking; leave it. It is the creators' responsibilities to sort of conflicting names and proper naming conventions.
- Product SKU - replace symbols (e.g. & into and) for hardware scanning compatibility purposes.
- If any of the above is conflicting with any of our 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 drop the new ones.
  - If you have the resources to drive the brand changes and prepared to possibly face any legal reprecussion from any socially undesirable creators, you can drive the conversation in a separate accord.
When the font is qualified for re-dstribution, please DO HELP the upstream creators to clean up their license file and marketing pitches. License should have:
1. A Copyright [YEAR] [ENTITY_FULL_NAME] (OPTIONAL_URL) <OPTIONAL_EMAIL> header.
  - [YEAR] - the earliest year is suffice. Copyright works on first birth; not range or latest.
  - [ENTITY_FULL_NAME] - the legally reponsible entity's full name.
  - [OPTIONAL_URL] - the entity's provided URL to contact. The url is enclosed with rounded parenthesis (( )) as defined by programming syntax. This is optional if URL is unavailable. However, Copyright requires at least 1 contactable channel so ensure the alternatives are available.
  - [OPTIONAL_EMAIL] - the entity's provided email to contact. The address is enclosed with angled parenthesis (< >) as defined by programming syntax. This is optional if URL is unavailable. However, Copyright requires at least 1 contactable channel so ensure the alternatives are available.
2. Update/remove the collective alias (e.g. The [PROJECT] Project Authors) definition clause template.
  - DO remove it if there is an existing project authors alias from upstream.
  - When re-distributing a font, MAKE SURE you remove it such a way that we ARE NOT the creators.
  - Update the alias and only use it for downstream communications if this is a new creation project.
3. 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.
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). The layer is an object path called indicator which will remain the same after the font changes.
- 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 text fields MUST BE converted into path data type and then union into a single foreground path layer. This is to make sure end-user can view the sample without needing to pre-setup the font files.
For artificial intelligence:

ONLY USE for internal research or Internet searches internally.
Any automated or "vibe" output commitments are STRICTLY PROHIBITED.
- This is a simple artifact re-distribution project. DO NOT LET ANY A.I. near any of your code and files commitment.
- If you sign-off any A.I. commitment, YOU WILL BE HELD FULLY LIABLE FOR ALL ITS CONCEQUENCES.
- Therefore: STRICTLY HUMAN COMMITMENT.
Use of passive A.I. (e.g. image upscaling) is allowed.

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: LyonsType's Gutbust (LT Gutbust) Font
Creators: The LyonsType's Gutbust Project Team
Packaged-By: (Holloway) Chew, Kean Ho
Contact: hello@chewkeanho.com
SKU: chewkeanho-visuals-fonts-lt-gutbust
UUID: CC1F919D-B849-4FC3-B67B-96289FBEDE13
License: SIL Open Font License (http://scripts.sil.org/OFL)
Repository Made On: 2026-04-06
Repository Made From: Malaysia, South East Asia
Procure: https://github.com/ChewKeanHo/visuals-fonts-lt-gutbust

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.