Bellarina Font: Hendra Pratama’s Monoline Signature Design

Hendra Pratama’s own HPTypeWork page identifies Bellarina and lists TTF, OTF and WOFF resources together with PUA encoding. His creator storefront describes it as a monoline signature font. This guide concerns that identified product rather than every font sharing the name Bellarina. The creator’s documented uses include personal name cards and display lettering, but those suggestions do not guarantee that one setting will remain legible in every application or physical output.

The creator’s PUA label is relevant when reviewing how optional glyphs are accessed, but it is not a promise that copying a styled result to any application will preserve its appearance. Keep a plain editable copy of the intended name and note any special glyph selections separately. Inspect the actual resource and the target application’s character controls. A name-line design and evidence that a person signed or authorized a document are different things.

Build an original name treatment using the actual capitalization, surname and any initials. Review the joins and repeated letters in a large working view, then place the same wording on the intended small card or attribution line. Leave space around long strokes so the name does not collide with a role or contact detail. If a flourish weakens recognition, compare the ordinary character before changing the spelling or adding unrelated symbols.

Set the name beside a plain role line and a realistic address or date. Review each line at its final size rather than shrinking the whole composition uniformly. Sacramento and Allura below are independent script comparisons; they do not provide Bellarina software or reproduce its optional glyphs. Follow the creator’s source for the intended Bellarina resource and retain the actual edition and supplied terms with the editable design so later revisions can reproduce the chosen letters.