I apologize for my dumb question yesterday. While I had read everything I
could find, I obviously didn't absorb much.
For the PDF version truncated lines issue: I have figured out what to do and
done some test edits. At the same time, I might as well fix the cases where
there is not truncation in the PDF, but text extending beyond the box in the
HTML (one example is bug # 680392)
Many .xml files will have to be edited. Would it be a problem if I were to
edit a file that someone else is also working on? Or does the merge process
figure it out and manage to put multiple branches back together? I.E. From
the wiki page, I see several people have stuff in progress.
If this question also seems dumb, please know that previously I have only
ever used revision control systems that locked source files upon sign-out,
and needed to be signed back in before someone could edit.
From: Peter Matulis [mailto
Sent: March-08-2012 08:19
To: Doug Smythies
Subject: Re: The Ubuntu Server Guide wants YOU!
On 12-03-08 10:58 AM, Doug Smythies wrote:
> Hi Everyone,
> I assume the HTML version of the serverguide is the master, and the
> PDF version is created from that master.
> I would like to try to fix the PDF version truncated lines problem
> 590519 and duplicate 674861) and the table format problem (Table 2.1,
> maybe others).
> For my "how to" do this stuff, I am using
> My question: How do I create the PDF version on my local bzr branch,
> the exact same way it would be done for real? I.E. How can I test any
> proposed changes in the HTML will give the desired result in the PDF
> before submitting a merge proposal?
As explained in the above wiki, you should read the rest of the Doc team
documentation to know more about how things are done. For instance, under
the Building link (at the top) you will find your answer.
ubuntu-server mailing list
More info: https://wiki.ubuntu.com/ServerTeam