jcompagner:
the content type should be already UTF-8
isnt that the case?
Do you have a sample where it doesn’t display the german chars correctly?
Hi Johan,
Normally I expect the default to be set to UTF-8, however, there’s no way of telling if that is the case - I can’t see it in the browser’s ‘View page source’.
Is there a way to enforce that if it is not showing? Might be helpful, as we are experimenting with content from different geographical location.
If not, what would be a best practice to ensure that a particular character encoding in ensured at the client side?
then you see what is selected, and for servoy you should see a bullet behind Unicode (UTF-8)
I’m using Firefox ver. 2.0.0.12.
Point of clarification: I mean Content-Type setting in a client’s tag. If you’d right-mouse click this forum’s page for instance, and choose option ‘View Source’ in IE or ‘View Page Source’ in Firefox, you’d probably find a meta tag Content-Type setting of the manner => charset=iso-8859-1. Is that right?.
What would then be a best practice to ensure that a particular character encoding in ensured at the client side? I have started with some German characters and I’m getting some wird results, here and there.
jcompagner:
Do you see them correctly in the smart client?
Because as i said the Servoy Webclient is all UTF-8 so it should be able to handle and display everything correctly.
Viewing/Running the solution under Servoy Smartclient doesn’t help either.
It appears to some extent, to be a database issue, specifically, the customers tables that was shipped with my version of Servoy - It produces some wird characters under Servoy as well as when it is viewed under Sybase Central. (ver. 5.0.0.3278)
Has anybody experience any such strange behavior? Is/Are there some tunning(s)/adjustment(s) that have to be done somewhere? Or maybe it’s a Servoy issue? I’m just curious