Non-ASCII not encoded correctly when assigned to db field as list

[Ed McDonagh]

The name Müller would be recorded correctly in PerformingPhysicianName for example. But the 'name' Müller\Smith would not be recorded correctly.

The issue seems to be that if we assign a MultiValue element to the database, it is entered as a python list and the characters are as they are passed, ie the above string would be encoded as: [u'M\xfcller', u'Smith'].

We therefore need to do one of two things:

1. break any multivalue person names into a new table and have an instance per name.
2. join the values together into a string.

Option 2 would be easy to implement and less disruptive!

[Ed McDonagh]

Created new list_to_string tool to join person name to make a string to ref #516. rdsr.py only for now.

→ <<cset 41163e88b993>>

[Ed McDonagh]

List_to_string for person name fields in ct_philips, dx and mam (except patient name). Refs #516

→ <<cset 2368acbc454b>>

[Ed McDonagh]

Added a single name and a multivalue name to the single source and dual source Flash test files. Added tests to make sure ref #516 works.

→ <<cset 762e7b2c9a3a>>

[Ed McDonagh]

Changes and CHANGES ref #516

→ <<cset 385c09db1a60>>

[Ed McDonagh]

Merged issue516nonASCIImultiValue into develop. Fixes #516

→ <<cset d25818c3aa2a>>

[Ed McDonagh]

@georgstamm - the presentation issue with the physician's names you brought to my attention should now be fixed. The example above should now appear as Müller | Smith.

This also improves the appearance of ASCII names too when they are MultiValue strings.