[DVIPDFMx] pdf:fstream not working

[Alexander Grahn]

Dear ChoF,

On Thu, Apr 28, 2011 at 09:24:10PM +0900, Jin-Hwan CHO wrote:
>You were right, Alexander. The version 20100328 (and xdvipdfmx too)
>had the problem.
>I tried the following code with the recent version of dvipdfmx but
>there were no error.
>
>text
>\special{pdf:fstream @obj1 (somefile.txt)}
>\special{pdf:ann bbox 0 0 10 10 <<
>  /Subtype /FileAttachment /FS <<
>    /Type /Filespec /F (somefile.txt)
>      /EF << /F @obj1 >> >>
>  /Name /PushPin >>}
>\bye
>
>Let me know if I can give you any help for your package.

I ran dvipdfmx-20110311 (TeXLive-2011) on your test file and the same
error

  [1
  ** WARNING ** Could not open file: somefile.txt
  ** WARNING ** Interpreting special command fstream (pdf:) failed.
  ** WARNING ** >> at page="1" position="(112.681, 759.927)" (in PDF)
  ** WARNING ** >> xxx "pdf:fstream @obj1 (somefile.txt)"
  ]
  ** WARNING ** Object @obj1 used, but not defined. Replaced by null.
  
and the unrelated but non-fatal
  
  ** WARNING ** 1 memory objects still allocated

still occur. The same result with XeTeX. Probably you tested a newer
(svn) version than the one marked for TeXLive-2011 inclusion.

Since there are no binary updates with TeXLive, do we have to wait another
year for this to be fixed? Or do you think it might be possible to put
a binary update in between?

Cheers,
Alexander

>
>Thanks, ChoF.
>
>P.S. Matthias, can you confirm my test?
>
>2011/4/26 Alexander Grahn <A.Grahn at hzdr.de>:
>> Hello,
>>
>> I'd like to use the pdf:fstream special of dvipdfmx (version
>> dvipdfmx-20100328), but I can't get it working. I always get the error
>>
>>  [1
>>  ** WARNING ** Could not open file: somefile.txt
>>  ** WARNING ** Interpreting special command fstream (pdf:) failed.
>>  ** WARNING ** >> at page="1" position="(112.681, 759.927)" (in PDF)
>>  ** WARNING ** >> xxx "pdf:fstream @obj1 (somefile.txt)"
>>  ]
>>  1779 bytes written
>>
>>  ** WARNING ** 1 memory objects still allocated
>>
>> when I try to process the dvi file generated from the minimal TeX file
>>
>>  text
>>  \special{pdf:fstream @obj1 (somefile.txt)}
>>  \bye
>>
>> The non-empty file `somefile.txt' resides in the same directory as the TeX
>> file and isn't opened by any another process. I am working under Linux.
>> Is there something wrong with my pdf:fstream usage?
>>
>> Alexander