[texworks] Drop of Python scripting support

[Jonathan Kew]

On 2 Nov 2011, at 09:20, Philip TAYLOR (Webmaster, Ret'd) wrote:
> 
> Excellent, re-opened the Window and I now see :
> 
> This is XeTeX, Version 3.1415926-2.2-0.9997.4 (Web2C 2010)
> entering extended mode
> (./A3-Poster.tex [1]
> ** WARNING ** Profile size: 7261
> ** WARNING ** Invalid ICC profile header in "(null)"
> ** WARNING ** Profile size: 7261
> ** WARNING ** Invalid ICC profile header in "(null)"
> ** WARNING ** Profile size: 7261
> ** WARNING ** Invalid ICC profile header in "(null)"
> )
> Output written on A3-Poster.pdf (1 page).
> SyncTeX written on A3-Poster.synctex.gz
> Transcript written on A3-Poster.log.
> 
>> That I don't know. Maybe they're always generated, but the timing is such that you don't always see them before the console panel is hidden?
> 
> OK, I will try to prevent the window from self-hiding and repeat ...
> Yes, consistently present.  So, next question -- how might I best
> go about tracking down the cause of these ?

(This is now a xetex (or more accurately dvipdfmx) question, rather than a texworks one, but anyhow....) I'd suggest simplifying your document to identify the specific graphic(s) responsible, and then searching for information on validating the relevant kind of file (JPEG?), and in particular the embedded colour profiles. I have no specific suggestions to offer, but Google is your friend. :)

It may be that the files are actually correct, but (x)dvipdfmx doesn't know how to read them properly; or it may be that the colour profiles are invalid and hence get ignored. Of course, if accurate colour matching isn't an important aspect of your project, perhaps ignoring them is the simplest solution.

The "(null)" in your warning messages does look like a bug; it's probably supposed to print the filename there.

JK