On Tue, 22 Jan 2013 14:50:02 +0000, Tim Newport-Peace wrote:


You might get more answers if you posted on Gliderpilot.Net, which is a
UK-specific group.

Basically, the reason you get a "goobly lump" is that in CUP files,
there is only one field for available for Description, but the BGA
Database has several field of Description, which are all concatenated
into one field in the CUP file, separated by commas.

I realize that's the reason that the displayed result is messy when the TP
file is fed to LK8000 or XCSoar: these programs treat the commas as just
another printable character and only line wrap at whitespace to prevent
words being split. What I'm trying to find out is if Jeff's TPSelect uses
commas as line delimiters because SYM, which I don't have a copy of, is
written treat commas as line delimiters. I've just mailed him as well
with the same question.

There is no mention of formatting very long descriptions in the "SeeYou
Waypoint file format description" on the naviter.com website, but as the
description can be arbitrarily long they must be using some form of line
wrapping, even in it is just 'start a newline every n characters'.

I'm only referring specifically to the BGA TP list because I know it
contains multi-line descriptions and that TPSelect injects commas at the
line breaks in its master file when its generating a CUP file: for CAI/
Winpilot output files it terminates the comment at the first linebreak.
The same considerations would apply to any other waypoint file that uses
the CUP file format.

I posted here because Naviter people sometimes read r.a.s and I don't
know whether the same applies to gliderpilot.net forums.


--
martin@ | Martin Gregorie
gregorie. | Essex, UK
org |