Google Code Exporter

``` Make deployment easy. 1. Use a tei2html.config file with all details 2. When this file is not found, run an auto-config file that detects the presence of required tools,...

Original comment by `jhellingman` on 16 Apr 2014 at 9:21 - Added labels: **Type-Enhancement** - Removed labels: **Type-Defect**

``` Also check generated table of contents, etc. ``` Original comment by `jhellingman` on 18 Jan 2011 at 11:24

``` See also: http://www.idpf.org/accessibility/guidelines/ http://shop.oreilly.com/product/0636920025283.do ``` Original comment by `jhellingman` on 18 Jun 2014 at 6:42

Original comment by `jhellingman` on 2 Sep 2014 at 1:22 - Changed title: **Improve accessibility of generated HTML output**

Original comment by `jhellingman` on 20 Oct 2006 at 7:14 - Changed title: **Output HTML is invalid when TEI contains nested paragraphs.**

``` In general, the current solution (inserting and using unquoted text) is fragile. A more robust solution would use XSLT 2.0 group-adjacent to pull out those elements forbidden in HTML...

``` See: http://www.pgdp.net/wiki/CSS_features_not_in_EPUB ``` Original comment by `jhellingman` on 5 Jul 2010 at 12:12

``` Maybe a graded approach will work best here, selecting a subset depending on support level. 1. Full CSS 2.0 or 2.1 2. Official ePUB limitations. 3. Bare minimum, with...

``` Also see http://www.pgdp.net/wiki/The_Proofreader's_Guide_to_EPUB * Remove page-numbers from generated ePub (but retain anchors) * Somehow designate some illustrations as non-essential (decorative initials, page ornaments), so they can be omitted from...