Ah, I see.
The problem then is that your desired strings are in unicode rather than extended ASCII / UTF-8. The main issue with this is that unicode strings use 2 bytes per character and DBPro's strings only use single-byte characters. Therefore storing such strings would have you implement the entire range of needed string operations yourself.
As for writing a unicode text file, most text reading applications will interpret a .txt file as being in unicode if it begins with the special byte-order mark word (0xfeff) and so could yours when you are reading text files.
Edit: In line with the above, a text file will be interpreted as UTF-8 by writing the byte sequence
0xef 0xbb 0xbf as a header to the file.