scripting:encoding

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision		 Previous revision
scripting:encoding [2014/02/09 01:50] – external edit 127.0.0.1scripting:encoding [2018/01/10 20:36] (current) – external edit 127.0.0.1
Line 1: Line 1:
 ====== Scripting Text Encoding ====== ====== Scripting Text Encoding ======
  
-Scripting functions in HippoEDIT (as internal functions of editor) always operate with Unicode (UTF-16 LE). +Scripting functions in HippoEDIT (as internal functions of the editor) always operate with Unicode (UTF-16 LE). 
-The original document encoding (code page) is only relevant during reading or saving of the document, when external file data is converted into internal HippoEDIT data.+The original document encoding (code page) is only relevant during reading or saving of the document when external file data is converted into internal HippoEDIT data.
  
 It is not possible to force scripting engine to use different code page rather than UTF-16.  It is not possible to force scripting engine to use different code page rather than UTF-16. 
  
 But: But:
-  * If you only want document to be saved in specific code page and reloaded correctly, you can set initial document encoding (before any text manipulation) by using property [[scripting:api:document:encoding|Document::Encoding]] or even better by passing right encoding when creating document. +  * If you only want a document to be saved in specific code page and reloaded correctly, you can set initial document encoding (before any text manipulation) by using property [[scripting:api:document:encoding|Document::Encoding]] or even better by passing right encoding when creating a document. 
-  * If you want to convert text from one encoding to another, you can change [[scripting:api:document:encoding|Document::Encoding]] even after text manipulation, but in this case, you can get data loss. Because text will be converted from initial encoding to new one, and this can lead to lose of some symbols not existing in destination code page.  +  * If you want to convert text from one encoding to another, you can change [[scripting:api:document:encoding|Document::Encoding]] even after text manipulation, but in this case, you can get data loss. Because text will be converted from initial encoding to new one, and this can lead to losing of some symbols not existing in destination code page.  
-  * If you want actually do conversion manually for some part of the text you can use [[scripting:api:application:wtoa|]] method. But this is not recommended, while only needed if you work with actually binary data...+  * If you want actually do the conversion manually for some part of the text you can use [[scripting:api:application:wtoa|]] method. But this is not recommended, while only needed if you work with actually binary data...