Re: [toolbox] LaTeXiT 1.2 beta

[<jer...@u-...>]

Le 4 juil. 05, =E0 10:05, Will Robertson a =E9crit :

> Hi Pierre,
>
> [...]
> On 3 Jul 2005, at 7:30 PM, Pierre Chatelier wrote:
>
>>> [in the error manager] so if it could be reliably determine what the=20=

>>> offending token is it would be nice to see that as well.
>> For now, I would prefer not to. I prefer to be less precise, but=20
>> ensure that the error-line is ok, rather than trying to deduce the=20
>> faulty token, with the risk of getting wrong and give a bad=20
>> indication. However, since LaTeXiT is open source and will be a=20
>> toolbox project, if anybody has the knowledge to improve that, this=20=

>> will be no problem I think. Do you agree with this opinion ?
>
> Sounds great!
> A log-file parser sounds like a pretty handy tool that many front ends=20=

> could use. I know Jonathan Fine was interested in such a thing a=20
> little while back on comp.text.tex...

Guess what, I have my own log parser in iTeXMac since a decade...
TeXnicenter also has a log parser and the same for auctex...
As far as I known, auctex technology should be of great help if anyone=20=

can understand the source code...

pdfsync like technology would be of great help here.

More seriously, there is a funny bug in latextit: start dragging the=20
output, but drop on the output pane, then play with the magnification=20
slider. The image gets fuzzy with some kind of gaussian bler... You can=20=

retrieve the original output by drag n drop on itself.