Git commit d63c0ed50ecea12a5cb5760733f48a719ab1d517 by Albert Astals Cid.
Committed on 15/11/2017 at 09:00.
Pushed by aacid into branch 'dont-use-docdata-for-annots-and-forms'.

okular archive -> okular document archive

M  +4    -4    doc/index.docbook

https://commits.kde.org/okular/d63c0ed50ecea12a5cb5760733f48a719ab1d517

diff --git a/doc/index.docbook b/doc/index.docbook
index 74140b40..4b35dc78 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -457,7 +457,7 @@ Context menu actions like Rename Bookmarks etc.)
                        <para>Using the context menu either in the 
<guilabel>Reviews</guilabel> view of the navigation panel or in the main window 
you can open a <guilabel>Pop up Note</guilabel> for any kind of annotation and 
add or edit comments.</para>
                        <para>Annotations are not only limited to &PDF; files, 
they can be used for any format &okular; supports.</para>
                        <para>
-                &okular; has the "document archiving" feature. This is an 
&okular;-specific format for carrying the document plus various metadata 
related to it (currently only annotations). You can save a "document archive" 
from the open document by choosing 
<menuchoice><guimenu>File</guimenu><guisubmenu>Save 
As</guisubmenu></menuchoice> and selecting <guilabel>Okular Archive</guilabel> 
in the <guilabel>Filter</guilabel> selector. To open an &okular; document 
archive, just open it with &okular; as it would be &eg; a &PDF; document.
+                &okular; has the "document archiving" feature. This is an 
&okular;-specific format for carrying the document plus various metadata 
related to it (currently only annotations). You can save a "document archive" 
from the open document by choosing 
<menuchoice><guimenu>File</guimenu><guisubmenu>Save 
As</guisubmenu></menuchoice> and selecting <guilabel>Okular document 
archive</guilabel> in the <guilabel>Filter</guilabel> selector. To open an 
&okular; document archive, just open it with &okular; as it would be &eg; a 
&PDF; document.
                        </para>
                        <para>
                          You can <emphasis>also</emphasis> save annotations 
directly into &PDF; files. You can use <menuchoice><guimenu>File</guimenu> 
<guimenuitem>Save</guimenuitem></menuchoice> to save it over the current file 
or <menuchoice><guimenu>File</guimenu> <guimenuitem>Save 
As...</guimenuitem></menuchoice> to save it to a new file.
@@ -929,7 +929,7 @@ Context menu actions like Rename Bookmarks etc.)
                                        </term>
                                        <listitem>
                                                <para>
-                                                       <action>Open</action> a 
supported file or &okular; archive. If there is already an opened file it will 
be closed. For more information, see the section about <link 
linkend="opening">Opening Files</link>.
+                                                       <action>Open</action> a 
supported file or &okular; document archive. If there is already an opened file 
it will be closed. For more information, see the section about <link 
linkend="opening">Opening Files</link>.
                                                </para>
                                        </listitem>
                                </varlistentry>
@@ -989,7 +989,7 @@ Context menu actions like Rename Bookmarks etc.)
                                                </menuchoice>
                                        </term>
                                        <listitem>
-                                         <para><action>Saves</action> the 
document including all the changes (annotations, form contents, &etc;), 
provided the document backend supports saving those changes, if the backend 
does not support saving the changes the user will be give the option to lose 
them or to save as &okular; archive.</para>
+                                         <para><action>Saves</action> the 
document including all the changes (annotations, form contents, &etc;), 
provided the document backend supports saving those changes, if the backend 
does not support saving the changes the user will be give the option to lose 
them or to save as &okular; document archive.</para>
                                        </listitem>
                                </varlistentry>
 
@@ -1004,7 +1004,7 @@ Context menu actions like Rename Bookmarks etc.)
                                                </menuchoice>
                                        </term>
                                        <listitem>
-                                         <para><action>Saves</action> the 
document under a new name including all the changes (annotations, form 
contents, &etc;), provided the document backend supports saving changes, if the 
backend does not support saving the changes the user will be give the option to 
lose them or to save as &okular; archive.</para>
+                                         <para><action>Saves</action> the 
document under a new name including all the changes (annotations, form 
contents, &etc;), provided the document backend supports saving changes, if the 
backend does not support saving the changes the user will be give the option to 
lose them or to save as &okular; document archive.</para>
                                         <note>
                                         <para>
                                             Note that, due to the way this is 
implemented, even if there are no changes to the file, the new file need not to 
be an exact bit-for-bit copy of the original file (&eg; can have a different 
SHA-1 hash, &etc;).

Reply via email to