[Pkg-gnupg-commit] [gpgme] 381/412: doc: Mention language bindings in the manual.

[Daniel Kahn Gillmor]

This is an automated email from the git hooks/post-receive script.

dkg pushed a commit to branch master
in repository gpgme.

commit db2398512796f28f0f92e32e0de3180d93f76a26
Author: Werner Koch <wk at gnupg.org>
Date:   Mon Sep 19 09:06:24 2016 +0200

    doc: Mention language bindings in the manual.
    
    --
    
    Signed-off-by: Werner Koch <wk at gnupg.org>
---
 doc/gpgme.texi | 12 +++++++++++-
 1 file changed, 11 insertions(+), 1 deletion(-)

diff --git a/doc/gpgme.texi b/doc/gpgme.texi
index 18fb6d5..ec7ebb7 100644
--- a/doc/gpgme.texi
+++ b/doc/gpgme.texi
@@ -298,6 +298,13 @@ library.  Experienced programmers might want to start looking at the
 examples at the end of the manual, and then only read up those parts
 of the interface which are unclear.
 
+The documentation for the language bindings is currently not included
+in this manual.  Those languages bindings follow the general
+programming model of @acronym{GPGME} but may provide some extra high
+level abstraction on top of the @acronym{GPGME} style API.  For now
+please see the README files in the @file{lang/} directory of the
+source distribution.
+
 
 @node Features
 @section Features
@@ -324,8 +331,11 @@ the programmer can focus on the other parts of the program, and still
 integrate strong cryptography in his application.  Once support for
 @acronym{GPGME} has been added to a program, it is easy to add support
 for other crypto protocols once @acronym{GPGME} backends provide them.
- at end table
 
+ at item it's language friendly
+ at acronym{GPGME} comes with languages bindings for several common
+programming languages: Common Lisp, C++, Python 2, and Python 3.
+ at end table
 
 @node Overview
 @section Overview

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/pkg-gnupg/gpgme.git