--- Log opened Fri Nov 14 00:00:36 2014
00:28 -!- redurgam is now known as magruder
03:44 -!- bzed_ [~bzed@devel.recluse.de] has joined #navit
03:46 -!- bzed [~bzed@devel.recluse.de] has quit [Ping timeout: 255 seconds]
03:46 -!- bzed_ is now known as bzed
04:30 -!- gringo [~gringo@unaffiliated/gringo] has quit [Ping timeout: 240 seconds]
05:35 -!- j_f-f [~quassel@orion2589.server4you.de] has quit [Remote host closed the connection]
05:38 -!- j_f-f [~quassel@orion2589.server4you.de] has joined #navit
05:53 -!- xenos1984 [~quassel@131-237-196-88.dyn.estpak.ee] has joined #navit
07:31 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has joined #navit
07:44 -!- drlizau [~liz@billiau.net] has joined #navit
08:02 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has joined #navit
08:06 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has joined #navit
08:29 -!- udovdh [~udovdh@pindarots.xs4all.nl] has joined #navit
09:03 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has joined #navit
09:03 -!- mode/#navit [+o KaZeR] by ChanServ
09:36 #navit: < Navit> kazer_ * r5939 /trunk/navit/po/fr.po.in: Update:Core:Updated French translation from launchpad http://sourceforge.net/p/navit/code/5939/
09:41 #navit: < Navit> kazer_ * r5940 /trunk/navit/po/af.po.in /trunk/navit/po/ar.po.in /trunk/navit/po/ast.po.in /trunk/navit/po/be.po.in /trunk/navit/po/bg.po.in /trunk/navit/po/bs.po.in /trunk/navit/po/ca.po.in /trunk/navit/po/ckb.po.in /trunk/navit/po/cs.po.in /trunk/navit/po/cy.po.in /trunk/navit/po/da.po.in /trunk/navit/po/de.po.in /trunk/navit/po/de_CH.po.in /trunk/navit/po/el.po.in /trunk/navit/po/en_AU.po.in /trunk/navit/po/en_CA.po.in /trunk/navit/po/en_GB.po.in /
09:41 #navit: < Navit> o/es.po.in /trunk/navit/po/et.po.in /trunk/navit/po/eu.po.in /trunk/navit/po/fa.po.in /trunk/navit/po/fi.po.in /trunk/navit/po/fil.po.in /trunk/navit/po/fo.po.in /trunk/navit/po/fr_CH.po.in /trunk/navit/po/fy.po.in /trunk/navit/po/gl.po.in /trunk/navit/po/he.po.in /trunk/navit/po/hi.po.in /trunk/navit/po/hr.po.in /trunk/navit/po/hu.po.in /trunk/navit/po/id.po.in /trunk/navit/po/it.po.in /trunk/navit/po/ja.po.in /trunk/navit/po/jv.po.in /trunk/navit/po
09:41 #navit: < Navit> unk/navit/po/ku.po.in /trunk/navit/po/lb.po.in /trunk/navit/po/lt.po.in /trunk/navit/po/lv.po.in /trunk/navit/po/mk.po.in /trunk/navit/po/mr.po.in /trunk/navit/po/nb.po.in /trunk/navit/po/nds.po.in /trunk/navit/po/nl.po.in /trunk/navit/po/nn.po.in /trunk/navit/po/pl.po.in /trunk/navit/po/pms.po.in /trunk/navit/po/pt.po.in /trunk/navit/po/pt_BR.po.in /trunk/navit/po/ro.po.in /trunk/navit/po/ru.po.in /trunk/navit/po/sc.po.in /trunk/navit/po/si.po.in /tr
09:41 #navit: < Navit> sl.po.in /trunk/navit/po/sr.po.in /trunk/navit/po/sv.po.in /trunk/navit/po/sw.po.in /trunk/navit/po/ta.po.in /trunk/navit/po/te.po.in /trunk/navit/po/th.po.in /trunk/navit/po/tr.po.in /trunk/navit/po/uk.po.in /trunk/navit/po/ur.po.in /trunk/navit/po/vi.po.in /trunk/navit/po/zh_CN.po.in /trunk/navit/po/zh_HK.po.in: Update:Core:massive translation update from launchpad to add new strings, fixed some headers http://sourceforge.net/p/navit/code/5940/
09:51 -!- woglinde [~henning@fb-n15-11.unbelievable-machine.net] has quit [Quit: zapp]
10:15 -!- udovdh [~udovdh@pindarots.xs4all.nl] has quit [Ping timeout: 250 seconds]
10:25 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
10:32 -!- udovdh [~udovdh@pindarots.xs4all.nl] has joined #navit
10:32 -!- udovdh [~udovdh@pindarots.xs4all.nl] has quit [Client Quit]
11:06 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection]
12:37 #navit: < Robotaxi> Hi jandegr,
12:48 #navit: < jandegr> hi robotaxi
12:48 #navit: < Robotaxi> I looked at your diff posted in #1082.
12:48 #navit: < Robotaxi> IMHO it's effective and simple.
12:49 #navit: < Robotaxi> There's just one point I would change in attr_def.h in order to keep the compatibility to existing official bin-files.
12:49 #navit: < jandegr> I will post a new one soon, also using the exit_to infor and fixes *_def.h
12:49 #navit: < jandegr> holdon...
12:50 #navit: < Robotaxi> Ah. that's ok.
12:51 #navit: < Robotaxi> I just have a proposal that you may have already build in in your next version:
12:51 #navit: < Robotaxi> If you insert the new items right in the middle of the 'type_string' block you push the existing string references back
12:51 #navit: < Robotaxi> and hence can't be accessed correctly any more. With this you must always create your own map.
12:52 #navit: < Robotaxi> I would add the items at the end right before ATTR2(0x0003ffff,type_string_end),
12:52 #navit: < Robotaxi> or use a block with the ATTR_UNUSED.
12:54 #navit: < jandegr> a sample with exit_to info http://www.openstreetmap.org/#map=19/49.03511/2.54104
12:56 #navit: < jandegr> or over here http://wiki.openstreetmap.org/wiki/File:High_Five.jpg
12:56 #navit: < Robotaxi> Hey, this pushes us forward!
12:56 #navit: < Robotaxi> It is one more info like the destination or even destination_sign.
12:56 #navit: < jandegr> I did a first testdirve on the High_five :)
12:57 #navit: < Robotaxi> How did you test it? Did you drive or simulate?
12:59 #navit: < Robotaxi> Oh, sorry, I got it.
12:59 #navit: < jandegr> uh, I did not take a plane in a hurry, use demovehicle :)
12:59 #navit: < Robotaxi> I looked at the picture afterwards...
13:00 #navit: < jandegr> as already said, will post latest version of maptool soon, and then we should agree on the attr. names I used
13:01 #navit: < jandegr> I put the real destination_sign on hold because (in random order) :
13:01 #navit: < jandegr> A) did not find a specimen on the OSM map yet
13:02 #navit: < jandegr> B) is still have an open order from kazer to announce "go left at the trafficlights", will cost a few hours too.
13:03 #navit: < jandegr> C) I can keep adding more info and new features, but by now I want to start working towards a usable version with what we have now, otherwise it will only remain all hypothetical
13:04 #navit: < Robotaxi> yes, cool. After migration I will invest some time to make a solid announcement concept. There is a bunch of ideas I have to sort by myself.
13:04 #navit: < jandegr> but if you come up with more usable info from OSM I will certainly look at it
13:06 #navit: < Robotaxi> And destinations in general are very complex if you want to integrate the direction info of OSM. Also lanes have it, which is very essential, btw.
13:08 #navit: < jandegr> I already have the most basic lanes info (number of lanes), this might be helpfull in deciding when or not to announce something, but the real lanes stuff is on hold as well, I have kind of an info overflow right now
13:08 #navit: < jandegr> meaning much more info available than we (navigation.c) can actually handle
13:09 #navit: < jandegr> but I allways try to ceep the code open for later extensions
13:10 #navit: < Robotaxi> just solid coding, right?
13:11 #navit: < Robotaxi> destination_sign is cool, but I will also not invest a line of code, before I don't really know how it's tagged.
13:13 #navit: < jandegr> I'll pull a diff of maptool now, will be up on #1082 later this afternoon so we can proceed
13:13 #navit: < Robotaxi> all right.
13:24 #navit: < jandegr> robotaxi the maptool diff is replaced with the new one, so no new attachemet, just replaced it with the same name, will make a post saying so on#1082 later.
13:36 #navit: < Robotaxi> jandegr at a glance it looks sound.
13:36 #navit: < Robotaxi> It's no problem for me to adapt my namings.
13:36 #navit: < jandegr> brb
13:40 #navit: < jandegr> I can provide you with a complete version of my navigation.c so you can start doing more than looking over my shoulder
13:42 #navit: < jandegr> you can pick the bits and pieces out of it that you need to actually use the new info, especially for the exit info, I take that from a node and place it on the ramp
13:43 #navit: < Robotaxi> Placing on a ramp was also my only idea I had with the current architecture.
13:45 #navit: < Robotaxi> Currently I made a long pause in changing navigation.c. I just start in these days to update my svn and merge with my personal version.
13:46 #navit: < Robotaxi> And, why not? I like to see your code. I can also provide mine, when updated.
13:50 #navit: < jandegr> may I suggest you update your code and chage the name of the destination (without    '_sign') and try it with the new maptool version, I have to fix a few things I just broke before I can send code.
13:52 #navit: < Robotaxi> That was also my idea. I will merge maptool and get it runnning and updated. :-)
14:23 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has joined #navit
14:23 -!- mode/#navit [+o KaZeR] by ChanServ
14:29 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has quit [Ping timeout: 265 seconds]
14:33 #navit: < jandegr> robotaxi still there ?
14:45 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has quit [Quit: Page closed]
16:02 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has joined #navit
16:07 -!- mvglasow [4d046fc3@gateway/web/freenode/ip.77.4.111.195] has joined #navit
16:45 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has joined #navit
16:45 -!- mode/#navit [+o KaZeR] by ChanServ
16:55 -!- Robotaxi [3ef5dbf5@gateway/web/freenode/ip.62.245.219.245] has quit [Ping timeout: 246 seconds]
17:38 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has joined #navit
17:44 #navit: < bafplus> hy guys
17:44 #navit: < jandegr> yo bafplus
17:46 #navit: < bafplus> noticed something strange today...when on a highway and there is an exit, navit send you "straight" but anounce as "turn right" with an arrow to left....
17:47 #navit: < bafplus> could this be i edited the xml to youre changes last week (without changing core)?
17:47 #navit: < bafplus> and a lot more bycicle paths are seen as road by navit and directs you into it
17:48 #navit: < jandegr> the last one is the fault of your vehicleprofile, and the first is a Navit-ism
17:49 #navit: < bafplus> the first one never happened before, and now about 6 times today...
17:50 #navit: < jandegr> navit send you "straight" is that draws a straight route on the screen ?
17:55 #navit: < jandegr> but in fact if you take the average of straight, left and right , the sum is straight so Navit is correct in some way :)
17:57 #navit: < bafplus> If the sum is straight why does it tell me to go right....
17:57 #navit: < bafplus> http://www.openstreetmap.org/#map=16/51.5786/4.7149
17:58 #navit: < bafplus> Driven from topright to bottemleft, navit draws a "straight" line on route, so thats correct, but announces it as "go right" (exit) and the OSD image is "left"
18:03 #navit: < jandegr> I don't need sample's bafplus, read log instead 15h39 http://irclogs.navit.ie/%23navit-2014-11-06.log
18:08 #navit: < bafplus> point noted ;-)
18:10 #navit: < bafplus> btw...is it "normal" that osm does have a lot of wrong classified roads? like bysicle path classified as road (car)?
18:10 #navit: < jandegr> and again 18h33 http://irclogs.navit.ie/%23navit-2014-11-08.log
18:12 #navit: < jandegr> and 18h52 of the 2014-11-08 as well
18:15 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has quit [Remote host closed the connection]
19:02 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has joined #navit
19:03 -!- mode/#navit [+o KaZeR] by ChanServ
19:11 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has left #navit []
19:14 -!- tryagain [~quassel@178.216.76.98] has joined #navit
19:20 -!- drlizau [~liz@billiau.net] has joined #navit
19:24 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has joined #navit
19:24 -!- jandegr [50c837be@gateway/web/freenode/ip.80.200.55.190] has quit [Client Quit]
19:26 #navit: < tryagain> KaZeR are you working right now on po files? I would attempt to fix them now unless you have some work in progress which could be broken.
19:27 #navit: < tryagain> http://trac.navit-project.org/ticket/1275
19:27 #navit: <@KaZeR> tryagain: i did a test build yesterday on my dev box which was successful after my last commit
19:27 #navit: <@KaZeR> mmm i don't recall hi failing here that's odd
19:28 #navit: < tryagain> it fails for me too
19:28 #navit: < tryagain> maybe some broken merge from launchpad?
19:29 #navit: <@KaZeR> let me double check. i have a script that should catch it
19:30 #navit: < tryagain> ok
19:33 #navit: < mvglasow> bafplus, I've followed your conversation with jandegr, I'm working on that piece of code at the moment
19:33 #navit: < mvglasow> in fact, the arrow and the spoken announcement are currently created in two different sections of the code
19:33 #navit: < mvglasow> and there's no guarantee that they match
19:34 #navit: < mvglasow> I'm trying to find a way to tackle that, so that they both agree
19:35 #navit: < mvglasow> so when we fix something regarding whether a maneuver should be announced as "left" or "right", we have to do so only in one place
19:45 -!- jandegr_ [50c837be@gateway/web/freenode/ip.80.200.55.190] has joined #navit
19:45 #navit: < bafplus> cool...strange thing is that it seems to happen more offten since my last build a few days ago...was there something commited regarding that?
19:47 #navit: < bafplus> KaZeR , i have few tracklogs...intrested?
19:47 #navit: < bafplus> afk for a while...
19:54 -!- drlizau [~liz@billiau.net] has quit [Remote host closed the connection]
19:56 #navit: < mvglasow> bafplus, I've made some improvements, but only regarding the decision whether to announce a maneuver or not
19:56 #navit: < mvglasow> I didn't touch the content of the announcements
19:57 #navit: < mvglasow> and the last commit that is not mine was in r5723 (some 200 commits and one year earlier)
19:57 #navit: < mvglasow> see http://sourceforge.net/p/navit/code/5943/log/?path=/trunk/navit/navit/navigation.c
19:59 #navit: < mvglasow> the only thing that I could think of is that the announcements in question didn't show at al before, so nobody noticed that the nav_next_turn OSD didn't agree with the verbal announcement
19:59 #navit: < tryagain> KaZeR for ru, please do s/msgstr[0] "чере%d милю"/msgstr[0] "через %d милю"/
20:00 #navit: <@KaZeR> ok tryagain
20:00 #navit: <@KaZeR> might have to go afk before finishing ( still trying to fix the script) but i'll finish today
20:02 #navit: < tryagain> ok
20:06 #navit:  * tryagain proud to announce a fresh map on our map servers
20:13 #navit: < jandegr_> congratulations with the new planet tryagain, have you found a way to make it repeatable on a regular basis ?
20:15 #navit: < tryagain> we will know it when it will repeat at least a few times :)
20:17 #navit: <@KaZeR> tryagain: haha :)
20:18 #navit: < Navit> kazer_ * r5944 /trunk/navit/po/hi.po.in: Fix:Core:Another attempt to fix hi plurals http://sourceforge.net/p/navit/code/5944/
20:18 #navit: < jandegr_> can anyone tell me the sense of map_convert_free() it contains one single instruction, g_free(str), what are the benifits here ?
20:19 #navit: <@KaZeR> tryagain: hopefully fixed both issues. will double check after food
20:19 #navit: < Navit> kazer_ * r5945 /trunk/navit/po/ru.po.in: Fix:Core:Fixed typo in ru|Thanks tryagain http://sourceforge.net/p/navit/code/5945/
20:19 -!- _rd [~rd@pD9E7DFE4.dip0.t-ipconnect.de] has joined #navit
20:26 #navit: < Navit> mdankov * r5946 /trunk/navit/po/ru.po.in: Fix:Core:Typo in ru http://sourceforge.net/p/navit/code/5946/
20:32 #navit: < mvglasow> can anyone tell me what the itm member of navigation_cmd refers to (in navigation.c)? is that the item just before the maneuver or the item right after the maneuver?
20:36 #navit: < mvglasow> I meant navigation_command, not navigation_cmd
20:39 #navit: < jandegr_> iirc it is the item you maneuver onto
20:55 #navit: < mvglasow> thx, just ran a test to confirm, which agrees with that
20:56 #navit: < mvglasow> but then something about robotaxi's patch for #694 is kind of strange... but I'll figure that out later
21:06 #navit: < jandegr_> mvglasow we can solve that right away in 10 minutes time, and IMVHO no single line of code in navigation.c should be worked on before it's fixed
21:07 #navit: < jandegr_> I mean #795 - 694 and a number of tickets alike
21:07 #navit: < mvglasow> #694/795 is what I'm currently working on
21:08 #navit: < jandegr_> this is too easy so nobody saw it in the last few years :)
21:09 #navit: < mvglasow> well... it took me some time to figure out which part of the logic is where... if you didn't write the code, it takes a while to find your way around
21:10 #navit: < mvglasow> at the moment I'm testing the patch robotaxi submitted for #694
21:10 #navit: < jandegr_> not this one, it's a schoolbook sample of a bug, think I'll have to send it in somewhere
21:10 #navit: < jandegr_> don't do it
21:11 #navit: < mvglasow> I'm beginning to realize something's wrog :-)
21:11 #navit: < mvglasow> in fact, there are a few other not-so-nice things in that code
21:12 #navit: < jandegr_> don't try the patch yet, it does not fix the real cause
21:12 #navit: < mvglasow> see my conversation with jandegr earlier
21:12 #navit: < jandegr_> only fight symptoms
21:12 #navit: < jandegr_> I am jandegr :)
21:13 #navit: < mvglasow> ah.. sorry, getting confused :-)
21:13 #navit: < jandegr_> holdon, open the current version of navigation.c and go to line ....
21:14 #navit: < mvglasow> I was thinking of adding a type member to navigation_command and setting it in command_new()
21:15 #navit: < mvglasow> to the correct type of maneuver, and use that both in show_maneuver() and navigation_map_get_item()
21:15 #navit: < jandegr_> goto line 1699
21:15 -!- _rd [~rd@pD9E7DFE4.dip0.t-ipconnect.de] has quit [Ping timeout: 272 seconds]
21:15 #navit: < jandegr_> and now a small quizz, al the silent ones can participate too :)
21:16 #navit: < mvglasow> ok, got it
21:16 #navit: < jandegr_> we enter there in line 1699 with a zero degree maneuver and who is the first who will tell me what navit will tell me to do ?
21:16 #navit: < mvglasow> TURN RIGHT :-)
21:16 #navit: < jandegr_> come on folks
21:17 #navit: < jandegr_> we have a winner :)
21:17 #navit: < mvglasow> that's another thing I was going to clean up
21:17 #navit: < jandegr_> mvglasow don't take me wrong, but you folks have been fighting symptoms instead of the cause
21:18 #navit: < jandegr_> and I have been shouting it here the last ten days
21:18 #navit: < mvglasow> jandegr I agree this piece of code needs a good rewrite
21:18 #navit: < jandegr_> +static int angle_straight = 6;	/* turns with -angle_straight <= delta <= angle_straight
21:19 #navit: < jandegr_> define on top , SPD and nice names !!
21:20 #navit: < mvglasow> I was working on a different end before and was going to tackle the content of announcements these days
21:21 -!- _rd [~rd@pD9E7DFE4.dip0.t-ipconnect.de] has joined #navit
21:21 #navit: < jandegr_> its the same problem with the choice of the osd icon's
21:21 #navit: < mvglasow> yep, that's on my list too :-)
21:22 #navit: < jandegr_> whats the use in refining the logic if Navit does what it wants with it ?
21:22 #navit: < jandegr_> -	const char *dir=_("right"),*strength="";
21:22 #navit: < jandegr_> +	const char *dir=_("straight"),*strength="";
21:22 #navit: < mvglasow> how about this: I'll develop a patch that fixes all these issues, share it and then we can discuss it
21:23 #navit: < mvglasow> right now, we have a mess of faulty logic and duplicate code
21:23 #navit: < jandegr_> no need, I have patch already for 2 weeks or so
21:23 #navit: < mvglasow> where can I find it?
21:23 #navit: < jandegr_> in my pc , lol
21:24 #navit: < jandegr_> it's 1200 lines (yes the patch)
21:25 #navit: < mvglasow> do you have SVN access?
21:27 #navit: < jandegr_> you did see I posted on #1265, or not ? the screenshot shows the patch at work :)
21:27 #navit: < jandegr_> back in 10
21:31 #navit: < mvglasow> cool :-) hadn't seen that update yet
21:36 #navit: < jandegr_> and this one shows it can actually be learned to go straight https://db.tt/EbdgCwfS
21:39 #navit: < mvglasow> :-)
21:40 #navit: < jandegr_> and check #1082
21:41 #navit: < mvglasow> good stuff
21:41 #navit: < jandegr_> I more or less agreed with robotaxi to do some major work on it, and silently hoping you would join in
21:42 #navit: < mvglasow> sure, I'm available :-)
21:43 #navit: < mvglasow> so how can I participate?
21:44 #navit: < jandegr_> first step is maptool, robotaxi gave his conscent on the patch I posted on #1082 but your opinion now counts too
21:49 #navit: < jandegr_> the link I gave redirects to a real url, and there you can browse from Capture3.jpg to Capture8.jpg to give some more samples
21:50 #navit: < jandegr_> and read today's irc log, was talking to robotaxi about is earlier, and also in the past few days.
21:51 #navit: < jandegr_> have to go for now , but I'll be in during the WE
21:51 -!- jandegr_ [50c837be@gateway/web/freenode/ip.80.200.55.190] has quit [Quit: Page closed]
22:01 -!- bafplus [~bafplus@5ED0A3EE.cm-7-1c.dynamic.ziggo.nl] has quit [Quit:  Want to be different? Try HydraIRC -> http://www.hydrairc.com <-]
22:23 -!- _rd [~rd@pD9E7DFE4.dip0.t-ipconnect.de] has quit [Ping timeout: 264 seconds]
23:14 -!- tryagain [~quassel@178.216.76.98] has quit [Remote host closed the connection]
23:24 -!- pini [~pini@bou-fi.pustule.org] has quit [Ping timeout: 244 seconds]
23:31 #navit: <@KaZeR> https://sourceforge.net/p/navit/code/1 -> navit will celebrate 9 years on sourceforge next week!
23:40 -!- xenos1984 [~quassel@131-237-196-88.dyn.estpak.ee] has quit [Remote host closed the connection]
23:54 -!- KaZeR [~KaZeR@c-174-62-70-239.hsd1.ca.comcast.net] has quit [Read error: Connection reset by peer]
--- Log closed Sat Nov 15 00:00:37 2014