Date: prev next · Thread: first prev next last
2012 Archives by date, by thread · List index


Hi :)
Hmm, it wont make any difference how the messages are posted will it?  They appear in Nabble etc 
which-ever way.
Regards from
Tom :)

--- On Sat, 14/1/12, Tom Davies <tomdavies04@yahoo.co.uk> wrote:

From: Tom Davies <tomdavies04@yahoo.co.uk>
Subject: Re: [libreoffice-users] Re: Triggering reports from html files
To: users@global.libreoffice.org
Date: Saturday, 14 January, 2012, 14:04

Hi :)
You are welcome :)  It might be best to use the Nabble interface to post messages
http://nabble.documentfoundation.org/Triggering-reports-from-html-files-tp3654402p3654673.html
That link goes directly to the right thread but you can use the button at the top to start a new 
thread or even navigate to other threads and other lists.  

Some of your emails went to my spam folder but your messages should be in the thread anyway so that 
people using Nabble or GMane see them (and people that have a quick glance through their spam/junk 
folders before deleting them.  
Regards from
Tom :)


-- 
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.