(0.7.1) Grammar/typo errors in Ch 2 and Part I intro
Looks like Chapter 2 onward has much fewer grammar problems and typos than the earlier sections. This is probably because most people skip over the Preface and Chapter 1 and they get less scrutiny.
ATTENTION! While creating this list, I noticed that your font-transformers are buggy for both HTML and PDF.
In the PDF, a lot of stuff is not getting properly italicized, where in the HTML the italics are working. (The other font decorations appear to be working correctly in PDF.)
In the HTML, see Preface: 3, and you'll notice that all of the constant width font examples erroneously look exactly the same (fixed-width/bold/italic). (Observed in both Opera and Firefox.)
You should probably double-check your print edition font-transformers while investigating the PDF and HTML issues.
And on to the errors:
-----
Chapter 2
2.5.2 First sentence
The period after "Installing Maven on Linux" should be a comma; second sentence should be second clause of this one.
2.5.3
Second sentence: Should "expose" be "export"?
Third sentence: Should you italicize or underline book titles? In the PDF, it is normal undecorated text. In the HTML, it is hyperlinked (and as such, underlined).
2.9
I humbly suggest putting a colon after "here" when presenting a URL, unless you've specifically chosen not to.
e.g. "the license available here: http://..."
(2 instances in this section)
Also in 2.9, notice that "[This license] allows you to:" is italic in the HTML, but non-italic in the PDF, in accordance with the font-transformation issue I described earlier.
Part I (intro)
(General) In the PDF, "Maven: A Developer's Notebook" is normal undecorated text. In the HTML, it's italicized. (Probably the font issue I described earlier.)
Third paragraph, last phrase:
"... Part II is motivated by real examples." -- Should be Part I.
ATTENTION! While creating this list, I noticed that your font-transformers are buggy for both HTML and PDF.
In the PDF, a lot of stuff is not getting properly italicized, where in the HTML the italics are working. (The other font decorations appear to be working correctly in PDF.)
In the HTML, see Preface: 3, and you'll notice that all of the constant width font examples erroneously look exactly the same (fixed-width/bold/italic). (Observed in both Opera and Firefox.)
You should probably double-check your print edition font-transformers while investigating the PDF and HTML issues.
And on to the errors:
-----
Chapter 2
2.5.2 First sentence
The period after "Installing Maven on Linux" should be a comma; second sentence should be second clause of this one.
2.5.3
Second sentence: Should "expose" be "export"?
Third sentence: Should you italicize or underline book titles? In the PDF, it is normal undecorated text. In the HTML, it is hyperlinked (and as such, underlined).
2.9
I humbly suggest putting a colon after "here" when presenting a URL, unless you've specifically chosen not to.
e.g. "the license available here: http://..."
(2 instances in this section)
Also in 2.9, notice that "[This license] allows you to:" is italic in the HTML, but non-italic in the PDF, in accordance with the font-transformation issue I described earlier.
Part I (intro)
(General) In the PDF, "Maven: A Developer's Notebook" is normal undecorated text. In the HTML, it's italicized. (Probably the font issue I described earlier.)
Third paragraph, last phrase:
"... Part II is motivated by real examples." -- Should be Part I.
1
person has this problem
I have this problem, too!
Tell me when someone solves it.
The more people who report this problem, the more it gets noticed.
The more people who report this problem, the more it gets noticed.
The company marked this problem solved.
-
Inappropriate?Alright, awesome, thanks for taking the time to do this. I've captured a tracking task for this in JIRA:
https://issues.sonatype.org/browse/MV... -
Inappropriate?I just published Edition 0.7.2 and I incorporated all of this feedback.
Here is the announcement: http://www.sonatype.com/people/2009/0...
Thanks again Grant.
I’m thankful
The company and 1 other person say
this solves the problem
Loading Profile...


EMPLOYEE