OESF Portables Forum
Model Specific Forums => Sharp Zaurus => Zaurus - pdaXrom => Topic started by: Meanie on April 29, 2006, 06:24:29 am
-
I just finished compiling abiword 2.4.4 on my C3000 natively and was able to open my staroffice documents! many of the plugins failed to compile but I managed to compile the ones important to me. How do I package up all these files? Do I make DESTDIR=/data/ipkroot/abiword/data install for each of the abiword subdirectories?
-
in OE/OZ we have Abiword + Abiword-plugin-NAME
-
hrw, stop post about OE in our forum. For every your message i will post message about pdaXrom in your forum.
https://www.oesf.org/forums/index.php?showt...95&#entry125095 (https://www.oesf.org/forums/index.php?showtopic=19096&st=0&p=125095&#entry125095)
-
Heh.. I wanted to say how we splitted Abiword into subpackages in OE - maybe this will interest Meanie.
Currently there are 'abiword' which contain main program with all what is needed to run and packages with plugins 'abiword-plugin-NAME'. This allow user to choose what to install and does not fill system with not necessary dependencies (some plugins can be not needed for user so why has to install extra deps).
Filelists: http://ewi546.ewi.utwente.nl/tmp/hrw/abiword/ (http://ewi546.ewi.utwente.nl/tmp/hrw/abiword/) (maybe this is too modular way but thats how we did it).
-
OZ OE - forbidden words here
-
OZ OE - forbidden words here
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125104\"][{POST_SNAPBACK}][/a][/div]
Heh, don't look at the title bar of your browser: "OE forums"
-
OZ OE - forbidden words here
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125104\"][{POST_SNAPBACK}][/a][/div]
Heh, don't look at the title bar of your browser: "OE forums"
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125106\"][{POST_SNAPBACK}][/a][/div]
you stole this name here for bitbake?
-
Koen blog' from Tue, 14 Mar 2006:
blablabla...
We can now use apps built with MaverickCrunch and iwmmxt on a regular rootfs.
pdaXrom uses iwmmxt about year - OZ sucks?
-
I just finished compiling abiword 2.4.4 on my C3000 natively and was able to open my staroffice documents!
Meanie, does this version support printing to PDF? Previous versions of Abiword from official feeds segfaulted when doing printing of any kind. beta3 Abiword does print to PDF without segfaulting but the results are far from satisfactory as can be seen from the screenshots
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
-- cheers
-
I just finished compiling abiword 2.4.4 on my C3000 natively and was able to open my staroffice documents!
Meanie, does this version support printing to PDF? Previous versions of Abiword from official feeds segfaulted when doing printing of any kind. beta3 Abiword does print to PDF without segfaulting but the results are far from satisfactory as can be seen from the screenshots
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125195\"][{POST_SNAPBACK}][/a][/div]
nope, it still crashes and i was not able to compile the pdf plugin either.
but, i was able to fix all the window sizes so now all the windows are correctly sized for the Z screen
I also discovered that gtk2 is to blame for a lot of other oversized windows so I hacked it to fit the screen
-
So, if I understand you correctly, if one installs your hacked gtk2 package, all windows will fit the Z screen. If that is the case, can you make an ipk of your hacked gtk2 package, please ? That would make many people happy.
You solve so many problems in so little time, you are amazing !!!
-
So, if I understand you correctly, if one installs your hacked gtk2 package, all windows will fit the Z screen. If that is the case, can you make an ipk of your hacked gtk2 package, please ? That would make many people happy.
You solve so many problems in so little time, you are amazing !!!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=125202\")
well, not yet. i meant all the windows in abiword are fixed so far. i havent gone through all gtk2 files yet, only the ones abiword uses but some apps that use the same widgets will benefit.
now to get all window sizes fixed gtk2 needs to be completely fixed, but some apps use gtk 1.2 while others use qt and other libraries like wx, gnome, kde... all of them need to be fixed up...
and then some apps hardcode the screen sizes too, so each of those apps need to be fixed individusally. abiword has some hardcoded values which I hacked to be zaurus friendly hardcoded values so i had all the abiword windows nicely fit on the screen except for the file open dialog. i spend hours looking and trying to make abiword resize that window correctly until i traced it back to gtk2 filechooser being the culprit. so i hacked gtk2
i also hacked gqview and xpdf btw. all the hacked binaries as well as the ip files are on my website
[a href=\"http://zaurus.daemons.gr/menaie/pdaxrom/]http://zaurus.daemons.gr/menaie/pdaxrom/[/url]
http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html (http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html)
-
nope, it still crashes and i was not able to compile the pdf plugin either.
Bummer, in that case I'll stick to the official version since I've now found that printing to PS does work.
-- cheers
-
So, if I understand you correctly, if one installs your hacked gtk2 package, all windows will fit the Z screen. If that is the case, can you make an ipk of your hacked gtk2 package, please ? That would make many people happy.
You solve so many problems in so little time, you are amazing !!!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=125202\")
well, not yet. i meant all the windows in abiword are fixed so far. i havent gone through all gtk2 files yet, only the ones abiword uses but some apps that use the same widgets will benefit.
now to get all window sizes fixed gtk2 needs to be completely fixed, but some apps use gtk 1.2 while others use qt and other libraries like wx, gnome, kde... all of them need to be fixed up...
and then some apps hardcode the screen sizes too, so each of those apps need to be fixed individusally. abiword has some hardcoded values which I hacked to be zaurus friendly hardcoded values so i had all the abiword windows nicely fit on the screen except for the file open dialog. i spend hours looking and trying to make abiword resize that window correctly until i traced it back to gtk2 filechooser being the culprit. so i hacked gtk2
i also hacked gqview and xpdf btw. all the hacked binaries as well as the ip files are on my website
[a href=\"http://zaurus.daemons.gr/menaie/pdaxrom/]http://zaurus.daemons.gr/menaie/pdaxrom/[/url]
http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html (http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125203\"][{POST_SNAPBACK}][/a][/div]
Is it gtk2 at fault? I always thought it was the window manager, as abiword (including the file open dialog) resizes to fit the screen perfectly under xfce4, but not in the default window manager. I wonder what xfce does to get gtk2 into line?
-
So, if I understand you correctly, if one installs your hacked gtk2 package, all windows will fit the Z screen. If that is the case, can you make an ipk of your hacked gtk2 package, please ? That would make many people happy.
You solve so many problems in so little time, you are amazing !!!
[div align=\"right\"][{POST_SNAPBACK}][/a][/div] (http://index.php?act=findpost&pid=125202\")
well, not yet. i meant all the windows in abiword are fixed so far. i havent gone through all gtk2 files yet, only the ones abiword uses but some apps that use the same widgets will benefit.
now to get all window sizes fixed gtk2 needs to be completely fixed, but some apps use gtk 1.2 while others use qt and other libraries like wx, gnome, kde... all of them need to be fixed up...
and then some apps hardcode the screen sizes too, so each of those apps need to be fixed individusally. abiword has some hardcoded values which I hacked to be zaurus friendly hardcoded values so i had all the abiword windows nicely fit on the screen except for the file open dialog. i spend hours looking and trying to make abiword resize that window correctly until i traced it back to gtk2 filechooser being the culprit. so i hacked gtk2
i also hacked gqview and xpdf btw. all the hacked binaries as well as the ip files are on my website
[a href=\"http://zaurus.daemons.gr/menaie/pdaxrom/]http://zaurus.daemons.gr/menaie/pdaxrom/[/url]
http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html (http://www.users.on.net/~hluc/myZaurus/custom-pdaxrom.html)
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125203\"][{POST_SNAPBACK}][/a][/div]
Is it gtk2 at fault? I always thought it was the window manager, as abiword (including the file open dialog) resizes to fit the screen perfectly under xfce4, but not in the default window manager. I wonder what xfce does to get gtk2 into line?
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125225\"][{POST_SNAPBACK}][/a][/div]
That's an interesting observation. I tried openbox (the default wm) and fluxbox, both behaved the same, ie oversized windows and once I hacked gtk, both behaved the way I wanted them to so I assumed gtk2 was to blame but since xfce is doing it properly, then maybe the other window managers aren't using gtk2 correctly. I will take a look at the source code for xfce and see how its done there. openbox might do it correctly if xinerama extension is enabled, fluxbox and blackbox just don't seem to care. so its either hacking gtk2 or openbox and fluxbox.
so does xfce display the qt config menus correctly as well? i should try xfce. it is next on my list to do after getting pdaX to work on my OQO. maybe i should bump up its position on the list...
-
That's an interesting observation. I tried openbox (the default wm) and fluxbox, both behaved the same, ie oversized windows
IceWM also does it's best to restrict windows/dialogs size to screen size. So PITA stuff like the GTK file dialog (which always open at a huge size) are brought to heel and open to fit screen.
so does xfce display the qt config menus correctly as well?
Still too large on icewm
-- cheers
-
I just finished compiling abiword 2.4.4 on my C3000 natively and was able to open my staroffice documents!
Meanie, does this version support printing to PDF? Previous versions of Abiword from official feeds segfaulted when doing printing of any kind. beta3 Abiword does print to PDF without segfaulting but the results are far from satisfactory as can be seen from the screenshots
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125195\"][{POST_SNAPBACK}][/a][/div]
I think I figured out the problem. pdf support in abiword requires poppler which in turn needs libjpeg. I bet poppler was compiled without libjpeg because the configure script in poppler doesn't detect libjpeg even though its installed.
-
so does xfce display the qt config menus correctly as well?
Yep, they work fine too.
-
I just finished compiling abiword 2.4.4 on my C3000 natively and was able to open my staroffice documents!
Meanie, does this version support printing to PDF? Previous versions of Abiword from official feeds segfaulted when doing printing of any kind. beta3 Abiword does print to PDF without segfaulting but the results are far from satisfactory as can be seen from the screenshots
[ You are not allowed to view attachments ] [ You are not allowed to view attachments ]
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125195\"][{POST_SNAPBACK}][/a][/div]
I think I figured out the problem. pdf support in abiword requires poppler which in turn needs libjpeg. I bet poppler was compiled without libjpeg because the configure script in poppler doesn't detect libjpeg even though its installed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125288\"][{POST_SNAPBACK}][/a][/div]
ok, I got PDF plugin compiled and working now so I can import PDF documents into abiword. I still can't print, it crashes abiword, but that seems to be caused by missing lpr package. Does beta3 come with lpr?
-
ok, I got PDF plugin compiled and working now so I can import PDF documents into abiword. I still can't print, it crashes abiword, but that seems to be caused by missing lpr package. Does beta3 come with lpr?
AFAICS lpr is not in the official feeds. You can get a workalike from cups (I believe it's in the contribs). But just "printing" to PS or PDF does not require lpr - does that work?
-- cheers
-
ok, I got PDF plugin compiled and working now so I can import PDF documents into abiword. I still can't print, it crashes abiword, but that seems to be caused by missing lpr package. Does beta3 come with lpr?
AFAICS lpr is not in the official feeds. You can get a workalike from cups (I believe it's in the contribs). But just "printing" to PS or PDF does not require lpr - does that work?
-- cheers
[div align=\"right\"][{POST_SNAPBACK}][/a][/div]
(http://index.php?act=findpost&pid=125533\")
printing in abiword crashes for me, even when i tried the new 2.4.2
this probably is a bug in rc1 and fixed in rc3. can you try out my 2.4.4 version and see if you can import pdf files and print to pdf?
[a href=\"http://zaurus.daemons.gr/menaie/pdaxrom/feed/abiword_2.4.4_armv5tel.ipk]http://zaurus.daemons.gr/menaie/pdaxrom/fe....4_armv5tel.ipk[/url]
http://zaurus.daemons.gr/menaie/pdaxrom/fe....1_armv5tel.ipk (http://zaurus.daemons.gr/menaie/pdaxrom/feed/poppler_0.5.1_armv5tel.ipk)
you probably need poppler too if you havent already installed it.
-
printing in abiword crashes for me, even when i tried the new 2.4.2
this probably is a bug in rc1 and fixed in rc3. can you try out my 2.4.4 version and see if you can import pdf files and print to pdf?
Printing to PS is OK, but printing to PDF still results in a mess just like before
Importing PDF works OK.
-- cheers
-
printing in abiword crashes for me, even when i tried the new 2.4.2
this probably is a bug in rc1 and fixed in rc3. can you try out my 2.4.4 version and see if you can import pdf files and print to pdf?
Printing to PS is OK, but printing to PDF still results in a mess just like before
Importing PDF works OK.
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125561\"][{POST_SNAPBACK}][/a][/div]
drats
does saving as pdf work? it crashes on me
btw, which version of poppler did you use? did you use mine?
-
printing in abiword crashes for me, even when i tried the new 2.4.2
this probably is a bug in rc1 and fixed in rc3. can you try out my 2.4.4 version and see if you can import pdf files and print to pdf?
Printing to PS is OK, but printing to PDF still results in a mess just like before
Importing PDF works OK.
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125561\"][{POST_SNAPBACK}][/a][/div]
drats
does saving as pdf work? it crashes on me
btw, which version of poppler did you use? did you use mine?
-
drats
does saving as pdf work? it crashes on me
Yep, but result is a mess exactly like printing to PDF
btw, which version of poppler did you use? did you use mine?
Yours, downloaded from the above links. I note that you've compiled poppler with libjpeg support. Where can I get my grubby hands on the header and static lib for libjpeg? I tried compiling my own but failed miserably because the source is so old and apparently it knows nothing about ARMs.
As an aside, I tried using ps2pdf from a version of ghostscript (can't remember where I got it from) to convert the good ps output to a pdf, but it fails with some postscript error. Tried converting the same file on my desktop and it works fine. I shall have to look into recompiling a ghostscript for pdaxrom.
-- cheers
-
I shall have to look into recompiling a ghostscript for pdaxrom.
A litle off-topic but, at some point ghostscript is also worth compiling for pdaxrom because at some point, it's needed to convert PDF to DJVU files using djvutools.
Thanks
-
I shall have to look into recompiling a ghostscript for pdaxrom.
A litle off-topic but, at some point ghostscript is also worth compiling for pdaxrom because at some point, it's needed to convert PDF to DJVU files using djvutools.
Unfortunately the program which does the PDF->DJVU conversion, GSDjVu, has license terms that forbid the distribution of executables. See this for more info:
http://djvulibre.djvuzone.org/gsdjvu.html (http://djvulibre.djvuzone.org/gsdjvu.html)
-- cheers
-
drats
does saving as pdf work? it crashes on me
Yep, but result is a mess exactly like printing to PDF
btw, which version of poppler did you use? did you use mine?
Yours, downloaded from the above links. I note that you've compiled poppler with libjpeg support. Where can I get my grubby hands on the header and static lib for libjpeg? I tried compiling my own but failed miserably because the source is so old and apparently it knows nothing about ARMs.
As an aside, I tried using ps2pdf from a version of ghostscript (can't remember where I got it from) to convert the good ps output to a pdf, but it fails with some postscript error. Tried converting the same file on my desktop and it works fine. I shall have to look into recompiling a ghostscript for pdaxrom.
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125572\"][{POST_SNAPBACK}][/a][/div]
I used the same source but I configured with --enable-static --enable-shared options and then stole the generated libtool from poppler and hacked it for jpeg6b
also hacked the .pc file for poppler to create a libjpeg.pc file but poppler does not detect it. the configure in abiword found the new libjpeg.pc and compiled jpeg plugin without problems but poppler was a bitch and i had to hack poppler's configure script and to manually add in the correct settings so it would detect libjpeg properly and compile build it with jpeg support
-
Nice job!
-
I have updated freetype to the latest .10 release and abiword does not crash anymore when saving as pdf
the document is still scrambled, but I will recompile poppler and abiword against the new freetype version and see if that fixes it. we will just have to wait and see now
-
I have updated freetype to the latest .10 release and abiword does not crash anymore when saving as pdf
the document is still scrambled, but I will recompile poppler and abiword against the new freetype version and see if that fixes it. we will just have to wait and see now
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125821\"][{POST_SNAPBACK}][/a][/div]
I'm very curious!
Creating PDF documents on the zaurus is one thing which I'd really need, not even TextMaker is able to do so.
This, and a good version of gnumeric (in rootless mode ;-) for my book keeping, would be THE killer applications to me, which I'd pay for if they work well.
It is amazing how you manage to do all that, probably besides another full-time job? Great! Thanks a lot!
daniel
-
I have updated freetype to the latest .10 release and abiword does not crash anymore when saving as pdf
the document is still scrambled, but I will recompile poppler and abiword against the new freetype version and see if that fixes it. we will just have to wait and see now
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125821\"][{POST_SNAPBACK}][/a][/div]
I'm very curious!
Creating PDF documents on the zaurus is one thing which I'd really need, not even TextMaker is able to do so.
This, and a good version of gnumeric (in rootless mode ;-) for my book keeping, would be THE killer applications to me, which I'd pay for if they work well.
It is amazing how you manage to do all that, probably besides another full-time job? Great! Thanks a lot!
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125840\"][{POST_SNAPBACK}][/a][/div]
openoffice could always create pdf files so this feature has been available on the zaurus and is nothing new really.
gnumeric in rootless mode works, i just fear you dont really understand what rootless mode means but we can discuss that in the appropriate sub forum.
and yeah, i do have a fulltime job working 10 hrs a day to pay the bills. i just have my zauri setting next to me compiling stuff while I am working
anyway, back to topic. pdf export/print is still not working. it seems abiword isnt actually doing the conversion and only has a stub framewoek. i am trying to build again with ghostscript installed.
-
openoffice could always create pdf files so this feature has been available on the zaurus and is nothing new really.
Yes, I know. But Openoffice is not usable on the Zaurus in my opinion.
Much too long startup time and not responding in time when writing. Much too inconvenient to really use it for daily work.
gnumeric in rootless mode works, i just fear you dont really understand what rootless mode means but we can discuss that in the appropriate sub forum.
Well, before moving that into another forum, let me just ask shortly: Doesn't it simply mean that no entire X/QT environment has to be started but that something like a runtime-X/QT is loaded with the actual program?
At least I know something like that from almost 10 years ago when I used Winword and Excel on a HP 200LX (MS-DOS) palmtop with a runtime-Windows-3.0 environment (without really loading the entire Windows). Was quite funny, and it worked well.
Not that it was called "rootless mode" back then, but it seems to be basically the same.
and yeah, i do have a fulltime job working 10 hrs a day to pay the bills. i just have my zauri setting next to me compiling stuff while I am working
I wish I had a job where I could do that easily. Too much colleagues and bosses in the same room here ;-)
anyway, back to topic. pdf export/print is still not working. it seems abiword isnt actually doing the conversion and only has a stub framewoek. i am trying to build again with ghostscript installed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125911\"][{POST_SNAPBACK}][/a][/div]
Thanks for all your efforts, Meanie!
daniel
-
openoffice could always create pdf files so this feature has been available on the zaurus and is nothing new really.
Yes, I know. But Openoffice is not usable on the Zaurus in my opinion.
Much too long startup time and not responding in time when writing. Much too inconvenient to really use it for daily work.
gnumeric in rootless mode works, i just fear you dont really understand what rootless mode means but we can discuss that in the appropriate sub forum.
Well, before moving that into another forum, let me just ask shortly: Doesn't it simply mean that no entire X/QT environment has to be started but that something like a runtime-X/QT is loaded with the actual program?
At least I know something like that from almost 10 years ago when I used Winword and Excel on a HP 200LX (MS-DOS) palmtop with a runtime-Windows-3.0 environment (without really loading the entire Windows). Was quite funny, and it worked well.
Not that it was called "rootless mode" back then, but it seems to be basically the same.
and yeah, i do have a fulltime job working 10 hrs a day to pay the bills. i just have my zauri setting next to me compiling stuff while I am working
I wish I had a job where I could do that easily. Too much colleagues and bosses in the same room here ;-)
anyway, back to topic. pdf export/print is still not working. it seems abiword isnt actually doing the conversion and only has a stub framewoek. i am trying to build again with ghostscript installed.
[div align=\"right\"][a href=\"index.php?act=findpost&pid=125911\"][{POST_SNAPBACK}][/a][/div]
Thanks for all your efforts, Meanie!
daniel
[div align=\"right\"][a href=\"index.php?act=findpost&pid=126048\"][{POST_SNAPBACK}][/a][/div]
yes, you are right about only running xqt runtime would be called rootless mode, however, xqt only implements experimental pseudo rootless mode, so it is not exactly the same but i have not figured out how much of the rootless thing is implmented/emulated yet, although it looks like it works appearance wise. well, i guess someone will need to do a lot of testing do you wanna volunteer?
on another note, I believe that the pdf printing problem is not caused by abiword. but rather by libgnomeprint which does not seem to be implemented correctly, ie they seem to have hacked the size of the paper to correspond to the size of the screen which on the Z will result in garbage
-
yes, you are right about only running xqt runtime would be called rootless mode, however, xqt only implements experimental pseudo rootless mode, so it is not exactly the same but i have not figured out how much of the rootless thing is implmented/emulated yet, although it looks like it works appearance wise. well, i guess someone will need to do a lot of testing do you wanna volunteer?
I will gladly test it. Tell me what's necessary... and off we go.
-
ok back to topic.
I did some more investigation and now am pretty sure that the pdf printing problem is caused by libgnomeprint and libgnomeprintui and not abiword since abiword is just using those libraries. i was able to directly generate ps document using abiword's command line invocation: abiword --print=output.ps test.txt and then I was able to convert the ps file to pdf using ghostscript, ie ps2pdf output.ps and the resulting pdf file was displaying correctly when viewed with xpdf. when i print to ps using libgnomeui, ie printing via abiword print dialog, the generated ps file is garbage and thus when converting it to pdf the result is also garbled.
so my conclusion is that abiword is fine now, but libgnomeprint libraries need fixing.
oh gosh, i just noticed, this was my 1000th posting
-
yes, you are right about only running xqt runtime would be called rootless mode, however, xqt only implements experimental pseudo rootless mode, so it is not exactly the same but i have not figured out how much of the rootless thing is implmented/emulated yet, although it looks like it works appearance wise. well, i guess someone will need to do a lot of testing do you wanna volunteer?
I would gladly test it, but on another thread the discussion seems to show that it does not work yet on Cacko ROM at all due to some glibc problems.
So I guess I have to wait until these problems are sorted out.
Or does it work on Cacko for some people? Then I'd begin to test it right away :-)
daniel
-
i was able to directly generate ps document using abiword's command line invocation: abiword --print=output.ps test.txt and then I was able to convert the ps file to pdf using ghostscript, ie ps2pdf output.ps and the resulting pdf file was displaying correctly when viewed with xpdf. when i print to ps using libgnomeui, ie printing via abiword print dialog, the generated ps file is garbage and thus when converting it to pdf the result is also garbled.
What's the difference between invoking print from the command line and from the gui?
so my conclusion is that abiword is fine now, but libgnomeprint libraries need fixing.
Seeing as gnumeric doesn't print properly (to PDF) either that would sound about right
on another note, I believe that the pdf printing problem is not caused by abiword. but rather by libgnomeprint which does not seem to be implemented correctly, ie they seem to have hacked the size of the paper to correspond to the size of the screen which on the Z will result in garbage
Is this peculiar to pdaxrom's version of libgnomeprint or something that also manifests in the upstream version? And more importantly do you think you can fix it?
-- cheers
-
I note that you've compiled poppler with libjpeg support. Where can I get my grubby hands on the header and static lib for libjpeg? I tried compiling my own but failed miserably because the source is so old and apparently it knows nothing about ARMs.
I used the same source but I configured with --enable-static --enable-shared options and then stole the generated libtool from poppler and hacked it for jpeg6b
also hacked the .pc file for poppler to create a libjpeg.pc file but poppler does not detect it. the configure in abiword found the new libjpeg.pc and compiled jpeg plugin without problems but poppler was a bitch and i had to hack poppler's configure script and to manually add in the correct settings so it would detect libjpeg properly and compile build it with jpeg support
I have found that simply copying the libjpeg header files ...
cp -a jconfig.h /usr/include
cp -a jpeglib.h /usr/include
cp -a jmorecfg.h /usr/include
cp -a jerror.h /usr/include
cp -a jpegint.h /usr/include... works -- at least I was able to php's gd module with jpeg support.
-- cheers
-
i was able to directly generate ps document using abiword's command line invocation: abiword --print=output.ps test.txt and then I was able to convert the ps file to pdf using ghostscript, ie ps2pdf output.ps and the resulting pdf file was displaying correctly when viewed with xpdf. when i print to ps using libgnomeui, ie printing via abiword print dialog, the generated ps file is garbage and thus when converting it to pdf the result is also garbled.
What's the difference between invoking print from the command line and from the gui?
so my conclusion is that abiword is fine now, but libgnomeprint libraries need fixing.
Seeing as gnumeric doesn't print properly (to PDF) either that would sound about right
on another note, I believe that the pdf printing problem is not caused by abiword. but rather by libgnomeprint which does not seem to be implemented correctly, ie they seem to have hacked the size of the paper to correspond to the size of the screen which on the Z will result in garbage
Is this peculiar to pdaxrom's version of libgnomeprint or something that also manifests in the upstream version? And more importantly do you think you can fix it?
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=126146\"][{POST_SNAPBACK}][/a][/div]
well, I recompiled libgnomeprint and libgnomeprintui and got it working, well sorta. It depends on the font I use. If I use Bitstream Vera fonts, the PDF file is perfect. Other fonts have some characters mangled. It's probably a font config problem since the PDF module in libgnomeprint only recognises TTF and Type1 fonts so the font.scale, etc... may need to be looked at.
-
well, I recompiled libgnomeprint and libgnomeprintui and got it working, well sorta. It depends on the font I use. If I use Bitstream Vera fonts, the PDF file is perfect. Other fonts have some characters mangled.
By "other fonts" do you mean non-TTF? ...
It's probably a font config problem since the PDF module in libgnomeprint only recognises TTF and Type1 fonts so the font.scale, etc... may need to be looked at.
... if print to PDF "only" works when using TTF fonts then that's no big handicap, I can't imagine why anyone would want to use bitmap fonts anyway
Anywhere we could download the recompiled libgnomeprint and libgnomeprintui?
-- cheers
-
well, I recompiled libgnomeprint and libgnomeprintui and got it working, well sorta. It depends on the font I use. If I use Bitstream Vera fonts, the PDF file is perfect. Other fonts have some characters mangled.
By "other fonts" do you mean non-TTF? ...
It's probably a font config problem since the PDF module in libgnomeprint only recognises TTF and Type1 fonts so the font.scale, etc... may need to be looked at.
... if print to PDF "only" works when using TTF fonts then that's no big handicap, I can't imagine why anyone would want to use bitmap fonts anyway
Anywhere we could download the recompiled libgnomeprint and libgnomeprintui?
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=126692\"][{POST_SNAPBACK}][/a][/div]
I finally figured out the root of the problem. It is a font config problem.
Abiword can display TTF and maybe Type1 (pfa/pfb) fonts. When printing, the gnome sub system that converts the content to postscript and pdf needs to convert the fonts to Type1 using the available encodings and glyphs. This requires a valid fonts.dir and encodings.dir file for the Type1 fonts. TTF fonts dont need those config files, however, the converted Type1 fonts need them so converting TTF fonts without those config files to Type1 fonts confuses that sub system. Abiword has a ttftool to do the font conversion, but the required font config files are usually missing since TTF fonts dont need them
The other problem is that xpdf needs the same Type1 fonts to display the text.
So, if you have a font that is availale in boths formats, TTF and Type1 with the font config files, then when you print to pdf, it will display correctly in xpdf.
But, if you copy the pdf file to a windows machine which usually have tons of fonts, chances are that it will display correctly in acrobat reader.
Now there is this fonts.alias file and if mapped correctly, you can alias the missing fonts and a substitute font will be used instead so it looks a bit different than the original but something readable is displayed.
Now I don't understand the format of these config files yet, maybe someone else knows. There are also tools to generate those config files like ttmkdir and ttfttool but I was unable to compile them for the Z. maybe someone with a linux machine and those tools can generate those config files.
as for the libgnome libraries, i am now not sure whether they actually need to be recompiled. maybe just fixing the font config files is sufficient. maybe they need recompiling to make the pdf files readable on the Zaurus itself but the generated pdf files seem to be ok if viewed on a PC.
-
I finally figured out the root of the problem. It is a font config problem.
Thanks for taking the time to diagnose the problem. However I'm not sure I quite follow your explanation
Anyway to cut to the chase, I've been trying to get PDF output via a roundabout way. Basically I compiled ghostscript and used its ps2pdf to create the pdfs. And the good thing is that there is no need to mess around with Type1 fonts. I only have TTF versions of the fonts that I use, and within each of Abiword, Gnumeric, Inkscape, I "printed" to a ps file which I then converted using ps2pdf. They all display correctly in xpdf
Now I don't understand the format of these config files yet, maybe someone else knows. There are also tools to generate those config files like ttmkdir and ttfttool but I was unable to compile them for the Z. maybe someone with a linux machine and those tools can generate those config files.
Does that mean generating these config files whenever you add TTF fonts to the Z? Bit of a pain
as for the libgnome libraries, i am now not sure whether they actually need to be recompiled. maybe just fixing the font config files is sufficient. maybe they need recompiling to make the pdf files readable on the Zaurus itself but the generated pdf files seem to be ok if viewed on a PC.
Not so for me, the messed up PDF look the same when viewed both on the Z and on my desktop machine.
-- cheers
-
I finally figured out the root of the problem. It is a font config problem.
Thanks for taking the time to diagnose the problem. However I'm not sure I quite follow your explanation
Anyway to cut to the chase, I've been trying to get PDF output via a roundabout way. Basically I compiled ghostscript and used its ps2pdf to create the pdfs. And the good thing is that there is no need to mess around with Type1 fonts. I only have TTF versions of the fonts that I use, and within each of Abiword, Gnumeric, Inkscape, I "printed" to a ps file which I then converted using ps2pdf. They all display correctly in xpdf
Now I don't understand the format of these config files yet, maybe someone else knows. There are also tools to generate those config files like ttmkdir and ttfttool but I was unable to compile them for the Z. maybe someone with a linux machine and those tools can generate those config files.
Does that mean generating these config files whenever you add TTF fonts to the Z? Bit of a pain
as for the libgnome libraries, i am now not sure whether they actually need to be recompiled. maybe just fixing the font config files is sufficient. maybe they need recompiling to make the pdf files readable on the Zaurus itself but the generated pdf files seem to be ok if viewed on a PC.
Not so for me, the messed up PDF look the same when viewed both on the Z and on my desktop machine.
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=126760\"][{POST_SNAPBACK}][/a][/div]
oh, that might explain it. xpdf and ghostscript both have their own set of type1 fonts. look in their config files and you will notice them pointing to some directory full of .afm and .pfa files. you might have a full set of them and just didnt know
so maybe libgnomeprint does need to be recompiled after all. I had the same setup working as you before, ie print to ps and then use ghostscript to convert to pdf before I recompiled lbgnomeprintui and got everything to work. I also noticed that my current setup only works if I use latin1 fonts, but unicode fonts don't work (missing font config for those fonts)
I'll package up and upload my recompiled libgnomeprintui and libgnomeprint libraries when I get them cleaned up for you to try. what I suggest you try is write a sentence and repeat it using every font in your system and see what the printed result gives. that is how i discovered which fonts worked and which don't and then correlated that the ones that worked had font config entries and the ones that didn't had no entries.
-
oh, that might explain it. xpdf and ghostscript both have their own set of type1 fonts. look in their config files and you will notice them pointing to some directory full of .afm and .pfa files. you might have a full set of them and just didnt know
Nope, "find / -name *.afm" and "find / -name *.pfa" doesn't show any. Also in testing whether Type1 fonts were necessary, I specifically installed a non-run-of-the-mill TTF (Alligator Puree to be exact )
so maybe libgnomeprint does need to be recompiled after all. I had the same setup working as you before, ie print to ps and then use ghostscript to convert to pdf before I recompiled lbgnomeprintui and got everything to work. I also noticed that my current setup only works if I use latin1 fonts, but unicode fonts don't work (missing font config for those fonts)
I'll package up and upload my recompiled libgnomeprintui and libgnomeprint libraries when I get them cleaned up for you to try. what I suggest you try is write a sentence and repeat it using every font in your system and see what the printed result gives. that is how i discovered which fonts worked and which don't and then correlated that the ones that worked had font config entries and the ones that didn't had no entries.
Strange. I believe all the fonts on my system are unicode, the MS ones most definitely are (Arial, Verdana, Lucida Console, Courier?, Times?). As you can see from my screenshot they convert to PDF just fine.
Not sure whether this has anything to do with it, but I'm using beta3 which is "UTF enabled".
Also another thing I noticed was that when I used Abiword from beta3 feed, a bunch very old MSWORD files when opened showed empty boxes instead of characters. These same files opened fine when I was using beta1. At the same time, files that I had created with Abiword (from beta1) also opened fine. Now using your version of Abiword, those dodgy MSWORD files can be viewed again.
[ You are not allowed to view attachments ]
-
oh, that might explain it. xpdf and ghostscript both have their own set of type1 fonts. look in their config files and you will notice them pointing to some directory full of .afm and .pfa files. you might have a full set of them and just didnt know
Nope, "find / -name *.afm" and "find / -name *.pfa" doesn't show any. Also in testing whether Type1 fonts were necessary, I specifically installed a non-run-of-the-mill TTF (Alligator Puree to be exact )
so maybe libgnomeprint does need to be recompiled after all. I had the same setup working as you before, ie print to ps and then use ghostscript to convert to pdf before I recompiled lbgnomeprintui and got everything to work. I also noticed that my current setup only works if I use latin1 fonts, but unicode fonts don't work (missing font config for those fonts)
I'll package up and upload my recompiled libgnomeprintui and libgnomeprint libraries when I get them cleaned up for you to try. what I suggest you try is write a sentence and repeat it using every font in your system and see what the printed result gives. that is how i discovered which fonts worked and which don't and then correlated that the ones that worked had font config entries and the ones that didn't had no entries.
Strange. I believe all the fonts on my system are unicode, the MS ones most definitely are (Arial, Verdana, Lucida Console, Courier?, Times?). As you can see from my screenshot they convert to PDF just fine.
Not sure whether this has anything to do with it, but I'm using beta3 which is "UTF enabled".
Also another thing I noticed was that when I used Abiword from beta3 feed, a bunch very old MSWORD files when opened showed empty boxes instead of characters. These same files opened fine when I was using beta1. At the same time, files that I had created with Abiword (from beta1) also opened fine. Now using your version of Abiword, those dodgy MSWORD files can be viewed again.
[ You are not allowed to view attachments ]
[div align=\"right\"][a href=\"index.php?act=findpost&pid=126845\"][{POST_SNAPBACK}][/a][/div]
very strange indeed, but good to know that unicode fonts convert properly in beta3
my compile includes all the text imort plugins, i think thre ones on the feed don't
oh and i made a mistake, those Type1 fonts are pfb or pfa. xpdf uses the pdb variant
-
A question for you guys - since you can print in Abiword running on pdaXrom, does your Print dialog show configured CUPS printers? I've compiled both 2.4.2 and 2.4.4 for pdaXrom, but in both cases Print dialog shows only "Create PDF" and "Generic Postscript", it doesn't show my CUPS printers. Also, I din;t find a way in Abiword to add/configure a new printer.
I'm running old rc11 pdaXrom, and Abiword (both versions) crashes when I'm trying to print to Generic Postscript or go into Print Preview.
I don;t have any experience with CUPS and Abiword, so hints on how to debug it are appreciated...
-albertr
-
A question for you guys - since you can print in Abiword running on pdaXrom, does your Print dialog show configured CUPS printers? I've compiled both 2.4.2 and 2.4.4 for pdaXrom, but in both cases Print dialog shows only "Create PDF" and "Generic Postscript", it doesn't show my CUPS printers. Also, I din;t find a way in Abiword to add/configure a new printer.
I'm running old rc11 pdaXrom, and Abiword (both versions) crashes when I'm trying to print to Generic Postscript or go into Print Preview.
I don;t have any experience with CUPS and Abiword, so hints on how to debug it are appreciated...
-albertr
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127765\"][{POST_SNAPBACK}][/a][/div]
abiword crashes on beta1 as well, but with updated version of freetype from my feed, it wont crash anymore and allows you to print to ps or pdf. for cups printers, you need to install the cups package that was recently announced and might also want to install ghostscript as well
-
A question for you guys - since you can print in Abiword running on pdaXrom, does your Print dialog show configured CUPS printers? I've compiled both 2.4.2 and 2.4.4 for pdaXrom, but in both cases Print dialog shows only "Create PDF" and "Generic Postscript", it doesn't show my CUPS printers. Also, I din;t find a way in Abiword to add/configure a new printer.
I did have the the "configured cups printer(s)" option come up before (when I was using probably beta1 and an older Cups package compiled by jacky_cs) but not now, unfortunately I couldn't remember whether I was using pdaXrom's Abiword or Debian's back then - most likely Debian's. So there are 2 possibilities:
- the Debian Abiword is different to pdaXrom's
- my Cups package is different to jacky_cs'
abiword crashes on beta1 as well, but with updated version of freetype from my feed, it wont crash anymore and allows you to print to ps or pdf. for cups printers, you need to install the cups package that was recently announced and might also want to install ghostscript as well
For printing to network printer you don't need to install ghostscript (at least I didn't, YMMV), just CUPs will do.
-- cheers
-
Yes, freetype it was! Thanks for figuring it out! I've compiled 2.1.10 and now AbiWord prints fine. I think you are right about Debian might have been patching AbiWord or maybe that's because AbiWord compiled with "--disable-gnome" configure option on pdaXrom.
Anyone noticed that some of the font's facesets are changed when switching from freetype 2.1.9 to 2.1.10?
Now if I only can make Firefox to print postscript correctly...
-albertr
-
Now if I only can make Firefox to print postscript correctly...
So Firefox does have print functionality? I've never tried Firefox on Z, always liked Mozilla better, but Mozilla wasn't compiled with print options
-- cheers
-
I've compiled Firefox 1.5.0.2 and it sure can print. The only problem is that it prints PS Level.3 that my office printer (HP8100) fails to interpret. And I don;t have any other PS printer here to see who to blame. I'm gonna take another look at this, since ability to print web pages from my Z is important to me.
-albertr
-
I've compiled Firefox 1.5.0.2 and it sure can print. The only problem is that it prints PS Level.3 that my office printer (HP8100) fails to interpret. And I don;t have any other PS printer here to see who to blame. I'm gonna take another look at this, since ability to print web pages from my Z is important to me.
Do you have a feed or somewhere where we can download Firefox? I notice that you've posted on the "New Packages Announcement" thread, but there is no attachment (probably too large) and no link
-- cheers
-
Yes, it was too big for an attachment...
http://www.zavrik.ru/feed/pdaxrom/firefox_....2_armv5tel.ipk (http://www.zavrik.ru/feed/pdaxrom/firefox_1.5.0.2_armv5tel.ipk)
-albertr
-
Yes, it was too big for an attachment...
http://www.zavrik.ru/feed/pdaxrom/firefox_....2_armv5tel.ipk (http://www.zavrik.ru/feed/pdaxrom/firefox_1.5.0.2_armv5tel.ipk)
-albertr
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127805\"][{POST_SNAPBACK}][/a][/div]
you can add entries in /etc/printcap to add extra printer entries such as cups...
i was suggesting ghostscript for converting ps to pdf. it is not needed for printing to cups...
-
I've compiled Firefox 1.5.0.2 and it sure can print. The only problem is that it prints PS Level.3 that my office printer (HP8100) fails to interpret. And I don;t have any other PS printer here to see who to blame.
I've installed your version of Firefox, when I try printing I just get a blank sheet . I also tried printing to ps file then convert to pdf, and surprise surprise, I also get blank page
(Meanie, sorry for hijiacking your thread )
-- cheers
-
I've compiled Firefox 1.5.0.2 and it sure can print. The only problem is that it prints PS Level.3 that my office printer (HP8100) fails to interpret. And I don;t have any other PS printer here to see who to blame.
I've installed your version of Firefox, when I try printing I just get a blank sheet . I also tried printing to ps file then convert to pdf, and surprise surprise, I also get blank page
(Meanie, sorry for hijiacking your thread )
-- cheers
[div align=\"right\"][a href=\"index.php?act=findpost&pid=127830\"][{POST_SNAPBACK}][/a][/div]
I don't mind as long as we find out what the cause of this printing problem is. Btw, printing to PDF works perfectly on the pdaX86 version. I wonder what is wrong with the Zaurus version.
-
Well, I've compiled Firefox 1.5.0.4 from yesterday's mozilla's cvs, but it still seems to have the same problem.
-albertr
-
Well, I've compiled Firefox 1.5.0.4 from yesterday's mozilla's cvs, but it still seems to have the same problem.
-albertr
[div align=\"right\"][a href=\"index.php?act=findpost&pid=128069\"][{POST_SNAPBACK}][/a][/div]
I think the culprit is somewhere between libgnomeprint, libgnomeprintui, fontconfig and freetype2
abiword and firefox and other apps all use the libgnomeprint library to print. libgnomeprint is the one that generates the pdf and ps files. however, libgnomeprint also uses freetype2 and fontconfig to determine the font characteristics to generate the fies and somewhere there its getting confused and that results in garbage being generated.
it works in pdaX86 and I got it to work under X/Qt, but pdaXrom zaurus version seems broke. i tried duplicating the exact fonts and configs, but no luck so far
-
Could be that, or just mozilla's postscript engine gets borked on arm platform (gcc optimization?)... I'm not a postscript expert, but take a look at the attached diff - doesn't it look like pagesize and color values got set incorrectly?
-albertr
-
Just out of curiosity, I've compiled firefox 1.5.0.3 with debian patches hoping mostly on debian patches, since Debian claims to support it on ARM, but unfortunately it didn't help with printing problem. So, like Meanie mentioned before, it looks more like pdaXrom-specific issue.
-albertr
-
Meanie, what happened to your Abiword package?
I'm trying to setup printing to my usb printer. Abiword crashes when I tell it to print (to ps) as well. What packages would I need to print documents from Abiword --> printer (epson for testing, in the end I'll be using a linux-compatible samsung laser printer)?
When I run an lpstat, everything looks ok, but when I try to print a text file it says "lpr: unsupported format 'text/plain'!".
If I try to print a postscript file I get "lpr: Unsupported format 'application/postscript'!".
So I guess being able to print to postscript won't help me either. I need to know what programs are involved in the printing process from "document in Abiword" --> usb printer.
Any help would be greatly appreciated.