Le samedi 18 juillet 2009 à 03:31 -0700, Graham Percival a écrit :
> Good point. I had a vague notion that having them there might
> make it easier to produce the top-level *.txt files, but I
> honestly would rather have them moved. If you're happy with that,
> then by all means let's move them.
On Sat, Jul 18, 2009 at 12:03:04PM +0200, John Mandereau wrote:
> I'd like to start working on the plan below real soon now
I'd also like you to start working on it real soon now. :)
Especially the creation on essay; that way, I can start doing the
doc rearrangement and tackle the content of the
On Sat, Jul 18, 2009 at 12:07:28PM +0200, John Mandereau wrote:
> Le jeudi 16 juillet 2009 à 16:45 +0200, John Mandereau a écrit :
> > Have you realized that it will make browsing Git history
> > more difficult and require hackery in translation checking scripts to
> > follow old history of files f
Le jeudi 16 juillet 2009 à 16:45 +0200, John Mandereau a écrit :
> Have you realized that it will make browsing Git history
> more difficult and require hackery in translation checking scripts to
> follow old history of files from docs/ to Documentation? We have this
> problem for input/texidocs,
I'd like to start working on the plan below real soon now so it can be
finished by the end of August; if it isn't I might have no time to
complete this within a year.
Le samedi 11 juillet 2009 à 03:21 -0700, Graham Percival a écrit :
> docs/
> docs/learning.tely
> docs/learning/*.itely
> docs/not
On Thu, Jul 16, 2009 at 04:45:35PM +0200, John Mandereau wrote:
> Le jeudi 16 juillet 2009 à 04:46 -0700, Graham Percival a écrit :
> > It's impossible to miss, as is
> > INSTALL.txt in the tarball, so the masocists that want to compile
> > from source can still find their instructions.
>
> Do you
Le jeudi 16 juillet 2009 à 04:46 -0700, Graham Percival a écrit :
> On Thu, Jul 16, 2009 at 01:30:56AM +0200, John Mandereau wrote:
> > I assume you mean Documentation.
>
> No; I really want to rename that dir. I've wanted to rename it
> since I first got involved in lilypond. Typing shift-d has
On Thu, Jul 16, 2009 at 04:02:28PM +0200, Valentin Villenave wrote:
> Another point is that, as far as I can see, we're ready to happily
> break any existing links to the former documentation, as well as URLs
> we've been using for years such as lily.org/web/install... and it's a
> bit frightening
2009/7/16 John Mandereau :
> The hourly script is useful to allow any web site maintainer to react
> quickly against typos and minor bugs that don't require fixing the
> Makefile or Python scripts, whereas it could take much longer if you (or
> another maintainer) are the only person that can fix
On Thu, Jul 16, 2009 at 01:30:56AM +0200, John Mandereau wrote:
> Le samedi 11 juillet 2009 à 03:21 -0700, Graham Percival a écrit :
> > docs/
>
> I assume you mean Documentation.
No; I really want to rename that dir. I've wanted to rename it
since I first got involved in lilypond. Typing shift
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Am Donnerstag, 16. Juli 2009 01:30:56 schrieb John Mandereau:
> Speaking of cross-references, I'll add sooner or later a makefile hook
> that runs the cross-reference checking script I wrote and/or some
> Texi2html-internal hook, which will break the d
Le samedi 11 juillet 2009 à 03:21 -0700, Graham Percival a écrit :
> Here's my proposal for the source/makefile view of documentation.
> (this is the big argument one)
...and here is my big reply :-P
> My understanding is that linking between texinfo manuals is easier
> if the main files are in
On Sat, Jul 11, 2009 at 03:02:33PM -0600, Carl Sorensen wrote:
>
> On 7/11/09 4:21 AM, "Graham Percival" wrote:
>
> > Here's my proposal for the source/makefile view of documentation.
> > (this is the big argument one)
>
> In general, I think these proposals are reasonable.
Actually, giving it
Carl Sorensen wrote:
As much as I like the lsr, I don't like having documentation depend on the
lsr. I shouldn't have to put snippets in the lsr in order to get them in
the documentation, or else I should have a much easier way of getting them
into the lsr.
Would it be easier to email the
On 7/11/09 4:21 AM, "Graham Percival" wrote:
> Here's my proposal for the source/makefile view of documentation.
> (this is the big argument one)
>
In general, I think these proposals are reasonable.
>
> My understanding is that linking between texinfo manuals is easier
> if the main files
Here's my proposal for the source/makefile view of documentation.
(this is the big argument one)
My understanding is that linking between texinfo manuals is easier
if the main files are in the same directory. With that in mind, I
propose:
docs/
docs/learning.tely
docs/learning/*.itely
docs/nota
16 matches
Mail list logo
