To take the possible urgency out of this topic, I would like to inform
you that UTF-8 support in Jahia 4.0.5 is just fine. We currently don't
know why, but it seems like our cutomized Jahia server.xml file for
Tomcat is the reason why tidy or UTF-8 support seems like to
misbehave. If we start our automatic build process the templates,
config file and other stuff is packaged and overwrites a fresh or
existing jahia version. When I restore our server.xml with a fresh
(from scratch jahia installation) server.xml, UTF-8 and tidy are fine.
Maybe you can have a look on the file?
Cheers
Daniel Zimmermann
On Mon, 06 Dec 2004 12:22:49 +0100, St�phane Croisier
<[EMAIL PROTECTED]> wrote:
>
> Strange because umlauts work fine for us on a fresh UTF8 4.0.5 install...
>
> So is this coming only for migrated data or also for new 4.0.5 data? Is
> this happening only for big texts (stored on the file system) or also for
> small texts (stored directly in the database)? Do you see the umlauts in
> the WYSIWYG Editors when loading the data or is it already wrong here (or
> only wrong when saving the data)? Are you sure your old big texts are still
> in UTF-8 format (if you, for example, reinstall the old data on a new
> server by zipping/tar.gzing the old data perhaps you this process converted
> your text files back in ISO format)? Are you sure that your linux config
> (etc/sysconfig/i18n) is correct?
>
> Finally if everything seems correct, could send us an exemple of big text
> with an umlaut and where the error occurs such as:
> E:\jahia405\tomcat\webapps\jahia\WEB-INF\var\content\bigtext\1-2-20-de.jahia
>
> 1-2-20-de.jahia = sitekey-pid-field-lang.jahia
> Version with -s means this is a staging version. Version with the timestamp
> that this is an archive.
>
> Cheers
> St�phane
>
>
>
> At 11:30 06/12/2004, you wrote:
> >...with german umlauts and other special characters again.
> >I have posted this before and the error is still in Jahia 4.0.5... and
> >even worse.
> >We use a UTF-8 MySQL database, with a UTF-8 RedHat Linux on Intel platform.
> >
> >tidy.properties is (after the jahia "wizard" installation) for standard
> >configured to latin-1 or UTF-8 (at least it was UTF-8 on 4.0.5PR) via
> >the content-encoding property. UTF-8 should be fine for our configuration.
> >
> >On 4.0.4 we could set the property to "raw" to get for example german
> >umlauts right.UTF-8 did never ever work correctly. That was strange,
> >but it was some kind of a solution. But with Jahia 4.0.5PR neither
> >value works. When a Jahia page is displayed in the browser, both IE6
> >SP1 and Firebird tell that it's UTF-8. If you already have Bigtext or
> >DB Fields with UTF-8 content (e.g. from migration) everything is
> >displayed correct. But if you try to edit a container, the text is
> >corrupted :(
> >
> >The failure arises regardless of which editor you use. ActiveX,
> >simple, HTMLArea... They all corrupt the text after you apply changes
> >or save via "ok". So it really seems to be something about the html
> >tidy option in Jahia or HTMLTidy itself.
> >
> >P.S.: Tidy is activated though. We can set "internal" links like 123
> >and they are resolved to the correct relative path URL for page 123.
>
>
<!-- A "Server" is a singleton element that represents the entire JVM,
which may contain one or more "Service" instances. The Server
listens for a shutdown command on the indicated port.
Note: A "Server" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<Server port="8005" shutdown="SHUTDOWN" debug="0">
<Listener className="org.apache.catalina.mbeans.ServerLifecycleListener"
debug="0"/>
<Listener className="org.apache.catalina.mbeans.GlobalResourcesLifecycleListener"
debug="0"/>
<!-- Global JNDI resources -->
<GlobalNamingResources>
<!-- Editable user database that can also be used by
UserDatabaseRealm to authenticate users -->
<Resource name="UserDatabase" auth="Container"
type="org.apache.catalina.UserDatabase"
description="User database that can be updated and saved">
</Resource>
<ResourceParams name="UserDatabase">
<parameter>
<name>factory</name>
<value>org.apache.catalina.users.MemoryUserDatabaseFactory</value>
</parameter>
<parameter>
<name>pathname</name>
<value>conf/tomcat-users.xml</value>
</parameter>
</ResourceParams>
</GlobalNamingResources>
<!-- A "Service" is a collection of one or more "Connectors" that share
a single "Container" (and therefore the web applications visible
within that Container). Normally, that Container is an "Engine",
but this is not required.
Note: A "Service" is not itself a "Container", so you may not
define subcomponents such as "Valves" or "Loggers" at this level.
-->
<!-- Define the Tomcat Stand-Alone Service -->
<Service name="Tomcat-Standalone">
<!-- A "Connector" represents an endpoint by which requests are received
and responses are returned. Each Connector passes requests on to the
associated "Container" (normally an Engine) for processing.
By default, a non-SSL HTTP/1.1 Connector is established on port 8080.
You can also enable an SSL HTTP/1.1 Connector on port 8443 by
following the instructions below and uncommenting the second Connector
entry. SSL support requires the following steps (see the SSL Config
HOWTO in the Tomcat 4.0 documentation bundle for more detailed
instructions):
* Download and install JSSE 1.0.2 or later, and put the JAR files
into "$JAVA_HOME/jre/lib/ext".
* Execute:
%JAVA_HOME%\bin\keytool -genkey -alias tomcat -keyalg RSA (Windows)
$JAVA_HOME/bin/keytool -genkey -alias tomcat -keyalg RSA (Unix)
with a password value of "changeit" for both the certificate and
the keystore itself.
By default, DNS lookups are enabled when a web application calls
request.getRemoteHost(). This can have an adverse impact on
performance, so you can disable it by setting the
"enableLookups" attribute to "false". When DNS lookups are disabled,
request.getRemoteHost() will return the String version of the
IP address of the remote client.
-->
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 80 -->
<Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
port="80" minProcessors="5" maxProcessors="75"
enableLookups="true" redirectPort="8443"
acceptCount="50" debug="0" connectionTimeout="20000"
useURIValidationHack="false" disableUploadTimeout="true" />
<!-- Note : To disable connection timeouts, set connectionTimeout value
to -1 -->
<!-- Define the top level container in our container hierarchy -->
<Engine name="Standalone" defaultHost="localhost" debug="0">
<!-- The request dumper valve dumps useful debugging information about
the request headers and cookies that were received, and the response
headers and cookies that were sent, for all requests received by
this instance of Tomcat. If you care only about requests to a
particular virtual host, or a particular application, nest this
element inside the corresponding <Host> or <Context> entry instead.
For a similar mechanism that is portable to all Servlet 2.3
containers, check out the "RequestDumperFilter" Filter in the
example application (the source for this filter may be found in
"$CATALINA_HOME/webapps/examples/WEB-INF/classes/filters").
Request dumping is disabled by default. Uncomment the following
element to enable it. -->
<Valve className="org.apache.catalina.valves.RequestDumperValve"/>
<!-- Global logger unless overridden at lower levels -->
<Logger className="org.apache.catalina.logger.FileLogger"
prefix="catalina_log." suffix=".txt"
timestamp="true"/>
<!-- Because this Realm is here, an instance will be shared globally -->
<!-- This Realm uses the UserDatabase configured in the global JNDI
resources under the key "UserDatabase". Any edits
that are performed against this UserDatabase are immediately
available for use by the Realm. -->
<Realm className="org.apache.catalina.realm.UserDatabaseRealm"
debug="0" resourceName="UserDatabase"/>
<!-- Comment out the old realm but leave here for now in case we
need to go back quickly -->
<!-- Replace the above Realm with one of the following to get a Realm
stored in a database and accessed via JDBC -->
<!-- Define the default virtual host -->
<Host name="localhost" debug="0" appBase="webapps" unpackWARs="true" autoDeploy="true">
<!-- Normally, users must authenticate themselves to each web app
individually. Uncomment the following entry if you would like
a user to be authenticated the first time they encounter a
resource protected by a security constraint, and then have that
user identity maintained across *all* web applications contained
in this virtual host. -->
<!-- Access log processes all requests for this virtual host. By
default, log files are created in the "logs" directory relative to
$CATALINA_HOME. If you wish, you can specify a different
directory with the "directory" attribute. Specify either a relative
(to $CATALINA_HOME) or absolute path to the desired directory.
-->
<!--
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="logs" prefix="localhost_access_log." suffix=".txt"
pattern="common" resolveHosts="false"/>
-->
<!-- Logger shared by all Contexts related to this virtual host. By
default (when using FileLogger), log files are created in the "logs"
directory relative to $CATALINA_HOME. If you wish, you can specify
a different directory with the "directory" attribute. Specify either a
relative (to $CATALINA_HOME) or absolute path to the desired
directory.-->
<Logger className="org.apache.catalina.logger.FileLogger"
directory="logs" prefix="localhost_log." suffix=".txt"
timestamp="true"/>
<!-- Define properties for each web application. This is only needed
if you want to set non-default properties, or have web application
document roots in places other than the virtual host's appBase
directory. -->
<DefaultContext crossContext="true"/>
<!-- PersistentManager: Uncomment the section below to test Persistent
Sessions.
saveOnRestart: If true, all active sessions will be saved
to the Store when Catalina is shutdown, regardless of
other settings. All Sessions found in the Store will be
loaded on startup. Sessions past their expiration are
ignored in both cases.
maxActiveSessions: If 0 or greater, having too many active
sessions will result in some being swapped out. minIdleSwap
limits this. -1 or 0 means unlimited sessions are allowed.
If it is not possible to swap sessions new sessions will
be rejected.
This avoids thrashing when the site is highly active.
minIdleSwap: Sessions must be idle for at least this long
(in seconds) before they will be swapped out due to
activity.
0 means sessions will almost always be swapped out after
use - this will be noticeably slow for your users.
maxIdleSwap: Sessions will be swapped out if idle for this
long (in seconds). If minIdleSwap is higher, then it will
override this. This isn't exact: it is checked periodically.
-1 means sessions won't be swapped out for this reason,
although they may be swapped out for maxActiveSessions.
If set to >= 0, guarantees that all sessions found in the
Store will be loaded on startup.
maxIdleBackup: Sessions will be backed up (saved to the Store,
but left in active memory) if idle for this long (in seconds),
and all sessions found in the Store will be loaded on startup.
If set to -1 sessions will not be backed up, 0 means they
should be backed up shortly after being used.
To clear sessions from the Store, set maxActiveSessions, maxIdleSwap,
and minIdleBackup all to -1, saveOnRestart to false, then restart
Catalina.
-->
<!--
<Manager className="org.apache.catalina.session.PersistentManager"
debug="0"
saveOnRestart="true"
maxActiveSessions="-1"
minIdleSwap="-1"
maxIdleSwap="-1"
maxIdleBackup="-1">
<Store className="org.apache.catalina.session.FileStore"/>
</Manager>
-->
</Host>
<!-- Einfuegung AccessLogValve, Scope Engine, loggt alle Request, die von allen Kontexten
in allen Hosts dieser Engine empfangen werden
Toralf Richter, 13.10.2004 -->
<Valve className="org.apache.catalina.valves.AccessLogValve"
directory="access_logs/"
prefix="access_log." suffix=".log"
pattern="combined"
resolveHosts="false" />
</Engine>
</Service>
</Server>
