2009/7/16 Steve Borho <st...@borho.org>
> On Thu, Jul 16, 2009 at 5:35 AM, Giampaolo Fadel<gp.fa...@gmail.com>
> wrote:
> >> 2009/7/16 Steve Borho <st...@borho.org>
> >> Is the base input file in XML? If so that's a bit regrettable, as XML
> >> is not a very writer friendly format. We should look into one of the
> >> more simpler markup languages like reST that can produce input for
> >> docbook.
> >
> > Yes, the input file is XML! I agree with you it is not so confortable to
> > edit in plain text,
> > but exist some editors that help a lot, like xmlmind or packages for
> emacs.
> > TortoiseSVN
> > manual is written directly in docbook (there is in its repository a
> > hacking.txt with some rules
> > that we can apply here). 'Mercurial. The definitive guide' has switched
> from
> > Latex to docbook.
> >
> > Now I'll look into reST and I'll test it.
>
> Great.
>
Started! Obviously the help from anyone is very very welcome.
>
> >>
> >> > I think that after the alignment of the content, it's time to move the
> >> > project in a subfolder of thg project, so it can better follow the new
> >> > features of thg and it can be integrated in the thg build process.
> >>
> >> Certainly.
> >
> > Now my repository is aligned with the wiki, and I've updated the download
> > section.
> > So if you want you can include them in the next 0.8.1 distribution .
> > I suggest you to wait the analysis of reST before move the repository in
> the
> > thg project.
>
> When I create 0.8.1, I'll take the docs available for download from
> your project page.
>
> BTW: The urls for bitbucket in the PDF header do not need www in front of
> them.
Fixed and uploaded
>
>
> >>
> >>
> >> > I'd like to know if TK is doing some work in contrast with my work and
> >> > what
> >> > he think.
> >> >
> >> > The stylesheet can be improved a lot but we can do it day by day.
> >> >
> >> > Up now there is no wiki Creole output so the online manual must be
> >> > remove or
> >> > we have two manual source documentation.
> >>
> >> Yep, I'll do this at the same time. This wiki will just have the CHM
> >> and PDF files for download, until we get a web host that can serve
> >> static HTTP pages.
> >
> > Yes
> >
> >
> > One things. Actually I've translated each wiki file of the manual in a
> > single chapter.
> > The result is that we have many chapter even for a simple topic.
> > I think it's better to give a better architecture to the whole manual,
> for
> > example, we can
> > write all the chapter with the title and the text TODO inside it. So the
> > manual structure doesn't
> > have big change in the time and we can easily fill it. Do you have any
> idea
> > on how this structure
> > will be? I'll try to look into the TortoiseXXX manuals!
>
> I agree it could be arranged better. There are people who do this
> sort of thing for a living, and I am not one of them, so I'm not going
> to try to lay down the law on the document layout. It does not need
> to follow the Wiki layout, that's for certain.
Sure that, I am less good than you in this. Even here help from anyone is
welcome.
>
>
> Moving the TODO lists into their own document is not a bad idea.
>
> --
> Steve Borho
>
paolo
------------------------------------------------------------------------------
Enter the BlackBerry Developer Challenge
This is your chance to win up to $100,000 in prizes! For a limited time,
vendors submitting new applications to BlackBerry App World(TM) will have
the opportunity to enter the BlackBerry Developer Challenge. See full prize
details at: http://p.sf.net/sfu/Challenge
_______________________________________________
Tortoisehg-develop mailing list
Tortoisehg-develop@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/tortoisehg-develop
