Hi guys (edit: and girls)!

Finally some good news for you: we've just put up the OpenEmbedded-based cross-compiler toolchain and the sources for the PDF viewer.

See the announcement on our forums:
http://forum.irexnet.com/viewtopic.php?t=590

Regards,

Matthijs
iRex SW Developer

Great news - thanks guys!

No girls involved? (yet?)

That's amazing! THanks Matthijs.

Thanks, Matthijs.

Thanks!!! :) Very good news! I am awaitng hollydays :)

Ah, now I see why ipdf first:

//////////////////////////////////////////////////////////////////////////
// **** bottleneck ****
// we have to convert from splashbitmap to xImage, which is very slow
//
XImage * XMgr::createImage(SplashBitmap * bmp,
int xSrc , int ySrc,
GBool bRelease )

I assume that if I pull this thorn out, you all might consider incorporating the fix into the mainstream?

No girls involved? (yet?)

I see a
Author: ann <ann@localhost>, (C) 2005
in liberdm/display.h

I see a
Author: ann <ann@localhost>, (C) 2005
in liberdm/display.h
LOL! Perhaps she's the lady who brings refreshment drinks from time to time.

Sorry to bother you guys at work...but allow me a non-coder total (maybe) nonsens question...:-)

Would it, at least in theory, be possible for someone from the community to create a reflow capability for the PDF viewer with the now available tools and sources?

Thanks.

Would it, at least in theory, be possible for someone from the community to create a reflow capability for the PDF viewer with the now available tools and sources?


In theory it is not possible (PDF tag system, scanned files, blah blah). In practice, who knows. Two ghostscript based tools, pstotext and ps2ascii are known to be able to extract some content. This content can be tagged with html and reinserted into minimo/browser. Actually it is something a non-coder can try: get these utilities (debian somewhere, and randomly for other OS) and try in your favorite pdf/postscript files.

EDITED: There is also prescript, which has already a html tag markup implemented.

EDITED: see http://www.nzdl.org/html/prescript.html and tell us! Perhaps in a general thread.

hmmm...let me get this clear...if I use "normal" tagged PDF files it will not work? My PDF viewer for the PDA did reflow without trouble as long as the files were tagged (which is easy to do in Acrobat and OpenOffice), but it was from Adobe...
Can only Adobe viewers reflow tagged PDF?

I'll look at the provided link and see what I can find out.
Thanks.

UPDATE:

I looked at the information behind the link...if I did not completely misunderstand it's just another way of extracting text from PDF...which is just about as far from what I want/need as I can imagine. I already do that all the time, I take the PDF apart, reformat it and then reconvert to PDF with the proper page-size. Reflow would make that unneccessary...that is why I asked...it would be a real pity if that weren't possible at all...at least until the HTML viewer appears...^^

OK I can confirm that iRex's tool chain works on Debian 3.1r3 but they didn't include their autoconf. I guessed wrong autoconf 1.9 and had to hand repair the Makefiles. :(

Feedback to iRex, please document the autoconf to use or, even better, include it in the tool chain.

I compiled ipdf and it's now working on my 2.7 (still unpatched to 2.7.1) iLiad.

I've spent a fair amount of time trying to re-flow PDF for my Librie, it's a mess. I have hopes for the new format and with the tools provided one could build a viewer for it. But at present there is no way to test/deploy it unless you have an exploitable 2.7 iLiad (and are willing to exploit it :D).

I used lsof to confirm my code was running, 515366 is the size of the file, I didn't strip my ipdf.

xpdf 943 root cwd DIR 100,2 1024 2 /
xpdf 943 root rtd DIR 100,2 1024 2 /
xpdf 943 root txt REG 3,1 515366 56 /media/cf/ipdf

Sorry, I totally missed this post.
We're working on Ubuntu 6.06 LTS, which has the following versions of autotools:
automake 1.9
autoconf 2.59(a)

I will update the PDF sources with the auto-generated files

Edit: I've done the autoreconf on the source and replaced the tarball with a new one that includes all missing files. If you want to start from the .ac files, you should use the versions indicated above.

I've done the autoreconf on the source and replaced the tarball with a new one that includes all missing files. If you want to start from the .ac files, you should use the versions indicated above.

Thank you! I appreciate you taking the time to do this.

How about we put all the information together in the Wiki how to install the toolchain and compile our own apps?

I have a bug report for the iRex tool chain:

arm-linux-as does not default to soft float.

You need to setup ASFLAGS = -mfloat-abi=soft to have your assembly files assembled and labeled correctly. Assuming they don't contain any hardware FP assembly code, in which case you'll get an error.