Closed ctjacobs closed 8 years ago
Worked-around by 416497774711ea132965301d659ad16f482782f7. Any characters that can't be decoded when writing/reading from an ADIF file are replaced by a replacement marker. Not a great solution but I didn't really want to go down the "try to guess the character encoding from all the possible options" route as this may cause problems later on at the database level.
PyQSO fails to import ADIF records containing latin-1 characters (e.g. ä). The addition of new records may fail as well.
The patch below causes PyQSO to try and replace the latin-1 characters with UTF-8 ones. The ADIF records will then be added instead of being skipped. However, I think some characters may be lost that way. Supporting all the different character encoding schemes seems rather difficult - Anyone have any experience with this sort of thing?
Thanks to Timo OH7JHA for reporting this problem.