Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Zdenek Wagner wrote: > In the very same way as TeX is called. It has to start a shell (cmd.exe > in Windows) and ask it to start the lua interpreter and execute the lua > script. If you want to analyze the log file immediatelly, I would write > a lua script that would run tex, then looked into

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

2016-03-13 18:34 GMT+01:00 Philip Taylor : > > > Zdenek Wagner wrote: > > > In MS-DOS, Windows, and OS/2 the script interpreter is recognized by a > > file extension. > > Er, yes; but does that help ? Does that in any way allow (say) TeXworks > to use a script written in

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Zdenek Wagner wrote: > In MS-DOS, Windows, and OS/2 the script interpreter is recognized by a > file extension. Er, yes; but does that help ? Does that in any way allow (say) TeXworks to use a script written in Lua, if its own internal scripting language is other than Lua ?

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

msk...@ansuz.sooke.bc.ca wrote: > If a script begins with the characters "#!" and the name of a script > interpreter, and has the execute bit set, then it can be executed like any > other program, and the front end can run it the same way the front end > would run any TeX engine. This is a

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On Sun, 13 Mar 2016, Philip Taylor wrote: > > Nowadays all TeX distros have lua. > > The fact that a distribution may have (and include) a particular > scripting language does not mean that a front-end such as TeXworks can > necessarily make use of scripts expressed in that language, surely ? It

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Zdenek Wagner wrote: > Then there would need to be a further extension that would allow any > package to signal a warning which could be handled in the same way. > > > In other words, a new TeX primitive will have to be added. Yes, that is what I meant by "a further extension". >

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

2016-03-13 17:41 GMT+01:00 Philip Taylor : > > > Julian Bradfield wrote: > > > Do you have a full list of all possible now-and-future events that > > you might want to flag this way? > > Yes. Anything/everything for which TeX issues a warning, either to the > log file or to

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Julian Bradfield wrote: > Do you have a full list of all possible now-and-future events that > you might want to flag this way? Yes. Anything/everything for which TeX issues a warning, either to the log file or to the console or both. The TeX source code is so modular and so well structured

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

I hav tried the log from a book having 512 pages. It still contains a lot of underful boxes. The log is not short because the book has 70 chapters, each in a separate file, and altogether about 80 pictures. The log contains the names af all files with chapters, all LaTeX packages, each chapter

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 2016-03-13, Philip Taylor wrote: > I respectfully disagree. I am advocating the philosophically correct > approach, requiring a small amount of work by a small number of people > -- those responsible for eTeX, PdfTeX and XeTeX : I assume that LuaTeX > can already handle

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Julian Bradfield wrote: > You are living 30 years ago. Today (or even 10 years ago), grepping a > log file for specified text consumes an unnoticeable amount of time > for any log file generated by a non-pathological TeX run, and it > allows TeXworks' problems to be solved by TeXworks, as they

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 2016-03-13, Philip Taylor wrote: > Yes, it is the "inspecting the log file" that I am trying to avoid, in > the interests of efficiency; an inspection of the log file should be > required (as it currently is) only if the status code returned by *TeX > is non-zero. You are

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Wilfred van Rooijen wrote: > It seems that the source code from TeXworks is available, so it should > be possible to add a feature to "turn overfull boxes into some sort of > error but not quite". You'd have to talk to the TeXworks people. Only by inspecting the log file; please see below. >

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Wilfred van Rooijen wrote: > Anyway, isn't there some kind of setting in TeXworks for this? Not at the moment. > Or is there perhaps a command line option for latex "turn warnings > into errors", like with gcc? Also not at the moment, but that is essentially what I am requesting, except that

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Dear Wilfred -- > I haven't followed the discussion in detail, but IMHO it would be > nonsense to turn overfull boxes into errors, because they are not > errors, rather the line breaking algorithm could not find a proper way > to fix things differently. I am happy to accept that, for some,

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

