Internationalization and Localization Using Microsoft .NET :

Rating:
Summary: He's My Brother, so . . .
Review: ...I have... been a project manager in various IT organizations for over 20 years and have worked with many (gasp!) software engineers in my time, and I must say that this is the first book of its kind that I was actually able to read and understand. .. Nick has managed to pen an authoritative and user friendly tome that explores its subject matter thoroughly.

Buy the book.

Rating:
Summary: A pretty good book, but... (read on!)
Review: DISCLAIMER: I was asked to review this book by a few people who were disappointed that I did not have plans to revise my efforts for .Net in the immediate future. So keep in mind that I am an expert with high expectations, rather than someone who bought the book to learn about the topic.

NOTE: I will call Mr. Symmonds "Nick" in the review but I do not actually know him. It just seemed too odd to be constantly referring to him as "Mr. Symmonds" when he made the effort to so carefully provide such a comfortable writing persona. I hope he will not be offended. :-)

ON TO THE REVIEW:

I have to say that I was quite pleased by the book, which does a good job of explaining much of what it means to produce good international applications with the .Net framework. It has examples and it really covers many important details of the Globalization and Encoding classes that are a part of the new framework, as well as the localization model in Windows Forms (WinForms). Production values are first rate (something I truly envy since there were so many problems with the rush to market for my book!) and examples are both on point and to the point. The subject matter is something that sells itself, and Nick packages things up quite well. His writing style is also solid and does not talk down to the reader at all -- it is that of a colleague telling you something that can literally mean the world to your applications (pun intended).

Not all was perfect, though, so I will spend most of the time here explaining my "gripes"...

There was no CDROM, which for me at least made the "includes a resource editor" blurb a bit less than truthful -- there was no "some assembly required" listed there. This book really needed a CD with it, as people want to be able to try things and test them right away. When you buy the book, prepare to do a lot of typing to keep up with it!

Internationalization gets good attention and examples as I said, but there is a lot less conceptual reasoning behind them than I would have liked. One of the biggest conceptual problems I had there was that the international features were actually designed by the very same NLS team that created the original Win32 APIs, based on all of the good and bad lessons they had learned over the last decade and a half, a point that seems to have been overlooked here (as an occasional "almost" member of that team, I tend to notice such things!). Perhaps if Nick had spent more time talking to the NLS+ team he would have been able to add more of that viewpoint, which would have (in my opinion) really enhanced the book.

He also failed to mention issues such as limitations on Win9x (controls such as WinForms TextBox controls do not support languages not on the default system code page). This is mainly a bad thing for the framework but in a book covering this topic it should have been mentioned, both for the sake of internationalization and for localization into other languages.

The book spent a lot more time on issues surrounding localizability rather than localization proper (which is actually okay, as localizability -- the process of making something that can be localized -- is usually more important to developers), but it completely glossed over *some* important localizability issues such as dealing with issues in different important international markets (example -- no good discussion on GB18030 requirements in China or HKSCS in Hong Kong). Since support for GB18030 is mandated in China and since HKSCS 2.0 support is really needed for Hong Kong but is not currently provided, discussion of them would have been nice.

