Red Hat Bugzilla – Bug 952418
[ALL LANG] - [Reports Portal] - Input Control Box Untranslated text +Mis-rendered special characters for the drop-down values.
Last modified: 2016-02-10 14:00:43 EST
Created attachment 736094 [details] [Reports Portal] - View-Search Results - Input Control Box Untranslated text +Mis-rendered special characters Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. Login Reports Portal 2. Click the View - Search Results button in the menu bar at the top of the reports portal. 3. Select Active Virtual Machine by OS (BR18) Actual results: See Screenshot: *'Input Controls' Expected results: The word 'annu00E9e' should read 'année' In Data Center & in Cluster, the word 'Default' should be 'Valeur par défaut'if possible. Additional info:
Is the database locale fr as well? Can you check the table enum transaltor to see, if it's ok there? Did you see any outher issues displaying é in the setup? Yaniv
*** Bug 953707 has been marked as a duplicate of this bug. ***
Created attachment 739807 [details] Drop-down values issues
NO, I did not see any other issue displaying é in the setup a priori Database locale in FR: yes Sorry I don't know what you mean by the enum table translator.
Eli, do you have a clue to why the db would return é as the sign code? yaniv
(In reply to comment #10) > Eli, do you have a clue to why the db would return é as the sign code? > > > > > yaniv Please provide the following information 1) output of : psql -U postgres -c "show LC_COLLATE" engine psql -U postgres -c "show LC_CTYPE" engine 2) output of the locale command from the shell prompt on the machine hosting the DB > locale bv
(In reply to comment #11) > (In reply to comment #10) > > Eli, do you have a clue to why the db would return é as the sign code? > > > > > > > > > > yaniv > > Please provide the following information > > 1) output of : > > psql -U postgres -c "show LC_COLLATE" engine > psql -U postgres -c "show LC_CTYPE" engine > > 2) output of the locale command from the shell prompt on the machine hosting > the DB > > > locale > > bv [root@rhevm32 yum.repos.d]# locale LANG=ja_JP.UTF8 LC_CTYPE="ja_JP.UTF8" LC_NUMERIC="ja_JP.UTF8" LC_TIME="ja_JP.UTF8" LC_COLLATE="ja_JP.UTF8" LC_MONETARY="ja_JP.UTF8" LC_MESSAGES="ja_JP.UTF8" LC_PAPER="ja_JP.UTF8" LC_NAME="ja_JP.UTF8" LC_ADDRESS="ja_JP.UTF8" LC_TELEPHONE="ja_JP.UTF8" LC_MEASUREMENT="ja_JP.UTF8" LC_IDENTIFICATION="ja_JP.UTF8" LC_ALL= [root@rhevm32 yum.repos.d]# psql -U postgres -c "show LC_COLLATE" engine ユーザ postgres のパスワード: lc_collate ------------ en_US.UTF8 (1 行) [root@rhevm32 yum.repos.d]# psql -U postgres -c "show LC_CTYPE" engine ユーザ postgres のパスワード: lc_ctype ------------ en_US.UTF8 (1 行)
(In reply to comment #12) > (In reply to comment #11) > > (In reply to comment #10) > > > Eli, do you have a clue to why the db would return é as the sign code? > > > > > > > > > > > > > > > yaniv > > > > Please provide the following information > > > > 1) output of : > > > > psql -U postgres -c "show LC_COLLATE" engine > > psql -U postgres -c "show LC_CTYPE" engine > > > > 2) output of the locale command from the shell prompt on the machine hosting > > the DB > > > > > locale > > > > bv > > [root@rhevm32 yum.repos.d]# locale > LANG=ja_JP.UTF8 > LC_CTYPE="ja_JP.UTF8" > LC_NUMERIC="ja_JP.UTF8" > LC_TIME="ja_JP.UTF8" > LC_COLLATE="ja_JP.UTF8" > LC_MONETARY="ja_JP.UTF8" > LC_MESSAGES="ja_JP.UTF8" > LC_PAPER="ja_JP.UTF8" > LC_NAME="ja_JP.UTF8" > LC_ADDRESS="ja_JP.UTF8" > LC_TELEPHONE="ja_JP.UTF8" > LC_MEASUREMENT="ja_JP.UTF8" > LC_IDENTIFICATION="ja_JP.UTF8" > LC_ALL= > [root@rhevm32 yum.repos.d]# psql -U postgres -c "show LC_COLLATE" engine > ユーザ postgres のパスワード: > lc_collate > ------------ > en_US.UTF8 > (1 行) > > [root@rhevm32 yum.repos.d]# psql -U postgres -c "show LC_CTYPE" engine > ユーザ postgres のパスワード: > lc_ctype > ------------ > en_US.UTF8 > (1 行) Seems as the database has the wrong locale the only way to fix it AFAIK is to backup DBs, fix with initdb and restore the databases , please follow: http://programming.aiham.net/2011/07/26/changing-locale-of-postgresql-db-cluster/ Please backup everything as recommended in this thread
Any news? Yaniv
(In reply to comment #14) > Any news? > > > > Yaniv Tried with Comment 13, but seems it didn't work and got error after that when accessing the report portal: Internal Server Error Internal server error occurred. Please contact your system administrator. Details: /etc/init.d/postgresql stop su - postgres pg_dumpall > backup.sql cp /var/lib/pgsql/data /var/lib/pgsql/data_backup initdb --locale=ja_JP.UTF-8 /var/lib/pgsql/data -bash-4.1$ initdb --locale=ja_JP.UTF-8 /var/lib/pgsql/data The files belonging to this database system will be owned by user "postgres". This user must also own the server process. The database cluster will be initialized with locale ja_JP.UTF-8. The default database encoding has accordingly been set to UTF8. initdb: could not find suitable text search configuration for locale ja_JP.UTF-8 The default text search configuration will be set to "simple". fixing permissions on existing directory /var/lib/pgsql/data ... ok creating subdirectories ... ok selecting default max_connections ... 100 selecting default shared_buffers ... 32MB creating configuration files ... ok creating template1 database in /var/lib/pgsql/data/base/1 ... ok initializing pg_authid ... ok initializing dependencies ... ok creating system views ... ok loading system objects' descriptions ... ok creating conversions ... ok creating dictionaries ... ok setting privileges on built-in objects ... ok creating information schema ... ok vacuuming database template1 ... ok copying template1 to template0 ... ok copying template1 to postgres ... ok WARNING: enabling "trust" authentication for local connections You can change this by editing pg_hba.conf or using the -A option the next time you run initdb. Success. You can now start the database server using: postgres -D /var/lib/pgsql/data or pg_ctl -D /var/lib/pgsql/data -l logfile start psql -f backup.sql postgres exit /etc/init.d/postgresql start
please provide again after doing the previous operation 1) output of : psql -U postgres -c "show LC_COLLATE" engine psql -U postgres -c "show LC_CTYPE" engine
(In reply to comment #16) > please provide again after doing the previous operation > > > 1) output of : > > psql -U postgres -c "show LC_COLLATE" engine > psql -U postgres -c "show LC_CTYPE" engine The locale still in English: [root@rhevm32 ~]# psql -U postgres -c "show LC_COLLATE" engine lc_collate ------------ en_US.UTF8 (1 行) [root@rhevm32 ~]# psql -U postgres -c "show LC_CTYPE" engine lc_ctype ------------ en_US.UTF8 (1 行)
Please try to configurate jboss to support UTF 8 1. Inside standalone.xml insert: <system-properties> <property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8"/> <property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true"/> </system-properties> 2. Adding -Dfile.encoding = utf-8 in JBoss AS start JVM arguments. Yaniv
(In reply to comment #23) > Please try to configurate jboss to support UTF 8 > > 1. Inside standalone.xml insert: > <system-properties> > <property name="org.apache.catalina.connector.URI_ENCODING" > value="UTF-8"/> > <property > name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" > value="true"/> > </system-properties> > I tried this, but not sure if the settings was right or not, issues still reproduced: [root@rhevm32 ~]# find / -name standalone.xml /etc/jbossas/standalone/standalone.xml [root@rhevm32 ~]# cat /etc/jbossas/standalone/standalone.xml <?xml version='1.0' encoding='UTF-8'?> <server xmlns="urn:jboss:domain:1.3"> <extensions> <extension module="org.jboss.as.clustering.infinispan"/> <extension module="org.jboss.as.configadmin"/> <extension module="org.jboss.as.connector"/> <extension module="org.jboss.as.deployment-scanner"/> <extension module="org.jboss.as.ee"/> <extension module="org.jboss.as.ejb3"/> <extension module="org.jboss.as.jaxrs"/> <extension module="org.jboss.as.jdr"/> <extension module="org.jboss.as.jmx"/> <extension module="org.jboss.as.jpa"/> <extension module="org.jboss.as.logging"/> <extension module="org.jboss.as.mail"/> <extension module="org.jboss.as.naming"/> <extension module="org.jboss.as.osgi"/> <extension module="org.jboss.as.pojo"/> <extension module="org.jboss.as.remoting"/> <extension module="org.jboss.as.sar"/> <extension module="org.jboss.as.security"/> <extension module="org.jboss.as.threads"/> <extension module="org.jboss.as.transactions"/> <extension module="org.jboss.as.web"/> <extension module="org.jboss.as.webservices"/> <extension module="org.jboss.as.weld"/> </extensions> <system-properties> <property name="org.apache.catalina.connector.URI_ENCODING" value="UTF-8"/> <property name="org.apache.catalina.connector.USE_BODY_ENCODING_FOR_QUERY_STRING" value="true"/> </system-properties> > 2. Adding -Dfile.encoding = utf-8 in JBoss AS start JVM arguments. Have no idea about how to config this, could you please login the server for a look? 10.66.11.52 root/redhat Thanks > > > > Yaniv
This doctext is no needed. It has been fixed in a way that doesn't need user intervention. Yaniv
Created attachment 803160 [details] Dropdown Box values fixed
Confirmed the fix in all 6 locales. Values in dropdown boxes are now readable. Screenshot attached. Moving the status to VERIFIED.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2014-0036.html