Extension: Custom Fonts

Custom Fonts for Result Rendering

Motivation

Proposal

• Extension of EndpointDescription to allow listing custom fonts: (items with Q: should be discussed)
  • Specification of custom fonts
    • ID: to allow to refer to it
    • URL: to download font (Q: credentials required?)
    • Q: Name, Description → UI info
    • Code Ranges that the font supports
    • Q: License information → UI info but should be some permissive/open license so that anyone can use the font for rendering text
  • Referring in Resource elements to custom fonts that might be required for displaying results correctly
    • ID of font
    • Q: Code Ranges?
• Extension of result Data Views
  • Q: how backwards compatible is this?
  • Advanced Data View: which Span requires the custom font for rendering and for which code points (all or just a subset, or a specific character range?)

• UI
  • Custom rendering using font for selected characters (will be computed in the frontend/client's browser)
  • Optionally offer user information about and option for download of font for future use (besides FCS)

Specification of custom fonts should be considered optional for environments where custom fonts can not be loaded (e.g., security concerns), supported (e.g., hypothetical text-based FCS client, simple XSLT FCS/SRU frontends, ...) or older FCS clients. So, FCS Endpoints can not rely on the support of FCS Clients of custom fonts.

Custom fonts should also use some open/free license.

Examples

• KompLett: https://tcdh.uni-trier.de/en/projekt/komplett
• Thesaurus Linguae Aegyptiae (Egyptian hieroglyphs): https://text-plus.org/themen-dokumentation/user-storys-2020/user-story-313/
• Fonts and support for sign language and spoken language?
  • HamNoSys, Hamburg Notation System

Questions