RDC XI R2 - Documentation for pdf export registry options

Where can we find documentation explaining the various registry options for controlling pdf export behavior?
For example, ForceLargerFonts, UsePrecisePositioningForText, etc...

Actually you can find a kbase and blog...
http://www.sdn.sap.com/irj/scn/advancedsearch?query=1435991
Short story is, set for CR 2008 but I verified from our source code it does exist in XI R2 also:
How to enable the registry keys for PDF exporting?
- Open the regedit on the machine and set the registry key at the similar location below:
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0Crystal ReportsExportPDF]
The following are the registry keys for PDF exporting:
u2022 ForceLargerFonts
Purpose: To deal with text truncation issues.
Value:
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 12.0Crystal ReportsExportpdf]
"ForceLargerFonts"=dword:00000001
0 u2013 disable
1 - enable
u2022 UsePrecisePositioningForText and TruncationAdjustment
Purpose: When "ForceLargerFonts" doesn't work, implement this one. This one is to deal with text truncation issues as well.
How to use:
The new behaviour is controlled by two registry keys,
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.0Crystal ReportsExportPdf]
"UsePrecisePositioningForText"=dword:00000001
[HKEY_LOCAL_MACHINESOFTWAREBusiness ObjectsSuite 11.0Crystal ReportsExportPdf]
"TruncationAdjustment"=dword:00000005
The new behaviour is turned on when u201CUsePrecisePositioningForTextu201D is set to 1.
u201CTruncationAdjustmentu201D is used for adjusting rounding. Itu2019s only activated when u201CUsePrecisePositioningForTextu201D is set to 1. Its valid values are 0 to 10. Default value 5 should be sufficient for eliminating virtually all truncation issues.
Itu2019s worth mentioning that u201CForceLargerFontsu201D setting is ignored when u201CUsePrecisePositioningForTextu201D is set to 1.

Similar Messages

Best documentation for import/export

Can some one please point me towards the best documentation for import/export.
Thank you very much.

The "Document not found" error is a nice touch on the
above link.The 9.0.2.2 and 9.0.2.6 Portal Export/Import FAQs have moved to the following locations:
Portal 9.0.2.2/9.0.2.3 FAQ for Portal Export/Import:
http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/DEPLOY_PERFORM/9023_EXPORT_IMPORT_FAQ_0308.HTM
Portal 9.0.2.6 FAQ for Portal Export/Import:
http://portalstudio.oracle.com/pls/ops/docs/FOLDER/COMMUNITY/OTN_CONTENT/MAINPAGE/DEPLOY_PERFORM/9026_EXPORT_IMPORT_FAQ_0308.HTM
Also, be sure to review the Chapter on Portal Export/Import in the Portal Configuration Guide (for 9.0.2.6/9.0.4/10g) here:
Portal Export/Import for the 10g (Portal 9.0.4) release is documented in detail in chapter 10 - The Portal Export/Import chapter in the Portal Configuration Guide.
The Portal Configuration guide can be downloaded/accessed at the following links on the Oracle Technology Network:
Acrobat PDF version (6MB): http://download-west.oracle.com/docs/cd/B10464_03/portal.904/b13675.pdf
Link to Chapter 10 (HTML version): http://download-west.oracle.com/docs/cd/B10464_03/portal.904/b13675/cg_imex.htm#i1030999
Best Regards,
Harry

Why pay for pdf Export if I am a member of Adobe Applications?

Why pay for pdf Export if I am a member of Adobe Applications? This membership was supposed to include each and every Adobe Applications?

Absolutely no reason. Because Adobe Acrobat includes this function already. It's just a service for people without Acrobat.

PDF export format options are ignored when exporting

I can't get the PDF export format options to work. No exception is thrown; it's as though the export format options are simply ignored. In broad terms, the relevant code looks like this:
ExportOptions exportOptions = new ExportOptions();
exportOptions.setExportFormatType(ReportExportFormat.PDF);
PDFExportFormatOptions pdfExportOptions = new PDFExportFormatOptions();
pdfExportOptions.setCreateBookmarksFromGroupTree(true);
exportOptions.setFormatOptions(pdfExportOptions);
ByteArrayInputStream byteArrayInputStream =
(ByteArrayInputStream)reportClientDoc.getPrintOutputController().export(exportOptions);
Other options (setting start and end pages for export) are also ignored.
Curiously, I am able to apply export format options just fine for other formats; e.g. when setting the export format type to ReportExportFormat.characterSeparatedValues and using a CharacterSeparatedValuesExportFormatOptions object as appropriate, I am able to set options like delimiter and separator just fine.
How can I prevent the PDF export format options from being ignored?

