Project

General

Profile

Actions

Bug #975

closed

Importing from CSV -> PX-777 loses special characters in channel name

Added by Chris Kantarjiev over 11 years ago. Updated over 11 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
Category:
-
Target version:
-
Start date:
07/13/2013
Due date:
% Done:

0%

Estimated time:
Chirp Version:
daily
Model affected:
PX-777
Platform:
Windows
Debug Log:
I read the instructions above:

Description

I imported a channel from a CSV file:

1,HAM-A,147.4650,0.0000,100,100,23,NN,NFM,5

and the resulting channel, when imported into the PX-777 window, is called "HAMA" - no hypen.


Related issues 1 (0 open1 closed)

Is duplicate of Bug #364: Incomplete charset px777ClosedTom Hayward12/16/2012

Actions
Actions #1

Updated by Chris Kantarjiev over 11 years ago

This appears not to be an import problem, but with the PX-777 formatted panel itself - I can't type in a channel name with a hyphen and have it stick.

Actions #2

Updated by Tom Hayward over 11 years ago

  • Status changed from New to Rejected
  • Assignee set to Tom Hayward

This is a dupe of #364.

I've got a fix for #364, but I haven't tested it. Maybe you'd like to test it for me?

Actions #3

Updated by Chris Kantarjiev over 11 years ago

I'd be happy to help test your fix. How do we proceed?

Actions #4

Updated by Chris Kantarjiev over 11 years ago

While I'm thinking about labels ... it appears that CHIRP doesn't always fully overwrite the existing labels on channels; I moved some things around and got extra characters where I had intended white space (typically at the end). I had to fix it with the Puxing software, typically by adding at least one space into the UI.

Actions #5

Updated by Tom Hayward over 11 years ago

I looked into it further... I tested and submitted this fix in December but it got missed somehow. So no need to test again.

Chris Kantarjiev wrote:

While I'm thinking about labels ... it appears that CHIRP doesn't always fully overwrite the existing labels on channels; I moved some things around and got extra characters where I had intended white space (typically at the end). I had to fix it with the Puxing software, typically by adding at least one space into the UI.

That sounds like a different unrelated bug.

Actions #6

Updated by Chris Kantarjiev over 11 years ago

I look forward to seeing this fix in a new build; when I get it, I'll try to reproduce the other bug and submit.

Actions

Also available in: Atom PDF