There's little reason, I suppose, why internationalizing the code of a software program is any less challenging than internationalizing an application. That is

There's little reason, I suppose, why internationalizing the code of a software program is any less challenging than internationalizing an application. That is to say: language keywords, function and variable names, comments, documentation, and perhaps even multi-token structures might all require associated translation strings. And as with translating an application (or any text, really), the source material might be written in one native language, and only later be translated into others based on demand and interest. Software projects have the interesting property that partial translations might make sense under some circumstances. A commonly-used API function could be translated first, for example. It'd be impressive to work on a project where multiple developers are each individually contributing to literally the same codebase, but each reading and writing it in their own native language(s). (clearly a situation like that would require a lot of input from translators too - ideally with context for the software language and the project itself)