There is no good discussion on security issues (in light of the last minute, month-long delay of the product's release from Microsoft to do intensive security reviews) is also unfortunate. There *are* internationalization issues that affect security even in .Net (casing and collation can still cause security problems for the unwary even if you are safer from "C/C++" problems like buffer overruns) so the lack of mention of them is unfortunate.

I tend to forgive these points (other than the lack of a CDROM!) since there was no room to cover them -- the book is way too short, in my opinion! I would have liked it to be a lot longer so it had room to cover all those issues, especially with [he]list price (mine was free since I was reviewing, but my recommendation to others has to take price into account). With that said, if Nick revises the book, he must make it longer! I have little doubt that such a revision could contain coverage of these missing topics and thus has a lot of potential to complete the topic's coverage and make for a stellar reference.

In the end, I am forced to give it a 3/5 (though I think it actually deserves a 3.5/5, Amazon does have its limits!). It is DEFINITELY a book worth owning but you will have a lot of work to do -- both as you are reading and after you are done -- if you want to create good globalized software with .Net.

Rating:
Summary: Probably the only .NET loc book. Not recommended.
Review: I have a bit of background in localizaiton engineering and I also wrote a few .NET apps (definitely not a professional level, though). Still I got lost in this book and my time was wasted.

If you really try hard, you may get something out of this book, but you'll still be annoyed by Chapter 3 "Using Multiple Resource Files in VB 6". I thought I bought a .NET book. The casual writing style may also make you feel that the author is looking down on you.

I also have to say that this book often just lists the info in MSDN (classes, methods, one-by-one) If this book got 1000 pages, it MAY be acceptable (NO, in my opinion), but it got 300 pages and lists VB, C# code, tries to show a "full-fledged resource editor" in VB, C#, unnecessary VB6 info, and the general localization concepts. No room for useful information on .NET localization.

This is probably the only book that explains .Net internationalization/localization. This book MAY be helpful, but I recommend you try and only try the docs that come with .NET SDK and VS.NET.

The "About the Author" page shows the authors is a electrical engineer who knows "VB, C++ and now .NET", but doesn't show he has any experience in localizaiton. It makes perfect sense to me.

Rating:
Summary: I hoped for more
Review: I was given this book by my boss because we were about to work on an internationalized application. She wanted us to consider doing it with Visual Studio .Net.

Unfortunately, it it did not work out that way. I agree with the other reviewers that the writing is quite good, its not that. The problem is that there is so very little there. There are too many things that this book simply does not cover. And this is from an expert?

I am now doing a lot of research: in MSDN, websites, newsgroups, and elsewhere. Things that should have been here in this book. I am really disappointed in APress for not making the author do the work here so I would not have to.

Rating:
Summary: A disappointment. The book is very 'padded'.
Review: I'm currently reading the book "Internationalization and Localization Using Microsoft .NET". The topic of this book is one which I'm very interested in. Unfortunately, this book has been very disappointing to me.

When read a book on a targeted technical subject, I like to read something which is concise and to the point. Preferably with many useful examples in the text.

This book fails on both points.

The author often wanders off topic in a very conversational tone and there is an entire chapter on Visual Basic 6, which is not .NET. This would be fine if I was reading a book on a general topic which benefits from anecdotes and humor. But this topic is one where I want to get to the "meat" of things and move on. I think with a good editor, this book could be reduced by 100 pages!

I've also found the example code to be trival implementations of the subject, with almost nothing which could be re-used in a professional environment.

Rating:
Summary: Do not waste your time with this book
Review: Our company purchased this book so that we could localize a C# .net project. This book offered very few technical details about important parts of the process.

I found that the author wastes a great deal of space explaining concepts such as "The History of XML" and the basics of localization.

The most glaring omission is the lack of source code for a "functional" globalized application that demonstrates the concepts of satellite assemblies. The lack of source code is a glaring omission on the part of the publisher. In the end, I learned more from the WorldCalc SDK example than I did from this book.

Much of the book rehashes information available in the Visual Studio help documents.

I wish this book would have covered assembly tools such as ildasm. I, also, could not find mention of the all important Assembly Binding Log Viewer (FUSLOGVW.EXE).

This book was rushed to the market by the publisher. Hopefully, the topic will be addressed by another author who has more current information specific to actually working with .NET

Rating:
Summary: I expected a lot more with that title
Review: With a title like "Internationalization and Localization Using Microsoft .Net" I expected a lot more than this really thin book with no CD. One of the big things I was hoping for was information about the new Chinese encoding standard and whether .Net supports it. The government of China requires support and so we needed to know what .Net provides for it. But there was not even a word on how our international application could support it. In the end, I really got more help from the various topics in the MSDN that came with Visual Studio .Net than I did from this book.

I was also hoping for a lot of utilities that could make it easier to work with .Net, but there were none bundled.

On the good side, it was better than the Kaplan book in terms of typos and Mr. Symmonds rambled a lot less, too. And I do have to admit that the writing style was good. I really felt like the author was speaking to me. Unfortunately, after I was done with the mere 350 pages I realized that he was not saying as much as I would have liked.