annoying typos - sigil can fix but any workable way to complain to publishers

[cybmole]

for my own reading, I have taken to using sigil to fix annoying typos ins what should be good quality sold books.

but is there any method that actually works when it comes to feeding these back to publishers
Two examples from current library loans, which I'll be returning soon

1. the book is called SLIVER OF TRUTH, but the title page has, in huge letters, SILVER OF TRUTH. how did that one slip through the net ?. ( it also has a forced embedded font which is very hard to read, compared to my e-readers default font, but I have to hack the book in order to be able to change font)

2. the book is Cloud Of Sparrows, It has a character called Hidé, with the accented e. That's fine, but much of the time he's called Hid#233; which is very annoying. I see that that's almost the correct html for an accented e special character, but not quite, it needs a & in place of the # I assume. I checked that one in 3 programs, sigil book view, Sony reader for PC, and my actual Sony T3 reader. that's how it is in all 3 views!

would it be a total waste of time to compose emails to the publishers, assuming I can even find an email address ?

[Tex2002ans]

Originally Posted by cybmole

for my own reading, I have taken to using sigil to fix annoying typos ins what should be good quality sold books.

I do the same thing. As I read, I have a piece of paper where I mark every single little typo/mistake that I find... and then I go fix it in Sigil to create an ultimate copy.

Luckily, almost everything I read is CC3.0 or in the Public Domain, so I just release my Fixed copy for the world (and hope the publisher updates their copy on their site/Amazon/B&N/elsewhere).

This is actually how I got my job! I kept bugging the publisher with all of my emails with fixed EPUBs.... and they finally decided to give in to my conversion superiority! I just completed my 200th book conversion not too long ago.

Originally Posted by cybmole

1. the book is called SLIVER OF TRUTH, but the title page has, in huge letters, SILVER OF TRUTH. how did that one slip through the net ?.

Title Pages, usually these are just type it in two seconds and forget it! I must admit, a few of those have slipped through me while I have been making EPUBs. (Who looks at Title Pages in ebooks anyway? I think the metadata being correct is much more important... now messing that up is embarrassing!).

Originally Posted by cybmole

( it also has a forced embedded font which is very hard to read, compared to my e-readers default font, but I have to hack the book in order to be able to change font)

This just needs to die. This can also happen in many cases where they export directly out of something like InDesign + embed their fonts.... or if they try to design for iBooks instead of the general ebook market.

Embedded fonts should only be used extremely sparingly if at all.

Originally Posted by cybmole

2. the book is Cloud Of Sparrows, It has a character called Hidé, with the accented e. That's fine, but much of the time he's called Hid#233; which is very annoying. I see that that's almost the correct html for an accented e special character, but not quite, it needs a & in place of the # I assume. I checked that one in 3 programs, sigil book view, Sony reader for PC, and my actual Sony T3 reader. that's how it is in all 3 views!

Indeed, you are correct.

This could have just been crappy conversions from previous material (let us say they had an old .lit file, ran it through a converter, and popped out an EPUB).

Or maybe something went wrong when flipping between different encodings.

Or it could have just been a horrible search/replace.

This whole horrible conversions reminds me of a few books I purchased from B&N. I read the entirety of the Wild Cards series (22 books so far). There were two in the series published by "Ibooks, Inc." which were HORRIBLE conversions:

• #16 (Deuces Down)
• #17 (Death Draws Five)

Here is a screenshot of #17... You can see they fed it right into calibre with all the wrong settings:



I mean.. chapters weren't event split! There was no TOC!

And they were just riddled with errors/typos left and right.

Originally Posted by cybmole

would it be a total waste of time to compose emails to the publishers, assuming I can even find an email address ?

You can try and hope for the best... perhaps they might take notice. In many cases though, your complaints go unheard.

If you can't get a hold of the publisher, maybe leaving your complaints/fixes in an Amazon Review?

If that fails, maybe just put it up on a site somewhere. (I really wish that there was a large Typo Database, where everyone can submit the mistakes they find).

I settled on this format for physical books/PDFs:

Page 123: par. 1: typo/explanation

Here is a sample sentence that I copied from the book which has a tpyo.

par. 0 if the paragraph carries over from the previous page. You can use other positions if it makes more sense (bottom paragraph, top paragraph, first paragraph after blockquote, ...). As long as it just helps quickly narrow the position down for a typesetter besides having just the page number on which the error occurred.

(Forgive the self-promotion) Here is an example of it in action for this book that I took off of Archive.org and converted, "Speeches, Arguments, Addresses, and Letters of Clement L. Vallandigham": http://misesbooks.blogspot.com/2013/...esses-and.html

(Forgive the self-promotion) For digital books... if there are a massive amount of typos, I typically use a code comparison program (I personally use Beyond Compare). And I compare the before/after. Then I would email that to the publisher + your fixed version + an explanation.

"On Doing the Right Thing" by Albert J. Nock was a conversion that I was paid to clean up. Attached to this post:

• ZIP file there is an HTML file generated by Beyond Compare
• Before/after EPUBs
• The original PDF

[cybmole]

a "most annoying typos " repository would be a great addition to this site, if practical

just a simple 1 thread per book place to dump findings so that someone else could maybe benefit

IBSN + format would suffice to uniquely identify ?

