Font metrics estimation

Open
#2 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
computer-graphics

Research direction

Start by tracing node sizing during layout and identify the rendering entry points that consume the fontsize and fontname attributes. Evaluate a font metrics library and bundled font files for the text_size(text, fontsize, fontname) -> (width, height) API; done means glyph dimensions are computed, the bundled font works without system discovery, and unavailable fonts fall back to it.

Written by the indexing model from the issue text.

Description

enhancement

Node sizing during layout depends on knowing how much space a label's text occupies. Use a font metrics library to compute exact glyph advances and text dimensions, exposing a function like text_size(text, fontsize, fontname) -> (width, height).

The library will need access to actual font files. Bundle a default font (e.g. a Liberation or Noto Sans variant) as a fallback so rendering works without relying on system font discovery, which is platform-specific. When fontname specifies a font that isn't available, fall back to the bundled default. This supports the fontsize and fontname attributes.

References

Dominant language
Rust
Stars
0
Forks
0
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from terror/dotgraph

All issues in terror/dotgraph

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.