On 8/25/2010 5:41 PM, Nick Coghlan wrote:
> On Thu, Aug 26, 2010 at 6:26 AM, Terry Reedy<tjreedy at udel.edu> wrote:
>> On 8/25/2010 2:31 PM, Michael Foord wrote:
>>> A downside (from experience with .NET which takes this approach - logic
>>> and class names are all English but error messages are localized) is
>>> that you then get bug reports with localized error messages. It makes
>>> frequent visits to google translate unavoidable...
>>
>> Localized messages should be in addition to rather than a replacement for
>> the English version. I thought we had this discussion somewhere -- here?
>> ideas? maybe a tracker issue?
>
> I remember the same discussion, and yeah, the final position was that
> including the original English text along with the localised text made
> the most sense. The idea didn't really go anywhere after that though,
> since it is still a *lot* of work.
Just after posting, I went to python-list, and read a response from OP
asked to paste the traceback for his problem:
...
File "C:\Python26\lib\socket.py", line 406, in readline
data = self._sock.recv(self._rbufsize)
socket.error: [Errno 10054] A lÚtez§ kapcsolatot a tßvoli ßllomßs
kÚnyszerÝtette n bezßrta
Fortunately, the OP could translate back well enough to "So this message
is meaning that the remote station forced close the existing
connection." and get additional help from other respondents. So the
idea, at least, of giving both versions would be a good one ;-).
--
Terry Jan Reedy
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