Alternate Font Format Embedding Now Available with in5

Justin | design,extensions,HTML5,InDesign | Tuesday, March 25th, 2014

One challenge with fonts on the web (aside from font licensing) is that different browsers support different formats for embedding. There are wonderful services like the FontSquirrel Web Font Generator that will generate all the different file formats from a single font file.

The latest version of in5 (InDesign to HTML5) now automatically searches for alternate font formats in the folder of the original font file as well as in the Document fonts folder (if available with the .indd file).

in5 now supports the following formats as alternates when rendering text as HTML with Local Embedding: eot, woff, svg, otf, and ttf. When any of the these alternates are found (with the same name as the primary font file, but a different extension), in5 grabs a copy of the file, includes it in the output, and automatically generates the @font-face CSS for every format that can be found. The primary font used with InDesign can be an otf  or ttf file.

Here’s the complete change log for version 2.0.5:

  • Added capability to embed local fonts from the Document fonts folder.
  • Added support for alternate fonts (eot, woff, svg, otf, and ttf).
  • Added support for lightbox links in SVG text.
  • Added Image Quality control support for items within a Group that has Object Export Settings applied at the Group level.
  • Added Image Quality control support for Pan and Zoom Overlay.
  • Improved leading for single-line text frames.
  • Improved positioning of images with drop shadows applied.
  • Improved automatic keyword generation.
  • Removed the load indicator for multi-page export options (Baker and Liquid State Publishing System).
  • Fixed missing SVG text for textframes that only contained a hyperlink.
  • Fixed On Page Click animation event.
  • Fixed issue with images rendered inside of scrolling frames.
  • Fixed issue with missing content in MSO object states.
  • Fixed miscellaneous crashing bug related to certain text frames.
  • Fixed leading/line-height issue for subscript and superscript when rendering text as HTML.
  • Fixed issue with the Application Cache and file names with spaces.
  • Fixed issue with long lines of text related to noBreak set to passthrough with style.

UX Design Tools: Photoshop Course Now Available on Lynda.com

Justin | design,Tutorials | Thursday, March 6th, 2014

My latest Lynda.com course is now available. Here are more details on the course, or you can jump right to the course page.

French Translation of in5 Dialog Options

Justin | design,extensions,HTML5,InDesign | Tuesday, February 25th, 2014

Cyril Ernou has a great post detailing all of the in5 settings in French.

How to Get Paid for your Digital Publications without Breaking the Bank

Justin | design,HTML5,InDesign | Wednesday, December 11th, 2013

I recently received an email containing the following questions:

Your product [in5] looks amaaazing!

One issue that has always hassled me is the deployment, monetization and DRM [Digital Rights Management] side of things. Do you have any solutions like this for clients selling their creations?

…Aside from the vastly expensive DPS hosting and app store – there don’t seem to be any options available for the small guy to monetize a digital document…?

These are good questions that I believe are of interest to many people. There are several affordable ways to monetize your content and provide some protection to your content at the same time. I’ve put together a list of the best options below (and more are sure to pop up).

1. Host Content Behind a Paid Firewall

Hosting the web content produced by in5 behind a paid firewall (i.e. users pay a membership fee which gives them access to a private part of a website) is a simple way to collect revenue and can provide some basic DRM. Only paid members would have access to the site (via username and password) and content would remain on the server.

Taking the output into app form can also provide revenue (through an app store) and DRM (since apps can be difficult to distribute outside of a store). The options that follow all involve creating an app(s).

Amazon HTML52. Submit Directly to Amazon

You can submit in5 content directly to Amazon. Amazon will actually do the packaging for you! The app is then available to Kindle Fire and several Android devices through the Amazon AppStore. A developer account and app submission are both free. Doesn’t get more affordable than that. (demo video)

Baker Framework3. Create an App Using the Baker Framework*

You can also export to the Baker Framework using in5, and then package as a app for iPhone or iPad. The Baker Framework is an open source library (completely free) for Xcode (the Apple developer code editor, which is free, but requires a Mac) that can produce a standalone app or issues for Apple Newsstand. An Apple Developer license is $99/year (and up) and if you charge for your app (or Newsstand issues), I believe Apple will take a percentage. (demo video)

PhoneGap4. Package as an App using PhoneGap*

You can also package in5 output as an app for multiple devices using PhoneGap. The core of PhoneGap is based on a free, open-source product and there is also a nice web service called PhoneGap Build. Depending on your technical comfort, the cost of this option will vary somewhat. The more you can do yourself, the cheaper this option is. Even if you prefer to use the web service (the least technical option) you can produce a single app for free and the next plan up starts at $9.99/month.

liquid-state-2005. Coming Soon: Package as an App using Liquid State*

Currently in beta, Liquid State is a web service that is designed to import several types of content, including content produced by in5. Liquid State can then create an app (or “issues”) for multiple devices. Liquid State will offer single app pricing and monthly subscriptions, both of which will be more affordable than the current Adobe DPS pricing. There’s also the possibility that there will be mutual discounts available to in5 and Liquid State customers. If you’re a current in5 user and you’d like to be part of the Liquid State beta you can contact the co-founder, Philip Andrews, directly (philip AT liquid-state DOT com).

*There are some costs associated with submitting to the app stores (I believe is the most costly is Apple’s at around $99/year for a single developer) which are separate from the product or service that does the “packaging” for you.

Mobile App Design and Submission has Never Been This Easy

Justin | design,HTML5,InDesign | Tuesday, December 10th, 2013

I mentioned a while back that Amazon had quietly revolutionized the app creation process by allowing submission of HTML5 apps to their marketplace. Very few people understood the significance of this change which allows people to publish without the burden of going through the traditional app production process. So I’m going to cover this topic a bit more within this post. Firstly, what does the existing process of creating and submitting an app to an app store look like?

The Typical App Submission Process

The steps required to create and submit an app vary depending on the tools you’re using and the app store you’re submitting to, but the steps go something like this:

  1. Pay for a developer account (recurring annual fee).
  2. Use your developer account to produce a code-signing certificate (a way to verify that you paid to publish).
  3. Insert the signing certificate into your app.
  4. If you’re a coder, compile your app. If you’re not a coder, pay some service or developer to compile your app.
  5. Submit your app to the app store and wait for approval.

The New Process Created By Amazon

Amazon essentially reduced this process to a single step: submit your content to the app store. No fee, no signing-certificate, no packaging, no need to know a heavy-duty programming language or to pay someone who does. Your content just has to be in the form of HTML.

I don’t think it was clear to many people just how easy Amazon’s app submission process has now become, and how favorably it compares to other options.

Thankfully, David Isbitski, recorded a video on how to submit an HTML5 Web App to the Amazon Marketplace:

Unlike other app stores, getting an Amazon Developer account and submitting an app is totally free!

Don’t know how to create HTML5? No problem.

You don’t need to be a web developer to take advantage of Amazon’s HTML5 app submission process. You can export HTML5 directly from InDesign using in5, upload your content to a server and submit the URL directly to Amazon. InDesign to app! No programming knowledge required and no recurring costs.

How it will get even easier

In version 2 of in5 (coming soon), you’ll be able to enter the Amazon Verification Key into the in5 dialog and in5 will even generate the web-app-manifest.json file for you so that you can focus entirely on the design of your app (and not programmer-type things like “manifest” files).

Here’s a preview of the two fields that will be available in the SEO & Meta section of the in5 dialog starting in version 2.0:

in5 Amazon options

Take a look at in5 and the Amazon HTML5 submission process and let us know what you think in the comments below.

Page 1 of 912345...Last »