Questions related to RTF file encoding

[qwert]

I've worked quite a bit with rich text, but I've run into a problem that I can't get past.

When I write rich text from AutoIt, I can read back my content with no problem. But when I try to read an RTF file written by WordPad, I get a null buffer from the Open/Read/Close sequence.  (My files work fine with the same calls.)  I've tried various options on the file encoding parameter on FileOpen().

So I resorted to the GetFileEncoding() function in order to unravel the mystery.  But WordPad's file returns "1024", which isn't a published choice.

Quote

Success: the file encoding using similar values to the FileOpen() function:
    $FO_UTF16_LE (32) = UTF16 Little Endian.
    $FO_UTF16_BE (64) = UTF16 Big Endian.
    $FO_UTF8 (128) = UTF8 (with BOM).
    $FO_UTF8_NOBOM (256) = UTF8 (without BOM).
    $FO_ANSI (512) = ANSI (containing char > 127 and < 255)

To make matters more confusing, the files I write return encoding = 16 ... also not a listed choice.

Can anyone shed light on this?  Is there a common denominator encoding that WordPad uses that AutoIt can also write.

BTW, I'm working with the raw rich text syntax ("\par" and so on), so StreamToVar won't help in this instance.

Thanks in advance for any help.

 

[jchd]

You seem to be using or refering to an old AutoIt version or helpfile.

[Trong]

$FO_UTF16_LE_NOBOM (1024)

$FO_BINARY = 16 ;  binary 
 $FO_UNICODE or $FO_UTF16_LE = 32 ; Unicode UTF16 Little Endian
 $FO_UTF16_BE = 64 ; Unicode UTF16 Big Endian
 $FO_UTF8 = 128 ; Unicode UTF8 = with BOM
 $FO_UTF8_NOBOM = 256 ; Unicode UTF8 = without BOM
 $FO_ANSI = 512 ; ANSI
 $FO_UTF16_LE_NOBOM = 1024 ; Unicode UTF16 Little Endian = without BOM
 $FO_UTF16_BE_NOBOM = 2048 ; Unicode UTF16 Big Endian = without BOM

 

Edited July 19, 2017 by Trong

[qwert]

1 hour ago, jchd said:

You seem to be using or refering to an old AutoIt version or helpfile.

Good point.  It's true that my transfer of AutoIt (this year) to a new PC had some bobbles.  It looks like the help file was among them.

Thanks for the fresh list of the indicators.  Now that I see that WordPad is writing UTF-16, I'll see if it can be changed to UTF-8.  I think that's the common denominator I need.

 

 

[qwert]

My preliminary testing has revealed that, apparently, WordPad is encoding the file according to the font's character set.  Tahoma, for example, results in a file where encoding=16, while Calibri results in encoding=1024.  I can't follow the rhyme or reasoning behind these results.  It seems that Tahoma should result in either 256 or 512.

Regardless, I can now build RTF files with WordPad (using Arial or Tahoma) that are equivalent to the files I write from the script, itself.  Both report encoding=16 and both read properly with FileRead(), when using a FileOpen($buffer, 256).

For now, my issue is resolved.  Thanks for the help.