Allow convert the contents of a text field (bidirectional): UTF-8 to UTF-16 (vice versa ... <-> ... )
- convertField ( < field > ; utf8_to_utf16)
- convertField ( < field > ; utf16_to_utf8)
ideal to b2b,... and others
What does this accomplish? As a feature of Export Records, being able to specify either UTF-8 or -16 has benefits others have described other places many times over. What do we get by doing it field-by-field or within the calculation dialog? My first instinct is that I'd rather not be thinking about the difference at all while working strictly within FileMaker.
agreed, within the Export, this would be more useful. However, within define fields, would this be helpful (not just UNICODE, but UTF-8 or UTF-16).
I need to communicate FMP, with two web services (xml).
I believe that creating an XML (full personalized) is extremely simple FM (via script, I like how simple it is). The code put it in a field and exported (simple and nice).
My only "risk" is that one (1 field) of the fields may contain character UTF-16 (all other fields are numerical). With that
I avoid using XSLT, export records, etc ...
For me,...the abundance ... not damaged.
Sorry my english
yes, and "conversion-in-field" may not be helpful if the Export dialog doesn't have greater capabilities.
Take a look at this simple XSLT for getting one-record-one-field "as-is":
Retrieving data ...