And that's the way it should be, and, s'truth, was the way it was ten years ago. You have to have a clean, organized, well-structured layout file to get any further than that local-print output. But in a world where you need to generate PDF, EPUB, HTML and other "downstream" document formats, using scissors and paste and white-out at the layout level will create all kinds of structural and conversion problems. That still works, if your end doc is on paper from your local laser printer. What you're encountering, here, is kind of the sunset for the "hack and slash and make it look good when you hit Print" mode of doing page layout.
CALIBRE READER LINE SPACING CSS FULL
Complaining that the entire field - a full decade later! - has moved to a more structured, professional and standards-based workflow, and that older methods are less and less supported/tolerated in new software, isn't very productive. but you were hardly alone, so it's common to have to clean up and redo work from that era. I could be harsh and say it's all your fault for not doing it right from the start, long ago. Using styles and spacing was fundamental with the third or so generation of layout tools. Putting a return between stanzas is hardly an arbitrary choice either, it's how people have done it for decades. It gets really messy when you try to fix older/noncompliant documents with complex layouts, graphics, etc. And, as well, your material is simply lightly formatted text. You could be writing out a completely clean revision with a quill pen. But before you invest any time in updating, I'd do at least a few rounds of tests to make sure you have identified all the technical faults in the CS6 document and correct them all at the same time - with a recommendation to follow standards, not patches that happen to work this round - rather than just fix this one problem. There are simple Find/Change and script solutions that would automate a lot of the update. And on the EPUB/reader end, v3.0 was still new and raw ten years ago, and almost no one complied with the doc standards. This is not a closed loop changes to hardware and OS and Adobe feature support are all fluid things, and it's been a long, long ten years in this game. I am not sure CS6 will still run and export EPUB without other problems we see posts here almost every day from users trying to get CS6 to work a decade after its release.
If you want to generate EPUBs that are compatible with current generations of readers, I don't see that there's any choice but to format the material correctly.
0 kommentar(er)
