Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 142002 - Default Locale / Konqueror problems
Default Locale / Konqueror problems
Product: Red Hat Network
Classification: Red Hat
Component: RHN/R&D (Show other bugs)
RHN Devel
All Linux
medium Severity medium
: ---
: ---
Assigned To: Mike McCune
Red Hat Satellite QA List
Depends On:
Blocks: rhnMilestone1
  Show dependency treegraph
Reported: 2004-12-06 12:55 EST by Michael Bowman
Modified: 2007-04-18 13:16 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-12-06 17:41:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Michael Bowman 2004-12-06 12:55:02 EST
Description of problem:
l18n in Konqueror doesn't work. Looks like Konqueror isn't sending the
locale struts is expecting. When we output strings in actual java code
using the localization service, it works. When we output strings via
the bean tag in a jsp, localization doesn't work. 

I think this is because we set the default locale in
localizationService.java, but we don't have a default resource bundle
for the bean tag. Struts in Action says that resource bundles follow
an inheritance tree so StringResource_en_US.properties inherits from
StringResource.properties (thereby setting StringResource.properties
as the default locale).

I've tried copying StringResource_en_US.xml to StringResource.xml, but
it doesn't work.

If you need more info on the problem, call or msg me.

Version-Release number of Konqueror:
3.1.3-5.4 (Default on RHEL 3 WS)

Note You need to log in before you can comment on or make changes to this bug.