Cgpsmapper lower case display bug

[Boyd]

I tried to find a solution for this a year ago and struck out. Just now finishing up a new project and I see that the same problem still exists. Any thoughts on this?

I am using TIGER road data in my map and everything looks great on my Oregon and 3 different models of Nuvi. However, on the 60csx, mixed case street names are not properly displayed. POI's and other map items are displayed correctly, but not street names. For example, let's say that a street is named "Jones Rd". This is how the name will appear on the Nuvi and Oregon. But on the 60csx, the first (capital) letter of each word is displayed, and dashes are then displayed in place of the lowercase characters. So, using this example, the 60csx would label this street as "J---- R-".

This is very strange... Garmin's own maps display mixed case names correctly and the same map compiled with Mapwel displays correctly with mixed case on the 60csx. So I have to conclude this is a cgpsmapper bug. I am running the current shareware version (97c).

I don't think I'm doing anything strange, just using the TIGER names without modification. My source file is built with Globalmapper and exported as .mp for compilation in cgpsmapper. In the past, I made a separate version of the map and converted all the names to UPPER CASE, which works correctly in cgpsmapper. But honestly, I'm not willing to go to all that trouble anymore and don't want to maintain two separate copies of the same map.

Unless there's some simple work-around, I guess I just won't support these older units anymore. It seems ridiculous that something this basic doesn't work. I mean, I'm old enough to remember writing FORTRAN programs on an ASR-33 teletype with UPPERCASE, but most software has progressed beyond that during the last 40 years! 

[maps4gps]

Ditto for the 76csx.  This time around I converted to all caps - that was before I got an Oregon300.  I suppose what displays well on the older units will not do so on the CO/OR/DKs.
Found some line features which were black on the older units, but display 'white' on the newer.  If you use a 'white' background' on the OR, these and those polygon features which are 'white' are not visible.  Seems it is becomming standard for designers/programs not to observe the results of what they create.

After I had combined the Census files into larger quads, I used dBase to replace the name field with upper(name). 

On my US Planimetric - xxxxx mapsets, I am seeing initial upper then lower case on both the 76csx and Oregon300.  The issue I have is that names that should be all upper case are also so displayed, i.e. NYC would display Nyc, or UPRR > Uprr.

[Boyd]

But Mapwel works as expected on both the old and new units. Cgpsmapper needs to catch up...

[Boyd]

I think it's doing auto capitalization where every word begins with a cap and continues as lowercase until whitespace. Seems to me that I've read about that bug before as well.

[Boyd]

Yes, I think the GPS is interpreting the text this way. But it may have something to do with the format which cgpsmapper uses, because Garmin's own maps seem to be fine and Mapwel maps also seem to be fine.

BTW - how did my comments end up before your post? 

[Boyd]

Aha, I see. So much for my time warp theory then. 

[Boyd]

Well, in the process of mapping the New Jersey Barrens, one day I wandered into Ong's Hat... http://deoxy.org/irc/index.htm