I am currently based in France and when I try and add a new section path which includes international characters such as: É è à ^à then an error is thrown. This is presumably because the URL does not support said characters... What would be the best method
to protect and validate against these types of inputs?
I have the same problem, as im fom Denmark with æ ø å. I had to put in some simulations like Spørg eksperterne -> Spoerg eksperterne. Its only visible in the breadcrump nav, i think, but it looks wrong.
I think the section path should be in plain english characters. That's why there are section path, section menu title and section title. If i am wrong, please correct me. Hope this help!
Yes but what seems to be happening is that it tries to encode characters that are not standard such as %20 being a space. But it is returning different characters. Surely this is not correct?
try putting in é as the section name (ctrl+alt+e) and when you roll over the link have a look in the status bar to see what I mean... you will then see what happens.
Yes, I have just try it. I think we have this problem since the CSK is in beta version. So, just avoid yourself to put international characters in the section name, use others english characters instead.
well the problem is not with me doing that, I build for my people here in Paris to share information and all of the keyboards here are not QWERTY! many people forget that not everyone speaks english in a global community. I suppose that a validation would be
in order to prevent special characters as anything goes at the moment. It should validate against the same rules as naming a folder but without the international characters.
Hi bentomkins, Thanks for using the Community Starter Kit! The CSK version 1.0 distinguishes between the Section Name (used for creating the path for a section) and the Section Menu Title (used for displaying the name of a section). You can't use special characters
in the section name -- such as the pound sign #, international characters, etc -- because browsers won't correctly interpret these characters when used in a URL. However, you can use these characters for the Section Menu Title. This isn't an issue unique to
the Community Starter Kit. If you create a folder named c#code and place a file named Default.aspx in that folder, then you won't be able to open the Default.aspx page in a browser. The browser will get confused because of the pound sign # in the folder name
c#code. Stephen Walther
bentomkins
Member
180 Points
36 Posts
International Characters
Jul 05, 2003 03:45 PM|LINK
para7
Participant
1925 Points
385 Posts
Re: International Characters
Jul 08, 2003 03:55 PM|LINK
bentomkins
Member
180 Points
36 Posts
Re: International Characters
Jul 08, 2003 04:18 PM|LINK
kkw
Member
645 Points
129 Posts
Re: International Characters
Jul 08, 2003 07:32 PM|LINK
GotCommunityNet
bentomkins
Member
180 Points
36 Posts
Re: International Characters
Jul 08, 2003 07:36 PM|LINK
kkw
Member
645 Points
129 Posts
Re: International Characters
Jul 09, 2003 05:39 PM|LINK
GotCommunityNet
bentomkins
Member
180 Points
36 Posts
Re: International Characters
Jul 09, 2003 05:41 PM|LINK
kkw
Member
645 Points
129 Posts
Re: International Characters
Jul 09, 2003 05:57 PM|LINK
GotCommunityNet
bentomkins
Member
180 Points
36 Posts
Re: International Characters
Jul 09, 2003 06:11 PM|LINK
swalther
Participant
887 Points
180 Posts
Microsoft
Re: International Characters
Jul 09, 2003 07:33 PM|LINK