Barry Warsaw wrote: > Another decidedly ignorant Anglophone here, but one problem that I see > with localizing stuff is that locale is app- (or at least thread-) > global, isn't it? That would suck for applications like Mailman which > are (going to be) multilingual in the sense that a single instance of > the application will serve up documents in many languages, as opposed > to serving up documents in just one of a choice of languages. > > If it seems I don't know what I'm talking about, you're probably > right. I just wanted to point out that there are applications have to > deal with many languages at the same time. Applications may also have to deal with output devices (i.e. GUI toolkits, printers, communication links) that don't necessarily have the same restrictions as the "default console". better do it the right way: deal with encodings at the boundaries, not inside the application. </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