[mapguide-trac] #617: Utf8 support for Selection (attribute value display)

[MapGuide Open Source]

#617: Utf8 support for Selection (attribute value display)
------------------------+---------------------------------------------------
 Reporter:  poulet1212  |         Owner:  chrisclaydon
     Type:  defect      |        Status:  closed      
 Priority:  medium      |     Milestone:              
Component:  Fusion      |       Version:  2.0.1       
 Severity:  major       |    Resolution:  fixed       
 Keywords:              |   External_id:              
------------------------+---------------------------------------------------
Comment (by poulet1212):

 Hi pagameba,
 at a firat approach I would like to say that

 {{{
 utf8_decode($value);
 and
 htmlentities($value,ENT_COMPAT,'UTF-8');
 }}}
 do the same (only regarding the charset naturally).

 But, if we do not handle the charset directly when getting a String
 property from the FeatureReader, we must do that later.

 So, is it better to do that when getting the string from featurereader
 like proposed in this ticket or is it better to handle the charset later
 like in ticket 83?
 I think it would be fine to do that when getting the string from
 featurereader because other scripts might use this utility function.

 Regards

-- 
Ticket URL: <http://trac.osgeo.org/mapguide/ticket/617#comment:6>
MapGuide Open Source <http://mapguide.osgeo.org/>
MapGuide Open Source Internals