c# pdf library itextsharp: C# read pdf metadata control Library system azure asp.net wpf console Visual_CUT_User

Page 201

MS Word Functionality

Note: PC must have MS Word installed.

Protecting MS WORD Files

Using a command line argument, you can instruct Visual CUT to:

a) allow viewing of a Word document only for user who knows the Open Password.

b) restrict the type of editing a user is allowed, unless the user knows the Modify Password.

A typical use scenario is when you have as a template document with form fields. Visual CUT

takes care of populating content in this template document using Word_Replace_Tags. Before

emailing the resulting file to a customer, you may need to restrict the customer to only form

fields modifications.

Here's an example of the command line argument structure:

…

"WORD_Protect:c:\in.doc>>c:\out.docx>>OpenPass>>ModifyPass>>ModType"

The parameters (after the "WORD_Protect:") are separated by a ">>" and are as follows:

1. The path & name of the source file

2. The path & name of the Save-To file (this can be same as the original file)

3. Open Password required to view the file

4. Modify Password required to remove the modify restrictions

5. Modify Type allowed for users without Modify Password. Valid options:

a. Allow_Only_Form_Fields (user can only modify form fields

b. Allow_Only_Comments (user can only add comments)

c. Allow_Only_Revisions (user can only add revisions)

Notes:

as usual, any of these arguments can contain references to fields or formulas and Visual CUT

would dynamically replace the reference with the value in the report. For example:

…

"WORD_Protect: {@in}>>{@out}>>Sesame>>mod123>>Allow_Only_Form_Fields"

C# read pdf metadata - add, remove, update PDF metadata in C#.net, ASP.NET, MVC, Ajax, WinForms, WPF

Allow C# Developers to Read, Add, Edit, Update and Delete PDF Metadata

pdf xmp metadata editor; view pdf metadata

C# read pdf metadata - VB.NET PDF metadata library: add, remove, update PDF metadata in vb.net, ASP.NET, MVC, Ajax, WinForms, WPF

Enable VB.NET Users to Read, Write, Edit, Delete and Update PDF Document Metadata

remove pdf metadata online; modify pdf metadata

Page 202

Inserting Crystal Values into MS Word Documents

Note: starting with Visual CUT 6.2002 (April 2010) this functionality is also available from the

Graphical User Interface by simply selecting Word_Replace_Tags as the export format.

Using a command line argument you can instruct Visual CUT to replace references to Crystal

field or formulas inside MS Word documents with values of these formulas. The file can then be

saved to a new dynamically named file and emailed as part of a bursting Visual CUT process.

The advantage of this technique over directly exporting/bursting a Crystal report to a Word

document is that Crystal exports to Word tend to have formatting and editing problems. By

creating your own Word document to act as a template, you ensure precise formatting and

problem-free editing.

Here's an example of the command line argument structure:

…

"WORD_Replace_Tags:c:\template.doc>c:\Contract_{Cust_Name}.doc>NoAppend"

The parameters (after the "WORD_Replace_Tags:") are separated by a ">" and are as follows:

1. The path & name of the original MS Word file (containing references to Crystal formulas).

2. The path & name of the target MS Word file (after replacing references with values).

3. optional Append (or NoAppend) directive: if you specify "

…>

Append" at the end of the

command line argument, the populated template document content will be appended to the end

of the target file, if the target file already exists

. If the target file doesn’t already exist, the target

file is created.

Specifying Field/Formula References (tags) in the Word document

If, for example, you wish to reference a Crystal formula called {@Customer_Name}, you

should use the following text inside your MS Word document: #{@Customer_Name}# . In

other words, simply enclose the formula name in # symbols.

Note that in order for Visual CUT to replace the reference with the value of the field/formula

during processing, the field or formula must be placed in:

1. The Report Header or Footer if the report is processed Whole by Visual CUT, or

2. Group Header 1 or Group Footer 1 if the report is being burst by Visual CUT.

C# PDF Image Extract Library: Select, copy, paste PDF images in C#

such as its location, zonal information, metadata, and so on. Extract image from PDF free in .NET framework with trial SDK components and online C# class source

c# read pdf metadata; pdf metadata viewer online

How to C#: Basic SDK Concept of XDoc.PDF for .NET

Various PDF annotation features can be integrated into your C# project, such as XDoc.PDF for .NET supports editing PDF document metadata, like Title

pdf metadata online; pdf xmp metadata

Page 203

Notes:



In bursting scenarios, you will want to target MS Word document path & name to be

dynamic as in the command line argument example above (where the target file name

contains {Cust_Name} as a dynamic portion).



You can specify the target file as the email attachment since the processing of this

command line argument occurs before emailing.



Any dynamic field shown as available for drag & drop in Visual CUT can be referenced

within the MS Word document. This includes the special date constants. Just remember

to enclose the reference inside # signs. For example, #{[yyyy]}# would return the current

year.



There is no limit on the length of field/formula text that can be used to replace

references. This means you can freely use data from memo or other large string fields.

VB.NET PDF Image Extract Library: Select, copy, paste PDF images

Get image information, such as its location, zonal information, metadata, and so on. Extract image from PDF free in .NET framework application with trial SDK

extract pdf metadata; remove metadata from pdf file

C# PDF Text Extract Library: extract text content from PDF file in

XDoc.PDF ›› C# PDF: Extract PDF Text. C# PDF - Extract Text from PDF in C#.NET. Best C#.NET PDF text extraction library and component for free download.

read pdf metadata java; clean pdf metadata

Page 204

Populating Word Tables with Crystal Formula Data

During WORD_Replace_Tags processing (see section above), you can instruct Visual CUT to

also populate tables with data from Crystal formulas. To populate the 1

table you name the

formula Word_Replace_Table_1. To populate the Nth table in the document, name the formula

Word_Replace_Table_N

Remember to place the formula in RH/RF section if not bursting or in GH1/GF1 section if the

formula provides different data for each Group level 1 during bursting. As always, the formula

or the section may be suppressed.

The formula should contain a strings delimited according to the following structure:

- Table Rows should be separated with a "][" delimiter.

- Table cells should be separated with a "||" delimiter

The table in the template Word document should already have at least as many rows as you

expect to populate. Visual CUT will delete the extra rows. This way, any formatting you

applied to the table would be maintained.

In most cases, the final formula would simply return the value of a global string variable that has

been accumulated via other formulas. For example, if you are bursting the sample report

Visual_Cut_11.rpt and wish to populate the 1

Table in a Word document with information

about the Product Name (1

column) and Revenue (2

Column), you may use the following 3

formulas:

GH1 Formula to reset the global string variable:

WhilePrintingRecords;

If NOT InRepeatedGroupHeader THEN Global StringVar Table_1 := "";

GH2 section Formula to accumulate the information into the Table_1 string variable:

WhilePrintingRecords;

Global stringvar Table_1;

IF Len(Table_1) = 0 Then

// First table row. Separate cell values with "||"

Table_1 := {Product.Product Name}+ "||" + "$" + ToText(Sum ({@value},

{Product.Product Name}),0)

ELSE

// Additional row, so add it to the accumulated string variable (Table_1)

// after a "][" to indicate a new row

Table_1 := Table_1 + "][" + {Product.Product Name}+ "||" + "$" + ToText(Sum

({@value}, {Product.Product Name}),0)

Group Footer Formula to pass the string to Visual CUT:

WhilePrintingRecords;

Global StringVar Table_1;

C# PDF - Read Barcode on PDF in C#.NET

NET edit PDF bookmark, C#.NET edit PDF metadata, C#.NET edit PDF digital signatures, C#.NET edit PDF sticky note, C#.NET print PDF, C#.NET read barcodes from

remove metadata from pdf; edit pdf metadata acrobat

C# PDF Library SDK to view, edit, convert, process PDF file for C#

C#.NET: Edit PDF Metadata. PDF SDK for .NET allows you to read, add, edit, update, and delete PDF file metadata, like Title, Subject, Author, Creator, Producer

edit multiple pdf metadata; acrobat pdf additional metadata

Page 205

Using the above scenario, a template document (c:\temp\Template.doc) that looks like this:

Can be used via the following command line (all in 1 line):

"C:\Program Files\Visual CUT 11\Visual CUT.exe" -e "C:\Program Files\Visual

CUT 11\Visual_CUT_11.rpt"

"WORD_Replace_Tags:c:\temp\template.doc>c:\temp\{Product_Type.Product Type

Name}.doc>NoAppend"

