Add speak-en-jp to switch language by speak_language rosparam and add test codes.

[snozawa]

Add new feature for speak.l.

I'd like to switch speak-en and speak-jp online: (demos for japanese guests and english guests).
I added speak-en-jp function and usage is:

(speak-en-jp "Hello world" "こんにちわ")

We need to write both japanese and english in speaking codes.
We can switch language by changing speak_language ros param.

Currently this is used in hrp2 73B2 demo and I copied the function into pr2eus.

[k-okada]

1. better to use `&rest args'
2. consider Chinese support, https://github.com/jsk-ros-pkg/jsk_robot/blob/master/jsk_naoqi_robot/jsk_201504_miraikan/euslisp/mirai-demo-20150413.l#L32 can be written with this feature, how about (speak "Hello"), (speak "こんにちは"), (spaak '(("en" . "Hello") ("jp" . "こんにちは") （”zn-CN" . "你好")
3. better to have function that if we call (speak "hello"), but speak_language is "jp", then we use speak-google to speak in Japanese

[snozawa]

Thanks!

better to use `&rest args'

I re-write the code to use &rest args.

consider Chinese support, https://github.com/jsk-ros-pkg/jsk_robot/blob/master/jsk_naoqi_robot/jsk_201504_miraikan/euslisp/mirai-demo-20150413.l#L32 can be written with this feature, how about (speak "Hello"), (speak "こんにちは"), (spaak '(("en" . "Hello") ("jp" . "こんにちは") （”zn-CN" . "你好")

Thats nice idea!
I re-write the code to support (spaak '(("en" . "Hello") ("jp" . "こんにちは") （”zn-CN" . "你好")) style and (speak "Heloo") style.

better to have function that if we call (speak "hello"), but speak_language is "jp", then we use speak-google to speak in Japanese

If adequate speech string is specified from arguments, use speak-google.

[k-okada]

for me, using intern seems suitable for this case.

12.eusgl$ (functionp (intern "SPEAK-JP"))
t
13.eusgl$ (functionp (intern "SPEAK-CN"))
nil
14.eusgl$ (functionp (intern "SPEAK-EN"))
t

[pazeshun]

This comment is reflected on #383

[k-okada]

if you can not find speak-func, use google, this is why we choose "en" instead of "english"

[pazeshun]

This comment is reflected on #383

[pazeshun]

@k-okada
This PR is moved to #383 and is being improved by @iory .
I think we can close this and release 0.3.14, unless you think #383 is required for 0.3.14.