3 ms·
I'm not completely sure how well that would work in practice, as many times programmers don't use actual works for names, but abbreviations (len, dict, etc.).
by saghm 9y ago
I'm not completely sure how well that would work in practice, as many times programmers don't use actual works for names, but abbreviations (len, dict, etc.). That being said, I think the example the author gave about Excel worked well because there was an already-enumerated set of functions that needed to be localized. I could totally see it being feasible, if tricky with regards to parsing, for (programming) langues to provide a compiler/interpreter flag to instead use a different translation/localization for keywords and standard library identifers, which although presumably more numerous than the number of functions in Excel, are still an already-enumerated set. Given how most languages rely on community contributions for translating documentation, they could presumably ask the same contributors to help with localization of a language's built-in and standard library identifers.