[XeTeX] Recent xdvipdfmx

[Jonathan Kew]

On 23 Jun 2006, at 1:03 pm, Akira Kakuto wrote:

> Hi Jonathan,
>
>>> Seems like on W32, either xdvipdfmx is doing something wrong when it
>>> reads the file, or else xetex is doing something wrong when it  
>>> writes
>>> the postamble; that would explain the difference between running
>>
>> Thanks. I think I had made mistakes in xetex rather than in  
>> xdvipdfmx,
>> because xdvipdfmx is ok for usual dvi files.
>> I'll try to fix the W32 bug this weekend.
>
> I've fixed the W32 bug.
> I hope the following change to be adopted in the
> original source.
>
> Thanks very much,
> Akira
>
>
> --- XeTeX_ext.c.orig	Tue Jun 20 23:23:46 2006
> +++ XeTeX_ext.c	Fri Jun 23 20:56:19 2006
> @@ -2051,7 +2051,7 @@
>  open_dvi_output(FILE** fptr)
>  {
> 	if (nopdfoutput) {
> -		return open_output(fptr, "w");
> +		return open_output(fptr, FOPEN_WBIN_MODE);
> 	}
> 	else {
> 		char*	cmd2 = concat(outputdriver, " -o \"");


Ah yes, another of those -- sorry, that's my careless non-Windows  
habits! I've checked-in the change.

(Note that I've also made a change today in xdvipdfmx to remove the  
risk of a "broken pipe" error, mentioned by Toralf Senger.)

Thanks,

JK