In this case, you should set Visual CUT to burst this report. Any format would do since you

would ignore the export and use the Word documents.

Here’s what Gloves.doc looks like

VB.NET PDF: Basic SDK Concept of XDoc.PDF

XDoc.PDF for .NET supports editing PDF document metadata, like Title, Subject, Author, Creator, Producer, Keywords, Created Date, and Last Modified Date.

pdf metadata editor online; pdf remove metadata

C# PDF File Compress Library: Compress reduce PDF size in C#.net

Bookmarks. Comments, forms and multimedia. Document and metadata. All object data. File attachment. Flatten visible layers. C#.NET DLLs: Compress PDF Document.

edit pdf metadata; preview edit pdf metadata

Page 206

Replace Formatting in MS WORD Files

Using a command line argument, you can instruct Visual CUT to find and replace a specified

format throughout a Word document.

This functionality was developed to allow an export from Crystal to Word to result in Double

Underline (typical for totals in accounting reports). Since Crystal doesn’t have a double

underline, you can apply a Strikethrough in Crystal, and then convert it to Double Underline in

the resulting MS Word export.

Here's an example of the command line argument structure:

…

"WORD_Replace_Format:c:\in.doc>c:\out.doc>Strikethrough>DoubleUnderline"

The parameters (after the "WORD_Replace_Format:") are separated by a ">" and are as

