<div dir="ltr">Yes, the existing links could point to the current version and we could host also all the older revisions as well.<br>mike<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Sep 12, 2013 at 3:56 AM, Stephan Bergmann <span dir="ltr"><<a href="mailto:sbergman@redhat.com" target="_blank">sbergman@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 09/11/2013 07:28 PM, Lionel Elie Mamane wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Sep 11, 2013 at 05:54:58PM +0200, bjoern wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Wed, Sep 11, 2013 at 05:04:01PM +0200, Michael Stahl wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 09/09/13 10:38, Lionel Elie Mamane wrote:<br>
</blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

Actually, it could make sense to document the API available in each<br>
version, that is, have something like:<br>
</blockquote></blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">

<a href="http://api.libreoffice.org/docs/3.3/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/3.3/idl/</a><br>
<a href="http://api.libreoffice.org/docs/3.6/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/3.6/idl/</a><br>
<a href="http://api.libreoffice.org/docs/4.0/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/4.0/idl/</a><br>
<a href="http://api.libreoffice.org/docs/4.1/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/4.1/idl/</a><br>
<a href="http://api.libreoffice.org/docs/4.2/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/4.2/idl/</a><br>
<a href="http://api.libreoffice.org/docs/current/idl/" target="_blank">http://api.libreoffice.org/<u></u>docs/current/idl/</a><br>
</blockquote></blockquote></blockquote>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Well, properly packaged versions come with their own api-docs, so<br>
IMHO no need to keep docs for unsupported releases around.<br>
</blockquote>
<br>
Packaged docs are much less practical for the user.<br>
</blockquote>
<br></div>
I always love it how <<a href="http://gcc.gnu.org/onlinedocs/" target="_blank">http://gcc.gnu.org/<u></u>onlinedocs/</a>> (linked as "Documentation: Manual" from the GCC homepage <<a href="http://gcc.gnu.org/" target="_blank">http://gcc.gnu.org/</a>>) unambiguously makes available the documentation for each released GCC major.minor version.  Could serve as a model for us.<span class="HOEnZb"><font color="#888888"><br>

<br>
Stephan</font></span><div class="HOEnZb"><div class="h5"><br>
______________________________<u></u>_________________<br>
LibreOffice mailing list<br>
<a href="mailto:LibreOffice@lists.freedesktop.org" target="_blank">LibreOffice@lists.freedesktop.<u></u>org</a><br>
<a href="http://lists.freedesktop.org/mailman/listinfo/libreoffice" target="_blank">http://lists.freedesktop.org/<u></u>mailman/listinfo/libreoffice</a><br>
</div></div></blockquote></div><br></div>