quoting extracts of copyright books purely to show errors should be legal ?

[Jellby]

Originally Posted by cybmole

would it be a total waste of time to compose emails to the publishers, assuming I can even find an email address ?

I guess that depends on the publisher, but most probably it will.

Originally Posted by Tex2002ans

I do the same thing. As I read, I have a piece of paper where I mark every single little typo/mistake that I find... and then I go fix it in Sigil to create an ultimate copy.

I used to do that, now I use my reader's highlight feature for that

[Tex2002ans]

(Be sure to see my edited post above, I added some stuff at the end)

Originally Posted by cybmole

a "most annoying typos " repository would be a great addition to this site, if practical

Well in the E-book uploads section on MobileRead, you can just post in the person's topic, and hope they see it... Usually the people who post books here are extremely proud of their conversions, and will fix typos up right away.

I know if I am informed of any typos, I fix them up ASAP and get new versions up.

Originally Posted by cybmole

just a simple 1 thread per book place to dump findings so that someone else could maybe benefit

IBSN + format would suffice to uniquely identify ?

I gave this some thought a while back when I was first hired... the typo situation really makes me angry!

I tried a Wiki, but it was pretty crappy... people don't have the same standards:

• Some people were using the dreaded calibre/ADE/iBooks/Kindle page numbers.
• What if a person was reading a slightly different version of the book than you (EPUB/Kindle)?
• There was no control on revisions. What if theirs was a "v3" and yours was a "v6"?
  • What is the naming convention from Amazon? I have never purchased a book from them (nor do I plan to).
  • This is why I started tagging everything I convert with a [DD.MM.YYYY] format.
• Some people were only posting partial sentences
  • More might also be helpful if it is a "potential" error/typo, so others can quickly gather context without having to look it up in the book.
  • This was enough for me working on a digital copy, I can just search/replace, but for the typesetter to go back and fix the physical copy, it was not so easy.
  • (Physical) This is why I upgraded to marking the Page + paragraph #.

A gathering of typos in books doesn't really exist anywhere (at least to my knowledge).... which is why I just started posting them on that blogspot I put up.

Maybe:

• link to directly to the B&N/Amazon/Kobo/whatever page you purchased it from
  • (or if Public Domain, directly to the Archive.org/PDF).
• Title
• Author
• any relevant info (filename, version number, etc. etc.).
  • Example: The books that I purchased from B&N come in the format:
    • ##############_epub.v#.epub
    • "ISBN#" + "_epub." + "version number" + .epub

If you have a book club, and a lot of people are reading the same book... make sure everyone just jots down any mistakes they find. Combine + post.

Or if you have a class where everyone is reading the same book, promote reporting errors! Combine + post!

If there is no digital copy of the book yet, it would be extremely helpful if there was a list of typos that people have already ran into in the physical/PDF, so when someone comes along in the future to digitize it, they can use it! For example, in my case, I work mostly on books that have never been digitized (besides the PDF scan). I want to put out the highest quality HTML/EPUB copy of the book, and the typo reports would help me towards that goal.

Having the typos out in a public place might be able to warn others of the crappiness, or push the publishers towards fixing the version... as a last resort, it can help others fix their own copies of the ebooks.

Originally Posted by cybmole

quoting extracts of copyright books purely to show errors should be legal ?

It should be.... although I don't know how they would like it if the conversion was so crappy there are typos on every paragraph. :P

Originally Posted by Jellby

I guess that depends on the publisher, but most probably it will.

LOL according to my knowledge, they usually just toss it in the trash filing cabinet because they don't have any plans of releasing any new versions of the book ever any time in the near future.

Side Note: I see that the A Song of Ice and Fire books came out with a few newer versions since I last downloaded them off of B&N. Time to compare them and see what they changed.

Originally Posted by Jellby

I used to do that, now I use my reader's highlight feature for that

My Nook has crappy highlighting, and I don't trust it to save the highlights correctly (I typically overwrite the EPUB as soon as I fix it in Sigil)! Now if only there was a way I could have Sigil while laying in bed reading... now that would be ultimate!

[eschwartz]

If you report books to Amazon for typos, they will sometimes pull the book down until the publisher updates a corrected version. I imagine that is a pretty good incentive...

[Hitch]

Originally Posted by eschwartz

If you report books to Amazon for typos, they will sometimes pull the book down until the publisher updates a corrected version. I imagine that is a pretty good incentive...

Yes: but it has to have some pretty good number thereof. The long and short of it is, a reader has to have complained; the reader has to have said that the vast number of typos impaired their ability to enjoy the book, and then Amazon will send a list of typos to the author, and ask--not tell--them to fix it.