hi
Are you using RAS or Crystal Report runtime? and what's the version? It might be a bug. Have you tried:
ByteArrayInputStream byteArrayInputStream =
(ByteArrayInputStream)reportClientDoc.getPrintOutputController().export(ReportExportFormat.PDF);
and does it work?

Allow pdfmark processing for PDF export

The title says it all. Right now we could insert pdfmarks backhandedly through placed EPS files (amongst others). But that does mean to go the Distiller way to process them.
Maybe a souped-up PDF export filter can handle that; eg. by checking a new feature called "Enable pdfmark processing" in an "Expert" section.
And if you wonder what a pdfmark is, read the following:
http://livedocs.adobe.com/acrobat_sdk/9.1/Acrobat9_1_HTMLHelp/pdfmark_Syntax.63.2.html
Or download the SDK for Acrobat:
http://www.adobe.com/devnet/acrobat/documentation.html
I think there are numerous applications for this feature…
One tiny one would be to process a PDF so that it will open in Acrobat showing the thumbnails right from the start.
EPS code for that is:
%!PS-Adobe-3.0 EPSF-3.0
%%BoundingBox: 0 0 144 144
%%EndProlog
/pdfmark where {pop} {userdict /pdfmark /cleartomark load put} ifelse
[ {Catalog} << /PageMode /UseThumbs >> /PUT pdfmark
%%EOF
Uwe

Hello Dov,
Here is my bit of postscript.
<< /Subtype /Text /Open true /Type /Annot /Popup 15 0 R /C [ 1 1 0.2500000 ]
/Rect [ 134.646 731.906 138.387 735.024 ] /Contents (Goodbye) >>
Creates an annotation 'Goodbye'.
P.

Maximum Image Quality for PDF Export

I'm having a pretty big pain with some of my images, and I wanted to make sure that when i'm exporting my document to a PDF, I'm getting the very best resolution possible. I've attached a screenshot of the settings I'm using... are these the best settings I can set for getting the best resolution from my PDF
export?

First, the cost of printng isn't necessarily directly related to quality. There are too many factors such as full color and additional spot plates, the size of the run, and the size and type of the press to make any judgements based on price, not to mention the skill and standards of the printer. And then you still have many printers willing to do the same quality work at a variety of prices depending on location, market, and how busy they are. Kind of like making a genearlization about the price of a car.
@ Luke, setting downsampling to none will guarantee that all images are sent at full resolution, but that isn't necessarily a good thing. As already pointed out there is no advantage in sending more data than required to print the image. The OP has alread chosen ZIP compression, which is lossless, so he isn't introducing any jpeg artifacts, so all the downsampling is doing is setting a ceiling above which images will be downsampled. Images below that threshold will be sent at full res.

I Paid for PDF Export and the files are not converting correctly

I purchased PDF Export to take a PDF file and convert it to a text file so I could import it into excel, when doing so I get a bunch of extra symbles plus the numbers that i'm trying to convert are not complete.

Could you try disabling the 'Recognize text' function and convert the file again?
Let us know how it goes!
-David

PageMaker 6.5 set default PostScript printer for PDF export

My boss uses PageMaker 6.5 and it appears when she uses the Export to PDF option it is selecting a PostScript printer at random and asking it to "print to file" to create the PostScript file that it later gives to Distiller to create the PDF. The problem is, she has a "virtual PDF print driver" installed that is not unlike the Adobe PDF printer driver, except it either doesn't support "print to file" or maybe just doesn't like something about the way PageMaker is using it. It works great from other apps, but not PageMaker. Anyway, is there a way to force PageMaker to use a specific PS printer for this, instead of picking the first one it finds? I thought it might be alphabetical order based on driver or printer name, or port name, but I've tried changing all of those, and no luck. I did install a new PS printer, and that worked for a bit (so I assumed it was using the most recent printer installed), but now it is selecting the virtual one again, and not working... not sure why.
If she sets the default printer to Adobe PDF Printer (she has Acrobat 9), it uses that one, and everything works fine. She doesn't want to use that for her default printer though, and the printer she wants as her default isn't a PostScript printer, so PM doesn't try to use it.
Maybe a registry setting or something? Or someone that can confirm the order that PageMaker looks for a printer to use, so that I can maybe trick it in to using a specific one?

If it wasn't my boss, I'd just tell her to do that. She's been using PM for many many years, and hard to retrain yourself. Of course, this might be the best option. Seems like a weird design to "pick a printer at random" though, so hoping someone knows of some hidden option to force a specific printer.

Combining documents with multiple layouts into a single book for pdf export

I have made a series of documents that feature 3 different layouts, however I would like to connect all these documents into a book and then export 1 layout style from each document into a pdf to form a book. However when I go to the export book as pdf the option to select pages or ranges is greyed out and not clickable for some reason, does anyone know of another way to get around this short of exporting each individual document layout and then merging them as a pdf?

You need to set up the book to contain precisely what you want to export.
However, it is basically better to export single documents and merging them later as PDF, regarding colour spaces, page numbering, paragraph styles, page formats etc.

SSRS 2008 R2 - Column Headers of a tablix visible while scrolling - Then the column headers not visible on 2nd page onwards for PDF EXPORT. it's vice versa. Hence it is possible to provide both at same time ?

Hi,
I am using SSRS 2008 R2.
I have two TABLIX in a report. One is TABLIX with row/clumn grouping. 2nd one is flat view.
Here each tablix is dispaly it's data on single page for each.
My Requirement on First TABLIX is:
1. I have to make column headers visible on scrolling down
2. Export to PDF - column headers must be visible on all the pdf pages for same tablix data.
But ... either one is achieved at my end.
so ... any suggestions please to achieve both at same time.
thank you in advance.
best regards,
venkat.

Hi G.V.Naidu,
According to your description, the first tablix is matrix to use display data.
In SSRS, if we want to fix matrix header visible while scrolling and repeat header columns on each page, we can select the corresponding option to enable this function. Please refer to the steps below:
1. Right click tablix, and select Tablix Properties.
2. Select “Keep header visible while scrolling” and “Repeat header rows on each page” to enable these function.
If we are use table to display data, please refer to the article about Repeat Header / Keep Header Visible in Tables.
http://blogs.msdn.com/b/robertbruckner/archive/2008/10/13/repeat-header-and-visible-fixed-header-table.aspx
If there are any misunderstanding, please feel free to let me know.
Regards,
Alisa Tang
Alisa Tang
TechNet Community Support

Linking between books for PDF export

Does anyone have any suggestions as to how to go about setting up links between books in such a way that they'll export to PDF? Here's my scenario: I have two books (indb files with many indd files each). One of the books needs to link to text anchors I've set up in the other. However, linking between the files doesn't work because each book is exported as a single PDF. I had planned to merge the files of the book that is being linked to prior to creating the links, but no matter what I try, Move Pages causes reflow (and given the length and intricacy of the documents I'm sure it's not worth the time to try to fix the reflow; I'd be better off linking the PDF by hand).
Is this just not a possible workflow? I considered linking to a 'dummy' file that was named like my second book is named, but from what I can tell ID doesn't really export the text anchors in any usable fashion; you either get the links when you export or you can't massage them into being. Any advice would be appreciated.

This is an interesting suggestion, but I'm not sure how it would work. I've tried outputting one PDF from this combo-indb file and then extracting the pages out into separate PDFs, but the links are lost. I've also tried selecting just the files from each of the actual books within the combo-indb and exporting PDFs for each one, but in that case it assumes it's looking for an anchor within the same PDF. Did you have another approach in mind?

Page X of Y functionality for PDF export in OBIEE

Hi,
Can any one of you please let me know how to implement page 1(2) and page 2(2) functionality in OBIEE when we export in PDF. Its very urgent requirement for us.

Hi,
Go to edit your report,
look at your PDF Control setting and use below syntax this will give u no of pages for each report
Sample report name @{pageNumber} of @{numberOfPages}
Thanks
Deva

Setting default magnification for PDF export

I've created a PDF in InDesign with image files in it. The image files are scaled to look good at a certain resolution & magnification. However, when I export my InDesign document to PDF, and then open the PDF, for some reason the PDF opens at 125% magnification. This makes the images look bad.
Is there some way I can limit the size the PDF can be opened at, or at least set the default size so the user won't be viewing it at a larger size than I intended?

Yes, but you have to do it in Acrobat.
File>Properties>Initial View
Bob

How to select color space for PDF export in Aperture 3

If you're exporting a book layout as a PDF for printing by a third-party album company, you may need to specify sRGB as the color space for images in the PDF. That's OK if your book is composed of JPEGs that are already in the sRGB color space. But, if your images are RAW, Aperture will export them into PDF using the Adobe RGB color space by default. Sending aRGB images to an sRGB printer will result in flat, unsaturated colors, as I learned the hard way. Apple tech support was unable to tell me how to handle this, but I stumbled on the answer myself. Select the book in the Library pane. Select File > Print Book. In the resulting printer dialogue window, pull down the Color Profile menu (default: No Profile Selected) and select sRGB or whatever target color space you desire. Then, click the PDF button and select Save as PDF. Presto! Your PDF images will now be in the appropriate color space.

Hi again, here some updates.
the issue is still there.
From Aperture, I tried to export to PDF the single images, and they look good (no posterization).
Furthermore, I created a photo book from iPhoto with the same pictures, and exported it to PDF. It also looks fine.
Also opening/exporting to PDF from photoshop does not show any problem.
The problem occurs only if I try to print the book from Aperture (option "print book" -> "save as PDF"), or if I make a book preview before placing the order (I suppose it's the same action).
Is anybody aware of what exactly Aperture does in these particular cases?
Please consider that:
1. my monitor (iMac 24") is hardware calibrated
2. the source pictures are in RAW (so no color profile on them) and (just a couple) in TIFF (16bit, Adobe RGB). I also tried reimporting in the album jpg converted versions, with no better results.
3. OS and Aperture are updated to the latest versions.
This problem is blocking me from placing the order...
Someone could give some help here?
thanks in advance
marco

Is Outside In's PDF Export library's function EXOpenExport thread-safe?

I'm writing a C++ wrapper, for Node.js, around the Outside In PDF Export library, on Ubuntu Linux. Node.js has a single threaded event loop and therefor any long-running processing is done on a worker thread. So, my wrapper is calling all of the PDF Export methods inside of this worker thread. I mention this so that you can be sure of two things: this is a threaded environment, and all PDF Export functions are being called on the same worker thread. Also, I am not making use of any redirected IO or PDF Export-handled threading. I've initialized the library specifying to use no threads. So all of this processing should be occuring within the thread that I call the functions on.
Everything seems to go fine when exporting a single PDF or even maybe two or three in quick succession. When I up the number of PDFs that I try to export to 5+, I receive a SIGSEGV segementation fault from within the OIT libs. The back trace is below:
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4fd0700 (LWP 1577)]
0x00007fffeef1da26 in HandlePoolCreateHandle () from /usr/local/lib/pdfexport/libwv_core.so
(gdb) bt
#0 0x00007fffeef1da26 in HandlePoolCreateHandle () from /usr/local/lib/pdfexport/libwv_core.so
#1 0x00007fffeef1925d in Win32VCreateHandle () from /usr/local/lib/pdfexport/libwv_core.so
#2 0x00007fffed49046b in WrapBrush(void*, GdiBrush*) () from /usr/local/lib/pdfexport/libos_pdf.so
#3 0x00007fffed46e8c8 in ?? () from /usr/local/lib/pdfexport/libos_pdf.so
#4 0x00007fffed46df63 in GNGetOutputSolutionInfoAt () from /usr/local/lib/pdfexport/libos_pdf.so
#5 0x00007fffeef1e32a in ?? () from /usr/local/lib/pdfexport/libwv_core.so
#6 0x00007fffeef1e214 in ?? () from /usr/local/lib/pdfexport/libwv_core.so
#7 0x00007fffeef18ed3 in Win32VLoadOS () from /usr/local/lib/pdfexport/libwv_core.so
#8 0x00007fffeddffb24 in VwExportOpen () from /usr/local/lib/pdfexport/libex_pagelayout.so
#9 0x00007ffff4062c4d in FAOpenExport () from /usr/local/lib/pdfexport/libsc_fa.so
#10 0x00007ffff7e53270 in EXOpenExport () from /usr/local/lib/pdfexport/libsc_ex.so
#11 0x00007ffff43c0a4d in topdf_convert(uv_work_s*) ()
from /home/ryan/repos/pdf-service/node_modules/topdf/build/Release/topdf.node
#12 0x00000000006e2ec7 in worker (arg=<optimized out>) at ../deps/uv/src/unix/threadpool.c:65
#13 0x00007ffff6fa6e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#14 0x00007ffff6cd3cbd in clone () from /lib/x86_64-linux-gnu/libc.so.6
#15 0x0000000000000000 in ?? ()
I'll explain the back trace a little. The function on #11 is the function inside my code. That is the function in which I call all of the OIT lib functions. The functions on lines #12 and higher are the Node.js-related threading functions, setting up the thread to run my code's function. Functions on lines #10 down to #1 are all the OIT-called functions.
In the documentation for PDF Export, it says that if you're going to be using this library inside a threaded environment, then you need to call the init and deinit functions each time within the worker thread. I'm doing this in my code, which you can see here: https://github.com/ryancole/topdf/blob/master/src/topdf.cc#L29-L74
Is there anything else that I need to be setting that would cause this? I'm only specifying the font directory, explicitly. Are these libraries actually thread-safe? It doesn't look like they are.

Well, upon receiving a second opinion on the meaning of the phrasing in the documentation, I have got the library working in a threaded environment now. The first parameter to DEInitEx was supposed to specify to enable PTHREAD support, which I did not have. I thought that it meant something other than it actually does.

RDC XI R2 - Documentation for pdf export registry options

Similar Messages

Maybe you are looking for