[XeTeX] Low-level diagnostic ("fwrite") generated by XeTeX

[George N. White III]

On Tue, Feb 2, 2010 at 2:49 PM, Khaled Hosny <khaledhosny at eglug.org> wrote:

> On Wed, Feb 03, 2010 at 05:11:51AM +1100, Ross Moore wrote:
>> Hi Jonathan, and Phil,
>>
>> On 03/02/2010, at 4:46 AM, Jonathan Kew wrote:
>>
>> >
>> >On 2 Feb 2010, at 16:43, Philip TAYLOR wrote:
>> >
>> >>If the PDF file to which XeTeX is to write
>> >>is already open in Adobe Acrobat, XeTeX
>> >>terminates with a low-level diagnostic
>> >>concerning "fwrite" :
>>
>> Surely this is just a normal function of how the operating
>> system works, to maintain integrity of the file-system.
>> That is, preventing 2 different applications from the
>> possibility of making incompatible changes to the same file.

Some OS's do support read while write without corrupting
a file system, but you can have program A viewing an old version
of a file after program B has made a new version, so programs
on OS's that allow this need to check for changes and take
appropriate action such as loading the new file.

> Since, AFAIK, Adobe Reader doesn't change files (it is a reader not
> writer), it shouldn't lock the file in the first place. This what other
> document viewers (Evince here) does, actually it also recognize that the
> file has been updated and reload it.

Sometimes when a file is loaded in acroread you get a message that
the file is damaged and is being repaired -- does that change the file
on disk?

>
>
> Regards,
>  Khaled
>
>
> --
>  Khaled Hosny
>  Arabic localiser and member of Arabeyes.org team
>  Free font developer
>
>
> --------------------------------------------------
> Subscriptions, Archive, and List information, etc.:
>  http://tug.org/mailman/listinfo/xetex
>



-- 
George N. White III <aa056 at chebucto.ns.ca>
Head of St. Margarets Bay, Nova Scotia