Hello !
Am 06.11.2010 16:57, schrieb John Ralls:
On Nov 6, 2010, at 4:09 AM, Christoph Holtermann wrote:
Could you give me a hint if there is a central starting point for
documentation
for example the website XXX or whatever or is it necessary to pick up bits
and pieces
Christoph Holtermann c.holterm...@gmx.de writes:
Hello !
Am 06.11.2010 16:57, schrieb John Ralls:
On Nov 6, 2010, at 4:09 AM, Christoph Holtermann wrote:
Could you give me a hint if there is a central starting point for
documentation
for example the website XXX or whatever
John Ralls jra...@ceridwen.us writes:
On Nov 6, 2010, at 4:09 AM, Christoph Holtermann wrote:
[snip]
Could you give me a hint if there is a central starting point for
documentation
for example the website XXX or whatever or is it necessary to pick up bits
and pieces here and there and even
Hello !
I got a question regarding the documentation of the gnucash-sources. I just
wandered around a bit in the directorys on my quest for documentation ;-).
I came across /src/engine/design.txt which told me
This document is becoming obsolete. Please refer to the design
documentation in
On Nov 6, 2010, at 4:09 AM, Christoph Holtermann wrote:
Hello !
I got a question regarding the documentation of the gnucash-sources. I just
wandered around a bit in the directorys on my quest for documentation ;-).
I came across /src/engine/design.txt which told me
This document is
Christian Stimming wrote:
Am Montag, 2. Februar 2009 14:08 schrieb Alan Jenkins:
This affects bullet point characters in src/optional/xsl/README, and
Benoit Grégoire's name in source files (and hence the Doxygen output).
Applied to trunk. Thanks a lot.
E.g. it should fix
Am Montag, 2. Februar 2009 14:08 schrieb Alan Jenkins:
This affects bullet point characters in src/optional/xsl/README, and
Benoit Grégoire's name in source files (and hence the Doxygen output).
Applied to trunk. Thanks a lot.
E.g. it should fix
://svn.gnucash.org/docs/HEAD/reference.html
which claims to be UTF8, but encodes Benoit's name in latin-1.
--
Attached (to avoid my mail client mangling the encoding).
Convert source documentation to UTF8
Most of the source tree is UTF8, but there are some latin-1 hangovers.
Apply iconv --from-code
