John Andersen wrote:

I vaguely remember this conversation. There was another option offered of installing a pdf printer in cups and just printing that way. Did you get a chance to test that approach?

Hi John, I tried to convert the odt file to pdf both by using the export to pdf in the dropdown list, and by using the print to file method. All the pdf's produced were by the export to pdf list. When I try to print to a file, I am not having any success. I don't know if I have forgotten how to do it, or what. I select the print to file option on the print dialog box, but it doesn't lead me where I want to go. I still have the odt file saved if you can refresh me how to do that, I will give it a try. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen wrote:

It varied by which version of the distro, but at one point It seemed to me that yast would install a pdf printer in cups for you.

probably - look in the filters however, kprinter do this for you (the print engine of kde) jdd -- Jean-Daniel Dodin Président du CULTe www.culte.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Mark Misulich wrote:

Hi, a couple of months ago I wrote about the large file sizes that I was getting when I converted a word .doc file to OO odt file, with the intention of later converting it to pdf. They were in the size of megabites. This is a bit of an ongoing saga for me, as this time I made up the newsletter for the organization using Open Office from the start, and then attempted to convert the odt file to pdf in linux. I ended up having to go back to windows in order to get the file sizes to a manageable size, the linux files were too large.

Here is a rundown of what I did. 1. I made up the newsletter using Open Office. The final file size was 198kb. Not too bad, I thought that it was going to work out as I expected the file to be smaller yet when I converted that to a pdf file.

2. I converted the odt file to pdf. The resultant pdf file was 758.8kb. I am shooting for around 200kb, but will send a file up to 300kb. Any larger and it takes too long for the dialup users to download it.

3. I tried to play around with the pdf conversion process by reducing picture quality, and/or reducing the quality of the total pdf document. I produced two other pdf's this way, and believe it or not when I reduced the quality of the document to 50% it actually produced a larger file on my first attempt. That file was 789kb. The second attempt (30% quality) was 750 kb. I decided to save the newsletter odt file in doc format to see how large it would be, before I quit linux for Windows. It came out to 270kb. I was hoping to open it in word in winxp, and then convert it to pdf. But the formatting was so messed up it was easier to start over fresh in Word. But then, they tell me it isn't going to work right when try to save it as a doc file in open office. The new word file displaying the same information (plus an extra couple of pages of text that I forgot on the copy that I produced in OO) as the newsletter produced in odt came out to 220kb.

4. Those linux pdf files were too large to use, so I went back to WinXP and made up the file in Word (220kb). I then converted that to pdf, and got a file size of 270kb. That is useable, and I don't know of any way to make it smaller in Windows unless I start removing some pictures from the newsletter.

As it stands now, I think that I will have to stick with windows for this task unless someone has a brainstorm and thinks of a way to make these linux pdf files smaller.

Mark

I have always had good luck doing it the cups way. setup is a breeze: Add the following print section to your smb.conf. testparm will complain about a global print definition inside the share. Just ignore it's complaint. [pdf-gen] path = /var/tmp guest ok = No printable = Yes comment = PDF Generator print-pdf 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/pdf" "//%L/%u" "%m" "%I" "%J" & ## print command = /home/david/bin/smbprintpdf "%s" "%H/pdf" "//%L/%u" "%m" "%I" "%J" & lpq command = /bin/true create the /usr/share/samba/scripts directory copy the following script there with 0755 permissions Also set /var/spool/samba permissions 0777 Here is the script: #!/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 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 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"` # 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 **Note, choose a good postscript print driver. I use the HP8500 Color Laserprinter driver that gives great color output with small file sizes. ***Note, the complete .pdf files are placed in ~/pdf -- David C. Rankin, J.D., P.E. Rankin Law Firm, PLLC 510 Ochiltree Street Nacogdoches, Texas 75961 Telephone: (936) 715-9333 Facsimile: (936) 715-9339 www.rankinlawfirm.com -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-06-23 at 23:10 -0400, Mark Misulich wrote:

Hi, a couple of months ago I wrote about the large file sizes that I was getting when I converted a word .doc file to OO odt file, with the intention of later converting it to pdf. They were in the size of megabites. This is a bit of an ongoing saga for me, as this time I made up the newsletter for the organization using Open Office from the start, and then attempted to convert the odt file to pdf in linux. I ended up having to go back to windows in order to get the file sizes to a manageable size, the linux files were too large.

I remember that conversation.

Here is a rundown of what I did. 1. I made up the newsletter using Open Office. The final file size was 198kb. Not too bad, I thought that it was going to work out as I expected the file to be smaller yet when I converted that to a pdf file.

