On Mon, 27 Aug 2018 11:14:28 -0500
Rob Gowin wrote:
> On Mon, Aug 27, 2018 at 7:50 AM, Mike Evans wrote:
> >
> > Hi Rob
> >
> > Referring to your mail of 2015-09-01 you "put the XSL file and a python
> > script to run the conversion process in a repository at
> >
One could, but I agree that a “General” component is better, so I’ve made one.
I think David’s 777893 belongs in the T, though, and he’s already moved it
there.
Regards,
John Ralls
> On Aug 27, 2018, at 10:39 AM, Derek Atkins wrote:
>
> Another option is to open bugs in each of the affected
Another option is to open bugs in each of the affected areas and reference
each other properly.
-derek
On Mon, August 27, 2018 1:30 pm, David T. via gnucash-devel wrote:
> Thanks, John; I found that about ten minutes after I sent it out!
>
> I do still think that a bug that crosses documents
Thanks, John; I found that about ten minutes after I sent it out!
I do still think that a bug that crosses documents causes categorization
issues. Adrien’s suggestion to add a General (I paraphrase) option might be
useful.
David
> On Aug 27, 2018, at 11:09 AM, John Ralls wrote:
>
>
>
>>
On Mon, Aug 27, 2018 at 7:50 AM, Mike Evans wrote:
>
> Hi Rob
>
> Referring to your mail of 2015-09-01 you "put the XSL file and a python
> script to run the conversion process in a repository at
> https://github.com/codesmythe/asciidoc-conversion.;
>
> This no longer exists, can you make it
> On Aug 27, 2018, at 7:28 AM, David T. via gnucash-devel
> wrote:
>
> Hello,
>
> I was just trying to track down the status of documentation bug 777893, and
> was stymied for a bit.
>
> A bit of history: I raised the bug to induce the addition of information
> about the SQL formats.
The Search function worked very well with the bug number and any combination of
the terms in the title. (or just a single term) But certainly, there could be a
‘product’ that covers *all/miscellaneous/generic* documentation bugs that apply
to multiple documents.
So I entered this:
Hello,
I was just trying to track down the status of documentation bug 777893, and was
stymied for a bit.
A bit of history: I raised the bug to induce the addition of information about
the SQL formats. Subsequently, I wrote a section for inclusion in the Guide,
which was submitted 10 days
On Thu, 23 Aug 2018 12:25:51 -0500
Rob Gowin wrote:
> On Thu, Aug 23, 2018 at 11:40 AM, John Ralls wrote:
>
> >
> >
> > So a new thought: One of the core devs use pandoc to convert the DocBook
> > source to one of the markup/markdown variants, do the necessary manual
> > fixups and commit the
