Error description in part of refactoring to patterns translation reconstruction and pattern (revision)

Error description in part of refactoring to patterns translation reconstruction and Pattern

People's post and telecommunications press, reconstruction and model (revised version), January 2013, 1st, January 2013 printing in Beijing in 1st.

Section 13th under "2.8 evolving new architecture", "public code should be obtained from the new framework layer ,..."
Common Code wocould be accessible from a new framework layer.
The error message "be accessible from" is better than "get from ".

"Public code can be accessed through the new framework layer ."

Page 30th, section 4.1, sentence 2nd under "2nd repeated code", "If methods in different subclasses do not have enough to create objects ..."

If a method in the subclasses is implemented Similarly, doesn t for an object creation step, applying introduce polymorphic Creation
With factory method will pave the way for removing more duplication by means of a template method.

Error Description: it should be translated as "different outside...", rather than "Beyond ..."

"If the methods in different subclass are different except object creation ..."

On the seventh page, under Section 32nd under "4.4 basic type paranoia", there are 1st sentences. "However, classes may need to be very specific because they are often created for specific purposes ."

Original ENGLISH: classes, on the other
Hand, may be as specific as you need them to be because you create them for specific purposes.

Incorrect description: the translation is not easy to understand.

On the other hand, classes may be as special as possible based on your needs, because you create classes for special purposes. "

Page 33rd, "4.6 solution spread" under the 1st sentence, "If many classes are useful to complete code and/or data for certain responsibilities,..."

When code and/or data used to perform a responsibility becomes sprawled into SS numerous classes, solution sprawl is in
Air.

Incorrect description: it should be translated into "A", rather than "some".

"If many classes are used to complete code and/or data for a specific role,..."

Page 35th, paragraph 2nd, sentence 1st, "... there is a preferred way to communicate with a group of classes,..."

The oddball solution smell is usually present when you have a preferred way to communicate with a set of classes, yet differences
In the interfaces of the classes prevent you from communicating with them in a consistent way.

Incorrect description: "Priority" is not natural.

When you have a preferred way to communicate with a group of classes,

Page 46th, the last 4th, "(2) applications using loan instances need to be converted between different types of loans. "

Original English:
Application that usedLoanInstances needed to transform
Loans from one kind of loan to another.

Incorrect description: I feel that the translation is not very accurate.

(2) applications that use loan instances need to convert one loan type to another. "

Page 47th, section 3rd, "... the following is a test example of..."

Here is one such caller that resides in a test case:

Error Description: test case should be translated as test case.

"... Below is a test case that appears..."