1) find guilty code. This is hard in general, but some things are easy such as printf's.

2) find code which tries to be innocent, ie, tries to support wide characters. Chances are, they've done it wrong. At least it provides us a starting point; the developer has gone to the trouble to identify this code as requiring I18N. This is easy since there are only a few functions which correctly support I18N.

3) Divine how the code must work to determine whether it needs I18N. To do this, read the user's manual.

4) Write tools to do the I18N automatically if possible. At least these tools may be used to identify suspicious source modules.

5) Stage the development. First stage is programmer's interfaces. Next stage is translator's interfaces. Third stage is user's interfaces.