Convert BDF to OTB
Turn BDF fonts into OTB. An OpenType bitmap font, the form Linux desktops read bitmap fonts in, with one-bit glyphs and the font's names, ascent and descent.
Converted in an isolated sandbox on our serversDeleted after 24 hours
Drop BDF files on the dialor turn it to pick what to do
A bitmap font in a form Linux reads.Each glyph keeps its pixels, at the font's own size.
What you get
An OTB file, which holds X11 bitmap-only fonts in an sfnt container. This is the form current Linux desktops read bitmap fonts in. The conversion gives you one file.
The glyphs keep their pixels, at the font's own size. Nothing is redrawn or resized.
What changes or is left out
The NUL character is left out. Glyphs that no character maps to are left out too.
Some X11 fonts give two characters the same glyph name, as many name the no-break space space. When a glyph repeats another's name, only the first character keeps it.
The OTB holds no outlines, so it looks right only at its size. Scaling it up or down does not give clean results.
BDF and OTB.What each format is.
The formats
BDF Font
Bitmap fonts in the X11 text format.
- Extensions
- .bdf
- MIME type
- application
/x -font -bdf - Kind
- Fonts
OpenType Bitmap
X11 bitmap-only fonts in an sfnt container, the form current Linux desktops read bitmap fonts in.
- Extensions
- .otb
- MIME type
- application
/x -font -otb - Kind
- Fonts
In your code.The same BDF to OTB conversion through the API, for your app or your agent.
$ cv convert font.bdf font.otb$ cv convert font.bdf font.otbQuestions.What people ask about BDF to OTB.
Yes. The glyphs keep their pixels, at the font's own size.
It is made for its own size only. It holds no outlines, so it looks right only at that size.
Many X11 fonts give the no-break space the name space. When a glyph repeats another's name, only the first character keeps it.
No. The NUL character is left out, and so are glyphs that no character maps to.