Mike wrote: > Any literal strings one embeds in code should be purely for the = benefit of > the code, not for the end user, who should be seeing properly = localized > text, pulled back from a localized text resource file _NOT_ python = code, and > automatically pumped through the appropriate native <--> unicode > translations as required by the code. that's hardly a CP4E compatible solution, is it? Ping wrote: > > But you're right, i've never heard of another language that can = handle > > configurable encodings right in the source code. XML? </F>
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4