NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: RichBowman on March 12, 2012, 12:45:55 PM
-
The degree symbol can be entered by typing Alt+0176. This works fine in my Win32 apps but my NT app can not display the record with this symbol. How can I handle this? I do not need input capability, just display.
Thank you,
Rich
-
The HTML code for the degree symbol is °
Give that a try and see if it works for you.
-
I don't think I explained my question well. The degree symbol is embedded in a field in the database. My Browse will not display a record that has that symbol in a field on the Browse. In fact, once the parent record is displayed, the parent Browse will not even do a Next. Is there a setting in NT that will allow this record to display?
Thank you,
Rich
-
Have you ticked allow xhtml for that column?
-
what settings have you set for "charset" and "save as" on the webserver procedure, advanced tab?
cheers
Bruce
-
"Allow xhtml" is checked for that column. Both Charset and Save As in the WebServer procedure are utf-8. I should mention that I actually display a local variable. It is 2 string fields concatenated like this (so I get a 2 line row):
LineDescription = OED:LineDescription & '<br />' & OED:LineDescription2
This is on a parent / child browse form. When a parent is displayed with a child record that has the degree symbol, the child records do not display and clicking next or previous on the parent browse does not display a new set of records.
Thank you,
Rich
-
xhtml is very strict. what i see is that the you result as xhtml is wrong and it is not displayed because of that.
-
Once you build your LineDescription try to scan for ascii value <176> and do a replace with °
If you use Firebug you can see the XML errors
-
>> Both Charset and Save As in the WebServer procedure are utf-8.
you've told the server you have your data stored as utf-8, but in practice you haven't stored the data as utf-8. This is, I think, perhaps the root of your problem.
If you change to "save as Ascii" you will probably have better success.
cheers
Bruce
-
Changing the "Save as" character set to ASCII worked.
Thank you,
Rich