dmraid failure when array name contains spaces

(see #1262151 concerning the same issue with mdadm)

Ubuntu: saucy dmraid: 1.0.0.rc16-4.2ubuntu1

System: Acer S5-391
Contains two flash drives configured as (Intel) fakeraid. dmraid detects this array exists, and attempts to assemble it, but the resulting block device name contains an escaped space that makes them effectively unusable. The raid array contains a GPT-formatted disk, and boots with UEFI.

dmraid -s
*** Group superset isw_foobar
--> Subset
name : isw_foobar_Aspire S5-391
...

dmraid -ay produces devices named like
/dev/mapper/isw_foobar_Aspire\x20S5-391
/dev/mapper/isw_foobar_Aspire\x20S5-391p[1-6]

These block devices correctly map to the correct disk blocks (eg, mkfs.ext4 /dev/mapper/isw_foobar_Aspire\\x20S5-391p4 successfully creates a new filesystem), but anything that attempts to pass the names through appears to either fail to interpret the escapes or incorrectly splits the device into two arguments.

`gparted` started without argument refuses to read the device (/dev/mapper/isw_foobar_Aspire does not exist)
`gparted /dev/mapper/isw_foobar_Aspire\\x20S5-391` correct shows the partitions on the disk, but attempts to launch further tools (eg, create an ext4 filesystem in an existing partition), fails with non-existent device errors
`ubiquity` shows the partitions (providing `dmraid -ay` was run first), but similarly fails to actually create a filesystem or write anything into it

I was eventually able to install this system using `mdadm` to mount the disks and `debootstrap` to install the base system (since ubiquity will not work with md devices), but the experience was not at all fun. Consequently the extra information/logs I can provide is probably a bit limited as I'd rather not start messing around with the RAID again if I can possibly help it.