|
I used the new workspace and bringed old personalization inside. So the migration is ok. I just found the solution : We use the i18n jakarta taglib. We need to change our bundle reference from <i18n:bundle baseName="com.sopra.i18n.app" id="bundleApp"/> to <i18n:bundle baseName="com.sopra.i18n.app" id="bundleApp" changeResponseLocale="UTF-8"/> and now everything is ok. Thanks for your help. Vincent -----Message d'origine----- De : wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]De la part de Mike Hockings Envoyé : mardi 1 mars 2005 18:54 À : Websphere Development Studio Client for iSeries Objet : RE: [WDSCI-L] Character encoding trouble Have you also removed the WFCharacterEncodingFilter ? If so you will need to set-up WAS to do the client encoding for you as described in the docs. By migration do you mean (I hope) that you used the WebFacing import tool to upgrade your project from 5.1 to 5.1.2 ? Or are you just using the old 5.1 workspace? Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@xxxxxxxxxx "Dupuis Vincent" <vdupuis@xxxxxxxxxxxxxx> Sent by: wdsci-l-bounces@xxxxxxxxxxxx 03/01/2005 09:51 AM Please respond to Websphere Development Studio Client for iSeries To "Websphere Development Studio Client for iSeries" <wdsci-l@xxxxxxxxxxxx> cc Subject RE: [WDSCI-L] Character encoding trouble just a precision : when we turn off web pages compression (removing the filter compression reference from the web.xml file) the characters are well printed but on the third page we received the error page saying WF0116: The encoding check field was received incorrectly by the application server. This is likely caused by the data transferred from the browser to the application server not being encoded in UTF-8. Please refer to the WebFacing documentation about how to set up UTF-8 client encoding in WebSphere Application Server -----Message d'origine----- De : wdsci-l-bounces@xxxxxxxxxxxx [mailto:wdsci-l-bounces@xxxxxxxxxxxx]De la part de Dupuis Vincent Envoyé : mardi 1 mars 2005 15:38 À : wdsci-l@xxxxxxxxxxxx Objet : [WDSCI-L] Character encoding trouble Hello, We are working in a webfaced application. We recently migrate our WDSC version from 5.1 to 5.1.2 Advanced Edition. We are encountering an issue with character encoding. The pages returned from the application server are not directly configured in utf-8. As a result, we see some uncorrect characters printed on screen (for example é instead of é). We need to select utf-8 manually to see characters like they should be and as they were before migration... Help would be appreciate. Vincent -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l. -- This is the Websphere Development Studio Client for iSeries (WDSCI-L) mailing list To post a message email: WDSCI-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/mailman/listinfo/wdsci-l or email: WDSCI-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at http://archive.midrange.com/wdsci-l.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.