1 <?xml version="1.0" encoding="utf-8"?>
2 <page xmlns="http://projectmallard.org/1.0/" xmlns:e="http://projectmallard.org/experimental/" type="guide" id="mergefeatures" xml:lang="sl">
5 <link type="guide" xref="index#merging"/>
6 <revision pkgversion="3.0" version="0.1" date="2010-05-04" status="incomplete"/>
7 <desc>Kaj lahko pričakujete od spajanja dokumentov.</desc>
10 <email>evins@snaught.com</email>
12 <credit type="author">
13 <name>Mario Blättermann</name>
14 <email>mariobl@gnome.org</email>
17 <p>Creative Commons Share Alike 3.0</p>
21 <title>Izvajanje spajanja dokumentov</title>
23 <p>Document Merge (sometimes called "Mail Merge") is a powerful
24 feature that allows a unique label or card to be printed for each
25 record in an external data source.</p>
27 <p>The first step to performing a document merge is to prepare
28 a source document that contains your merge data. This data could
29 be mailing addresses or any other data that you wish to create
30 unique labels or cards for. Currently back-ends only exist for
31 text files and the evolution data server -- others are planned. The currently
32 supported text-file format is very simple: each line is a record;
33 fields are delimited by commas (CSV), tabs, or colons; and newlines
34 can be embedded into fields by using the "\n" entity. This file
35 could be created using any text editor or could be created by
36 another program or script. A common way of creating CSV files is
37 to export them from a spreadsheet program.</p>
39 <p>A label must then be configured to "point at" this data file.
40 To configure the merge properties of a document, choose
41 <guiseq><gui>Objects</gui>
42 <gui>Merge Properties</gui></guiseq> menu item
43 to display the <gui>merge properties</gui> dialog. This
44 dialog is used to select the exact data file format and file
45 name (location) of the merge data.</p>
47 <p>Finally, once the label has been configured for a data file,
48 field keys can be inserted into text objects and used as source
49 or data for barcode objects and image filenames for image objects.
50 See <link xref="editprop"/> for more information
51 on using merge data for these object types.</p>
53 <p>Now that your label is configured, <app>gLabels</app> will print a unique
54 label for each record in your source document -- substituting fields
55 from each record for field keys in the all text, barcode, and
58 <p>See <link xref="merge"/> for a detailed
59 tutorial on the document merge feature.</p>