[kde-doc-english] [okular] doc: Fix my typo

Yuri Chornoivan yurchor at ukr.net
Wed Jul 22 06:19:59 UTC 2015


Git commit 793b8ee3f21d8d5ca46585fff940f029515c4387 by Yuri Chornoivan.
Committed on 22/07/2015 at 06:19.
Pushed by yurchor into branch 'master'.

Fix my typo

M  +1    -1    doc/index.docbook

http://commits.kde.org/okular/793b8ee3f21d8d5ca46585fff940f029515c4387

diff --git a/doc/index.docbook b/doc/index.docbook
index 1b42e10..1896af3 100644
--- a/doc/index.docbook
+++ b/doc/index.docbook
@@ -1036,7 +1036,7 @@ Context menu actions like Rename Bookmarks etc.)
 						</menuchoice>
 					</term>
 					<listitem>
-					  <para><action>Save</action> saves the document under a new name including all the changes (annotations, form contents, &etc;), provided the document backend supports saving changes. With the &PDF; backend it is possible to save the document with the changed values of the form fields.<!--Only useful for pdf? what happens with other formats/backends?--> It can be possible (provided that the data were not secured using DRM) to save annotations with &PDF; files.</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. With the &PDF; backend it is possible to save the document with the changed values of the form fields.<!--Only useful for pdf? what happens with other formats/backends?--> It can be possible (provided that the data were not secured using DRM) to save annotations with &PDF; files.</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 (⪚ can have a different SHA-1 hash, &etc;).


More information about the kde-doc-english mailing list