OpenGD77

I think I've fixed the lat/long values in the script now, seems like the CPS import wants dots and isn't too happy with commas. Please try again!

73 de SA0ASM

Sorry SA0BUX, that Lat/Long error may be a problem with the decimal precision output by my python script. Not related to this bug for sure!

73 de SA0ASM

This has nothing to do with the CSV import, we are just talking about the functionality of editing channel/contact names in the CPS UI. I understand if you don't want to support extended character sets, but it's a bit of a shame that the UI could be fully functional for the few extended characters t...

If this is the case, could you please replace "gb2312" with "latin1" in the CPS code so that the characters that happen to be supported by the firmware actually work in the CPS? Also, I believe the CSV import issue that SA0BUX is having is not related to character encoding but probably field delimet...

Thinking a bit more about your symptoms, it seems like you have a problem with the field delimeters in your CVS files. Are you sure you aren't using commas to separate fields and also as decimal point in your frequencies?

73 de SA0ASM

You shouldn't need to convert anything to ASCII, the firmware supports an extended latin characterset and the CSV files should contain UTF-8 encoded data for this to work. I don't know what problems you are having with the split frequency, the following CSV data imports fine for me: Channel Number,C...

Updating this thread to ask the CPS developers if it would be possible to implement the simple fix suggested by me previously.

73 de SA0ASM

@SA0BUX I don't think you understand, the "unusable" nature of the CPS is a bug in the CPS software UI, not of the CVS import. You can import correct labels and even edit the results in the CPS, but the CPS will always show the UTF-8 names garbled. Everything works fine in the radio though, once the...

Yes, this is a known issue in the OpenGD77 CPS. The label texts are converted to a chinese character set in the GUI, however importing UTF-8 from CSV works fine as you have witnessed. I have reported this bug here: https://www.opengd77.com/viewtopic.php?f=11&t=3625&p=28295 Please feel free to chime ...

Hej!

The curses module is actually not needed and you can remove the import statement.
Your other issue seem to be related to the file not being correctly detected as UTF-8 encoded, I'll see if that can be hinted to allow it to work on Windows.

73 de SA0ASM