The size of the .odt or .doc file has nothing to do with the size of the .pdf.

2. I converted the odt file to pdf. The resultant pdf file was 758.8kb. I am shooting for around 200kb, but will send a file up to 300kb. Any larger and it takes too long for the dialup users to download it.

Converting to PDF from the OO menu produces very good quality files (with links and indexes), but large. There are two reasons: a) the quality of the photos included and b) the fonts chosen that are included partially or in full into the PDF file. There is a bugzilla affecting b). To have more control of both points above you need to produce an intermediate .ps file, and then convert that file to .pdf using the "ps2pdf" script. Forget about the tools that print directly to PDF using cups, kprinter, etc: you loose the fine control. The choice of fonts used in your original file can have quite a big impact on the final size, so you need some experimentation there, or some knowledge. This is true for windows, too. If you want, you could create a sample file in OOo similar to your newsletter, a page or two, and let us play with it to see how much we can reduce it.

I decided to save the newsletter odt file in doc format to see how large it would be, before I quit linux for Windows. It came out to 270kb. I was hoping to open it in word in winxp, and then convert it to pdf.

You know that there is OO for windows, too. You could use OO in windows with acrobat to do the conversion to PDF with much less hassle. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIYOKftTMYHG2NR9URAgHDAJ4w72040KfgE+NzSldiC8HTsTDx+QCgiCEb hKt8ukOEF2VOysKQkua+y9s= =QhS+ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-06-24 at 14:03 +0200, Carlos E. R. wrote: ...

If you want, you could create a sample file in OOo similar to your newsletter, a page or two, and let us play with it to see how much we can reduce it.