IF a book is put up that is just unreadably bad, Amazon will remove it from sale until fixed, but there seems to be no realistic, logical, pattern-recognizable methodology for this. I had a client (I've told this story here) that had a book that was an anthology of character studies. Instead of an inline TOC called, "TOC," she had "Cast of Characters." The doofi (doofuses) at Amazon actually removed it from sale until she "fixed" it, and I gave them what for on that, as the book met the tech specs, the CoC was set as the TOC on the Guide, and those geniuses didn't have the sense to LOOK at the thing to see that on the GoTo, it went to the "Cast of Characters" and figure it out from there.

I posted here on MR recently that while I am certainly no fan of typos, I think the craze for fixing every little typo in a BOOK has done no one any favors, particularly the authors OR the readers. I said, and I stand by the idea, that this concept that books can be fixed instantly leads writers to think that it's okay to put up substandard work and "fix it later," or that a book isn't a fixed (as in, completed, not as in repaired) creation, but rather, a WIP posted on Amazon et al for a form of crowd-sourcing editing and proofing. This means that we, the readers, get stuck with crap that should never have been published, and it's considered acceptable. Don't believe me? Read the Amazon forums, and see how on nearly every "need editing" post they talk about how they'll "get it edited after some sales when I can afford it." Or the authors who "help" others with "republishing" and "updating" their books, bragging about how they've updated theirs "ten times."

This is a DIRECT result of the whole silly, self-satisfied cycle of "reader finds typo, reader complains about typo, publisher races to satisfy need for instant gratification of reader and fixes typo, rinse-repeat." NONE of us would have done this 10 years ago, nor would we do it NOW with print books. We wouldn't, and we all know it.

This whole system does nothing but reinforce the idea that digital books are nothing more than Word documents, typed any which way. I find it really vexing. I personally won't bother to fix any typo I find in a book I've purchased; why should/would I? I wouldn't take a John Sandford hardback down to a copy shop, whiteout a typo, type over it, copy the book and rebind it, would I? No, I'd infer what was intended and read on. Nor would I send the publisher a list of typos. I mean, when did this "send the publisher a list of typos" mindset even start?

I find this fix every typo in Calibre and Sigil thing kind of obsessive, to tell the truth, particularly for one's own library. I mean, how many times are you going to re-read something? Would 5 typos in 100K words really kill off the whole book?

If it bugs you (generally--I'm not addressing anyone individually or specifically) so much that you feel like you have to break the DRM, put it in Sigil/Calibre, fix it, well, great if that's what makes you happy, but what type of numbers are we talking about here? (I can see that the "Hid#233;" thing would, indeed, annoy me to the point of making Amazon or whomever take it back and tell them I wanted a fixed copy.) Do we mean 10 typos per book? 100? In how many words? What's really a valid number to complain to a publisher? And, bigger question: would you return the book if the same typos were in the print edition? Because that's MY standard. Just because MR'ers think it's easy for an author to fix a book doesn't mean that's so. Not everyone makes their own books.

I certainly found more than 20 typos in Annie Lamott's Bird By Bird, when it came out in MOBI. It neither scarred me for life nor impaired my ability to enjoy the book. I didn't complain to the publisher, nor post bad reviews about the formatting. There were patent formatting errata, as well; broken paragraphs, and the like. Somehow, I suffered through. ;-)

I don't know...again, if people see books that are rife with typos and formatting errors, they certainly should complain. But reporting 2 typos, (like the story I told about our superstar author's 350K-word novel), 1 of which wasn't even a typo, but a Brit spelling, and complaining about that to Amazon seems petty. And I don't believe that most of it is trying to "help" the author or the publisher. In that instance, certainly, it felt supercilious; a type of showing off. (n.b.: this type of supercilious showing off seems to have emerged as a consequence of both the advent of user reviews AND self-publishing. It seems that now that everyone is both a reviewer AND an author, they feel the need to indulge in some type of schadenfreude-based nitpicking of typos in other author's books. This is merely a theory of mine, obviously; worth what you paid for it, natch.)

And the "showing off" thing isn't intended to apply to anyone here on MR. Not the same crowd at all.

@Cyb: the font thing...sometimes you can talk them out of it, sometimes you can't. I have a book in right now with {sigh}, NINE fonts. NINE. Oish.

Hitch

[cybmole]

my theory - could be wrong:
in ye olden days of printed books, publishers paid humans to read them and point out errors BEFORE book went to final print.
so there was a trade called "Proofreader " & you could get paid - probably badly - for doing it.
That seems to have gone. I can be quite forgiving of new/self-published authors ( except for those who would fail a basic grammar exam- they poured over the text, looking for mistakes before uploading to there web sight ) but there's no excuse for it in high priced books by famous authors ( especially when other famous authors, with different publishers, achieve a far higher standard.

as an example ,I've read a lot of Frederick Forsyths e-books - I don't ever recall an annoying typo in those.

it not just the typos, its books with 57 flavours of indents/ margin settings each with its own CSS, because it's a sloppy scan, so a page or two of dialogue looks like it was set by a drunken typesetter.

So it we would be good to have a way to name & shame the worst offenders. & to list the funniest examples

I have on 2 occasions "returned" books to amazon because the layout was so bad, but I'm not aware that any new-improved versions have been produced since.

[Tex2002ans]

Originally Posted by Hitch

I posted here on MR recently that while I am certainly no fan of typos, I think the craze for fixing every little typo in a BOOK has done no one any favors, particularly the authors OR the readers. I said, and I stand by the idea, that this concept that books can be fixed instantly leads writers to think that it's okay to put up substandard work and "fix it later," or that a book isn't a fixed (as in, completed, not as in repaired) creation, but rather, a WIP posted on Amazon et al for a form of crowd-sourcing editing and proofing. This means that we, the readers, get stuck with crap that should never have been published, and it's considered acceptable.

Indeed indeed... this entire post reminded me of a paper/discussion in my software ethics class. And me, being very interested in economics, came to this conclusion via marginal/sunk costs.

In the case of software (digital):

Olden Times: Before the internet age, you would not get every minor revision, you would have had to wait for a major revision of your software (or not get an update at all). The "marginal cost" of getting a fix out there would not be trivial. You would have to print CDs/floppies and physically ship those to your customers.

Modern Times: Having computers connected to the internet lowers the "marginal cost" of fixing bugs to (less than pennies). This means that you can spend a hell of a lot less time bug checking your code... because it is trivial to get updates out to users (you can release v1.01 of your software and have it out to everyone in seconds).

This has a tendency to push towards faster iterations, and less money spent on initial bug testing/squashing, and not as strict standards. (If you DO make a mistake, it will be quick/cheap fix).

We also discussed software in vehicles, software in medical appliances, and a general recalling of physical products:

BECAUSE it costs the company a massive amount to actually recall/fix these products if something in the software goes wrong, manufacturers are willing to spend much more INITIALLY in development to squash as many problems as possible in the first place. Software in these tends to be run through much more rigorous product testing, more stringent standards, etc. etc.

Originally Posted by Hitch

I personally won't bother to fix any typo I find in a book I've purchased; why should/would I?

I see typos in a book just like I see bugs in a program. No matter how minor, they should be squashed/fixed.

For those who read public domain books, it can be released so those who come after won't have to suffer through the same buggy code typos in the book.

For those who read purchased titles that are in copyright.... well that is up to you. You may share the copy with a friend (they will not have to suffer through the typos), if you reread it at a future date (not a high chance, but you might!), or for those who are more gray in their alignment (and we cannot ignore this), those who wear pirate patches and want quality!!

Originally Posted by Hitch

Would 5 typos in 100K words really kill off the whole book?

Bugs Typos must be squashed... no matter how miner minor...

Originally Posted by Hitch

I didn't complain to the publisher, nor post bad reviews about the formatting. There were patent formatting errata, as well; broken paragraphs, and the like. Somehow, I suffered through. ;-)

Wow, how do you do that? Ever since I started making these ebooks.... my reading style has changed completely. Now I can't help but scan for problems that must be fixed (honing my skills for future books I guess so my ebooks get minimum errors! ).

I must admit though, it has turned my reading into a snail's pace...

Originally Posted by Hitch

But reporting 2 typos, (like the story I told about our superstar author's 350K-word novel), 1 of which wasn't even a typo, but a Brit spelling, and complaining about that to Amazon seems petty.

Indeed indeed... I wouldn't want anything taken down, just reporting it for informational purposes (which is why I wouldn't mind collecting them on a forum/website). I mean, B&N can continue selling that horrible Wild Cards #17 book I posted above.... but people should be aware of how crappy of an EPUB it is. :P

I see typo reporting as being especially helpful in the case of books that have yet to be digitized. I am just one set of eyes looking the book over while OCRing, it would be better to get two, three, four sets of eyes.... and what better way than having a bunch of eyes who actually READ the book (not just scan it quickly like me).

Also, reporting the typos can't hurt if they ever do decide to come out with a second edition of the book.

Originally Posted by Hitch

@Cyb: the font thing...sometimes you can talk them out of it, sometimes you can't. I have a book in right now with {sigh}, NINE fonts. NINE. Oish.

Wow... Nine fonts... nine different characters talking? All with their own fonts?

[exaltedwombat]

Wow... Nine fonts... nine different characters talking? All with their own fonts?

Was one of them Comic Sans? :-)

