Using plugin (360Works ScriptMaster) may be simplest.
Or 'insert from URL' into container field. This get the content as is, so 'export field content' make a file as gbk.
If you want the file into a text field, you can make a folder and put the file into it, then 'import records from folder'.
user is correct. on FMPro, Export Field Contents become encoded as UTF-16 with BOM (byte-order-mark). There are alternatives to export to preserve the "as is". Export one field one record as tab-delimited, if and only if you don't have tab characters or return characters in the field.
Plug-ins are wonderful (several out there) at "exporting" (actually reading and writing) the field. As well as AppleScript and VBScript. These all preserve the exact characters in the field.
thank you user and forgive me for delaying reply~
I ve try the way that you shared~ but it does not work ~ i set the field html as a container~ i use insert from url~ and i get a html shotcut html in the field~ when i try to explore ~i found it can not explore container field~ then i set field html as a text field~ explore as a tab linedelimited encode as utf-8 then import again~ but found no exchangeing~ i fount the same result when encode as gbk or others~
Thank you for feplying~
~ i try the way that user share in this topic~but it dont work ~maybe it is not the problem of html encode~ oruse insert form url to get the result in the field can not be encode again~ but really apporciate for your reply~ thanks again~
When you get HTML in container field, you need to 'export field content'.(to newly created folder for further convinient)
Then 'import folder' as GB.
The exported file from container is GBK encoded, saying UTF-16 is when it from text field.
FM has only GB as import encoding, I'm not sure how this is differ from GBK.
If gb to Unicode conversion by fm isn't enough for your GBK page, try plugin.
The UTF-16 comes from "Export Field Contents" on FMPro.
0ddly enough, the same call on FMGo uses UTF-8