I can't say what's wrong with DocBook, because using Org is a personal
preference of mine, so first and most important: This is personal
opinion.
* Pros of Org Mode
- Org Mode's markup is easier to understand and start using. No need to
remember tag names (at least for most used formating
Thank you Derek,
This improves my understanding of the current situation considerably.
Certainly as I noted, I have no issue using the present methods.
Thank you for taking the time to explain this.
Regards,
Adrien
> On May 25, 2017, at 9:45 AM, Derek Atkins wrote:
>
>
Adrien,
Adrien Monteleone writes:
> Geert,
>
> If the opposite were possible, would that meet the needs?
>
> If using the wiki as the collaboration platform opened up
> documentation editing to non-developer types but still gave you the
> desired formats, is that
> On May 24, 2017, at 11:43 AM, Geert Janssens
> wrote:
>
> On woensdag 24 mei 2017 17:16:41 CEST Derek Atkins wrote:
>> Michael Ferrara writes:
>>>There's no good way to translate from Wiki to PDF
>>>
>>> Really? PDF can handle hard links
On woensdag 24 mei 2017 17:16:41 CEST Derek Atkins wrote:
> Michael Ferrara writes:
> > There's no good way to translate from Wiki to PDF
> >
> > Really? PDF can handle hard links within a document. Reference books with
>
> Yes, really. And it's more than just PDF. We
Adrien Monteleone writes:
> On that note, I already knew about html2pdf for *nix, but even better
> - there’s this: Extension:Pdf_Export on the mediawiki site.
Docs are in HTML, PDF, Mobi, and I believe one more format. There's no
tool that I'm aware of that will
Adrien Monteleone writes:
> I’m certainly no expert on the matter and I have no beef with the GIT
> process for documentation, but that seems odd at first glance since
> wikis are markdown inside HTML which is a subset of XML which the doc
> procedures turn into PDF.
Adonay Felipe Nogueira writes:
> Personally, I think this would be mostly solved by switching to TeXInfo,
> or to Org Mode. The latter also supports TeXInfo publication.
What's wrong with Docbook?
-derek
--
Derek Atkins, SB '93 MIT EE, SM '95 MIT Media
There's no good way to translate from Wiki to PDF
Really? PDF can handle hard links within a document. Reference books with
linearly organized chapters and cross-references have been around since
before the Bible. Understandably, the wiki is spineless and completely
semantic in the way its pages
> On May 23, 2017, at 8:50 PM, Adrien Monteleone
> wrote:
>
>>
>> On May 23, 2017, at 3:22 PM, Derek Atkins wrote:
>>
>> Hi,
>>
>> On Tue, May 23, 2017 1:11 pm, doncram wrote:
>>> Wow the process to change documentation (at
>>>
> On May 23, 2017, at 3:22 PM, Derek Atkins wrote:
>
> Hi,
>
> On Tue, May 23, 2017 1:11 pm, doncram wrote:
>> Wow the process to change documentation (at
>> http://wiki.gnucash.org/wiki/Documentation_Update_Instructions ) seems
>> pretty complicated, even impossible for
Thanks for replies. I had previously confirmed my email, but I tried again
now and it works, and I made a first edit at the page named "Concept Guide"
to clarify that the page is to be about development of the GnuCash Tutorial
and Concept Guide. I also revised the Introduction and set up a
Hi,
On Tue, May 23, 2017 1:11 pm, doncram wrote:
> Wow the process to change documentation (at
> http://wiki.gnucash.org/wiki/Documentation_Update_Instructions ) seems
> pretty complicated, even impossible for Windows users.
What's so complicated about a git checkout and using the appropriate
Personally, I think this would be mostly solved by switching to TeXInfo,
or to Org Mode. The latter also supports TeXInfo publication.
--
- [[https://libreplanet.org/wiki/User:Adfeno]]
- Palestrante e consultor sobre /software/ livre (não confundir com
gratis).
- "WhatsApp"? Ele não é livre,
Wow the process to change documentation (at
http://wiki.gnucash.org/wiki/Documentation_Update_Instructions ) seems
pretty complicated, even impossible for Windows users. I would hope it
should be possible to have a full working version of the Tutorial and
Concepts Guide that is open for
On dinsdag 2 mei 2017 18:10:35 CEST David T. via gnucash-devel wrote:
> Here’s what I mean:
>
> On the Documentation Update instructions, section 3 contains 17 different
> steps.
>
> Step 3.1: Create a Bugzilla Bug is a step that should be undertaken with
> every proposed change to the
> On May 2, 2017, at 8:16 PM, Derek Atkins wrote:
>
> David,
>
> First, sorry to come at this late...
>
> "David T. via gnucash-devel" writes:
>
>> Hello,
>>
>> Once again, the documentation bug has bit me, and I am trying to use
>> the accepted
David,
First, sorry to come at this late...
"David T. via gnucash-devel" writes:
> Hello,
>
> Once again, the documentation bug has bit me, and I am trying to use
> the accepted GnuCash toolset to implement a change to the Guide.
Excellent. Thank you for your
On zaterdag 29 april 2017 09:03:54 CEST David T. via gnucash-devel wrote:
> So, apparently, there is a decision-making process in place. I’m not sure
> how it might be improved, since this is quite literally the first I have
> heard about it.
>
> Since you seem to be one of the folks in charge of
So, apparently, there is a decision-making process in place. I’m not sure how
it might be improved, since this is quite literally the first I have heard
about it.
Since you seem to be one of the folks in charge of the decisions on the wiki,
perhaps *you* might consider how to improve the
David,
Am 27.04.2017 um 14:01 schrieb David T.:
> Frank,
>
> I don't know what you mean by "ninja status", and I don't
> particularly care, but I do know that without some mechanism for
> resolving disagreements on content, a wiki doesn't really function
> well, since it leaves the resolution of
Frank,
I don't know what you mean by "ninja status", and I don't particularly care,
but I do know that without some mechanism for resolving disagreements on
content, a wiki doesn't really function well, since it leaves the resolution of
such disagreements to the person who is willing to push
David,
I am really sorry, but you and 2 other authors got by accident a
ninja-like status for a few month in the wiki. So your changes did not
appear on
http://wiki.gnucash.org/wiki/Special:RecentChanges . Else we would have
given you earlier some advice, were we thought your changes might have
Geert,
See below.
> On Apr 26, 2017, at 5:54 PM, Geert Janssens
> wrote:
>
> By doing so you may have implicitly configured your source directory
> resulting
> in the errors below. As a rule of thumb, avoid running any "make" command in
> your source tree. The
David,
Am 25.04.2017 um 16:33 schrieb David T. via gnucash-devel:
> Hello,
>
> Once again, the documentation bug has bit me, and I am trying to use
> the accepted GnuCash toolset to implement a change to the Guide.
>
> Most recently, this toolset has been changed to use “make”, and when
> I
Hello,
Once again, the documentation bug has bit me, and I am trying to use the
accepted GnuCash toolset to implement a change to the Guide.
Most recently, this toolset has been changed to use “make”, and when I attempt
to refresh my memory by going to the wiki page, I fail to find an
26 matches
Mail list logo