[DiapDealer]

It couldn't be easier to find an email address for a publisher and send off your comments about typos and/or formatting errors in a title they released. I've done it myself on occasion (only for egregious cases -- because like Hitch, I believe ebooks tend to be judged way more harshly than their print counterparts ever would have been). In each case, I sent off the email (CCing the author thinking they may know better who to direct the complaint to) and then promptly forgot about it. Because my part as the reader /consumer was done.

I think a big part of the problem with this sort of thing is that those readers "reporting" the typos/formatting don't seem to understand their role in this particular show. They seem to want some sort of feedback from someone--to know they made a difference. It's not enough to let the publisher know; they want everyone to know that they let the publisher know. You know?

I'm not suggesting cybmole suffers from that particular affliction or anything, just an observation.

The pat on the back isn't going to come. The online, crowd-sourced, proof-reading, instant-revision-resulting engine isn't going to happen. Not for already (traditionally) published, revenue-generating books, anyway.

So fix it for yourself, if you like, and jot an email to the publisher and/or author, if you feel so compelled, and move on. Whether it's effective or not isn't all that relevant, really.

[HarryT]

Some publishing imprints encourage readers to support errors. "SF Gateway", for example, a Hachette imprint, ask people to tell them about errors, and promptly fix them when they are reported.

[theducks]

9 Fonts (you are talking about 9 font families which include :Normal, Bold, Italic... ?)

When I took 'Print Shop' in High School, we were taught that 6 was the maximum for any single document.

Sorry, but releasing a book with ragged indents is just sloppy and a refund is due. (looking at the stylesheet will tell the tale)

Typos (spelling), Homonym errors spell check won't find these, bro ken wo rds

