Hi, I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char). PS. I'm going to convert doc/xls files from wine Codeweavers Office. Any links? Regards and Thanks, -- Marek Chlopek
Hi,
I'm looking for working well pdf converter. Printing to pdf in KDE
ps2pdf and other *2pdf from ghostscript-library.
unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Uh. If you find an application that can read DOC/XLS and at the same time write to a format you find a pdfconverter for...
Any links?
<a href="">SCNR</a> Jan Engelhardt --
Marek Chlopek wrote:
Hi,
I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
On Wednesday 13 September 2006 12:58, James Knott wrote:
Marek Chlopek wrote:
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
i'll second that. OOo produces astoundingly good PDF output. And it can import Word docs really well. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
i'll second that. OOo produces astoundingly good PDF output. And it can import Word docs really well.
It does fail to open its own files, though. Jan Engelhardt --
On Wednesday 13 September 2006 13:10, Jan Engelhardt wrote:
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
i'll second that. OOo produces astoundingly good PDF output. And it can import Word docs really well.
It does fail to open its own files, though.
i've only had this problem when opening files written with a pre-2.0 OOo beta which was shipped with one of the Suse 9.x releases. It's XML schema was different (incompatible) with that of the final OOo 2.0 release, which hosed opening of many (if not all) OOo word docs. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
i'll second that. OOo produces astoundingly good PDF output. And it can import Word docs really well.
It does fail to open its own files, though.
i've only had this problem when opening files written with a pre-2.0 OOo beta which was shipped with one of the Suse 9.x releases. It's XML schema was different (incompatible) with that of the final OOo 2.0 release, which hosed opening of many (if not all) OOo word docs.
The ODT was written in OOO-1.?-Win32, and I tried to open it using OOO-1.1.1-20.i586.rpm on SLES9. OOO displayed an empty doc. Jan Engelhardt --
On Wednesday 13 September 2006 13:32, Jan Engelhardt wrote:
The ODT was written in OOO-1.?-Win32, and I tried to open it using OOO-1.1.1-20.i586.rpm on SLES9. OOO displayed an empty doc.
ODT is the new OASIS format, native to OOO 2. In the 1.x series you need 1.1.5 to work with it
The ODT was written in OOO-1.?-Win32, and I tried to open it using OOO-1.1.1-20.i586.rpm on SLES9. OOO displayed an empty doc.
ODT is the new OASIS format, native to OOO 2. In the 1.x series you need 1.1.5 to work with it
Ah thanks for mentioning. Jan Engelhardt --
On Wednesday 13 September 2006 12:03, stephan beal wrote:
i'll second that. OOo produces astoundingly good PDF output. And it can import Word docs really well.
Hmm, I found that the PDFs produced by OO's internal PDF convertor are _huge_ compared to the same file printed to KPrinter and then converted to PDF there. So, I tend to use KPrinter's converter most of the time. I haven't had problems with this, but if there are odd characters or otherwise broken output from there, then yes, the OO one does work very well, and might fix the problem. Now, at the other end of the toolchain, I agree that OO's import of MS document formats is very good, it still breaks sometimes. Therefore, how about (as an alternative route) installing a generic PostScript printer driver on the Windows side (haven't used Crossover so don't know how this would be done there), printing to PostScript from Word / Excel, then using the already-mentioned ps2pdf tool to make the PDF. If OO can't import the MS documents well enough, then perhaps ps2pdf will do a good enough job on the PostScript.
On Wednesday, 13 September 2006 13:12, William Gallafent wrote:
Therefore, how about (as an alternative route) installing a generic PostScript printer driver on the Windows side (haven't used Crossover so don't know how this would be done there), printing to PostScript from Word / Excel, then using the already-mentioned ps2pdf tool to make the PDF. If OO can't import the MS documents well enough, then perhaps ps2pdf will do a good enough job on the PostScript.
thanks all. this above advise seems to be worth to examine. i personally prefer to use OOo but business documents can not be imported into OOo without mistakes. All the best, -- Marek Chlopek
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-09-13 at 13:35 +0200, Marek Chlopek wrote:
Therefore, how about (as an alternative route) installing a generic PostScript printer driver on the Windows side (haven't used Crossover so don't know how this would be done there), printing to PostScript from Word / Excel, then using the already-mentioned ps2pdf tool to make the PDF. If OO can't import the MS documents well enough, then perhaps ps2pdf will do a good enough job on the PostScript.
this above advise seems to be worth to examine. i personally prefer to use OOo but business documents can not be imported into OOo without mistakes.
If you want to create PDFs in the windows side, try PDFcreator. It installs as a printer, and needs ghostscript, I think. The results are pretty good. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFB/WjtTMYHG2NR9URAjHZAJwJ7LNW720vJD+kNjuMeSAO4AJwqQCeP5ah PPFWb+I8FOlyABsoBGoWmzE= =Exxs -----END PGP SIGNATURE-----
On Wednesday, 13 September 2006 14:12, Carlos E. R. wrote:
If you want to create PDFs in the windows side, try PDFcreator. It installs as a printer, and needs ghostscript, I think. The results are pretty good.
nope. i would like to avoid using windows. i'm just not happy with kde print to pdf feature and was asking about any other solution. thanks, -- Marek Chlopek
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Wednesday 2006-09-13 at 17:13 +0200, Marek Chlopek wrote:
On Wednesday, 13 September 2006 14:12, Carlos E. R. wrote:
If you want to create PDFs in the windows side, try PDFcreator. It installs as a printer, and needs ghostscript, I think. The results are pretty good.
nope. i would like to avoid using windows. i'm just not happy with kde print to pdf feature and was asking about any other solution.
Ah. I thought you said you where using wine. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (GNU/Linux) Comment: Made with pgp4pine 1.76 iD8DBQFFCE7LtTMYHG2NR9URAthJAJ9DPP6uc8YP0zx4i9/X82gxkHVKugCcDKPT uT5Pq+54A+OaSKSvmd/yotE= =j/cN -----END PGP SIGNATURE-----
From: "Marek Chlopek" <mchlopek@post.pl>
On Wednesday, 13 September 2006 13:12, William Gallafent wrote:
Therefore, how about (as an alternative route) installing a generic PostScript printer driver on the Windows side (haven't used Crossover so don't know how this would be done there), printing to PostScript from Word / Excel, then using the already-mentioned ps2pdf tool to make the PDF. If OO can't import the MS documents well enough, then perhaps ps2pdf will do a good enough job on the PostScript.
thanks all.
this above advise seems to be worth to examine. i personally prefer to use OOo but business documents can not be imported into OOo without mistakes.
See my previous post for a working setup of printing from windows directly to pdf via samba. The .pdf files are created in the users home directory on the linux box. http://linux.derkeiler.com/Mailing-Lists/SuSE/2005-08/2043.html Here is the entire post: Mates, I apologize to the cannibalizing distributions, but in having problems with pdf-gen or, as otherwise known, print-pdf, I thought I would share a little on just how easy it actually is to get working on any system. The cannibalizing involved taking the mdk print-pdf script and dumping it into SuSE -- nothing less than blasphemy. Anyway it works. BACKGROUND I had pdf-gen working on mdk 2005LE as a new box to replace the 7.2 box at work. After transition, pdf-gen was reporting "out of memory" errors on XP clients. Made no sense, since (no pun intended) it was working fine on the new box before adding additional shares. So I dug into print-pdf to try and get it working. TEST -SETTING IT UP ON SUSE To troubleshoot, I thought I would start from scratch and try and get it working on my SuSE 9.0 server at home which had no such capability. I figured I could learn how it worked in the process and then fix the 2005LE box at work. The basic process was: (1) to copy the mdk print-pdf script to the SuSE box. That is the: [david@bonza scripts]$ ll /usr/share/samba/scripts/ total 12 -rwxr-xr-x 1 root root 3555 Apr 4 09:03 print-pdf* (note file permissions) The actual script is: ****************************** #!/bin/bash # samba-print-pdf # This is a script which allows you to set up a virtual printer on samba # which will take the file (generated by a postscript filter on windows) # and turn it into a PDF, informing the user of where it is when it # is done # # (c) Buchan Milne <bgmilne@cae.co.za> 2002 # License: GPLv2 # Changelog # v0.0.6 20030428 # - Allow options passed as env. variables from print command # - Inline and simplify sed (use tr) clean script # - Ensure file arrives in PREFIX even if TEMP is used without provided name # - Changes from Joshua M. Schmidlkofer <joshua@imr-net.com> 20030425 # - Debugging, adjustments, and corrections. # - Stupid sed sanitizing script. [probably horribly inefficient also]. # - Temp file usage cleanup. # v0.0.5 20020723 # - Add support for preset settings # - Allow passing of filename provided by client as final filename # # Arguments: # $1 = file (usually passed with %s from samba) # $2 = unix prefix to where to place the file (~%u should work) # $3 = windows prefix to the same location (//%L/%u should work) # $4 = user/computer to send a notification to (%u or %m) # $5 = IP address of client (%I) # $6 = Name of destination file without extension (%J) # $7 = PDF setting (prepress,print,screen etc) # # If you want to customise any of the following configuration defaults, # you can place them in the file /etc/samba/print-pdf.conf. # If you need to modify anything in this script, please provide me with your # changes, preferably in such a way that the changes are configurable. PS2PDF=ps2pdf13 OPTIONS="-dAutoFilterColorImages=false -sColorImageFilter=FlateEncode" #Values taken from arguments: INPUT=$1 PREFIX="$2" WINBASE=$(echo "$3"|sed -e 's,/,\\\\,g') #NAME=`echo "$6"|sed -e 's/[&/:{}\\\[<>$#@*^!?=|]/-/g;s/\]/-/g'` NAME=`echo "$6"|tr '[:punct:]' '[-*]'` # Source config file if it exists: CONFFILE=/etc/samba/print-pdf.conf [ -e $CONFFILE ] && . $CONFFILE #Values not taken as arguments, could be set via env. vars (?) or config file KEEP_PS=${KEEP_PS=0} PERMS=${PERMS=640} BASEFILE=${BASEFILE=pdf-service} TEMP="${TEMP=$2}" UMASK=${UMASK=006} #Make sure that destination directory exists mkdir -p "$PREFIX" INFILE=$(basename $INPUT) umask $UMASK [ -n "$NAME" ] && TEMP="$PREFIX" #make a temp file to use for the output of the PDF OUTPUT=`mktemp -q $TEMP/$BASEFILE-XXXXXX` if [ $? -ne 0 ]; then echo "$0: Can't create temp file $TEMP/$OUTPUT, exiting..." exit 1 fi if [ -n "$NAME" ]; then FINALOUTPUT="$PREFIX/$NAME" else FINALOUTPUT="$OUTPUT" fi if [ -n "$7" ]; then OPTIONS="$OPTIONS -dPDFSETTINGS=/${7#pdf-}" else OPTIONS="$OPTIONS -dPDFSETTINGS=/default" fi WIN_OUTPUT="$WINBASE\\"`basename "$FINALOUTPUT"` #mv "$INPUT" "$INPUT.ps";INPUT="$INPUT.ps" # create the pdf $PS2PDF $OPTIONS "$INPUT" "$OUTPUT.pdf" >/dev/null 2>&1 mv -f "${OUTPUT}.pdf" "${FINALOUTPUT}".pdf # Generate a message to send to the user, and deal with the original file: MESSAGE=$(echo "Your PDF file has been created as $WIN_OUTPUT.pdf\n") # Cleanup if [ $KEEP_PS != 0 ];then mv -f $INPUT "${FINALOUTPUT}".ps MESSAGE=$(echo "$MESSAGE and your postscript file as $WIN_OUTPUT.ps") # Fix permissions on the generated files chmod $PERMS "${FINALOUTPUT}".ps "${FINALOUTPUT}".pdf else rm -f $INPUT # Fix permissions on the generated files chmod $PERMS "${FINALOUTPUT}".pdf fi #Remove empty file from mktemp: rm -f $OUTPUT # Send notification to user echo -e $MESSAGE|smbclient -M $4 -I $5 -U "PDF Generator" >/dev/null 2>&1 ****************************** literally .... copy and paste it into ... /usr/share/samba/scripts/print-pdf on whatever box you are using The permissions are: [david@bonza scripts]$ ls -al /usr/share/samba/scripts/ total 20 drwxr-xr-x 2 root root 4096 Jul 16 10:24 ./ drwxr-xr-x 3 root root 4096 Apr 4 09:03 ../ -rwxr-xr-x 1 root root 3555 Apr 4 09:03 print-pdf* -rwxr-x--- 1 root adm 5757 Apr 4 09:03 smb-migrate* (2) Confirm you have ps2pdf13 installed or edit the script to work with what you do have. You will at least have one of the following if you have ghostscript installed: skyline:/home/david # ls /usr/bin/ps2* /usr/bin/ps2ascii /usr/bin/ps2frag /usr/bin/ps2pdf12 /usr/bin/ps2pdf14 /usr/bin/ps2pk /usr/bin/ps2epsi /usr/bin/ps2pdf /usr/bin/ps2pdf13 /usr/bin/ps2pdfwr /usr/bin/ps2ps (3) Then, just edit /etc/samba/smb.conf and add the following share: [pdf-gen] path = /var/tmp guest ok = No printable = Yes comment = PDF Generator (only valid users) printing = bsd printcap name = cups #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP & print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" & lpq command = /bin/true (4) Then (run testparm -- always; and (5) restart Samba): testparm will complain about a global print definition inside a share, but that can be ignored. On SuSE (as root): rcsmb restart On mdk (as root): /etc/rc.d/init.d/smb restart (6) Then from M$ clients, browse to the pdf-gen share and double-click it or control panel - printers - add printer - network and select it. Choose OK to 'manually select' the driver. Choose one of the latest HP Laserjet postscript (PS) drivers; (eg. Laserjet 8150 color PS, or Laserjet 6P/6.. PS, or Laserjet 5, etc.. That's it, that's all it takes! Open Word, (choose your most used app), select pdf-gen as your printer and BINGO your pdf is created in the users home directory -- no questions asked. Damn slick! (but it still hasn't solved my original problem, but -- learning has occurred) But FWIIW, I thought I would post it. YMMV. But from simply having to dump a mdk script onto suse, confirm that ps2pdf13 was there, set the permissions, add a share to smb.conf, add a printer to the weak clients and presto -- your done, your printing to pdf from anywhere. Anyway, I thought it was cool. -- David C. Rankin, J.D., P.E. RANKIN LAW FIRM, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 (936) 715-9333 (936) 715-9339 fax www.rankinlawfirm.com --
On Wednesday 13 September 2006 06:58, James Knott wrote:
Marek Chlopek wrote:
Hi,
I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Why not use OpenOffice? It works with MS Office files and can export PDF.
I second the motion. When our QA dept let the tech writer go nobody could figure out how to get into his computer for a while and they needed to release a specification document for customers. When they asked for help I donned my Super Penguin costume, loaded their large MS Word document in OOo and saved it as PDF. Looked fabulous.
Marek Chlopek wrote:
I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
Bad spacing around specific characters often means there's a problem with the particular font. Cheers, Dave
On Wednesday 13 September 2006 12:02, Marek Chlopek wrote:
I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Just coincidentally, this showed up via newsforge today: http://news.com.com/2100-1012_3-6114752.html It's for Office 2007, so you'll apparently have to wait a while before you can use it. -- ----- stephan@s11n.net http://s11n.net "...pleasure is a grace and is not obedient to the commands of the will." -- Alan W. Watts
On Wed, 2006-09-13 at 13:23 +0200, stephan beal wrote:
On Wednesday 13 September 2006 12:02, Marek Chlopek wrote:
I'm looking for working well pdf converter. Printing to pdf in KDE unfortunately do not produce acceptable documents (there are some errors around letters X or $ char).
PS. I'm going to convert doc/xls files from wine Codeweavers Office.
Just coincidentally, this showed up via newsforge today:
http://news.com.com/2100-1012_3-6114752.html
It's for Office 2007, so you'll apparently have to wait a while before you can use it.
Well considering Windows 1993 came out in 1995 I figure Office 2007 will be out in 2010 if ever. -- ___ _ _ _ ____ _ _ _ | | | | [__ | | | |___ |_|_| ___] | \/
On Friday 15 September 2006 01:04, M Harris wrote:
By 2010 M$ will be dead.
Au Contraire, mon ami! With 80% of the world's computers now running some version of Windows with all that business software, with the federal gummit committed to M$ AND considering the resistance to change in business, I would bet that it's going to take a long, long time to get rid of M$. Just because something smells dead does not make it so. Fred
On Fri, 2006-09-15 at 06:56 -0500, Stevens wrote:
On Friday 15 September 2006 01:04, M Harris wrote:
By 2010 M$ will be dead.
Au Contraire, mon ami!
With 80% of the world's computers now running some version of Windows with all that business software, with the federal gummit committed to M$ AND considering the resistance to change in business, I would bet that it's going to take a long, long time to get rid of M$. Just because something smells dead does not make it so.
Fred
No Fred, he probably means, by 2010 all installed window/office appication come from CD's copied in china ;-) -- pgp-id: 926EBB12 pgp-fingerprint: BE97 1CBF FAC4 236C 4A73 F76E EDFC D032 926E BB12 Registered linux user: 75761 (http://counter.li.org)
participants (14)
-
Anders Johansson -
Carl William Spitzer IV -
Carlos E. R. -
Dave Howorth -
David Rankin -
Hans Witvliet -
James Knott -
Jan Engelhardt -
Ken Jennings -
M Harris -
Marek Chlopek -
stephan beal -
Stevens -
William Gallafent