follows:

6. The path & name of the source file

(typically, this would be the exported file but you can convert any WORD file).

7. The path & name of the Save-To file (this can

’t be

same as original file)

8. Format to search for (currently, only Strikethrough is supported)

9. Format to replace with (currently, only DoubleUnderline is supported)

Notes:

as usual, any of these arguments can contain references to fields or formulas and Visual CUT

would dynamically replace the reference with the value in the report. For example:

…

"WORD_Replace_Format:{@in}>{@out}>Strikethrough>DoubleUnderline"

Page 207

Printing MS WORD Files

Using a command line argument, you can instruct Visual CUT to print a specified MS Word file.

Using field/formula references, you can dynamically set the file to be printed, the printer to be

used, and the number of copies.

Here's an example of the command line argument structure:

…

"WORD_Print:{@Word_File}>>{@Printer_Name}>>{@Copies}"

…

"WORD_Print:c:\temp\test.docx>>Default>>1"

The parameters (after the "WORD_Print:") are separated by ">>" and are as follows:

6. The path & name of the MS Word file

7. The name of the destination printer, or Default

8. The number of copies

Notes:

as usual, any of these arguments can contain references to fields or formulas and Visual CUT

would dynamically replace the reference with the value in the report.

Page 208

Printing MS WORD Files with Watermarks

You can print exported Word files with dynamic watermarks for each printed copy

(e.g. "Copy 1 of 4"). See sample image: http://screencast.com/t/oSaqXcqvidWF

If you also need to export to another file format, simply specify multiple export file names.

For example, c:\temp\{@Invoice}.pdf;c:\temp\{@Invoice}.doc

The command line argument structure:

…

"WORD_Print_Watermark:{@Word_File}>>{@Printer_Name}>>{@Copies}>>

WatermarkText>>Font>> Bold>>Italic>> FontSize>>Width>>Height>>

Rotation>>Transparency>>Options"

Example 1: (stretching to Watermark to length of 7.5 inches and height of 1.3 inches):

…

"WORD_Print_Watermark:c:\test.docx>>Default>>2>>Copy [[N]] of [[M]]>>

Calibri>>False>>False>>12>>1.3>>7.5>>315>>0.5>>"

Example 2 (62 point font size without width/height stretching):

…

