BMFont font descriptor parsing library.
Manipulate, import and export BMFont descriptor files in text, binary, XML formats and more.
This crate provides manipulation, import and export functions for BMFont descriptor files.
The core data object is the Font. This object holds, in it's entirety, the information contained within a BMFont descriptor file. Font, when paired with the associated texture file/s, allows us to render the described bit-mapped text.
This crate contains no unsafe code and minimal dependencies.
The modules are organized around the core BMFont file formats:
- text : text format
- binary : binary format
- xml : XML format, requires: --features xml
Each module is provides a number of import from_... and export: to_... functions.
To use: 1. Select the desired BMFont format you want to work with. 2. Select the appropriate from/ to methods based on the data structures you want to work with.
Example: import a BMFont text format file.
```rust use std::io; use std::io::prelude::*; use std::fs;
fn main() -> bmfontrs::Result<()> { let mut buf = fs::read("font.fnt")?; let font = bmfontrs::text::from_bytes(&buf)?; println!("{:?}", font); Ok(()) } ```
Example: export a BMFont text format file. ```rust use std::io; use std::io::prelude::*; use std::fs::File;
fn main() -> bmfontrs::Result<()> { let font = bmfontrs::Font::default(); let mut writer = File::create("font.fnt")?; bmfontrs::text::towriter(&mut writer, &font)?; Ok(()) } ```
Additonal format and source/ destination parameters are supported. Kindly refer to the documentation for details.
The above text was generated with the render.rs example.
If you are uncertain how one might use a BMFont descriptor to render output, this example would be worth studying. Substituting your own graphics backend should not be too difficult.
Due to the numerous graphics backends and usage requirements, this crate makes no attempt at offering a universal rendering solution.
Execute from the project root with:
bash
cargo run --example render FILE
Where FILE is the output image destination (png or jpg) extension:
bash
cargo run --example render ~/Desktop/lorem.png
BMFont text format files are ubiquitous, human readable and easily tinkered with. However, not all tools obey the correct parameter types or constraints, which may result in incompatibility.
Execute from the project root with:
bash
cargo run --example text
BMFont binary files are compact, unambiguous and efficient to parse. However, tooling support may be limited and they are not human readable.
Execute from the project root with:
bash
cargo run --example binary
XML functionality is feature gated: --features xml.
When activated, additional dependencies are pulled in assist with XML processing.
Execute from the project root with:
bash
cargo run --example xml --features xml
JSON is not natively supported. However, as we do support Serde, we can easily cobble together support with Serde JSON.
By default our Serde serializers map boolean types to JSON boolean types: true and false.
However, at least one JSON BMFont parser expects integer boolean types: 1 and 0.
To facilitate the latter we can pass --features serde_boolint, which casts boolean values to integers and vice versa.
Execute from the project root with:
bash
cargo run --example json --features serde`
bash
cargo run --example json --features "serde, serde_boolint"`
The BMFont homepage is here. The site includes detailed documentation, BMFont itself and source code.
I am in no way affiliated with www.angelcode.com or BMFont.
All trademarks belong to their respective owners.
Licensed under either of
at your option.