Where can I get the latest version of Ubuntu Server Guide(PDF)?

[Dougie Richardson]

I understand that we can't build one big book but what I said is we
can do sections as PDF.

Internet justs requires "dblatex internet.xml" and bob's your uncle. I
haven't tried any of the other sections yet and I created this section
as a book containing chapters which might make a difference.

Incedently, the malformed tables in the server guide are because of
the size of the table in the XSL.

I built a one off server guide for 7.10 and had to rewrite the tables
to make them compile but dblatex seems not to throw an exception over
this now. I can't remember the exact size but it was either 620 or
680px wide and it didn't like them.

2009/4/7 Matthew East <mdke at ubuntu.com>:
> Hi,
>
> (amending quoting and back on list)
>
> On Tue, Apr 7, 2009 at 11:15 AM, Dougie Richardson
> <dougierichardson at ubuntu.com> wrote:
> On 2009/4/7 Matthew East <mdke at ubuntu.com>:
>>> Hi,
>>>
>>> On Mon, Apr 6, 2009 at 11:30 PM, Jim Campbell <jwcampbell at ubuntu.com> wrote:
>>>> On Mon, Apr 6, 2009 at 4:46 PM, Dougie Richardson
>>>> <dougierichardson at ubuntu.com> wrote:
>>>>> Thanks Matthew,
>>>>>
>>>>> this gets requested quite regularly - should we think about more PDF
>>>>> integration for Karmic?
>>>>>
>>>>
>>>> Is it that certain links don't work when converted to PDF?  If so,
>>>> what kinds of links break?
>>>
>>> The issue is not really the tools - fop is relatively stable now and
>>> the xsl required isn't particularly complicated. It's
>>>
>>> Our documentation is written to be part of a coherent system of
>>> documentation. As a result it contains a lot of links pointing to
>>> other documents and individual application manuals. These just won't
>>> work with PDF, because there is no method of linking one PDF to
>>> another.
>>>
>>> The Server Guide is ideal for PDF conversion, because it is a
>>> standalone document. But our other documents are not, and I can't
>>> think of any way to resolve that issue at the moment. It's simply the
>>> difference between writing standalone "books" or "articles", and
>>> writing a help system. The two types of documentation also require
>>> different styles, as well as different structures.
>>>
>>> The only solution is to develop two types of documentation, one for
>>> the system help, and another "book" about Ubuntu on the desktop. I'm
>>> fairly confident that maintaining two types of documentation alongside
>>> each other is beyond our scope and resources as a team.
>>
>> That's true but doesn't preclude the possibility of a PDF for each article.
>
> Well, I think it does and have given reasons. Can you explain how we'd
> get around those issues?
>
> --
> Matthew East
> http://www.mdke.org
> gnupg pub 1024D/0E6B06FF
>
> --
> ubuntu-doc mailing list
> ubuntu-doc at lists.ubuntu.com
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-doc
>



-- 
Regards,

Dougie Richardson
http://www.lynxworks.eu/
dougierichardson at ubuntu.com