1 Reply Latest reply on Sep 19, 2012 12:34 PM by disabled_ntaylor

    No UNICODE support for selecting radio buttons / value list

    jeutzsch

      Summary

      No UNICODE support for selecting radio buttons / value list

      Product

      FileMaker Pro

      Version

      12.0v2

      Operating system version

      Mac OS 10.7.4

      Description of the issue

      Non-standard unicode characters are treated as the standard characters they are based on (instead of the actual character they should be) when selected in a radio button field based on a value list.

      Steps to reproduce the problem

      A text field is created and designated 'unicode' for indexing.

      A value list is created for the data for this field containing non-standard (i.e., not English) characters. as an example:

      value 1: á
      value 2: a
      value 3: ä

      In a layout, data in the relevant field is displayed using radio buttons reflecting this value list:
      o á
      o a
      o ä

      Expected result

      when the user clicks 'á', the 'á' button is selected.
      when the user clicks 'a', the 'a' button is selected.
      when the user clicks 'ä', the 'ä' button is selected.

      Actual result

      when the user clicks 'á', the 'á' button is selected.

      when the user clicks 'a', the 'á' button is instead selected, being the first value in the list which is based on 'a'. It is thus impossible to select 'a' because FMP automatically chooses 'á'.

      when the user clicks 'ä', the 'á' button is instead selected, being the first value in the list which is based on 'a'. It is thus impossible to select 'ä' because FMP automatically chooses 'á'.

      Exact text of any error message(s) that appear

      (no error messages appear)

      Configuration information

      (nothing special concerning configuration)

      Workaround

      Currently using other combinations of standard characters to represent these non-standard (non-English) characters (such as aa for á, ae for ä), but that is not an elegant solution, plus it completely goes against the whole point of unicode support.

      unicodeSample.jpg