Menu
▾
▴
[Tm4j-developers] [ tm4j-Bugs-881422 ] TM4Web: display of special chars broken in main display
|
From: SourceForge.net <no...@so...> - 2004-08-17 15:32:33
|
Bugs item #881422, was opened at 2004-01-21 14:56 Message generated for change (Comment added) made by kal_ahmed You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=881422&group_id=27895 Category: TM4Web Group: TM4Web/Velocity 0.1 >Status: Closed >Resolution: Rejected Priority: 5 Submitted By: Nobody/Anonymous (nobody) Assigned to: Kal Ahmed (kal_ahmed) Summary: TM4Web: display of special chars broken in main display Initial Comment: hi, i am very impressed by the recent status of TMNav and TM4Web. thank you! here is a minor problem: TM4Web's display method for all topics on the main page seems broken (display works in topic.vm) in addition, TMNav displays topics only fine when (4) is used (äöü...). this behaviour does not seem to depend on using LTM char encoding headers (none = default, @"utf-8" or @"ISO-8859-1"). used versions: - tmnav-0.2.7a1-bin (alpha) - tm4web-velocity-bin-0.1-nodeps.zip my example topic: [Umlaute = "Umlaute_ä_œ_ Œ_Œ_œ_äöüß_ÄÖÜ"] i.e.: (1) ä (2) œ_ Œ (oe/OE lig) (3) Œ_œ (same) (4) äöüß_ÄÖÜ results: -------- TMNav: (4) ok TM4Web: Main page with all topics: none working (4) looks like UTF-8 viewed in ISO-8859-1 topic.vm: (1), (2), (3) ok alex -- Alexander Sigel, M.A. U Cologne, Dept. for Information Systems & Information Management si...@wi... http://wim.uni-koeln.de/ phone +49 221 470-5322 Pohligstr. 1, Room 406, 50969 Köln, GERMANY --- ---------------------------------------------------------------------- >Comment By: Kal Ahmed (kal_ahmed) Date: 2004-08-17 16:32 Message: Logged In: YES user_id=176992 Works OK with pages now generated as UTF-8 and carrying correct HTTP header (this may be dependent on the version of Tomcat too). ---------------------------------------------------------------------- Comment By: Kal Ahmed (kal_ahmed) Date: 2004-01-26 16:15 Message: Logged In: YES user_id=176992 All pages generated by TM4Web/Velocity should be UTF-8 encoded. I think this might be a Tomcat problem that you are seeing. You don't say which servlet container you are using, but Tomcat 4.1.29 does not set the HTTP headers specifying content encoding properly. I have found that everything is fine with Tomcat 4.1.27. Can you check this out and let me know if the problem is still there with the older version of Tomcat ? ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=391879&aid=881422&group_id=27895 |