"WORD_Print_Watermark:c:\test.docx>>Default>>2>>Copy [[N]] of [[M]]>>

Calibri>>False>>False>>62>> >> >>135>>0.5>>"

The parameters (after the "WORD_Print_Watermark:") are as follows:

1. The path & name of the MS Word file

2. The name of the destination printer, or Default

3. The number of copies

4. The Watermark text. Visual CUT replace [[N]] with the copy number and [[M]] with

number of copies, so Copy [[N]] of [[M]] becomes Copy 1 of 4, Copy 2 of 4, etc.

5. Font (e.g. Calibri)

6. Bold: True or False

7. Italic: True or False)

8. Font Size: in points. Note: gets stretched if Width and/or Height are specified!

9. Width: in inches. Stretches text to desired width. Leave blank or space to ignore

10. Height: in inches. Stretches text to desired height. Leave blank or space to ignore

11. Rotation: Clockwise rotation in degrees. use 315 for diagonal, 0 for horizontal etc

12. Transparency: from 0 to 1. 0.5 = semi-transparency

13. Options: leave blank

Notes:

as usual, any of these arguments can contain references to fields or formulas and Visual CUT

would dynamically replace the reference with the value in the report.

Page 209

Convert WORD Files to PDF

Using a command line argument, you can instruct Visual CUT to save a WORD file to a PDF

File. Here's an example of the command line argument structure:

…

"WORD_Save_As:c:\temp\Invoice.doc>c:\temp\Invoice.pdf>PDF>0>0>0>1>0"

The parameters (after the "WORD_Save_As:") are separated by a ">" and are as follows:

14. The path & name of the WORD file (typically, this would be the exported file or the

File you created using WORD_Replace_Tags, but you can convert any WORD file).

15. The path & name of the target PDF file

16. Save As Format (PDF)

17. Optimized For Screen (1/0): a value of 0 would create a higher-quality (optimized for

print) but larger pdf file.

18. Create Bookmarks (0=No, 1=by Word Section Headings, 2=by Word Bookmarks)

19. Create Tagged (structured) PDF (1=Yes, 0=No)

20. Substiture Bitmaps for Missing Fonts (1=Yes, 0=No)

21. Use PDF/A Standard (for archiving purposes) (1=Yes, 0=No)

Notes:

as usual, any of these arguments can contain references to fields or formulas and Visual CUT

would dynamically replace the reference with the value in the report. For example:

…

"WORD_Save_As:{@file_name}.doc>{@file_name}.pdf>PDF>0>0>0>1>0"

The machine must have MS Word 2007 or higher. For Word 2007 you may need to

download the "2007 Microsoft Office Add-in: Microsoft Save as PDF or XPS AddOn" from:

http://www.microsoft.com/downloads/details.aspx?FamilyId=4D951911-3E7E-4AE6-B059-

A2E79ED87041&displaylang=en

Page 210

Text Functionality

Splitting Text Files by Embedded Tags

Using a command line argument, you can instruct Visual CUT to look for tags inside a text file

and to split the file into multiple files. The process is faster than regular bursting and can be

useful for generating many thousands of files.

Here's an example of the command line argument structure:

…

"TXT_Split_Tags:c:\temp\ToolTips.txt>>Replace"

The parameters (after the "TXT_Split_Tags:") are separated by a ">>" and are as follows:

1. The path & name of the text file you wish to split

2. Desired action when split file already exists: Replace or Append

Within the text file, you should embed text tags that indicate the split file path & name that

should apply for the following text. The structure and location of the tags should follow this

example:

Notes:

The tag [[#Split_Tag:: … #]] comes

before the text that would be written to that split file.

- If the target folder of the split files does not exist, Visual CUT creates it on the fly.

[[#Split_Tag::c:\temp\Some_File_Name.htm #]]<HTML>

TML>

…

</HTML>

[[#Split_Tag::c:\temp\Another_File_Name.htm#]]<HTML>

TML>

…

</HTML>

Documents you may be interested

c# pdf library itextsharp : C# read pdf metadata control Library system azure asp.net wpf console Visual_CUT_User_Manual20-part525