At some point we'll have a full v3.4 book of chapters that will need to be
linked from the website along with the v3.3 chapters, so we'll need to
decide how best to show the two streams. I'm thinking about possibilities
but haven't come to any conclusions yet.

It's not clear to me whether your objection is to having the two streams or
having the second stream be incomplete.

--Jean

On Wednesday, November 30, 2011, Tom Davies <[email protected]> wrote:
> Hi :)
> I think it might be confusing to add them to the website.  I carefully
set-up tables on the wiki to make it clear about which chapter belongs to
the guide for which branch but that sort of thing would just be confusing
on the website.
> Regards from
> Tom :)
>
> --- On Wed, 30/11/11, Jean Weber <[email protected]> wrote:
>
>> From: Jean Weber <[email protected]>
>> Subject: [libreoffice-documentation] Re: Published chapters of Getting
Started and Writer Guide
>> To: [email protected]
>> Date: Wednesday, 30 November, 2011, 8:43
>> On Wed, Nov 30, 2011 at 18:42, Jean
>> Weber <[email protected]>
>> wrote:
>> > I've published those few chapters of Getting Started
>> and Writer Guide
>> > for LO v3.4 that have been reviewed by both Hazel and
>> me, and I have
>> > put them on the wiki.
>> > https://wiki.documentfoundation.org/Documentation/Publications
>> >
>> > They are not yet linked from the website; I haven't
>> had time. I'm also
>> > a bit dubious about putting incomplete lists of
>> chapters on the
>> > website, even though I'm happy to have them on the
>> wiki. What do you
>> > think?
>> >
>>
>>
>> By "on the website" I mean this page:
>> http://www.libreoffice.org/get-help/documentation/
>>

-- 
Unsubscribe instructions: E-mail to [email protected]
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/documentation/
All messages sent to this list will be publicly archived and cannot be deleted

Reply via email to