MartyConnelly
martyconnelly at shaw.ca
Thu May 10 19:12:00 CDT 2007
I can't see the code for the ASP page as an example "http://online.creativesystemdesigns.com/projects/programming3.asp?pcode=1,&position=1" So as far as I understand, one way is to encode your ASP documents as UTF-8 and indicate the encoding as the code page (UTF-8 is code page 65001 e.g. There are probably are other methods. Something like this <%@ Language="VBScript" CodePage="65001" %> <% Response.ContentType = "text/plain; charset=UTF-8" For Each Key In Request.Form Response.Write Key & "=" & Request.Form(Key) & VbCrLf Next Response.Write "Original request data: " & Request.Form & VbCrLf %> or maybe something like Response.ContentType = "text/xml" Response.CharSet = "UTF-8" oOutputDOM.save Response That way ASP will properly decode the data send as application/x-www-form-urlencoded; charset=UTF-8 automatically, there Jim Lawrence wrote: >Hi Marty: > >I do understand your comments about UTF encoding but I have not been able to >resolve the issue even though, on the surface, it would seem to be simple. > >See the following site, page and app sample and this will demonstrate the >issue that I am having and maybe the code will suggest a solution. It should >be straight-forward but I have just missed some small point: >http://online.creativesystemdesigns.com/projects/programming.asp > >TIA >Jim > >-----Original Message----- >From: accessd-bounces at databaseadvisors.com >[mailto:accessd-bounces at databaseadvisors.com] On Behalf Of MartyConnelly >Sent: Thursday, May 10, 2007 1:18 PM >To: Access Developers discussion and problem solving >Subject: Re: [AccessD] OT AJAX question > >I would have to see the Javascript that is doing this > >Generally this would be set in the encoding parameter of the XML >PI Processing instruction, there are about 30 of these some dependant >on the Windows codepage. SQL Server or Access punts it out in UTF-8 even >without >including a PI. There are ways to transliterate between encodings using ADO >streams. It can also be determined by the BOM marker at the start of >the file. > >In your case for Unicode encoding, you would want something like >this XML PI > ><?xml version="1.0" encoding="UTF-8"?> > >http://www.geocities.com/pmpg98_pt/CharacterEncoding.html >http://support.microsoft.com/kb/q275883/ > > >XML Encodings > >MSXML supports all encodings that are supported by Microsoft Internet >Explorer. >Internet Explorer's support depends on which language packs are installed >on the computer; this information is stored under the following registry >key: >HKEY_CLASSES_ROOT\MIME\Database\Charset > >xml example > ><?xml version="1.0" encoding="ISO-8859-1"?> ><character> > <chr>í</chr> ></character> ><!-- ISO-8859-1 encoded (Windows Code Page 1252?) --> ><!-- It must have the correct encoding declaration --> ><!-- The special char will display correctly on system that suport that >codepage --> > >Jim Lawrence wrote: > > > >>OT AJAX >> >>Hi all: >> >>This question is totally off-topic but the list members here have an >>incredible berth and depth of knowledge and I am sure someone will know or >>know where to look. >> >>For anyone here that has worked with AJAX/XML by default the information >>coming back from the server only supports 128 bit ASCII. That is great for >>straight English but any other single byte language, 256 bits is a minimum. >> >>Has anyone ran across a solution or knows where to find a solution? If so >>many thanks is advance. (...have researched a number of potential solutions >>but have been unable to either get them to work or have them fall-over with >>one client or another.) >> >>Jim >> >> >> >> >> > > > -- Marty Connelly Victoria, B.C. Canada