It's just now being kicked into useful, consistent shape by groups like the one supporting Thorium Reader.ĮPUB was never really meant for fixed page layout like PDF it's a packaged web format that was meant to use the flowing, liquid layout of (now somewhat old-school) HTML, defined by the reader/browser instead of the author/designer. Instead of finding a solid niche of usefulness, it became something of the freeware, loosely implemented "in between" standard for electronic documents. It incorporates several layers of standards so that it's useful for accurate color rendering and prepress use.ĮPUB is a community-developed standard that has never really been implemented in a rigorous fashion by anyone it was drafted (v3.0, almost 12 years ago) and left to the individual interpretation of whomever wanted to write an export tool, editor, validator, whatever. PDF is an Adobe-developed standard that has had careful development and tremendous support from the major platform tools it's compact, it's universal and its primary advantage is that it can create a precise electronic page from almost any application, even ones that need to do it through a PDF "print" utility. Need to stop paying all this money for such lacking software. I need to embed fonts in two major book projects and once again, Adobe has let me down.
Adobe indesign ebook manual#
if I wanted the manual read to me I would get my nephew to do so. Do I risk using a template from online only to find out it has hundreds of lines of code that adversely affect my book in other ways? Nope.Īdobe [and I know Adobe is not listening - I've posted in these forums before, Adobe is nowhere to be found due to their extreme lack of support, i.e. Adobe can't even provide within its own app a simple "embed font" css stylesheet. So - appears the only solution is to hack it open and inject custom css. Why is this Adobe?Īnyways, if a simple little app like Sigil [ actually worked I wouldn't be pulling my hair out, but Apple deems it as malware. Adobe cannot possibly not know this shortcoming in their flagship software. So, of course I look up all of the help online and find many complaints and a few resources. embedding fonts. Why is there no checkbox in the export process that specifically requests embedding fonts? So the authors were OK with opaque overlaying in the epubs.īut where InDesign fails miserably - yet again - it's always something. This needed to be in CMYK colour for print, so PNG was not possible in the print layouts, and updating both books given the amount of images. I saw a few issues with overlapping images - looks great in print - but doesn't export. I have two books I have created for authors - gorgeous 250 and 480 page books that can only be handled as fixed layout epubs. InDesign handles this remarkably well. once again - extremely let down by Adobe apps.
0 kommentar(er)
