Item5926: Topics with Chinese in UTF8 destroys page view in Internet Explorer

some topics in firefox and ie. are different.

like this:

• TechnicalShare1.txt: TechnicalShare1.txt

• TechnicalShare: TechnicalShare

-- TWiki:Main/AngelLi - 15 Aug 2008

This bug report is impossible to react on.

You attach a .swp file which is something I cannot even find a Google hit for.

And you attach some html files. We need to see the original topic and we need to see screen shots in a format we can see (gif, png, jpg).

We also need to know your settings. I can see that your html is full of utf8. Is this a Chinese topic in UTF8?

And what it is that is different? Most of us cannot read Chinese so you have to explain very detailed what the problem is.

-- TWiki:Main.KennethLavrsen - 15 Aug 2008

According to file TechnicalShare1.txt.swp, this is a VIM swap file (I'm not really a VIM user, so I don't see how this could be of use since ":rec"[over] doesn't work for me).

CfcnAngel, it would be helpful if you could upload the TML source as well (i.e., http://kbs4.asc.cnz.alimama.com/twiki/bin/view/Main/TechnicalShare?raw=all), because external access seems to be blocked.

-- TWiki:Main.MarkusUeberall - 16 Aug 2008

some bugs are repaired .

http://my.huhoo.net/archives/2008/08/twiki422bug.html

-- TWiki:Main.AngelLi - 18 Aug 2008

i use my Chinese topic in UTF-8 and the charset is utf-8, too.

this problem is depended on urlencode. some Chinese char should do this.

-- TWiki:Main.AngelLi - 18 Aug 2008

I do not know how to interpret the http://my.huhoo.net/archives/2008/08/twiki422bug.html. Is that supposed to be a patch?

Can you try and provide a more standard way to

• explain what the bug is solving
• provide a proper patch for proposed fixes or at least a clear explanation of what you have changed - here in this bug report. It is too much guessing otherwise and we risk introducing new bugs

-- TWiki:Main.KennethLavrsen - 19 Aug 2008

I provide old version files about 4.2.1 and my new patch files , there are some pictures about bugs for you.

• old.tar.gz: 4.2.1 version some source files

• new.tar.gz: my new source files

You can use order diff to compare the different and create the patch files. the patch solve some chinese or East Asia char strip some char, eg: '>', and so on.

• ie view:
  

• ie view:
  

• ie edit:
  

by the way: I register my account in twiki.org, like CnAngel, CfcnAngel and CfcfcnAngel, but i use to fail after some days. Why??? I report some bugs about twiki, and i can't use the account, like CnAngel, CfcnAngel and CfcfcnAngel, how can i do?

-- TWiki:Main.AngelLi - 21 Aug 2008

You also use diff order compare TechnicalShare from firefox and TechnicalShare1.txt in ie6, you can find some different areas. becase of firefox recognize character strongly, there is no out of shape. like this picture:

• firefox view:
  

• firefox view:
  

The patch files:

• patch.tar.bz2: patch files

-- TWiki:Main.AngelLi - 21 Aug 2008

Could you attach the RAW .txt file for TechnicalShare. Zip it first so no conversion happens. We need to have the raw source for the topic you view. Not the HTML file seen from your browser because we cannot even open it because it contains internal references that only work from your computer inside your firewall.

-- TWiki:Main.KennethLavrsen - 21 Aug 2008

You can look at http://www.jl607.com/twiki/bin/view/Main/New in ie6. how ugly!! You can download raw from http://my.huhoo.net/raw.txt

-- TWiki:Main.AngelLi - 21 Aug 2008

Please give me a account, i am tried.

-- TWiki:Main.AngelLi - 21 Aug 2008

I have confirmed the bug finally.

It could have been faster if we had known all the facts from the beginning.

• The TWiki must be running UTF8
• The topic must contain Chinese text with at least one heading with the text in Chinese

The result is that in IE only the entire layout of the left bar is goofed up and all fonts in the page become large. We are not talking that the two look different but the entire layout is garbage and useless.

I looked at the screen shots for a long time trying to see how the Chinese signs differed between IE and FF but this was not the problem. The entire IE layout is destroyed. The screenshots from IE are not zommed in. They look like this.

-- TWiki:Main.KennethLavrsen - 22 Aug 2008

I renamed the account renamed discussing it with Junliang to "AngelLi".

-- TWiki:Main.PeterThoeny - 25 Aug 2008

i successful report the bug finally. :))

-- TWiki:Main.AngelLi - 25 Aug 2008

I've tried, but I can't seem to get a valid utf-8 encoded test file from the raw.txt example.

Kenneth, you said you had reproduced the bug? I decoded Li's patch (against Foswiki 1150)

Index: lib/Foswiki.pm
===================================================================
--- lib/Foswiki.pm   (revision 1127)
+++ lib/Foswiki.pm   (working copy)
@@ -1149,7 +1149,7 @@
     my $anchor = '';
     while ( my $p = shift @args ) {
         if ( $p eq '#' ) {
-            $anchor .= '#' . shift(@args);
+            $anchor .= '#' . urlEncode( shift(@args) );
         }
         else {
             $ps .= ';' . $p . '=' . urlEncode( shift(@args) || '' );
Index: lib/Foswiki/Render.pm
===================================================================
--- lib/Foswiki/Render.pm   (revision 1120)
+++ lib/Foswiki/Render.pm   (working copy)
@@ -466,9 +466,10 @@
         $anchorName =~ s/[\s_]+$//;    # no trailing space, nor '_'
     }
 
-    # No need to encode 8-bit characters in anchor due to UTF-8 URL support
+    # There should be no need to encode 8-bit characters in anchor
+    # due to UTF-8 URL support. However encoding apparently cures Item5962
 
-    return $anchorName;
+    return Foswiki::urlEncode( $anchorName );
 }
 
 # dispose of the set of known unique anchornames in order to inhibit the

Can you try that, and if it cures the problem, check in? Thanks,

-- CrawfordCurrie - 03 Dec 2008

I cannot see the problem now either.

Need to test this at work on IE6. It can be an IE6 problem. I have gotten a new machine at home since this one and I do not have an IE6 here. That I need to do something about.

-- KennethLavrsen - 08 Dec 2008

I can confirm that I can reproduce the problem in TWiki 4.2.4 but not in our Foswiki code.

So the fix works

Waiting for release

-- KennethLavrsen - 10 Dec 2008