[ received via private mail; I report results here for comments ] First quick test: Via OO export menu, at 300 dpi -> 947K (1) at 150 dpi -> 1022K (larger!) Via OO print to ps, convert via ps2pdf -> 397K (2) You see already that via ps2pdf there is an important size reduction, more that 50%. Font info (pdffonts): (1) name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- URWBookmanL-DemiBold Type 1 yes no yes 334 0 URWBookmanL-DemiBoldItal Type 1 yes no yes 339 0 URWBookmanL-Ligh Type 1 yes no yes 349 0 EAAAAA+DejaVuSans-BoldOblique TrueType yes yes yes 319 0 FAAAAA+DejaVuSans-Bold TrueType yes yes yes 314 0 GAAAAA+DejaVuSans TrueType yes yes yes 304 0 HAAAAA+Arial-BoldMT TrueType yes yes yes 324 0 URWBookmanL-LighItal Type 1 yes no yes 344 0 JAAAAA+DejaVuSans-Oblique TrueType yes yes yes 309 0 KAAAAA+Arial-BoldItalicMT TrueType yes yes yes 329 0 (2) name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- OWDFYY+URWBookmanL-DemiBold Type 1C yes yes no 8 0 VYXGFR+URWBookmanL-DemiBoldItal Type 1C yes yes no 10 0 STEJSX+URWBookmanL-Ligh Type 1C yes yes no 18 0 VWKDOV+DejaVuSans-BoldObliqueFID2HGSet1 TrueType yes yes no 30 0 PUHKTK+DejaVuSans-BoldFID1HGSet1 TrueType yes yes no 45 0 HIRYKA+DejaVuSansFID5HGSet1 TrueType yes yes no 47 0 KPSHBO+OpenSymbolFID190HGSet2 TrueType yes yes no 49 0 FHWBCU+URWBookmanL-LighItal Type 1C yes yes no 61 0 JVHKIS+DejaVuSans-ObliqueFID4HGSet1 TrueType yes yes no 64 0 QEGMJO+OpenSymbolFID190HGSet1 TrueType yes yes no 72 0 The point to notice is the "sub" column, meaning that OO embeds the entire font definition, not the subset used. This is a bug, IMO. The next step is changing the fonts, but that will be later. [...] Ok, I took a smaller piece of your file: - -rw-r--r-- 1 cer users 97K 2008-06-24 22:11 4-pages.odt I converted it to PDF via the OO converter: - -rw-r--r-- 1 cer users 481K 2008-06-24 22:12 4-pages.pdf and via intermediate .ps and ps2pdf: - -rw-r--r-- 1 cer users 157K 2008-06-24 22:16 4-pages-via_print_to_ps.pdf - -rw-r--r-- 1 cer users 4.3M 2008-06-24 22:15 4-pages-via_print_to_ps.ps So, the ps2pdf converter produces a pdf file about three times smaller. The font info is: cer@nimrodel:~/tmp/OOPDF> pdffonts 4-pages.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- URWBookmanL-DemiBold Type 1 yes no yes 169 0 URWBookmanL-DemiBoldItal Type 1 yes no yes 174 0 URWBookmanL-Ligh Type 1 yes no yes 164 0 EAAAAA+DejaVuSans-BoldOblique TrueType yes yes yes 159 0 cer@nimrodel:~/tmp/OOPDF> pdffonts 4-pages-via_print_to_ps.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- WOOWVU+URWBookmanL-DemiBold Type 1C yes yes no 8 0 UMPCZU+URWBookmanL-DemiBoldItal Type 1C yes yes no 10 0 ZIOPXQ+URWBookmanL-Ligh Type 1C yes yes no 18 0 VWKDOV+DejaVuSans-BoldObliqueFID2HGSet1 TrueType yes yes no 30 0 The different size is probably that ps2pdf embeds a subset of the fonts, and OO embeds the complete set (plus graphic defaults). Now, I analyze the .odt file. The first detail I notice is that you are not using styles. The default style uses the DejaVuSans font, but then you modify each paragraph to use a variation of URW Bookman L. It is more efficient to first modify the default style to use your font of choice, and any other thing you modify, and then create more styles for each type of paragraph you use. This way, by simply modifying the style, in one stroke you modify the settings for the whole file, in a consistent way. The next step is choosing the fonts that do not need to be embed. Have a look at the list here: http://lists.opensuse.org/opensuse/2008-04/msg01610.html http://lists.opensuse.org/opensuse/2008-04/msg01616.html These fonts do not need to be embedded, or rather should not: | 19. Bookman-Demi | 20. Bookman-DemiItalic | 21. Bookman-Light | 22. Bookman-LightItalic But those are not the same that you are using, those are the so called printer fonts. To see them in OO you need to go to option, writer, compatibility options, and enable "use printer metrics". Then, you can select "Bookman" instead which might, only might, do the trick (it doesn't). - -rw-r--r-- 1 cer users 160K 2008-06-24 22:17 4-pages-mod-via_print_to_ps.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- WOOWVU+Bookman-Demi Type 1C yes yes no 8 0 XQKHNR+Bookman-DemiItalic Type 1C yes yes no 10 0 ZIOPXQ+Bookman-Light Type 1C yes yes no 19 0 OOHPAU+URWBookmanL-DemiBoldItal Type 1C yes yes no 21 0 VWKDOV+DejaVuSans-BoldObliqueFID2HGSet1 TrueType yes yes no 27 You see that the dejavu font is still used? I find it on blank lines. I change them to Bookman, and the change in size is: - -rw-r--r-- 1 cer users 152K 2008-06-24 22:23 4-pages-mod-via_print_to_ps.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- WOOWVU+Bookman-Demi Type 1C yes yes no 8 0 UMPCZU+Bookman-DemiItalic Type 1C yes yes no 10 0 ZIOPXQ+Bookman-Light Type 1C yes yes no 19 0 See? DejaVuSans-BoldOblique uses 8 Kb for some useless white lines. Now I do a quick change, and switch to "Times": - -rw-r--r-- 1 cer users 135K 2008-06-25 00:03 4-pages-mod-via_print_to_ps-times.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- Times-BoldItalic Type 1 no no no 8 0 Times-Roman Type 1 no no no 7 0 Times-Bold Type 1 no no no 9 0 Notice that this font is not embedded at all, it uses the internal font of the reader. We have gone from the initial 160 down to 135 just playing withfonts. Of course, the alignment and placements have gone out of the board, but this was intended as a test only :-) The internal OO converter gives a much larger size: - -rw-r--r-- 1 cer users 474K 2008-06-25 00:09 4-pages-mod-2.pdf name type emb sub uni object ID - ------------------------------------ ----------------- --- --- --- --------- NimbusRomNo9L-Medi Type 1 yes no yes 158 0 NimbusRomNo9L-MediItal Type 1 yes no yes 163 0 NimbusRomNo9L-Regu Type 1 yes no yes 168 0 What?? This is broken, it should be using "Times", not nimbus. Another Bug :-/ Oh, well... my point is proven ;-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIYYLbtTMYHG2NR9URAtU4AKCHqEKcDHHCH4kVL731QIucl3HTBACdF/ne n32rpxPq/JgY3Oa/hz26Hgs= =l79z -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org