AW: [opencms-dev] Do you want to use directory translation?

[Oppermann, Joerg]

Hallo,

our experience with charset problems in V5 beta 2. 
We tried the following configurations:
1. CATALINA_OPTS unset, jdk 1.3.x (we did not care about the jvm requirement in the release notes - sorry), tomcat 4.1.x
- Administration was opened but we got javascript errors, I tried to research the problem and found that opencms.css was cutted on a 'Umlaut'.
2. CATALINA_OPTS set to -Dfile.encoding=UTF-8, jdk 1.3.x
- same problems like configuration 1
3. CATALINA_OPTS set to -Dfile.encoding=UTF-8, jdk 1.4.1
- no problems in the administration
- we installed the news module with some tricks and now have problems with 'Umlauten' in news entries, I'm currently in research for the problem.

For each configuration we installed a new opencms version. 
Opencms is running on a Windows System and a Sun Solaris System.
As browser we tried IE 5.5 and IE 6.

regards, Joerg

-----Ursprungliche Nachricht-----
Von: Alexander Kandzior [mailto:alex at opencms.org]
Gesendet: Freitag, 6. Dezember 2002 12:17
An: opencms-dev at www.opencms.org
Betreff: RE: [opencms-dev] Do you want to use directory translation?


Thomas,

> I hope these charset problems don't get annoying to you.

they certainly are, but they must be fixed, so I very much appreciate
your input.

> Testing scenarios:
> ------------------
> 
> CATALINA_OPTS           | directory translation    | result
> -----------------------------------------------------------------
>   unset                 |   yes                    |   working
>   unset                 |   no                     |   not working
>                         |                          |
>   -Dfile.encoding=UTF-8 |   yes                    |   working
>   -Dfile.encoding=UTF-8 |   yes                    |   not working

Can you explain the last 2 lines? Seem to be the same to me. 

> The results that didn't work displayed no folders and files 
> in the explorer-windows, but I got a JavaScript error message.

We already have located an issue in the JavaScript and have fixed that,
so that problem might be gone in the next release. 


Best Regards,
Alex.

Alexander Kandzior
OpenCms Group / Alkacon Software