Update (11/05/2020): Read The 1Z0-819 Exam page to learn how you can easily our Java 11 Study Guides to prepare for Oracle’s 1Z0-819 Exam, as well as the 1Z0-817 Upgrade Exam.
Our OCP 11 (IZ0-815) book is at the printer. It comes out this month! In fact we are doing a CodeRanch promo for it next week. The book comes with an online test bank. The online bank includes two full length mock exams and every question in the book.
While uploading our questions to the test bank software, one of the test bank staff noticed an error. Two of our answer choices were the same. Luckily this wasn’t the correct answer, so a pretty minor errata. But it is our first errata so time to start the errata list.
For our Java 8 books, we used an HTML table for the errata list because our WordPress instance didn’t have table support. Editing the HTML was a pain so I was happy to see that now there are native WordPress tables. So I tried it out. Easy to enter data, add/remove rows/columns. Excellent. It’s all you could want in a table editor. Well. Almost.
Attempt #1
I chose the striped option. And this is what I got my default. I agree that the error column is the most important. And it’s nice that it is wide. But the other columns are so narrow to be unreadable.
Attempt #2
I looked at what my options were on the table. There was only one option that looked relevant. So I clicked it
Yuck; that’s even worse. The error column is the most important and it is so narrow it is hard to read. And there is lots of wasted whitespace.
Attempt #3
I got rid of the Type column to get a bit more real estate. Then I discovered there was a CSS option. I made up a unique CSS class name. Given that 815 is in the exam name, that sounds unique on our site.
I also went to the Additional CSS screen:
Settings
Appearance
Customize
Additional CSS
I added this CSS:
/* By default, wordpress only allows default or equals column size. Both look bad on the errata table so using CSS to customize */
/* page # */
.ocp-815-errata-table td:nth-child(1) {
width: 10%;
}
/* chapter #*/
.ocp-815-errata-table td:nth-child(2) {
width: 10%;
}
/* actual errata */
.ocp-815-errata-table td:nth-child(3) {
width: 50%;
}
/* reporter */
.ocp-815-errata-table td:nth-child(4) {
width: 15%;
}
/* confirmed */
.ocp-815-errata-table td:nth-child(5) {
width: 15%;
}
As Scott and are finishing up on Z0-815 book, I want to share an example of an error’s progress through the editing process.
We have a method. Pay careful attention to the name of the method:
public void requiresAssistance() { }
Then we reference the method: new MoreHelp().requireAssistance();.It’s an error. Let’s see what happens to it as the editing process proceeds:
Scott and I read each other’s chapter.
Our Tech Editor reads the Word document and runs all the examples. In theory it should get caught here. And most things do. But I’ve tech edited. There’s a lot to see and a ton of detail.
We reply to our tech editors comments.
The book gets turned into a PDF.
Our Tech Proofer reads the PDF. Excellent it got caught at this phase.
We submitted the request to change “requireAssistance” to “requiresAssistance”. Scott and I proofread each other’s change requests to ensure we don’t introduce more errors.
We got the final PDF back for review. (I’m not sure if this is part of the process, but we ask for them anyway). It says “requiresAssistence”.
We submitted a request to get this fixed before the book prints. But this shows how hard it is to get all the errors out of book. “Assistance” was spelled correclty in every draft and revision except the final one.
If you followed that process closely, the Tech Editor and Tech Proofer didn’t even have the opportunity to catch this. And it wasn’t created by the authors.
