|
|
2006-07-13
, 02:45
|
|
Posts: 114 |
Thanked: 11 times |
Joined on Oct 2005
|
#112
|
This is probably your problem. XML uses the UTF-8 encoding (by default - I think this can be changed). In order to support the ņ character (and other non-ASCII characters), you need to use multi-byte UTF-8-encoded characters. In UTF-8, the first waypoint in the file you uploaded actually looks like this:
The <f1> character is screwing up the parsing. You're better off using "Save As..." and moving the resulting file to the MMC. Otherwise, you should use an editor that supports UTF-8 and copy/paste with that.Code:Head northeast from Calle de Emilio Ortu<f1>o. Go 0.7 km.
Or, you can try adding encoding="latin1" to the "<?xml?>" tag, but I can't guarantee that that will work.
Or, you can just replace all the non-ASCII characters with ASCII characters.
|
|
2006-07-13
, 02:46
|
|
Posts: 112 |
Thanked: 6 times |
Joined on Feb 2006
|
#113
|
gnuite, I love how you worked out the new driver-orientation, with the line extending out. I had imagined this with a triangle, but after seeing the line, it's obviously more useful that way. Great job.
1 Gig Generic MMC, Sprint EV-DO for data(25-45 Kb/s d/l speeds), & Samsung A940: one GREAT phone!
|
|
2006-07-13
, 03:19
|
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#114
|
Adding the 'encoding="latin1" ' does nothing.
If I do "save as" (with firefox) from your webpage, what I get is the html code of the GPX Driving Directions page (!!!!)... not the directions xml file ... So, the only way to get this is to copy&paste the result.
If I select UTF-8 in firefox, the result is the same.
Those characters are generated by your gpx page, not me.
|
|
2006-07-13
, 03:30
|
|
|
Posts: 1,245 |
Thanked: 421 times |
Joined on Dec 2005
|
#115
|
Next. In your item list of enhancements you're going to work on, my idea for larger announcement popups, it states the reason for adding this is for ?people with bad eyes.? I have 20/20 vision, heh. Sometimes people have valid resons for requesting a feature that devs cannot predict, that's all. In this case, I installed the 12 Point Font themes. I believe the native 770 font is 16 Point, thus my popups are miniscule, even for my 20/20 vision. Hehehe.
I haven't gotten around to looking into the popup font size. I don't even know if it's possible to set the font size - it's not in the API so far as I've seen.1) Routing Alternatives. Sometimes, how Maemo Mapper computes the route seems a little off for my needs at that moment, and I would like an option to hold down the center button for 3-4 seconds and -blam!- it generates an alternative route based on different rules. If current routes are generated by rules like 'take the shortest path not deviating from major roads' then the alternate would gen routes based on rules like 'take the shortest path including dirt roads' heh.
2) Screensaver Mode
In this mode, when Fullscreen, the screen shuts off but the Bluetooth and cellphone connections stay active, waking up at each announcement popup... to save battery life on longer trips where you don't need yur route for a long time. So the screen's sleeping and waking are determined by the 'Advance Notice Settings.'


3) Automatic Destination Zooming?Autozoom? More of my time is spent fumbling for the zoom keys as I near my destination than anything, and I've noticed it's putting me at greater risk because my attention is focused on this process. I would like a mode where it automatically zooms in for you as you near your destination... I would be happy to drive-test the correct settings to help get them right, but I am guessing thus: a) at 8 blocks to 6 blocks, Autozoom to zoom level 2. b) at 3 to 5, Autozoom to level 1. Less than 3 blocks, Autozoom to level 0. This feature would improve overall safety, and just feel slick.
|
|
2006-07-13
, 07:59
|
|
|
Posts: 35 |
Thanked: 0 times |
Joined on Dec 2005
@ München
|
#116
|
Then why do you use the 12-point font theme?I haven't gotten around to looking into the popup font size. I don't even know if it's possible to set the font size - it's not in the API so far as I've seen.
|
|
2006-07-13
, 13:28
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Jul 2006
|
#117
|
The waypoint data is independent of the "kilometers/miles" setting. Maemo Mapper displays exactly what is in the GPX file (it doesn't try to convert units). The units used in the GPX file generally depend on the locale of the route source and/or destination (directions in the U.S. use miles; in Europe , kilometers; etc.). The source of directions hasn't changed in some time, so I'd be surprised if you entered the same source/destination and got km in v1.0.2 and miles in v1.1.
Originally Posted by hallax
2. the auto-update with routes does not seem to work. it did with 1.0.2
Odd - it worked for me in my testing. I'll try again.
You cannot auto-update a loaded route. You can only auto-update using "Download Route..." (i.e. not "Open Route...").
The amount of advance notice scales linearly with your current speed, which should be sufficient to provide sufficient notice in town and on the highway.
|
|
2006-07-13
, 13:32
|
|
Posts: 14 |
Thanked: 0 times |
Joined on Jul 2006
|
#118
|
There's already a feature request for auto-zooming based on speed. I've also considered an auto-zoom mode such that the nearest of either the last or next waypoints is forced to be visible. I'm lukewarm on both of these ideas, or anything that attempts to automatically control zoom level, but I'll probably experiment with it eventually.
|
|
2006-07-13
, 16:56
|
|
Posts: 114 |
Thanked: 11 times |
Joined on Oct 2005
|
#119
|
Yes, the UTF-8 characters are generated by my GPX page. Firefox understands UTF-8 (as do most browsers). Notepad or Wordpad, however, do not write UTF-8 by default, so if you copy from a UTF-8-understanding browser into a UTF-8-misunderstanding text editor, you will inadvertently be converting the UTF-8 characters into the "latin" character set, aka iso-8859-1, rendering the file invalid XML and unreadable by Maemo Mapper.
"Save as..." in my also-mozilla-based browser saves the XML, not the form page, so that must be a peculiarity of Firefox, so maybe you can try with IE or Opera.
If not: I don't use Windows much, so I haven't used any UTF-8-native text editors in it, but a simple google search led me to Notepad2 - try it and let me know if you still have problems. If so, message me and attach the file that Notepad2 created (yes, I cleaned out my ITT message box, so messaging me works again).
Sorry for the inconvenience. :-/
|
|
2006-07-13
, 17:11
|
|
Posts: 114 |
Thanked: 11 times |
Joined on Oct 2005
|
#120
|
...
I did some additional testing. This bug has something to do with regional settings of my 770. If I use "English / United Kingdom" as my reagion, the auto-update works. But if I use "Suomi (Finland)" it doesnīt work...
Ok. Could this be a feature? If I download a long route (from Finland to southern Europe for example) it might be nice to save the route. And then just open it every morning in a new location with Auto-update enabled. Iīm not sure if this actually would make any difference though. After POI functionality itīs so easy to calculate the route again...
Ok, I can live with this. ;-)
- Hallax
Or, you can try adding encoding="latin1" to the "<?xml?>" tag, but I can't guarantee that that will work.
Or, you can just replace all the non-ASCII characters with ASCII characters.