Crates.io | bmfont_rs |
lib.rs | bmfont_rs |
version | 0.2.0 |
source | src |
created_at | 2021-09-10 13:56:07.724506 |
updated_at | 2022-06-24 15:38:19.777042 |
description | Load/ save/ manipulate BMFont files |
homepage | https://github.com/shampoofactory/bmfont_rs |
repository | https://github.com/shampoofactory/bmfont_rs |
max_upload_size | |
id | 449255 |
size | 184,849 |
BMFont font descriptor parsing library.
Manipulate, import and export BMFont descriptor files in text, binary, XML formats and more.
This crate provides building, manipulation, import, and export functions for BMFont descriptor files.
The core data object is the Font. This struct holds, in its entirety, the data contained within a BMFont descriptor file. When paired with the associated texture bitmap file/s, we have the information required to render the font in question.
Due to the numerous graphics backends and usage requirements, this crate does not attempt to offer a universal rendering solution.
This crate contains no unsafe code. Also, unless specified by compilation switches, it doesn't pull in any external dependencies.
The modules are organized around the core BMFont file formats:
text
: text formatbinary
: binary formatxml
: XML format, requires: --features xml
Each module is provides a number of import from_...
and export: to_...
functions.
To use:
Example: import a BMFont text format file.
use std::io;
use std::io::prelude::*;
use std::fs;
fn main() -> bmfont_rs::Result<()> {
let mut buf = fs::read("font.fnt")?;
let font = bmfont_rs::text::from_bytes(&buf)?;
println!("{:?}", font);
Ok(())
}
Example: export a BMFont text format file.
use std::io;
use std::io::prelude::*;
use std::fs::File;
fn main() -> bmfont_rs::Result<()> {
let font = bmfont_rs::Font::default();
let mut writer = File::create("font.fnt")?;
bmfont_rs::text::to_writer(&mut writer, &font)?;
Ok(())
}
Unfortunately, there exist several BMFont tools that output broken files.
Either they do not comply with the BMFont standard as written or contain other errors.
When attempting to load these files, bmfont_rs
will emit an error describing the problem.
We may be able to work around or ignore some of these problems using the LoadSettings struct.
Simply build the LoadSettings
instance using the desired behavior switches and pass it into the ext
form of the load function.
If you encounter a BMFont file that appears to work with other tools, but not bmfont_rs
then kindly open a ticket.
It may be possible to add the correct behavior switch in future versions of bmfont_rs
.
Example: import a BMFont text file with incorrect character counts.
use std::io;
use std::io::prelude::*;
use std::fs;
fn main() -> bmfont_rs::Result<()> {
let src = fs::read_to_string("font.txt")?;
let settings = bmfont_rs::LoadSettings::default().ignore_counts();
let font = bmfont_rs::text::from_str_ext(&src, &settings)?;
println!("{:?}", font);
}
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:
cargo run --example render FILE
Where FILE is the output image destination (png or jpg) extension:
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:
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:
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:
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:
cargo run --example json --features serde`
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.