From e71b2d533d4b3a732b17ff7342130d3d17f03a3a Mon Sep 17 00:00:00 2001
From: Nick Burch <nick@apache.org>
Date: Thu, 13 Jan 2011 13:56:02 +0000
Subject: [PATCH] Update the HMEF page with the latest status of the code

git-svn-id: https://svn.apache.org/repos/asf/poi/trunk@1058557 13f79535-47bb-0310-9956-ffa450edef68
---
 src/documentation/content/xdocs/hmef/index.xml | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/src/documentation/content/xdocs/hmef/index.xml b/src/documentation/content/xdocs/hmef/index.xml
index 95ad88460..99a3c9229 100644
--- a/src/documentation/content/xdocs/hmef/index.xml
+++ b/src/documentation/content/xdocs/hmef/index.xml
@@ -36,9 +36,11 @@
             TNEF (Transport Neurtral Encoding Format), aka winmail.dat,
             which is used by Outlook and Exchange in some situations.</p>
           <p>Currently, HMEF provides a low-level, read-only api for 
-            accessing core TNEF attributes. Embedded MAPI attributes
-            are not yet processed, and attachments are not properly
-            handled either.</p>
+            accessing core TNEF attributes. It is able to provide access
+            to both TNEF and MAPI attributes, and low level access to
+            attachments. Compressed RTF is not yet fully supported, and
+            user-facing access to common attributes and attachment contents
+            is not yet present.</p>
           <p>HMEF is currently very much a work-in-progress, and we hope
             to add a text extractor and attachment extractor in the not
             too distant future.</p>