Hungarian

[Robert Brenstein]

>  >I think only Unicode can resolve all such problems.
>>Btw, how you keep hungarian strings in the Access ?
>>It have some encoding parameters?
>
>the hungarian field doesn't have "unicode compression" if it's the
>question...
>I try with unicode compression enable...
>
>>>  of course the best solution will be a "working" version of ODBC_Valentina
>>>  but you aren't the one behind it, no ?
>>Why you not try old/good ASCII import/export?
>
>because my char (o) disappears in ascii, no ?
>
>WilG
>

If you don't use unicode, then your hungarian chars will appear bogus 
(incorrect) when opened in a text editor but when you apply the 
correct font, they should reappear correctly (the same happens in MS 
Word for example). So, ascii import should work per se. If the 
character encoding is not correct to produce the results in your end 
program, you may need to massage the ascii codes (I mean replace them 
with appropriate ones). You can do this as an intermediate step 
before importing into Valentina or after the import.

Robert