Hi, Le 4 mai 2009, Tal a écrit : > Number 1 is indeed a problem, but it is solved by removing the magic > number check for *.gpx files.
Yes, that is a better way to handle gpx files than the one currently used. > Number 2 is not a problem. The file is parsed in gpx.c using the xml > library expat, which is responsible for most of the xml related > headaches, including proper character encoding and decoding for > utf-8, utf-16, etc. gpx.c reads bytes, feeds them to expat, and gets > back parsed and re-encoded utf-8 strings. I didn't know that expat library handled the utf-16 encoding directly. In this case, I have no objection :) I remember in my trials that the utf-16 gpx file was not correctly read by the xml parsing, but it might be because I removed the BOM marker before sending the string to libexpat. I will do a trial next week. Can you send me an utf-16 encoded file so I can understand what I did wrong ? Thanks, Jocelyn ------------------------------------------------------------------------------ Register Now & Save for Velocity, the Web Performance & Operations Conference from O'Reilly Media. Velocity features a full day of expert-led, hands-on workshops and two days of sessions from industry leaders in dedicated Performance & Operations tracks. Use code vel09scf and Save an extra 15% before 5/3. http://p.sf.net/sfu/velocityconf _______________________________________________ Viking-devel mailing list Viking-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/viking-devel Viking home page: http://viking.sf.net/
