Re: A couple of filtering problems with CSV

Gavin Treadgold wrote:

> You've helped me indirectly solve one problem, and I think I've  
> further refined the second!

It's all part of my evil ploy to get you to do as much of the work
as possible. :-)

> from my perspective. Bad assumption of mine to be able to place  
> comments in the file.

Huh. I never really noticed that don't have any way to express comments
in that scheme, but we don't. As sure as we make '#' parse as a comment,
we'll get hammered by people that have waypoints named "waypoin #9" that
would become unhappy, so it's tempting to leave it as it is.


> For the second, I think I have refined it down to something choking  
> on unicode characters. When viewing the source in terminal, the  
> breaks appear to be occurring at <E2><80><99> - which appears to be a  

We have crazy code that tries to decompose special characters into the
most recognizable glyph available in the character set for any target
format.  For example, GPX is typically UTF-8 which can represent about
anything.    Our CSV formats are ASCII.   So something has to give.


> Command used was...
> 
> gpsbabel -i gpx -f source.gpx -i csv -f ignore.csv -x  
> duplicate,shortname,all -o gpx -F results1.gpx

That's what I'm looking for.   Discussion on -code in scant moments.


RJL


-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
Gpsbabel-misc@xxxxxxxxxxxxxxxxxxxxx
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc