English   Deutsch
Home Font Catalog Support About Ascender
Search
Font Store Font Store Fonts for Developers Multilingual Fonts Custom Fonts Microsoft® Fonts

Custom Fonts

Custom Fonts

Fonts for Branding

OpenType Font Conversions

Portfolio

Custom Font FAQs


< back to
Custom Fonts

CUSTOM FONT & BESPOKE FONT FAQs

The Ascender team understands that not every font problem can be solved with an off-the-shelf solution. While it would be nice to have a ready-made font for every situation, this is often not the case.

The process of developing a custom font or bespoke font starts with Ascender working together with the custom to answer the following Frequently Asked Questions (FAQs):

Typeface Design

  • Do you have an existing font that you want to start from, or will Ascender create a new typeface design?
  • Is it a single font, or a family with numerous weights and styles?
  • What is the design criteria, what is the audience?


Character Set

  • In what countries will the font be used?
  • What languages and scripts need to be supported?


Font Formats/Operating System

  • Bitmap, TrueType, Type 1, OpenType?
  • Windows, Macintosh, Linux, Unix, Embedded?


Screen or Printing Quality

  • How will the font be used?
  • What type of display technology will be used (CRT, LCD, etc.)?
  • Are there specific sizes that need to be tuned for readability?


Licensing

  • If Ascender starts from an existing typeface do we need permission from the original type designer/foundry?
  • Is the font for your company’s internal use, or will you distribute it?
  • Do you want exclusivity on the custom design?

The above questions represent a sampling of the questions we ask to help define the scope of the project and determine the specifications from which we can provide a quotation.

To learn more about Ascender’s custom font and bespoke font services or to enquire about your specific needs, please contact us.




All trademarks and copyrights are property of their respective owners. Click here for a list of all trademarks used on this site. Site Map