And my all time hate: Maintaining 'Hardback' layout for chapter heads.
margin-top: 12em; margin-bottom: 9em;
Is 'No thinking Allowed' the rule for the contractors used by BPH's?

[Hitch]

Alas, my best friends:

No, 'tis not one or two fonts with all their faces, 'tis 9 unique fonts, and all THEIR faces. I have tried, quite earnestly, to talk them out of it, using my last-resort tactic of pointing out what it will weigh in terms of book size, but....to no avail.

I am perfectly willing to embed chapter head/title page font. That doesn't faze me. Body font, though...I really try to wriggle out of that. Or using special fonts for text-messages, IM's, email, letters, mostly because of all the devices that won't support them. Of course, we create fallbacks, but people don't think about that, about what a fallback MIGHT look like on someone's old Sony, or what have you.

Newer readers are increasingly either overriding the font choices to begin with (yes, I'm talking to you, B&N!!!) or allowing the reader to do it, even with embedded fonts, so...it's hard to know how the Great Font Wars of 2013 will turn out, in the end. ;-)

@Exalted: no, t'was not Comic Sans, but, bygod, I was certainly expecting it by the time I got to the bottom of the fonts list in the PDF.

Hitch

[cybmole]

Originally Posted by theducks

Sorry, but releasing a book with ragged indents is just sloppy and a refund is due. (looking at the stylesheet will tell the tale)

for giggles here is just some of the 1360 lines of CSS in my worst ever retail example:

let's assume the publisher worked from a PDF or similar, I cannot figure where they found such a BAD conversion program. I think they have not quite but almost used very possible margin left value from 1px up to 99px, and a similar range of margin-right values

Spoiler:

}
p.P20 {
font-size:100%;
text-align:center;
margin-top:38px;
margin-bottom:0px;
}
.C892 {
font-size:85%;
text-align:center;
margin-top:60px;
margin-bottom:0px;
}
p.C908 {
font-size:105%;
margin-left:0px;
margin-top:14px;
margin-bottom:0px;
text-align:right;
}
.C908a {
font-size:105%;
margin-right:0px;
margin-top:14px;
margin-bottom:0px;
text-align:right;
}

