ubuntu-developer-manual team mailing list archive

[Kyle Nitzsche <kyle.nitzsche@xxxxxxxxxxxxx>]

How about;
 1. identify requirements
 2. identify options
 3. discuss
 4. decide

We have people with capabilities in LaTeX, docbook, mallard source 
formats/toolchains and each of these has distinct, albeit not obvious, 
implications for the above.

A comment from Mark Pilgrim's blog:

"My next book,Dive Into HTML5 <http://diveintohtml5.org/>, is also written in 
HTML, and my editor tells me that they will handle the nasty business of 
converting it into suitable formats for print."

In this case, we are the "editors".

Perhaps we can analyze this systematically on a wiki?

This is probably somewhat incorrect and self-aggrandizing ( ;), but I throw it 
out there to provide a format for information gathering and collective 
decision-making:

https://wiki.ubuntu.com/DesktopTeam/10.10/DeveloperManual/SourceFormatAnalysis

cheers,
Kyle

https://launchpad.net/doctemplate

On 01/24/2011 09:05 PM, Shane Fagan wrote:
> Hey,
>
> > Dang it, I wrote both of the Quickly tutorials in HTML, and then changed
> > them to docbook because someone told me I was "supposed to".
> Well I changed them :P Isnt the reason why we switched because its
> easier to use gettext with docbook than html.
>
> > I suppose we could author in HTML, and then use a transform to create
> > DocBook out of that if we are strict with our HTML.
> There is no way to actually transform from html to docbook at least not
> in the repo anyway. I looked pretty hard to find ways to do it but in
> the end I just swapped out the tags by hand. I could write up a script
> to do it if you want.
>
> --fagan
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~ubuntu-developer-manual
> Post to     : ubuntu-developer-manual@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~ubuntu-developer-manual
> More help   : https://help.launchpad.net/ListHelp