gpgme/lang
Ben McGinnes 1ae3ead2cd Conflict with Phabricator files
* The developers of Phabricator, the web front-end on dev.gnupg.org
  have not implemented renderers for Markdown, Org-Mode or any other
  common markdown like language.
* They also refuse to do so.
* Instead they re-invented the wheel and implemented their own version
  of Markdown-like thing which is incompatible with everything else.
  It is called Remarkup.
* The developers of Phabricator and Remarkup have refused to provide
  conversion tools to move files to/from any format to/from Remarkup.
* They expect everyone to learn their new favourite pet project.
* Remarkup may or may not display Org Mode files, but if so then it is
  likely to only want to do so as plain text.
* There is an unaffiliated and unofficial project to convert Github
  Markdown to Remarkup via Pandoc.  This might be adapted for our use,
  but requires testing.
* Until then exporting from Org Mode to UTF-8 text is likely the least
  worst plan.
* Which means renaming this file to README.org first.
2018-02-20 02:51:02 +11:00
..
cl .gitignore: flesh out rules and add subdirectory-.gitignores. 2012-04-20 16:05:11 +02:00
cpp cpp: Add SpawnShowWindow flag 2018-02-09 16:11:40 +01:00
python Conflict with Phabricator files 2018-02-20 02:51:02 +11:00
qt tests: Makefile portability. 2018-02-15 11:14:49 +09:00
Makefile.am build: Declare all languages for make dist. 2016-08-10 16:28:36 +02:00
README python: Rename Python module from PyME to gpg. 2016-10-31 15:42:27 +01:00

Language Support for GPGME
--------------------------

This directory contains support for other languages than C.

Please note that language support components may be under a different
license than GPGME itself.  You can find more information in each
sub-directory.

Directory	Language

cl		Common Lisp
cpp		C++
qt		Qt-Framework API
python		Python 2 and 3 (module name: gpg)