Bug 124751 - incorrect internationalization when displaying error message
Summary: incorrect internationalization when displaying error message
Status: RESOLVED REMIND
Alias: None
Product: konqueror
Classification: Applications
Component: general (show other bugs)
Version: 3.5
Platform: Debian testing Linux
: NOR normal
Target Milestone: ---
Assignee: Konqueror Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-02 13:32 UTC by Robert Gomułka
Modified: 2008-07-06 01:23 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
Bad look (13.83 KB, image/png)
2006-04-02 13:32 UTC, Robert Gomułka
Details
Good look (12.07 KB, image/png)
2006-04-02 13:33 UTC, Robert Gomułka
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Gomułka 2006-04-02 13:32:08 UTC
Version:            (using KDE KDE 3.5.2)
Installed from:    Debian testing/unstable Packages
OS:                Linux

When I have network problems and cannot connect to http server, konqueror displays error message. This message is localized. Almost always it is displayed improperly, but sometimes ok - I don't know what it depends on.
The message itself comes from http.cc:
       case IO_TimeOutError:
          errMsg = i18n("Connection was to %1 at port %2").arg(m_state.hostname).arg(m_state.port);
          errCode = ERR_SERVER_TIMEOUT;
          break;

which is translated in kdelibs.po:
#: ../kioslave/http/http.cc:2110
msgid "Connection was to %1 at port %2"
msgstr "Nawiązano połączenie z serwerem %1 na porcie %2"

I might be wrong, but couldn't find any other occurencies of the string.
Comment 1 Robert Gomułka 2006-04-02 13:32:51 UTC
Created attachment 15417 [details]
Bad look
Comment 2 Robert Gomułka 2006-04-02 13:33:22 UTC
Created attachment 15418 [details]
Good look
Comment 3 Thiago Macieira 2006-04-05 01:19:47 UTC
I thought we had fixed this.
Comment 4 Jaime Torres 2008-05-16 18:13:40 UTC
Works for me in trunk 20080507
Comment 5 Jaime Torres 2008-05-17 09:35:50 UTC
Works for me in svn trunk r807691 (20080507)
Comment 6 Michael Leupold 2008-05-20 23:25:02 UTC
Is it possible that this is related to the encoding of the website you are trying to visit (eg. the header has already been transferred but it dies on the body)?
Well, maybe this problem doesn't occur any longer. If so, please tell us.
Comment 7 A. Spehr 2008-07-06 01:23:17 UTC
no response...

If this happens to you again in a recent 4 version, can you reopen? Thanks!