[Rock-dev] [rock] #395: Orogen: Non US-ASCII characters...

[rock]

#395: Orogen: Non US-ASCII characters...
---------------------+-----------------------------------
 Reporter:  mzenzes  |      Owner:  rock-dev-mailing-list
     Type:  defect   |     Status:  new
 Priority:  major    |  Milestone:
Component:  base     |   Keywords:  orogen,utf8
---------------------+-----------------------------------
 The 90ties are calling!

 Non ascii-characters in parsed header files will break typelib/orogen (not
 sure about the correct nomenclature here...).

 Putting a "µ" inside a header (for example) will break with a message like
 this:

 {{{
 ndlcom_bridge.orogen:10: cannot load one of the header files
 /home/mzenzes/TransTerrA/rock3/install/include/representations/ArmCommands.h,
 /home/mzenzes/TransTerrA/rock3/install/include/representations/Register.h,
 /home/mzenzes/TransTerrA/rock3/orogen-
 ndlcom_bridge/.orogen/typekit/types/ndlcom_bridge/ndlcom_bridgeTypes.hpp:
 invalid byte sequence in US-ASCII
 }}}

 Only the appropriate grepping (`grep -R --color='auto' -P -n "[\x80-\xFF]"
 ~/TransTerrA/rock3/install/include/representations/*`) will reveal the
 culprit: a single hidden µ. This broke on my system (Ubuntu 12.04), while
 Ajish (?) is fine.

 [http://stackoverflow.com/a/17031719 Putting] an `#encoding: UTF:8` in
 front of the orogen-script didn't help.

 According to the `orogen-ndlcom_bridge-orogen.log`, `$LANG` is set to `C`,
 magically even if the parent process has `export LANG=en_US.utf-8`...
 meh...

-- 
Ticket URL: <http://rock.opendfki.de/ticket/395>
rock <http://rock.opendfki.de>
rock: the robot construction kit