Quote:
Originally Posted by davidchavez
Yes, I get your point. I actually have the full indd package. The problem is on the declaration of styles. Each new chapter has a new style, instead of defining few reusable ones, and other problems I am having with this type of packages I have.
Right now I am doing a manual deletion of the new lines which are actually new paragraphs. I do that right now manual, since I tried to delete them using regular expressions on the code view, and I encountered a bug in Sigil that the text did not overflow at the end of the margin and continued to the right. Checked the code and it was fine, so it was a Sigil bug apparently.
Anyways, I don't always use WYSIWYG approach, but most of the time yes. I think that my best bet right now is either to work on fixing the indd (medium term) and continue to do the manual work via doc files or PDF editors. My pain points are new paragraph instead of new line and keeping italics from my copy/paste. So, thanks to all your comments I have a quick and dirty solution, and as I realize there is no best way to solve it, then I have to work with the people that creates the indd package and lets see if eventually I have a working file that does not mean more time to convert than my manual work that I'm doing for now.
Thanks again for your comments  |
Well...FWIW, we deal with this all day long. We not only get files from myriad different designers--and we have zero control over this--but we get a lot of them from, god help us, Indy authors that have signed up for a whole MONTH of INDD, and think that they know how to use it. What we get from those folks is typically worse than the worst Word files, for the same reason--ad hoc styles, etc.
We go through and fix the INDD files, first. To me, that's the simplest method, and then export to HTML/ePUB, and do regex cleaning from there.
If you stopped using regex because the text was overflowing, your CSS is wrong, as Diap mentioned. OR, if you think that there's an actual bug, post it so that the guys can fix it, but I don't recall us running into this, not anytime in the past 5 years+.
If you're doing this commercially, you can't "fix" the problem. You'll simply keep getting cruft, like we do. But working in WYSIWYG, or manually deleting the additional paragraph codes--that's utter crap use of your time and worse, you're going to have junk below.
Why on EARTH anyone that's used INDD for more than 10 minutes would use different styles, from one chapter to another...only God knows. It's bad enough that we still get Book-mode files, in which I end up having to sometimes reassemble files. Just because that's "how we've always done it." (sigh).
Have you tried exporting the main content to doc or docx format, if you're copy-pasting? At least that way, you should retain the font characteristics like italics, etc. (Of course, that assumes that they're not creating faux italics, which happens ALL the freaking time, or using spans, or, or or...)
Hitch