I recently posted a topic about a file-parser called detox (see last post).
I took a look into the code now and here's my result so far (not finished on this yet).

First:
The delivered and downloaded sourcecode doesn't compile.
There is a some miracle 'config.h' missing and the sources probably still lack other codes.
Just strange that the program delivered from my repo does work 'somehow', 'sometimes', 'somewhere', 'maybe'... :-)

Second:
The program as is is usable but only with strong limitations.
The config-file parsing function doesn't run clean and lags proper exception-handling.
The config-file isn't parsed correctly, means, if you change the sequences in a way deviating from using only 'standard settings' and chaining sequences not in the way proposed by the inventor of this code the configuration-parsing process fails without a comprehensive error-message.

Third:
You can't design your own tables (so far I see it correct) and use them/ include them in the conversion-chain.
But you can modify the so called safe.tbl file and get expected results.
Side-effects not observed yet.


Temporarily result:
I didn't finish my studies on this topic yet and as I am no professional who deals with low-level or midlevel languages on a daily basis it is tough for me to review all the lines of code.
As far I see it does this kind of software not belong into a repository of a big OS.
I'd suggest to kick it out.

Greets
Gee

on ubuntu you can install it: apt-get install detox, do not need to compile it.

grrr


Funny, nobody wants to negotiate with me the configure script ;-)

I saw the post on the configure issue where it wasn't doing something. Not sure I have an answer however.

i'm not sure about this.

you are not showing us any actual code, just paraphrasing how things are not right in your opinion, vaguely hinting at the possiblility that you might want to fix it...

also you are using 2 very different versions of linux and never seem to tell us on which version you experience problems.

also i'm not quite sure what you actually want/expect the software to do (that is mostly re your last thread, which you should at least provide a link to btw) and where it objectively fails.

REAL output from REAL commands and REAL files, please.

goto website, download bullshit and wonder.
The whole project if fucked up.
Anyone interested in working on a fork?

Bye


*Edited: I have her a 100% compiling translation-unit of Zeus. Maybe you'd like to watch to that compiling flawless, alright?