Until a localized version exists, we can use the English page in case of documentation not found. Better than the unprofessional blank background message. When a localized version becomes available, we simply replace the English file with the localized version.

Here is the way the newly patched code looks:

====================================

TQString HelpProtocol::lookupFile(const TQString &fname, const TQString &query, bool &redirect) { redirect = false;

TQString path, result;

path = fname;

result = langLookup(path); if (result.isEmpty()) { result = langLookup(path+"/index.html"); if (!result.isEmpty()) { KURL red( "help:/" ); red.setPath( path + "/index.html" ); red.setQuery( query ); redirection(red); kdDebug( 7119 ) << "redirect to " << red.url() << endl; redirect = true; } else { const TQString helpNotFound = "khelpcenter/helpnotfound/index.html"; if (!langLookup(helpNotFound).isEmpty()) { KURL red; red.setProtocol("help"); red.setPath(helpNotFound); red.setQuery(query); redirection(red); kdDebug( 7119 ) << "redirect to " << red.url() << endl; redirect = true; } else { unicodeError( i18n("There is no documentation available for %1." ).arg(path) ); finished(); return TQString::null; } } } else kdDebug( 7119 ) << "result " << result << endl;

return result; }

====================================

Does that mean all i18n users will not see the new English page or a translated page?

Would be nice if i18n users saw the default English page. I really hate the blank page and lame error message.

I have no experience tinkering with i18n. I probably should learn how and at least install the en-GB i18n package.

Darrell