1 / 0

Web Fonts Process Information Session

Web Fonts Process Information Session. Design and Learning Architect Studios A more in-depth presentation of the Process will be scheduled with Design as a follow up to this presentation . 02/20/2014. Agenda. Background (Fiadhna Gannon): History of the Flash to ePub Transition

jam
Download Presentation

Web Fonts Process Information Session

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Web Fonts Process Information Session

    Design and Learning Architect Studios A more in-depth presentation of the Process will be scheduled with Design as a follow up to this presentation. 02/20/2014
  2. Agenda Background (Fiadhna Gannon): History of the Flash to ePub Transition OpenType Print Font Challenges in ePub3 Web Fonts: An introduction Web Font Process Initiative Background Web Font Challenges Summary Web Fonts Process: High-Level Process (Fiadhna Gannon) Detailed End to End Process: What’s relevant for Design & Learning Studios (Kay Selke) Design Visual Issue Resolution Guide (Jerry Malone) RACI (Lisa DiBattista) Web Fonts Next Steps (Fiadhna Gannon) Q&A The Web Font Process Initiative Working Group Product Strategy & Requirements (Fiadhna Gannon) Design Architecture (Kay Selke, Jerry Malone, Lisa DiBattista) Content Engineering (Stephen Goggin, Ciara Flanagan) Font Support (Joan Werlinsky and David Wettengel)
  3. History of the Flash to ePub Transition Image-based, static content Not mobile compatible Used OTF print fonts Market shift towards HTML5 Dynamic content Compatible with mobile (HTML5-based content) Use of OTF fonts presented issues HTML5 drove the need for Web Font’s
  4. OpenType Font Challenges in ePub3 The DEAL BREAKER: OTF fonts are incompatible with IE10 and iOS7.
  5. Web Fonts – An introduction What are Web Fonts? A “web font” is type face font software that has been created and optimized for displaying and styling text online via web browsers Advantages: Web fonts display consistently across browsers and operating systems Web fonts are often optimized for screen display Designed for quick loading Licensed for digital use Four font types in a web font delivery package: WOFF: Moving toward becoming the standard across browsers EOT: Used for Windows SVG: Legacy format - required for Android devices TTF: Can’t be included in HMH ePub3 products due to licensing compliance issues
  6. Web Font Process Initiative Background Problem Description: As Web Fonts were introduced to HMH for digital content deliveries; two core challenges from a technical and compliance perspective were identified that required quantification, analysis and resolution: Technical: The method to analyse and select replacements was non-standard. In addition, as Web Font replacements are not an exact replica of Print fonts, the use of Web Fonts in ePub3 based content has resulted in content rendering/display issues. Compliance: In order to meet compliance and licensing regulations; a Web Font type (TTF), included in the delivery package to HMH, needed to be removed from content deliveries prior to release to market and/or retrospectively updated post release. Approach: A team was established across CDG (Design Architecture, Content Engineering) & TG organisations (Font Support). This team conducted an in-depth analysis of the issues, identified and proposed solutions, which were reviewed and approved by cross-functional stakeholders. Solution summary:To address Web Font rendering issues; process efficiencies were identified to: Ensure that the majority of rendering/display issues were identified and resolved upstream, minimizing downstream impact. Ensure that the appropriate downstream processes were in place to ensure rendering/display issues were resolved prior to content market release. To address compliance and licensing issues; measures were taken to: Ensure that the compliance and licensing position regarding which Web Font types can and cannot be used, including associated rationale, was documented and communicated. Validated that removing non-compliant Web Font types did not present any additional rendering or other technical issues. Ensure appropriate processes were in place to mitigate compliance & licensing risk to the business.
  7. Web Font Challenges: Summary Technical Problems Not all print fonts in HMH products have web font equivalents. Web font libraries must contain ONLY the fonts used in a project, not full families. Web font spacing is often slightly different than print font versions. We don’t yet have a mechanism to pre-view HMH content within a browser. TTF font must be removed prior to inclusion in product. Limitations within our vendor’s delivery system (20 fonts per set).

  8. Web Fonts Process

  9. High-Level Web Font Process Overview
  10. Detailed End to End Process
  11. DA/LA Steps within Print and Web Font Process

  12. Design Visual Issue Resolution Guide

  13. RACI
  14. HMH Primary Font Documentation
  15. Process Document Outputs End to End Process Flow (Visio) – existing programs RACI – Roles & Responsibilities Matrix Visual Issues Resolution Guide – Design Guide for Build Studio Production Issues Resolution Matrix Production Manager Checklist Production Vendor Checklist
  16. Documentation Descriptions & Locations

  17. Web Fonts – Next StepsQ1 2014 on-going activities

  18. Q1 2014 Web Fonts Improvement Areas

  19. Appendices

    Various documents supporting initiative and resolutions
  20. Primary Issues & Solutions
  21. Primary Issues & Solutions
  22. Print to Web Font Mapping Document Sample
  23. Font Due Diligence Template - Sample
  24. Issue Resolution Matrix - Examples
  25. Production Management Checklist
  26. Production Vendor Checklist
  27. Service Level Agreements - Web Font Delivery A standard turnaround time from the beginning of web font analysis to the delivery of web fonts will be 6-10 business days. This is based on a standard web font request of 150-200 fonts requested during a period when the workload is considered "normal".  For requests over 200 fonts and/or during a period with extremely heavy workloads, the turnaround time on requests will be decided on a case-by-case basis Standard Web Font Requests SLA’s: Web Font Analysis (FS): 2-3 days Design Identification (DA): 2-4 days Web Font Compilation and Delivery (TPS): 2-3 days Total: 6-10 days
  28. Web Font Process Points of Contact Production Management Process Champion: Tony Hetherington Production Strategy & Requirements: Fiadhna Gannon Font Support: David Wettengel Design Architecture: Kathryn Selke, Jerry Malone, Lisa DiBattista Content Engineering: Stephen Goggin & Ciara Flanagan
More Related