Expert. NET 2.0 il explorer · one school diary

11.18
The summary after each chapter is translated as a summary.
In addition, summary is generally translated as a summary in other places.
V-table is uniformly translated into V table.

Stub translation as a stub
Sections are translated as sections, and segment is translated as segments.

Token translation as an identifier
Label translation is a label, which must be changed in many places (originally translated as a label)

Convention translation as conventions
Local variable is translated as a local variable. It seems that the translation is wrong in many places.
Specification is translated as a description
Constructor is translated as a constructor instead of a constructor.

Explicit it layout display Layout
Union layout joint Layout

Nested embedded

The index is not required this time. It should be replaced by a Chinese-English comparison table.
Verbal description translation?

The directory has been proofread.

Title in bold
Chapter 2
1.1 3
1.1.1 4

Notes, caution entity, double slash

1.5 times the row spacing,
Text font no. 10
An empty line is added between the image, code, and body, and title.

11.18
Chapter 2:

 

This module includes the Assembly identification information in its metadata. Identity translation as an identifier

Notes are translated as instructions (within the dual horizontal line)
Listing1.1 translated as Example 1-1

You only need to leave the assemblyref range empty. -- Scope translation is a range

Not but translation error, should it be......

Will decide to support "instantiation" and completely ignore the field ing-this sentence has a problem.

 

11.19
Change the image to Chinese
All codes are marked as code.

After being sent to the press, correct some "ranges" to "Scopes"

Start Chapter 1 proofreaders end at pm
Chapter 1 should be completed at the next day for your reference, especially in the last section.

I started to proofread Chapter 1 typographical work. How should I deal with the table? Sleep

11.21
Chapter 4 re-process the image-a little smaller
The end of the "Description" unit in the table does not end with a full stop.

11.22
Start-up translation start
CLR-aware OS translation supports CLR OS
Versioning translation version control

Fixup translation? Location? Or fixed? Liu said that the positioning is good and he has adopted it for the time being.

Emit translation for sending

11.23
The original Article is throughout the history of humanity, deviations from orthodoxy, however tempting, have always brought some unpleasant complications, it is inevitable to abide by unpleasant and cumbersome systems.

 

This array ends with null, so this field is not null. This sentence is not fluent.
The offsettodata and size fields describe the corresponding chunk features of resource data. These chunks constitute an independent resource. Corrected

Before the data description is reached, its type, name, and language can all be obtained from the path, which is traversed by the search algorithm to reach the location of the data description. The search algorithm uses its type, name, and language to find the appropriate path to reach the data description.
Corrected

Unmanaged resources are indexed by type, name, and language, and sorted in binary order by type, name, and language. This sentence is not fluent
Changes to unmanaged resources are indexed by type, name, and language, and sorted in binary order based on these three features.

These strings are arranged in 2 bytes. Changed to 2-byte alignment, corrected

The set composed of records whose directory entries are addressable is changed to a group of records whose directory entries are addressing.

During execution, it is not fluent to replace the method with its own address or the address of the mail replacement program that provides an unmanaged item for the method.
Each slot modified to v-table contains metadata tokens of each method. These metadata tokens are replaced with the method's own address during running, or a sending stub, the unmanaged entry used to provide the method, corrected

11.24
Several things to do today

1) Chapter 1-4 + preface OK
Il Compiler Errors translated into ilasm should be changed back
The IL anti-compiler translation for ildasm should be changed back.

2) Chapter 1 reprocessing the image OK
3) Chapter 1 several Sentence Translation questions: Head and Anders
4) Chapter 1-4 entry Translation
5) Chapter 1-4 integration of emit Translation Problems
6) Chapter 1-4 page numbers are not required for future translation index preparation

7) aligned terms need to be changed many places

The author does not pay attention to the difference between ilasm and IL explorer.

11.25
Start proofreading Chapter 2

Unified in this case.
Blob is not translated.

Confused sentence :.

Constraints descriptor, specifying type parameters for generic classes and generic methods

 

Validation and Verification need to be changed in many places with unified terminology
Validity

The figure in Chapter 1 has not been processed yet.

11.27
Emit outbound Chapter 1-6 completed verification
Chapter 1 Completed

 

 

Entry TRANSLATION 1: entry point (Entry Point), entry ...... To enter ......
Translation 2 is generally translated as an item, that is, an element in the set.
If you can elaborate on what this "item is, such as: an entry of the Data Directory table, it will be translated into a table. Sometimes it is converted into a tag, a field, and so on according to the context.
3. Flags entry of the CLR header is translated as a field and usually appears in the table (at the same time, there is always a struct code on the table)
From Chapter 1 to Chapter 2

 

I found that there was a paragraph without translation. It seems that I had to check it again in the second school.

 

The difference between compiler and compiler is that you must correct Chapter 1-5 OK.
1. Modify il/ilasm compiler to Il/ilasm assembler. The author's error should be explained in the preface.
2. Search for compiler in the original book and correct it as the author's error according to the context.
3. Find the compiler in the translation and correct the IL or ilasm to the assembler my error.

Verification Chapter 1-5

11.28

Start proofreading Chapter 2
Carry translation must be carried in a unified manner
Employ in Chapter 6th translation for deployment for the Assembly

Additional unified translation for additional, rather than additional to unified

The translation of strong name and strong name signature must be changed many places.
Strong strong name is a technology.
Strong named is a verb with a strong name. The corresponding strong-named is an adjective.
Strong name Signature: a strong name signature, which is a hash value.

There is no official definition of strong signature. However, strong names, strong names, and strong name signatures are all called strong signatures.

Consumer users should be unified

Flag Flag changed to flag
Change token to mark
Mark

Hardware ring Conversion
Hardware force

Majorversion main version
Minor version
Buildnumber internal version number
Buildnumber revision version number

Tracking

Where and in the code

Offset translation as offset

Instruction and Directive should be differentiated

11.29
The scope code is translated as the scope, and other places are translated as the scope

Unified: publisher and Publisher

Translate hash into Hash
Translate hashed into Hash

11.30
Whether blob translation should be unified
Locale region settings
Localization
Location
Region region

Offset offset changed to offset

Segment segment

The teminator must be the Terminator.

12.2
Chapter 2
Examine translation for analysis should be unified
Full name translation should be unified, and full class name should also be unified.
Nested translation should be unified
Power or translate to multiplication party
Check the binary mask.

Full picture Panorama