Darren Boss 1:20 PM
|
I'm having a problem with the TAP container displaying accented characters that I wasn't having with a previous setup. I've got both running at the moment with a subject exhibiting the issue loaded on both deployments. Where should I start looking in order to solve the display issue?
|
1:21
|
The accented characters are in the subject name (cn, sn)
|
1:21
|
source is openldapChris Hyzer 1:23 PM
|
hmmm, this page has some notes about it... https://spaces.at.internet2.edu/display/Grouper/Grouper+internationalization i will try to take a look also todayShilen Patel 1:25 PM
|
Interesting, I'm having the same problem it appears.Darren Boss 1:35 PM
|
Name | Owner | Encoding | Collate | Ctype | Access privileges
|
-----------+----------+----------+-------------+-------------+-----------------------
|
grouper | postgres | UTF8 | en_US.UTF-8 | en_US.UTF-8 |
|
1:35
|
but I don't think this has anything to do with the databaseChris Hyzer 1:36 PM
|
its probably one of the java or tomcat flags that we need to update in the container, or you could temporarilyDarren Boss 1:36 PM
|
I don't mind being a guinea pig on this, this is not a production setupShilen Patel 1:37 PM
|
For me adding -Dfile.encoding=UTF-8 fixes itChris Hyzer 1:37 PM
|
that should be a default catalina opt right?Shilen Patel 1:38 PM
|
i would think soDarren Boss 1:38 PM
|
I did make note that when I listed the running processes in the container, I did not see -Dfile.encoding=UTF-8 in the output of the java process (edited) Chris Hyzer 1:40 PM
|
make sure you are using 2.5.23 and change the docker run command to add this var, and see if it helps :slightly_smiling_face:
|
-e GROUPER_EXTRA_CATALINA_OPTS='-Dfile.encoding=UTF-8'
|
:+1:
|
1NewDarren Boss 1:43 PM
|
tested and workingChris Hyzer 1:44 PM
|
ok, i will get that in the next container and you can remove that from your command then :slightly_smiling_face:
|
Bug
Minor