p.C909 {
font-size:160%;
text-align:center;
margin-top:60px;
margin-bottom:0px;
}
p.P24 {
font-size:100%;
text-align:justify;
margin-top:38px;
margin-bottom:0px;
}
p.P25 {
font-size:100%;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P26 {
font-size:100%;
text-align:justify;
text-indent:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P27 {
font-size:100%;
text-align:justify;
margin-left:64px;
margin-top:0px;
margin-bottom:0px;
}
p.P28 {
font-size:100%;
margin-top:38px;
margin-bottom:0px;
}
p.P29 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:19px;
margin-top:0px;
margin-bottom:0px;
}
p.P31 {
font-size:100%;
text-align:justify;
text-indent:190px;
margin-top:0px;
margin-bottom:0px;
}
p.P32 {
font-size:100%;
margin-left:16px;
margin-top:12px;
margin-bottom:0px;
}
p.P34 {
font-size:100%;
text-align:justify;
text-indent:16px;
margin-top:12px;
margin-bottom:0px;
}
.C911 {
font-size: 160%;
text-align:center;
margin-top:60px;
margin-bottom:0px;
}
.P35 {
font-size:100%;
text-align:center;
margin-left:67px;
margin-right:67px;
margin-top:38px;
margin-bottom:0px;
}
.P35a {
font-size:100%;
text-align:justify;
margin-left:67px;
margin-right:67px;
margin-top:38px;
margin-bottom:0px;
}

p.C912 {
font-size:100%;
margin-left:0px;
margin-top:12px;
margin-bottom:0px;
text-align:right;
}
p.C912a {
font-size:100%;
margin-right:80px;
margin-top:12px;
margin-bottom:0px;
text-align:right;
}

p.C914 {
font-size:130%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.C915 {
font-size:160%;
text-align:center;
margin-top:9px;
margin-bottom:0px;
}
p.P39 {
font-size:100%;
margin-top:0px;
margin-bottom:0px;
}
p.P40 {
font-size:100%;
margin-left:16px;
margin-top:14px;
margin-bottom:0px;
}
p.P41 {
font-size:100%;
text-align:justify;
text-indent:61px;
margin-top:0px;
margin-bottom:0px;
}
p.P42 {
font-size:100%;
text-align:justify;
margin-top:12px;
margin-bottom:0px;
}
p.P43 {
font-size:100%;
text-align:right;
margin-top:0px;
margin-bottom:0px;
}
p.P44 {
font-size:100%;
text-align:justify;
margin-top:0px;
margin-bottom:0px;
}
p.P37 {
font-size:110%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
.P37a {
font-size:100%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}

p.P48 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:34px;
margin-top:0px;
margin-bottom:0px;
}
p.P49 {
font-size:100%;
text-align:justify;
margin-right:19px;
margin-top:0px;
margin-bottom:0px;
}
p.P225 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:8px;
margin-top:0px;
margin-bottom:0px;
}
p.P51 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P231 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:5px;
margin-top:0px;
margin-bottom:0px;
}
p.P52 {
font-size:100%;
margin-top:14px;
margin-bottom:0px;
}
p.P53 {
font-size:100%;
text-align:justify;
text-indent:50px;
margin-top:0px;
margin-bottom:0px;
}
p.C923 {
font-size:150%;
text-align:center;
margin-left:0px;
margin-right:0px;
margin-top:9px;
margin-bottom:0px;
}
p.P924 {
font-size:100%;
text-align:justify;
text-indent:49px;
margin-top:0px;
margin-bottom:0px;
}
p.P86 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:17px;
margin-top:0px;
margin-bottom:0px;
}
p.P55 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:24px;
margin-top:0px;
margin-bottom:0px;
}
p.P56 {
font-size:100%;
text-align:justify;
margin-right:6px;
margin-top:12px;
margin-bottom:0px;
}
p.P236 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:15px;
margin-top:0px;
margin-bottom:0px;
}
p.P238 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:14px;
margin-top:0px;
margin-bottom:0px;
}
.P14 {
font-size:100%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.P61 {
font-size:100%;
text-align:justify;
text-indent:91px;
margin-top:0px;
margin-bottom:0px;
}
p.P249 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:7px;
margin-top:0px;
margin-bottom:0px;
}
p.P62 {
font-size:100%;
margin-left:63px;
margin-top:0px;
margin-bottom:0px;
}
p.P63 {
font-size:100%;
text-align:justify;
text-indent:36px;
margin-top:0px;
margin-bottom:0px;
}
p.P259 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:10px;
margin-top:0px;
margin-bottom:0px;
}
p.C951 {
font-size:140%;
text-align:center;
margin-top:60px;
margin-bottom:0px;
}
p.C952 {
font-size:100%;
text-align:justify;
margin-left:56px;
margin-right:55px;
margin-top:38px;
margin-bottom:0px;
}
p.P68 {
font-size:100%;
text-align:right;
margin-top:14px;
margin-bottom:0px;
}
p.P69 {
font-size:100%;
text-align:justify;
margin-right:27px;
margin-top:0px;
margin-bottom:0px;
}
p.P70 {
font-size:100%;
text-align:justify;
text-indent:41px;
margin-top:0px;
margin-bottom:0px;
}
p.C964 {
font-size:100%;
text-align:center;
margin-left:162px;
margin-right:162px;
margin-top:12px;
margin-bottom:0px;
}
p.P72 {
font-size:90%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.P281 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:4px;
margin-top:0px;
margin-bottom:0px;
}
p.P73 {
font-size:100%;
text-align:justify;
margin-right:5px;
margin-top:0px;
margin-bottom:0px;
}
p.C970 {
font-size:110%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.P38 {
font-size:150%;
text-align:center;
margin-top:9px;
margin-bottom:0px;
}
p.P74 {
font-size:100%;
margin-left:42px;
margin-top:0px;
margin-bottom:0px;
}
p.P148 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:12px;
margin-top:0px;
margin-bottom:0px;
}
p.P75 {
font-size:100%;
text-align:justify;
text-indent:184px;
margin-top:0px;
margin-bottom:0px;
}
p.P76 {
font-size:100%;
text-align:right;
margin-right:5px;
margin-top:0px;
margin-bottom:0px;
}
p.P296 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P298 {
font-size:100%;
text-align:justify;
margin-left:19px;
margin-right:7px;
margin-top:0px;
margin-bottom:0px;
}
p.P77 {
font-size:90%;
margin-top:38px;
margin-bottom:0px;
}
p.P78 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:30px;
margin-top:0px;
margin-bottom:0px;
}
.P23 {
font-size:150%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.P79 {
font-size:100%;
text-align:justify;
margin-left:76px;
margin-right:74px;
margin-top:38px;
margin-bottom:0px;
}
p.P80 {
font-size:100%;
margin-left:103px;
margin-top:12px;
margin-bottom:0px;
}
p.P81 {
font-size:90%;
margin-left:180px;
margin-top:0px;
margin-bottom:0px;
}
p.C976 {
font-size:110%;
margin-left:0px;
margin-top:0px;
margin-bottom:0px;
text-align:center;
}
p.P83 {
font-size:100%;
text-align:justify;
text-indent:26px;
margin-top:0px;
margin-bottom:0px;
}
p.P84 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:25px;
margin-top:0px;
margin-bottom:0px;
}
p.P85 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:16px;
margin-top:12px;
margin-bottom:0px;
}
p.P339 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:33px;
margin-top:0px;
margin-bottom:0px;
}
p.P131 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:9px;
margin-top:0px;
margin-bottom:0px;
}
p.P623 {
font-size:100%;
margin-left:66px;
margin-top:0px;
margin-bottom:0px;
}
p.P87 {
font-size:100%;
text-align:right;
margin-top:38px;
margin-bottom:0px;
}
p.P88 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:24px;
margin-top:12px;
margin-bottom:0px;
}
p.P90 {
font-size:100%;
text-align:justify;
margin-top:19px;
margin-bottom:0px;
}
p.P336 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:13px;
margin-top:0px;
margin-bottom:0px;
}
p.P91 {
font-size:100%;
text-align:justify;
margin-left:49px;
margin-top:0px;
margin-bottom:0px;
}
p.P93 {
font-size:100%;
margin-left:35%;
margin-top:38px;
margin-bottom:0px;
text-align: left;
}
p.P94 {
font-size:100%;
margin-left:35%;
margin-top:0px;
margin-bottom:0px;
text-align: left;
}
p.P95 {
font-size:100%;
margin-left:115px;
margin-top:12px;
margin-bottom:0px;
}
p.P96 {
font-size:90%;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P97 {
font-size:100%;
text-align:justify;
text-indent:10px;
margin-top:0px;
margin-bottom:0px;
}
p.P98 {
font-size:100%;
margin-left:36px;
margin-top:0px;
margin-bottom:0px;
}
p.P99 {
font-size:100%;
text-align:justify;
text-indent:66px;
margin-top:0px;
margin-bottom:0px;
}
p.P101 {
font-size:100%;
text-align:justify;
margin-right:13px;
margin-top:0px;
margin-bottom:0px;
}
p.P102 {
font-size:100%;
margin-left:50px;
margin-top:0px;
margin-bottom:0px;
}
p.P103 {
font-size:100%;
text-align:justify;
margin-right:29px;
margin-top:12px;
margin-bottom:0px;
}
p.P105 {
font-size:100%;
margin-left:69px;
margin-top:0px;
margin-bottom:0px;
}
p.P106 {
font-size:100%;
text-align:justify;
margin-right:27px;
margin-top:38px;
margin-bottom:0px;
}
p.P678 {
font-size:100%;
margin-left:35px;
margin-top:0px;
margin-bottom:0px;
}
p.P107 {
font-size:100%;
text-align:justify;
text-indent:20px;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P108 {
font-size:90%;
margin-left:16px;
margin-top:38px;
margin-bottom:0px;
}
p.P109 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:34px;
margin-top:12px;
margin-bottom:0px;
}
p.P110 {
font-size:100%;
text-align:justify;
text-indent:15px;
margin-left:16px;
margin-right:17px;
margin-top:0px;
margin-bottom:0px;
}
p.P111 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:28px;
margin-top:12px;
margin-bottom:0px;
}
p.P112 {
font-size:100%;
text-align:justify;
text-indent:15px;
margin-left:16px;
margin-right:23px;
margin-top:0px;
margin-bottom:0px;
}
p.P691 {
font-size:100%;
margin-left:19px;
margin-top:0px;
margin-bottom:0px;
}
p.P113 {
font-size:100%;
text-align:justify;
margin-left:20px;
margin-right:19px;
margin-top:38px;
margin-bottom:0px;
}
p.P114 {
font-size:100%;
text-align:justify;
margin-left:280px;
margin-right:20px;
margin-top:12px;
margin-bottom:0px;
}
p.P115 {
font-size:90%;
text-align:justify;
margin-left:58px;
margin-right:20px;
margin-top:0px;
margin-bottom:0px;
}
p.P116 {
font-size:90%;
text-align:justify;
margin-left:206px;
margin-right:20px;
margin-top:0px;
margin-bottom:0px;
}
p.P694 {
font-size:100%;
text-align:justify;
margin-left:287px;
margin-right:19px;
margin-top:12px;
margin-bottom:0px;
}
p.P118 {
font-size:100%;
text-align:justify;
margin-left:179px;
margin-right:20px;
margin-top:12px;
margin-bottom:0px;
}
p.P696 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:20px;
margin-top:0px;
margin-bottom:0px;
}
p.P120 {
font-size:100%;
margin-left:24px;
margin-top:0px;
margin-bottom:0px;
}
p.P121 {
font-size:100%;
text-indent:16px;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P122 {
font-size:100%;
text-align:justify;
text-indent:16px;
margin-left:16px;
margin-right:33px;
margin-top:0px;
margin-bottom:0px;
}
p.P123 {
font-size:100%;
margin-left:58px;
margin-top:0px;
margin-bottom:0px;
}
p.P124 {
font-size:100%;
text-align:justify;
margin-right:33px;
margin-top:0px;
margin-bottom:0px;
}
p.P125 {
font-size:100%;
margin-left:16px;
margin-top:4px;
margin-bottom:0px;
}
p.P126 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:31px;
margin-top:4px;
margin-bottom:0px;
}
p.P127 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:30px;
margin-top:12px;
margin-bottom:0px;
}
p.P128 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:19px;
margin-top:4px;
margin-bottom:0px;
}
p.P129 {
font-size:100%;
text-align:justify;
text-indent:27px;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P453 {
font-size:100%;
text-align:justify;
margin-left:19px;
margin-right:13px;
margin-top:0px;
margin-bottom:0px;
}
p.P132 {
font-size:100%;
text-align:justify;
text-indent:21px;
margin-top:0px;
margin-bottom:0px;
}
p.P133 {
font-size:100%;
margin-left:28px;
margin-top:0px;
margin-bottom:0px;
}
p.P473 {
font-size:100%;
text-align:justify;
margin-left:19px;
margin-right:15px;
margin-top:0px;
margin-bottom:0px;
}
p.P134 {
font-size:100%;
text-align:justify;
text-indent:76px;
margin-top:0px;
margin-bottom:0px;
}
p.P135 {
font-size:100%;
text-align:justify;
margin-right:22px;
margin-top:0px;
margin-bottom:0px;
}
p.P784 {
font-size:100%;
margin-left:243px;
margin-top:12px;
margin-bottom:0px;
}
p.P137 {
font-size:100%;
text-align:justify;
margin-left:60px;
margin-right:59px;
margin-top:26px;
margin-bottom:0px;
}
p.P786 {
font-size:100%;
margin-left:235px;
margin-top:12px;
margin-bottom:0px;
}
p.P139 {
font-size:100%;
text-align:center;
margin-top:12px;
margin-bottom:0px;
}
p.P141 {
font-size:100%;
text-align:justify;
text-indent:111px;
margin-top:0px;
margin-bottom:0px;
}
p.P142 {
font-size:100%;
text-align:justify;
margin-left:31px;
margin-top:0px;
margin-bottom:0px;
}
p.P805 {
font-size:100%;
margin-left:33px;
margin-top:0px;
margin-bottom:0px;
}
p.P144 {
font-size:100%;
text-align:justify;
text-indent:184px;
margin-top:38px;
margin-bottom:0px;
}
p.P524 {
font-size:100%;
text-align:justify;
margin-left:19px;
margin-top:0px;
margin-bottom:0px;
}
p.P145 {
font-size:100%;
margin-left:16px;
margin-top:38px;
margin-bottom:0px;
}
p.P860 {
font-size:100%;
text-align:justify;
margin-right:24px;
margin-top:0px;
margin-bottom:0px;
}
p.C866 {
font-size:100%;
text-align:justify;
margin-left:0px;
margin-top:0px;
margin-bottom:0px;
text-indent:15px;
}
p.P19 {
font-size:370%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
p.P152 {
font-size:100%;
margin-top:24px;
margin-bottom:0px;
}
p.P153 {
font-size:100%;
text-align:right;
margin-right:93px;
margin-top:0px;
margin-bottom:0px;
}
p.P154 {
font-size:100%;
margin-left:92px;
margin-top:0px;
margin-bottom:0px;
}
p.P155 {
font-size:150%;
text-align:center;
margin-top:14px;
margin-bottom:0px;
}
p.P156 {
font-size:100%;
text-align:right;
margin-right:132px;
margin-top:16px;
margin-bottom:0px;
}
p.P157 {
font-size:70%;
margin-left:134px;
margin-top:0px;
margin-bottom:0px;
}
p.P158 {
font-size:120%;
margin-left:146px;
margin-top:0px;
margin-bottom:0px;
}
p.P159 {
font-size:80%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
.C889 {
font-size:100%;
text-align:center;
margin-top:120px;
margin-bottom:0px;
}
.C891 {
font-size:85%;
text-align:center;
margin-top:14px;
margin-bottom:0px;
}
.C893 {
font-size:85%;
text-align:center;
margin-top:0px;
margin-bottom:0px;
}
.C894 {
font-size:85%;
text-align:center;
margin-top:12px;
margin-bottom:0px;
}
p.C900 {
font-size:85%;
text-align:justify;
margin-left:9px;
margin-right:8px;
margin-top:12px;
margin-bottom:0px;
}
p.P559 {
font-size:60%;
margin-left:87px;
margin-top:0px;
margin-bottom:0px;
}
p.C906 {
font-size:100%;
text-align:justify;
margin-left:87px;
margin-right:76px;
margin-top:0px;
margin-bottom:0px;
}
.C906a {
font-size:100%;
text-align:center;
margin-left:0px;
margin-right:0px;
margin-top:0px;
margin-bottom:0px;
}

p.P603 {
font-size:110%;
text-align:center;
margin-top:38px;
margin-bottom:0px;
}
p.P607 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:27px;
margin-top:0px;
margin-bottom:0px;
}
p.P609 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:26px;
margin-top:0px;
margin-bottom:0px;
}
p.P625 {
font-size:100%;
text-indent:174px;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P681 {
font-size:110%;
margin-top:0px;
margin-bottom:0px;
}
p.P695 {
font-size:90%;
text-align:justify;
margin-left:230px;
margin-right:20px;
margin-top:0px;
margin-bottom:0px;
}
p.P697 {
font-size:100%;
text-align:justify;
text-indent:13px;
margin-left:16px;
margin-right:19px;
margin-top:0px;
margin-bottom:0px;
}
p.P714 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:17px;
margin-top:4px;
margin-bottom:0px;
}
p.P726 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:22px;
margin-top:4px;
margin-bottom:0px;
}
p.P730 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:23px;
margin-top:4px;
margin-bottom:0px;
}
p.P744 {
font-size:110%;
margin-left:16px;
margin-top:0px;
margin-bottom:0px;
}
p.P785 {
font-size:90%;
margin-left:189px;
margin-top:0px;
margin-bottom:0px;
}
p.P787 {
font-size:100%;
margin-left:106px;
margin-top:0px;
margin-bottom:0px;
}
.right {
font-size:100%;
margin-right:0px;
margin-top:1em;
margin-bottom:0px;
text-align: right;
}

p.P789 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:28px;
margin-top:0px;
margin-bottom:0px;
}
p.P800 {
font-size:100%;
text-align:justify;
margin-left:16px;
margin-right:210px;
margin-top:12px;
margin-bottom:0px;
}
p.C859 {
}
p.C986 {
text-align:justify;
text-indent:15px;
margin-bottom:0px;
margin-top:0px;
}