[COMMIT LOGREPORT] docs/website/htdocs faq.html,NONE,1.1
Joost van Baal
vanbaal at users.sourceforge.net
Wed Apr 18 16:51:22 CEST 2007
Update of /cvsroot/logreport/docs/website/htdocs
In directory sc8-pr-cvs6.sourceforge.net:/tmp/cvs-serv14494
Added Files:
faq.html
Log Message:
wget-ed lire/faq.php
--- NEW FILE: faq.html ---
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/1999/REC-html401-19991224/loose.dtd">
<html lang="en"><head>
<link rel="Stylesheet" rev="Stylesheet" href="/css.php" type="text/css">
<link rel="icon" href="/images/lire-16.png" type="image/png">
<title>
</title></head>
<body><table border="0" width="100%" cellspacing="0" cellpadding="0" align="left" class="lightbg">
<!-- start heading row -->
<tr>
<td valign="top"><img
src="/images/top.gif"
alt="Logreport.org: Your destination for log analysis on the web"
width="651" height="47" hspace="0" vspace="0" border="0"></td>
</tr>
<tr>
<td><table border="0"
cellspacing="0" align="left" cellpadding="0" class="lightbg">
<tr>
<td width="135" valign="top" class="darkbg"><a href="/lire/"><img src="/images/lire.gif" alt="Logreport.org: the home of Lire"
width="94" height="96" align="top" border="0"></a></td>
<td valign="top" align="left"><table
border="0" cellspacing="0" cellpadding="0" class="lightbg">
<tr>
<td width="12"><img src="/images/midb.gif"
alt="" width="12" height="83"></td>
<td width="292"><img src="/images/mida-2.gif"
alt="" width="292" height="83"></td>
<td width="208"><table border="0"
cellspacing="0" cellpadding="0" align="left">
<tr>
<td width="152" valign="top"><img
src="/images/powera1.gif" alt="" width="153"
height="11"></td>
<td valign="top"><img src="/images/powera2.gif"
alt="" width="55" height="11"></td>
</tr>
<tr>
<td valign="middle" width="153" class="poweredby">
Powered by Lire </td>
<td><img src="/images/poweredby-buff.gif"
alt="" width="49" height="24"></td>
</tr>
<tr>
<td class="leftborder" width="208" colspan="2"><img
src="/images/powerb.gif"
alt="" width="195" height="48"></td>
</tr>
</table></td>
</tr>
<tr>
<td width="12" valign="bottom"><img
src="/images/midc.gif"
alt="" width="12" height="26"></td>
<td width="292" valign="bottom" class="titlebox"> LogReport </td>
<td class="leftborder"> </td>
</tr>
</table>
</td>
</tr>
</table></td>
</tr>
<tr>
<td valign="top"><table border="0"
cellspacing="0" cellpadding="0" align="left" class="darkbg">
<tr>
<td valign="top" class="rightborder">
<table border="0" width="130"
cellspacing="0" cellpadding="3" align="left" class="darkbg">
<tr>
<td><p class="smallwhite">[<a
href="/lire/dl.php" class="navlist">download</a>]
[<a href="/lire/or/" class="navlist">responders</a>]</p></td>
</tr>
<tr><td class="navbar"><a href="/" class="navlink">Home</a>
</td></tr>
<tr><td class="navbar"><a href="/about" class="navlink">About</a>
</td></tr>
<tr><td class="navbaron"><a href="/lire" class="navlinkon">Lire</a>
<ul class="navlist">
<li><a href="/lire/dl.php" class="navlist">Download</a></li>
<li><a href="/lire/or" class="navlist">Online Responders</a></li>
<li><a href="/lire/../doc/lire" class="navlist">Documentation</a></li>
<li><a href="/lire/ex" class="navlist">Example Reports</a></li>
<li><a href="/lire/NEWS.php" class="navlist">Lire NEWS</a></li>
<li><a href="/lire/lire201.php" class="navlist">Lire 2.0.1</a></li>
<li><a href="/lire/lire20.php" class="navlist">Lire 2.0</a></li>
<li><a href="/lire/lire15.php" class="navlist">Lire 1.5</a></li>
<li><a href="/lire/lire14.php" class="navlist">Lire 1.4</a></li>
<li><a href="/lire/l10n.php" class="navlist">Localization</a></li>
</ul>
</td></tr>
<tr><td class="navbar"><a href="/doc" class="navlink">Documentation</a>
</td></tr>
<tr><td class="navbar"><a href="/dev" class="navlink">Developer Info</a>
</td></tr>
<tr><td class="navbar"><a href="/lire/faq.php" class="navlink">FAQ</a>
</td></tr>
<tr><td class="navbar"><a href="/contact" class="navlink">Contact Us</a>
</td></tr>
<tr><td class="navbar"><a href="/search" class="navlink">Search</a>
</td></tr>
<tr>
<td class="topborder">
</td>
</tr>
</table>
</td>
<td class="topbotborder"><img
src="/images/spacer.gif" width="4" height="1"
alt="" border="0"></td>
<!-- start body portion of row -->
<td class="bodytable">
<table border="0" width="100%" cellspacing="0" cellpadding="5" align="left">
<tr><td valign="top">
<h1>Frequently Asked Questions about Lire</h1>
<p>Send questions that you'd like an answer here to the <a href="mailto:questions(a)logreport.org">Questions mailing list</a>.
</p>
<h1>1 Often Encoutered Errors</h1>
<h2>1.1 When I use HTML or XHTML output with images, I get an empty
index.html</h2>
<p>When I use HTML or XHTML output with images, the xsltproc segfault.</p>
<p>You are probably using a version of the DocBook XSLT stylesheets newer
than version 1.50 with an old version of xsltproc.</p>
<p>This is related to a bug in xsltproc in versions previous to 1.0.20.
Upgrade to version 1.0.20 or later of xsltproc and the problem will be
solved.
</p>
<h2>1.2 In my reports, hyphens (-) occur where data is expected.
What does this mean?
</h2>
<p>The <code>-</code> marker was used to denote missing data.
This was used for DLF converter as the value for fields they don't
support or for which the field doesn't apply in that context. Lire
1.3 introduced proper "missing values" handling. Unfortunately,
the old DLF converters don't take advantage of it yet.
</p>
<h2>1.3 When running <code>xmllint</code> (e.g. when building
Lire from CVS), the check fails with an error: <code>1: validity error:
xmlValidateAttributeCallback(application): internal error</code>. How
can I solve this?
</h2>
<p>This is related to a bug which got solved in libxml2 2.4.28. THe bug
was present in libxml2 2.4.27 (and some other versions too, probably).
libxml2 2.4.24 didn't suffer from the bug. So: up- or downgrade your
libxml2.
</p>
<h1>2 Licensing</h1>
<p>In this section, you will find answers to common questions about
various aspects of Lire's licensing, e.g. questions which might
arise if you plan to extend Lire with your own code.
</p>
<p>Be aware that the LogReport team is very happy to include and
maintain contributed code. We want to make this as easy as
possible. See the first question. If you write code to be used
with or as a part of Lire, please consider contributing it. This
will not only benefit Stichting LogReport Foundation, but also
you: the LogReport team will maintain and distribute your code,
and will take care of handling bug reports.
</p>
<p><strong>Note</strong> Apply the usual disclaimers about the
fact that this information doesn't represent "legal advice" and
that you should consult an appropriate legal advisor for the
definitive answers.
</p>
<h2>2.1 I wanna contribute code, and would like it to get distributed as a
part of Lire, what should I do, license-wise?</h2>
<p>As with any software, it's a good thing to add a copyright
notice to your code, like
<pre>
Copyright (C) 2001,2002 Joe Hacker joe(a)example.org.
</pre>
</p>
<p>This makes it easy to find out who holds the copyright of this
particular piece of code. Furthermore, you should add a license
notice, like e.g. the modified BSD license which reads
<pre>
Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the distribution
3. The name of the copyright holder may not be used to endorse or promote
products derived from this software without specific prior written
permission.
THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT,
INDIRECT, INCIDENTAL , SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMI TED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PR OFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILI TY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING
IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN I F ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
</pre>
</p>
<p>or a referal to the GPL, which reads
<pre>
This program is free software; you can redistribute it and/or modify
it under the terms of the GNU General Public License as published by
the Free Software Foundation; either version 2 of the License, or
(at your option) any later version.
This program is distributed in the hope that it will be useful,
but WITHOUT ANY WARRANTY; without even the implied warranty of
MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
GNU General Public License for more details.
You should have received a copy of the GNU General Public License
along with this program (see COPYING); if not, check with
http://www.gnu.org/copyleft/gpl.html or write to the Free Software
Foundation, Inc., 59 Temple Place - Suite 330, Boston, MA 02111,
USA.
</pre>
</p>
<p>This makes it clear what people are allowed to do with your
code. See the questions below for other licenses you could use.
If you sent us code along with a copyright notice ans license
notice as above, we have no problems licence-wise with your
contribution.
</p>
<h2>2.2 Why is Lire licensed under the GPL?</h2>
<p>The Stichting LogReport Foundation exists to develop, maintain and
propagate tools as well as knowledge for log file processing and
report generation (among other things). The Foundation's statutes
mandate that all software owned by the Foundation should be made
available under an open source license.
</p>
<p>The chosen license was the GNU General Public License (aka GPL)
because it was one of most widespread "open source" licenses and it
would allow integration of many existing code.
</p>
<p>You can find more about the Stichting LogReport Foundation on our
website. Unfortunately, our articles of association are available in
Dutch only at this time.
</p>
<h2>2.3 If I make a contribution to Lire do I have to put my code under
the GPL?</h2>
<p>The short answer: no. As copyright holder of your contribution, you
are free to choose whatever license terms please you. Be aware though
that to be included in Lire, your contribution must be made
available under terms compatible with the GPL. Examples of licenses
that have compatible terms are the GNU GPL, the modified BSD license,
the X11 license or the Clarified Artistic License (a list is on
<acronym title="Broken link to http://www.gnu.org/licenses/license-list.html"></acronym>.
</p>
<p>The more adequate answer is that it depends of the nature of your
contribution. Contributions that cannot really be considered
independent of Lire's distribution and thus have to be considered
as "derived work" must be distributed under the GPL. This would
include most patches to Lire's internals or to programs or reports
included in Lire, but not additions of superservices, services or
reports.
</p>
<h2>2.4 We want to write a DLF converter for the users of our proprietary
product, can we distribute it under the same proprietary terms as our
other products?</h2>
<p>Yes. If your DLF converter doesn't include any code from Lire you
are free to distribute it under the terms of your choice. Note that
converters that use the publically defined DLF converter API include
link to developer's documentation, aren't considered to be including
or copying from Lire's code.
</p>
<p>Remember though that in this case, your DLF converter won't be
able to be distributed as part of Lire.
</p>
<h2>2.5 Can I distribute my XML report specifications under
other terms than the GPL?</h2>
<p>Yes. The Lire Report Specification Markup Language used to
define those reports is publically defined and no patent is held
over it, so you are free to choose whatever license terms please
you for them.
</p>
<p>Remember though that if your license terms aren't compatible
with the GPL, your report specifications cannot be included in
Lire's distribution.
</p>
<h2>2.6 I want to reuse your file formats (DLF format, XML
report) in my project, but I want to release this project under a
MIT X-like license, may I?</h2>
<p>Yes. Those for't protected by any patent so you are
free to write software that read and write files in those
formats if you find them convenient for your project.
</p>
<br>
<img src="/images/spacer.gif" width="520" height="1" alt="" border="0">
</td>
</tr></table>
</td>
<td class="lightbg"><img src="/images/spacer.gif" width="5" height="1" alt="" border="0"></td>
</tr>
</table>
</td></tr>
<!-- end body portion of row -->
<tr><td>
<!-- start footer table row -->
<table border="0" cellspacing="0" cellpadding="0" align="left">
<tr>
<td width="136" class="darkbg"><img src="/images/spacer.gif" height="1" width="136" alt=""></td>
<td valign="bottom" align="left"><img src="/images/botcurve.gif" alt="" width="38" height="33"></td>
<td class="lastmod">Last updated 2003-11-13 22:18:46 by Francis Lacoste.</td>
<td width="50"><img src="/images/spacer.gif" height="1" width="50" alt=""></td>
<td><a href="http://validator.w3.org/check/referer"><img border="0" src="/images/html4.gif" alt="Valid HTML 4.01!" height="31" width="88"></a></td>
<td width="10"><img src="/images/spacer.gif" height="1" width="10" alt=""></td>
<td><a href="http://jigsaw.w3.org/css-validator/"><img border="0" src="/images/css.gif" alt="Valid CSS!" height="31" width="88"></a></td>
</tr>
</table>
<!-- end footer table row -->
</td></tr>
</table></body></html>
--
To UNSUBSCRIBE, email to commit-request at logreport.org with a subject of
"unsubscribe". Trouble? Send an email with subject "help" to
commit-request at logreport.org
More information about the Commit
mailing list