Translation errors in Windows Programming-learning notes

1. (23 pages, 13th rows): "Unicode is not required for wide characters. Unicode is a possible wide character encoding ." What does this mean? Check the original article. It turns out to be: wide characters aren't necessarrily Unicode. Unicode is one possible wide-character encoding. It means: "The width character is not equivalent to Unicode. Unicode is only a feasible wide character encoding (solution )."

2. (35 pages, 13th rows): "You must separate them with sizeof (tchar ." In fact, when reading a book, you should know that it should not be "separated". Instead, you should look up the original text by "division". The result is: you must divide it by sizeof (tchar ). has the translator been ignorant of the meaning of "separation" that only knows the word divide?

3. (7th rows on page 65): "…… It must be regarded as a specific size, or the size remains unchanged when the program is running ." This seems to be against common sense. Compare the original text (the section in the brackets is the previous sentence) :( you can do almost anything you want with your program's client area)-anything, that is, when T assume that it will be a particle size or that the size will remain constant while your program is running. while your program is running. obviously, the part starting with the word anything should be translated as: "It cannot be determined that its size is a specific size or remains unchanged during program operation." The opposite is true.

4. (lines 4th on page 76): "It is the size of Space recommended by the font designer to add between horizontal characters ." This is a bit incorrect. tmexternalleading is clearly a vertical length. How can we say "between horizontal characters "? See the original article: This is an amount of space that the designer of the font suggests be added between successive rows of displayed text. now you know: it's ridiculous that the translated book translated successive rows (meaning "adjacent lines") into "Horizontal characters ".

5. (row 100 on page 1): "When the sif_range flag is used by the getscrollinfo function, the Nmin and Nmax fields should be set to the current range returned by the function ." This is obviously incorrect. The original Article is: when you use the sif_range flag with the getscrollinfo function, the Nmin and Nmax fields will be set to the current range on return from the function. translation: "If the sif_range flag is specified when the getscrollinfo function is called, The Nmin and Nmax fields are set to the current range value when the function returns."

6. (row 100 on page 1): "Only the sif_disablenoscroll flag is used in the setscrollinfo function. If this flag is specified and the new scroll bar parameter makes the scroll bar invisible, the scroll bar is disabled ." This section is a bit confusing. See the original article: you use the sif_disablenoscroll flag only with the setscrollinfo function. if this flag is specified and the new scroll bar arguments wocould normally render the scroll bar invisible, this scroll renders the scroll bar disabled instead. (I'll explain this more shortly .) the sif_disablenoscroll flag is used only with the setscrollinfo function. (When calling this function) if a new parameter of the scroll bar is provided, which usually causes the scroll bar to be invisible, and this flag is specified, in this case, the scroll bar is only disabled rather than hidden." (The translation of this sentence is a little difficult. For the sake of smoothness, I have made some adjustments to the order of the translation)

7. (the last 100 rows on the 2nd page): "A good function of the new scroll bar function is to use a page with the same size as the scroll bar ,......" What is "Use a page with the same size as the scroll bar "? Look at the original article: one nice feature of the new scroll bar functions is that when you use a scroll bar page size. Use a scroll bar page size should be translated into "use scroll bar page size" instead of "Use a page with the same size as the scroll bar range ".

8. (The last 107 rows on the 5th page): "on a slow machine, you can consider using the sb_slowmachine parameter for getsystemmetrics as a replacement process ." I found myself not familiar with Chinese. :-) Read the original article: But try your code out on a slow machine, and perhaps think about using the sb_slowmachine argument to getsystemmetrics for alternative processing for slow machines. "However, you should test your code on a slow machine. In addition, you can also use the sb_slowmachine parameter to call the tsystemmetrics function, in order to provide different processing processes for slow machines."

9. (the last 120 rows on the 2nd page): "These seem more like direct definitions ." It seems that there is no problem, but compare the original article: These seem like straightforward definitions until one begins to think through their implications. this sentence was cut down by the translation, and the complete meaning should be: "This seems to be a direct definition, but if you think about the meaning, you will find that this is not the case."

10. (122 rows on page 14th): "10 lbs is 10/72 inch. If you multiply the value by 96, it is about 13 pixels per inch ." This is definitely not true. Let's see the original article: ten points is 10/72 inch, which if you multiply by 96 dots per inch yields a result of (approximately) 13 pixels. Do you understand the problem now? Dots per inch is the unit of resolution, it should be translated into "point per inch" or "point/Inch" (just as the unit of speed is "meter per second" or "meter/second ). Knowing this, this sentence is actually very simple: "10 lbs is 10/72 inch, multiplied by 96 points per inch, it is about 13 pixels ." The following 18th rows have similar problems. Replace "multiply by 120 points, equals to" every inch "with" multiply by 120 points per inch, equals ".

11. (122 rows on page 19th): "like in chapter 4, the actual metric size is displayed again, so you can understand how it works. Do not write code for this in your program ." What is "write code for this "? Let me emphasize again that I'm showing you actual metrics so that you can understand how this works. Do not code these numbers in your programs. This is not difficult to translate: "as I did in Chapter 4th, I would like to emphasize again that the actual dimensions here are just for your understanding of the working mechanism. Do not use these numbers directly in your program ."

12. (The last 125 rows on the 9th page): "note that the most important bit is the 8 bits marked as 0: why are these eight zeros "the most important ". See the original article: notice that the most-significant 8 bits are zero. Most-significant indicates the "highest", not the "most important "!

13. (row 128 on page 1): "Most programmers use savedc and restoredc in different ways. However, more like the push and pop commands in assembly language, when you call savedc, you do not need to save the return value ." What are the methods for most programmers? See the original article: most programmers use savedc and restoredc in a different manner, however, much like push and pop instructions in assembly language. when you call savedc, you don't need to save the return value. This should be translated into: "However, most programmers use savedc and restoredc in another way, just like using push and pop commands in assembly languages. When savedc is called, you do not need to save the return value ."

14. (The last 153 rows on the 2nd page): "You can imagine drawing lines from a point inside an infinitely closed area." Is that true? You can imagine a line drawn from a point in an enclosed area to infinity. This should be translated into: "You can imagine extending the line from a point in the Closed Area to an infinite distance ". The translation of books is really funny. You can still ......" The same problem exists. After all, the same pig can only put the same smell! :-)

15. (163 rows on page 1): "More like customer zone coordinates ." There is no problem with this sentence, but there is a lot of doubt when it is combined with the previous content. Compare the original article: most likely client-area coordinates. God, Our translators have translated likely into "elephant "!!! I am a little embarrassed to write such a simple sentence: "Most of them are the coordinates of the customer zone ."

16. In Windows, xviewext is set to the number of pixels and xwinext is set to the length of several hundred pixels within 1 inch of xviewext pixels ." What is "xviewext's pixel length of several hundred pixels in 1 inch "? See the original article: Windows sets xviewext to be a certain number of pixels and xwinext to be the length in hundredths of an inch occupied by xviewext pixels. This sentence is a little difficult, but even
The English language is so crude that I should be able to give the correct translation: "In Windows, xviewext is set to a certain number of bytes, set xwinext to the length occupied by xviewext pixels, which is 1 inch in a single bit." The following sentence "The ratio gives a value of several hundred pixels in 1 inch" is also the same. It should be changed to "The ratio gives the number of pixels in the length of 1% ".

17. (193 rows on page 1st): "In some overlapping operations, they are usually used together ." What is "overlapping operations "? See the original article: often complementing each other with some overlap. This is simple and should be translated into: "their functions are often complementary and overlap ."

18. (The last 199 lines on the 1st page): "In windows for Working Groups" anyone familiar with Windows knows what the problem is: in the original article, Windows forworkgroups is one of the Microsoft Windows products. The interpreters translate the product name directly. Although the meaning is correct, it will confuse people who are not clear. Product names are generally not translated and can be used directly. Just like PowerPoint in office, if you want to translate it, it is a "power outlet" (I really don't know how Microsoft can name my product as follows :-)). If you want to know if someone has installed PowerPoint on his computer, if you ask him, "Does your computer have a power outlet?", he will definitely stare at you like a monster, answer: "Of course. There are not only computers, but also a few on the wall !" Haha!

19. (lines 213 on page 1): "These character messages are the first message we encounter when passing text to the window. They are not the only messages ." A little hard to understand? These character messages are the first messages we 've encountered that deliver text to the window procedure. They're not the only ones. This should clearly be translated: "These messages are the first message we encountered to deliver text to the window process. They are not the only message with this function ."

20. (row 213 on page 1): "Any window process is associated with the window class you registered with registerclassa (ANSI version of registerclass) to obtain messages containing the ANSI character code." Why! What about registerclassw? What is it? See the original article: any window procedure associated with a window class that you register with registerclassa (the ANSI version of registerclass) gets messages that contain ANSI character codes. Junior high school students should not understand this sentence! It means: "Any window that is close to the window class you registered with registerclassa (the ANSI version of registerclass function) will receive messages containing ANSI character code ."

21. (bottom of p681 page), rowlength = (bmch. bcwidth * bmch. bcbitcount + 31) & 31)> 3; I don't understand. Isn't it true that & 31 intercepts 5 lower digits? It should be rowlength = (bmch. bcwidth * bmch. bcbitcount + 31 )&~ 31)> 3; this is equivalent to "/32.