language characters still not works in V1.5. Is that your server does not have uft8 support? Are you going to solve this problem?

The problem is not ours to solve - our server does support UTF-8. With v1.5. Try this... a) use your control panel to view the Core Data settings. Click the URL to see the data for your app b) Open your app and create a new plain text file in the BT_Config folder, name it mynewconfig.txt or anything you choose. c) Open the URL to the data (From your control panel)... copy this data to the configuration file you made in the previous step d) Open yourAppDelegeate.m and change the name of the configuration file name on line 34. The idea is to tell the app to use the file you just created and not the file at the URL e) In your new configuration file, remove the dataURL element - this will force your app to use your local file f) Edit this new configuration data and replace any characters you think are not displaying OK See if the characters you are using display ok? You may also have a look at the English file in the Localizable directory.

I will do it. I will post the solution here on the forum, if I find one. :)

Thanks. v1.5 is designed to allow you to SEE all the data and text and characters used in the configuration file - this should help you and us figure out where the issue is. It surely has something to do with the way the characters are pulled from the database and then added to the text file for configuration. Let us know.

I watch a bit of character, when I fill in a word with åäö characters so it looks ok in backend. But when I save it will åäö sign it will be à question mark. Copy this word ( böcker ) to a line in backend and save it, you will ser that ö characters will change after saveing. when I download the source code, then characters will be wrong all the way, from backend to source code. I hope you understand what I mean!

Yeah, we do understand what you mean. It sounds like you're going to be best off using a LOCAL configuration file instead of pulling all the data from the database everytime. This is why we provided the link to the Configuration Data in your control panel. The idea is that you could download this file (with it's messed up characters), over-write the problematic characters then add the file to your project. Then, in your app delegete.m, change the configuration file to the one you saved. Does this make any sense? The other way you could do it is the same as the first idea but instead, place the file on YOUR server, then change the dataURL in your proeject so the app pulls data form your server, not ours.

Ok thanks! I will try the different options in the week.

Hi David. I was wondering if it would work in Localizable.strings that one can add three special characters which I then translate to the åäö. $ = ö; I don´t use dollar signs so often. :) so when I write a text in the backend with a dollar sign so translated the character at all, where there is a dollar sign. Would this be possible?

Ongoing urgh.... Until we figure out how to successfully store AND retrieve your international characters you will continue to have issues - not sure where else to go with this. We will get to it eventually but it's likely to be awhile due to all the other goings on.

Thanks for any help. hope you solve it. Should you need a server in Europe to solve the problem so I can help you with that. I have a hosting company and we can set up a server here if it would help. We think BT is a super duber best CRM system for apps.

Hi David. Now, I have tried with a new config file. and I removed all dataurl elements. but it seems not work anyway. do you have any tips on what I can do?

At this point I don't have any tips. Let's start over again so I can get re-engaged with this problem (it's been awhile). a) What app b) What screen has the crazy characters? I'll review again and see if I can come up with a solution that doesn't require us to re-write anything ;-) There has to be a way!

look at http://www.buzztouch.com/forum/thread.php?tid=0FABD2074B7741E23B7A79B&status=&searchInput=search...&sortColumn=FT.dateStampUTC&sortUpDown=DESC¤tPage=1&doViews=1 I found a solution!