I haven't followed the discussion in detail, but IMHO it would be nonsense to turn overfull boxes into errors, because they are not errors, rather the line breaking algorithm could not find a proper way to fix things differently. Remember, there is always the "draft" mode which will clearly show

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Zdenek Wagner wrote: > This is not even mentioned on the console, the user must read the log > file. Overfull boxes make the output at least readable, missing > characters present a serious problem. No, they can both render the output meaningless, particularly when the overfull box

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

There is a more dangerous problem which returns with a zero code, namely missing characters. Try this XeLaTeX code: \documentclass{article} \usepackage{fontspec,bidi} \setmainfont[Script=Arabic]{FreeSans} \begin{document} \beginR مجھے \endR \end{document} This is not even mentioned on the

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On Sun, 13 Mar 2016, Philip Taylor wrote: > that no error has occurred. All I am asking is that XeTeX be given the > option to inform TeXworks that an error has occurred when an overfull > box has been generated. Why is this a XeTeX issue and not a TeXworks issue? -- Matthew Skala

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 13 March 2016 at 10:14, Philip Taylor wrote: > > > David Carlisle wrote: > >> Philip Taylor wrote: > >>> Also please consider the following text from Wikipædia : >> (Well from Wikipedia actually) >> >> Yes the relevant part is >> >>> On many systems,

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

David Carlisle wrote: > Philip Taylor wrote: >> Also please consider the following text from Wikipædia : > (Well from Wikipedia actually) > > Yes the relevant part is > >> On many systems, the higher the value, the more severe the >> cause of the error. > > so the

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On 13 March 2016 at 09:43, Philip Taylor wrote: > Also please consider the following text from Wikipædia : (Well from Wikipedia actually) Yes the relevant part is > On many systems, the higher the value, the more severe the > cause of the error. so the status code should

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Such a change will break a lot of build tools. If overful boxes were reported as errors, the full build will be unsuccessful. In early stages of devewlopment I am concerned with functionality of macros or wich communication between several pieces of software, not with the beauty. Overful boxes

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

Also please consider the following text from Wikipædia : > The parent and the child can have an understanding about the meaning > of the exit statuses. For example, it is common programming practice > for a child process to return zero to the parent signifying success. > Apart from this return

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

msk...@ansuz.sooke.bc.ca wrote: > TeXworks is free to read the log file, just like everybody else has > to to detect things like undefined references. Agreed, but at the moment it does not, unless the status code is non-zero. I believe that the suggested command-line switch (which would not

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

On Sun, 13 Mar 2016, Philip Taylor wrote: > "Make" (etc) are not really my concern, but the behaviour of TeXworks > is. If TeXworks can decide whether or not to conceal the log file based > solely on the status code returned by TeX (XeTeX, etc), then that status TeXworks is free to read the log

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

P.S. > "Make" (etc) are not really my concern, but the behaviour of TeXworks > is. If TeXworks can decide whether or not to conceal the log file based > solely on the status code returned by TeX (XeTeX, etc), then that status > code should (again, IMVHO) be able to indicate "things were not

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

David Carlisle wrote: >> non-zero status codes should be reserved for various categories >> of warning, error, severe error, fatal error, etc., should they not ? > > No I think the (now, whatever the convention in vms was) normal convention > is that programs have a clear distinction between

Re: [XeTeX] Overfull boxes return status of 0 in XeTeX

David Carlisle wrote: > that would seem rather odd unless you actually made them errors and > stop with a normal > ? error prompt etc. > > The status code should reflect whether an error is reported so if > there were an option it > should be to make overfull boxes errors, not just to affect

[XeTeX] Overfull boxes return status of 0 in XeTeX

A (very) recent discussion on the TeXworks list included the following extract : >>> 6) [new] A test file yields (in the log) : >>> >>> Overfull \hbox (0.58942pt too wide) in paragraph at lines 20--20 >>> []\bodyfont brian.smith0...@btinternet.com[] | >>> >>> With "Hide console window" set to