From 5bc4912d14144b4187b7aa5f4b6cf918c61928c6 Mon Sep 17 00:00:00 2001 From: Geoff Stratton Date: Thu, 9 Sep 2021 10:24:42 -0700 Subject: [PATCH] Updating license to GPLv3 --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index edd197e..5d9c972 100644 --- a/README.md +++ b/README.md @@ -12,4 +12,12 @@ Prerequisites: 1. When building this I had the Microsoft.Office.Interop.Word 12.0 (Word 2007) library referenced from the project. The easiest way to meet this requirement is to install some recent version of Office, but any version of the Microsoft.Office.Interop.Word library that natively handles the .docx format should work. 2. I had the very useful Html Agility Pack version 1.4.6 library referenced as well. I was using .NET 4.0 and the 4.0 version of the library. Html Agility Pack now [lives on Github](https://github.com/zzzprojects/html-agility-pack) so you can grab it easily and reference it from your project. -Later I realized a better way to do this might be to invoke the LibreOffice converter on the command line, convert your document to HTML or text, filter it with Python's BeautifulSoup library or sed or Ruby's Nokogiri, and then insert the results straight into the database of your web system. But maybe not: in text, tags like <table> and <ul> would be lost, and LibreOffice's HTML is still pretty ugly. \ No newline at end of file +Later I realized a better way to do this might be to invoke the LibreOffice converter on the command line, convert your document to HTML or text, filter it with Python's BeautifulSoup library or sed or Ruby's Nokogiri, and then insert the results straight into the database of your web system. But maybe not: in text, tags like <table> and <ul> would be lost, and LibreOffice's HTML is still pretty ugly. + +License +--------------- +GNU General Public License v3.0 + +Author +--------------- +Geoff Stratton