sed error

2017-01-17 Thread Stephen Brown 
Hi All,

In a msys shell I see
--
GNUCash@Ace ~
$ cd /c/gcdev/gnucash-on-windows.git

GNUCash@Ace /c/gcdev/gnucash-on-windows.git
$ install.sh
Build Starting at Wed Jan 18 16:59:56 AUSEDT 2017


###  MSys

Updating catalogue: package-list.xml; (item 1 of 1)
Checking catalogue: mingw32-package-list.xml; (item 2 of 4)
Checking catalogue: mingw32-autoconf.xml; (item 3 of 37)
Checking catalogue: mingw32-automake.xml; (item 4 of 37)
Checking catalogue: mingw32-basic-bsdtar.xml; (item 5 of 37)
Checking catalogue: mingw32-binutils.xml; (item 6 of 37)
Checking catalogue: mingw32-bzip2.xml; (item 7 of 37)
Checking catalogue: mingw32-dos2unix.xml; (item 8 of 37)
Checking catalogue: mingw32-expat.xml; (item 9 of 37)
Checking catalogue: mingw32-gcc3.xml; (item 10 of 37)



Checking catalogue: msys-base.xml; (item 110 of 112)
Checking catalogue: mingw-developer-toolkit.xml; (item 111 of 112)
Checking catalogue: msys-system-builder.xml; (item 112 of 112)
upgrade: mingw-get-0.6.2-mingw32-beta-20131004-1-gui.tar.xz
mingw-get.exe: *** INFO *** package 
mingw-get-0.6.2-mingw32-beta-20131004-1-gui.tar.xz is up to date
upgrade: mingw-get-0.6.2-mingw32-beta-20131004-1-lic.tar.xz
mingw-get.exe: *** INFO *** package 
mingw-get-0.6.2-mingw32-beta-20131004-1-lic.tar.xz is up to date
Attempting to install msys-wget-1.12-1
  0 [main] sed 9840 open_stackdumpfile: Dumping stack trace to 
sed.exe.stackdump

GNUCash@Ace /c/gcdev/gnucash-on-windows.git
$

How do I fix sed?

Cheers
Stephen Grant Brown
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

RE: Document Update Instructions have been revised

2017-01-17 Thread Chris Good 
> -Original Message-
> From: Geert Janssens [mailto:geert.gnuc...@kobaltwit.be]
> Sent: Tuesday, 17 January 2017 10:14 PM
> To: Chris Good 
> Cc: GnuCash Developers 
> Subject: Re: Document Update Instructions have been revised
> 
> Op dinsdag 17 januari 2017 11:16:39 CET schreef Chris Good:
> > Hi,
> >
> >
> >
> > I've finished updating the wiki Document Update Instructions [1] to
> > include instructions for using 'make' rather than xmllint and xsltproc
> directly.
> >
> > Thank you very much Geert for all the info.
> >
> >
> >
> > [1] http://wiki.gnucash.org/wiki/Documentation_Update_Instructions
> >
> >
> >
> > Regards, Chris Good
> 
> Chris,
> 
> Thanks for improving our documentation on improving our documentation ;)
> 
> Seriously, I appreciate the effort you're spending here.
> 
> I'm proof reading what you have written and below follow some remarks:
> 
> * You are referring to the required use of make, which I like obviously as
I
> suggested that myself. What is not clear in your documentation however is
> how to obtain make and the related tools. On linux this is usually
obtained via
> the package manager. There is usually some kind of package group related
to
> development that installs all the required dependencies in one go. On OS X
I
> don't know how to get it. That's John's expertise although David T may
know
> this by now as well... And on Windows it's probably even more complicated.
> TBH I never tried manually building the gnucash documentation on that
> platform, so I can't give precise instructions. It will likely involve
installing an
> msys environment.
> 
> * Step 5 confuses me:
> "Experienced developers instruct that you should focus first on the
modules
> in either of these two directories (found in the step 1 downloaded files):
> gnucash-docs/help/C or gnucash-docs/guide/C. "
> What do you mean by this ? The "C" directories contain the documentation
in
> English. All other directories contain translations of these in other
languages.
> As I see it there is no need to present this as some kind of mythical
> knowledge only understood by "Experienced developers".
> 
> * The next paragraph confuses me as well. How would opening each file
> reveal errors ? This is not really clear to me.
> 
> * A bit further you suggest to add a pair of comments around your changes
> to help translators. I would propose not to do that as I believe this is
> redundant information. This is what a version management system is used
> for.
> One can use the git history to see what has changed since the last time
one
> has worked on the translation. There are graphical tools like gitk or the
github
> website that help you visualize these changes.
> 
> * "If you are adding or deleting an xml file, for example adding a new
chapter
> or appendix, you also need to update files
[guide|help]/[language]/gnucash-
> {guide|help}.xml and [guide|help]/[language]/Makefile.am. There is no
> need to update Makefile.in as this is generated by running autogen.sh."
> Perhaps here it's best to more explicitly state autogen.sh and
../configure.sh
> should be re-run.
> 
> * There is a section on testing the documentation locally on linux. I have
> slightly modified it, because parts of it were outdated. And I'm
considering
> whether we shouldn't simplify it even more. For now I have stated you can
> run this test with any version of gnucash higher than 2.6.0, with the
> restriction that yelp is installed and working. The text is not too clear
about
> that second part, but that is what the "linux" restriction is actually all
about.
> This does reduce the cases where a full build of a development version of
> gnucash is necessary IMO. It believe this is only necessary when you want
to
> test context help for features that are only in a more recent version than
you
> currently have. But this begs the question whether we really need gnucash
> at all in the other cases. Only yelp suffices as explained at the end of
step
> 11.3. Perhaps we should make that the preferred testing method and only
> propose linux tests in case new context help should be tested. What do you
> think ?
> 
> * Lastly you describe how to format a patch. While this is certainly one
of the
> accepted methods, it may be interesting to document how to make a pull
> request as well.
> 
> That's it. Again, thanks for all the effort you spent on this so far!
> 
> Regards,
> 
> Geert

Hi Geert,

Thanks for reviewing my work and adding extra suggestions. I really enjoy
learning more from your insights. I like to know, at least generally, 'why',
as well as 'how'.
I totally agree your suggestions would be helpful to new documenters. I'm a
little concerned that the bulk of this page could be a little off-putting.
However, I think it is better to have too much info than not enough.
I would like to point out that your suggestions are mostly changes to things
other people wrote. :-)

Originally, I myself started

Re: GnuCash page Glossary has been changed by Sunfish62

2017-01-17 Thread David via gnucash-devel 
Frank,

I appreciate your input.

Personally, I feel that information should be provided at its most direct 
point. Definitions that relate to GnuCash, and to GnuCash specifically, were 
terms I left in. Definitions that, while helpful but more generally applicable 
to an operating system or programming platform, were terms I removed. At some 
point, a line needs to be drawn between what gets kept, and what is left out. I 
draw it more closely to GnuCash than you do.

Many of these terms are, as you imply, more important to the development -- 
that is, the actual coding -- of GnuCash. I see the wiki as a more end user 
resource now, which might also explain the difference in content choice.

Since you feel strongly about this, I apologize. I also don't agree, however.

Best,
David



_
From: "Frank H. Ellenberger" 
Sent: Tue Jan 17 23:44:20 GMT+05:00 2017
To: "David T." 
Cc: "gnucash-devel@gnucash.org" 
Subject: Re: GnuCash page Glossary has been changed by Sunfish62


Hi David,

I do not agree with you cleanup. All terms here have been asked on our
different support channels.

When I created the page I moved a bunch of simple questions from the
FAQ. Later I moved a few terms which were explained on multiple pages -
often in contradictory versions.

Almost every term was asked in one or the other way. And many are
referenced somewhere else in the wiki.

While the glossary in the documents has no need for DocBook, Doxygen,
... the developer pages of the wiki reference them.

So I will revert your change.

Regards
Frank

Am 17.01.2017 um 12:47 schrieb GnuCash:
> Dear Fell,
> 
> The GnuCash page Glossary has been changed on 17 January 2017 by
> Sunfish62, see https://wiki.gnucash.org/wiki/Glossary for the current
> revision. 
> 
> See
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=next=12403
> to view this change.
> 
> See
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=0=12403
> for all changes since your last visit.
> 
> Editor's summary: Add note to refer readers to Guide Glossary, and to
> remove generic definitions not directly germane to GnuCash 
> 
> Contact the editor:
> mail: https://wiki.gnucash.org/wiki/Special:EmailUser/Sunfish62
> wiki: https://wiki.gnucash.org/wiki/User:Sunfish62
> 
> There will be no other notifications in case of further activity unless
> you visit this page while logged in. You could also reset the
> notification flags for all your watched pages on your watchlist.
> 
> Your friendly GnuCash notification system
> 
> --
> To change your email notification settings, visit
> https://wiki.gnucash.org/wiki/Special:Preferences
> 
> To change your watchlist settings, visit
> https://wiki.gnucash.org/wiki/Special:EditWatchlist
> 
> To delete the page from your watchlist, visit
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=unwatch
> 
> Feedback and further assistance:
> https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: GnuCash page Glossary has been changed by Sunfish62

2017-01-17 Thread Frank H. Ellenberger 
Hi David,

I do not agree with you cleanup. All terms here have been asked on our
different support channels.

When I created the page I moved a bunch of simple questions from the
FAQ. Later I moved a few terms which were explained on multiple pages -
often in contradictory versions.

Almost every term was asked in one or the other way. And many are
referenced somewhere else in the wiki.

While the glossary in the documents has no need for DocBook, Doxygen,
... the developer pages of the wiki reference them.

So I will revert your change.

Regards
Frank

Am 17.01.2017 um 12:47 schrieb GnuCash:
> Dear Fell,
> 
> The GnuCash page Glossary has been changed on 17 January 2017 by
> Sunfish62, see https://wiki.gnucash.org/wiki/Glossary for the current
> revision. 
> 
> See
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=next=12403
> to view this change.
> 
> See
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=0=12403
> for all changes since your last visit.
> 
> Editor's summary: Add note to refer readers to Guide Glossary, and to
> remove generic definitions not directly germane to GnuCash 
> 
> Contact the editor:
> mail: https://wiki.gnucash.org/wiki/Special:EmailUser/Sunfish62
> wiki: https://wiki.gnucash.org/wiki/User:Sunfish62
> 
> There will be no other notifications in case of further activity unless
> you visit this page while logged in. You could also reset the
> notification flags for all your watched pages on your watchlist.
> 
> Your friendly GnuCash notification system
> 
> --
> To change your email notification settings, visit
> https://wiki.gnucash.org/wiki/Special:Preferences
> 
> To change your watchlist settings, visit
> https://wiki.gnucash.org/wiki/Special:EditWatchlist
> 
> To delete the page from your watchlist, visit
> https://wiki.gnucash.org/wiki/index.php?title=Glossary=unwatch
> 
> Feedback and further assistance:
> https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Contents
> 

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: cpp branch

2017-01-17 Thread Geert Janssens 
Op dinsdag 17 januari 2017 13:34:44 CET schreef Robert Fewell:
> Geert,
> 
> The boost error was due to me not building boost with icu support.
> 
I'm glad you managed to get past this.

> I have pulled your cpp branch and tried to build which was OK but had some
> errors when I used it.
> With the following changes at
> https://github.com/Bob-IT/gnucash/commits/fork_branch, I can import a csv
> file with no observed errors.
> 
> You may already have noticed them but you never know.
> 
Thanks for debugging my work. I was aware I still had some issues to debug in 
the fixed width importer. You've hit several of them. I'll evaluate your 
commits when I have some time again to work on gnucash.

> Now to look at the price importer...
> 
Heh, have fun!

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: cpp branch

2017-01-17 Thread Robert Fewell 
Geert,

The boost error was due to me not building boost with icu support.

I have pulled your cpp branch and tried to build which was OK but had some
errors when I used it.
With the following changes at
https://github.com/Bob-IT/gnucash/commits/fork_branch, I can import a csv
file with no observed errors.

You may already have noticed them but you never know.

Now to look at the price importer...

Bob

On 10 January 2017 at 18:26, Geert Janssens 
wrote:

> Op dinsdag 10 januari 2017 15:38:27 CET schreef Robert Fewell:
> > Geert,
> >
> > Thank you for the comments, especially the date ones which now make
> sense.
> > I will have a look at my changes and why I made them as it may relate to
> > changes I will need to the price importer.
> >
> You're welcome :)
>
> I have just pushed the most recent state of my cpp branch (minus a final
> work
> in progress) to my github repository. You may want to rebase to that one.
> It
> should present a more or less usable csv transaction import assistant.
>
> Note I don't expect you to take the whole transaction related code for your
> price importer. You may follow the design obviously if it suits you as
> well.
> But I think there are a number of useful classes in there which you
> probably
> can reuse as they are. I'm thinking about the gnc-tokenizer class and its
> subclasses for csv separated or fixed width column data. They should allow
> you
> to split your csv file in a table of values to be interpreted by a price
> specific parser. For transaction importing this specific parser is
> implemented
> in the GncTxImport class (note the absence of "csv" in that name - I
> believe
> the class is generic enough to also handle transactions coming from qif or
> ofx
> data in the future by adding specialized tokenizers for these formats).
>
> The design principles in my csv importer are as follows:
> - the assistant code is "dumb". It's responsible for displaying data and
> passing user commands to the real parser. So it shouldn't make any
> decisions
> other than what's needed to properly display all the information (including
> enabling/disabling options and buttons)
> - the real intelligence is stored in the GncTxImport class, which is
> responsible for everything related to the data. It will massage the data
> found
> in the input file into proper gnucash transactions. This class is
> completely
> gui-less, so it could potentially even be used from non-gui interactions,
> such
> as our python bindings (if someone would add the currently still missing
> bindings).
> - Some parts are delegated to helper classes. One such example is the
> tokenizer class which handles everything from loading a file to splitting
> the
> data into a table of strings. From there GncTxImport takes over. The
> settings
> are also stored in a separate class to simplify loading and saving user
> presets and switching between them. This is heavily based on your initial
> work
> to load and save these presets, mostly reworked into a c++ class and
> redesigned a bit to make it a more central piece of the GncTxImport class.
>
> I hope this information will help you better understand the new csv
> importer
> and at the same time help you to model your own price importer, which can
> probably be implemented less generically. I would keep the strict
> separation
> of gui and business logic though. Make your price importer class such that
> it
> can be used without a gui and let the gui interact with it by querying the
> information it needs/passing the inputs it receives from the user.
>
> Regards,
>
> Geert
>
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Wiki Section on Reports

2017-01-17 Thread David T. via gnucash-devel 
I have updated the Wiki for this section, and included a link to the new 
Reports chapter. I hope it works for everyone.

David

> On Jan 17, 2017, at 4:17 PM, Geert Janssens  
> wrote:
> 
> Op maandag 16 januari 2017 09:48:51 CET schreef David T. via gnucash-devel:
>> Hello,
>> 
>> I will start by saying: “Yes, I know it’s a wiki…”
>> 
>> However, now that the Reports chapter (which incorporates nearly all the
>> Wiki reports information verbatim) is officially available as part of the
>> normal Documentation distribution, I propose removing this information in
>> the wiki, and adding a note to say that the wiki information has been moved
>> to the Tutorial and Concepts Guide as of GnuCash 2.6.15.
>> 
>> As this is rather a substantial amount of information that will go away from
>> the wiki, I thought it best to double check in the community before acting.
>> 
> I also prefer removing this from the wiki.
> 
> There simply is not enough people around to properly maintain the information 
> in two places and keep them in sync.
> 
> I don't mind keeping the wiki page as testing ground for new ideas or 
> additional sections. That may even be mentioned explicitly there next to the 
> link to our official documentation.
> 
> Thanks for working on this David!
> 
> Geert


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Wiki Section on Reports

2017-01-17 Thread Geert Janssens 
Op maandag 16 januari 2017 09:48:51 CET schreef David T. via gnucash-devel:
> Hello,
> 
> I will start by saying: “Yes, I know it’s a wiki…”
> 
> However, now that the Reports chapter (which incorporates nearly all the
> Wiki reports information verbatim) is officially available as part of the
> normal Documentation distribution, I propose removing this information in
> the wiki, and adding a note to say that the wiki information has been moved
> to the Tutorial and Concepts Guide as of GnuCash 2.6.15.
> 
> As this is rather a substantial amount of information that will go away from
> the wiki, I thought it best to double check in the community before acting.
> 
I also prefer removing this from the wiki.

There simply is not enough people around to properly maintain the information 
in two places and keep them in sync.

I don't mind keeping the wiki page as testing ground for new ideas or 
additional sections. That may even be mentioned explicitly there next to the 
link to our official documentation.

Thanks for working on this David!

Geert

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Document Update Instructions have been revised

2017-01-17 Thread Geert Janssens 
Op dinsdag 17 januari 2017 11:16:39 CET schreef Chris Good:
> Hi,
> 
> 
> 
> I've finished updating the wiki Document Update Instructions [1] to include
> instructions for using 'make' rather than xmllint and xsltproc directly.
> 
> Thank you very much Geert for all the info.
> 
> 
> 
> [1] http://wiki.gnucash.org/wiki/Documentation_Update_Instructions
> 
> 
> 
> Regards, Chris Good

Chris,

Thanks for improving our documentation on improving our documentation ;)

Seriously, I appreciate the effort you're spending here.

I'm proof reading what you have written and below follow some remarks:

* You are referring to the required use of make, which I like obviously as I 
suggested that myself. What is not clear in your documentation however is how 
to obtain make and the related tools. On linux this is usually obtained via 
the package manager. There is usually some kind of package group related to 
development that installs all the required dependencies in one go. On OS X I 
don't know how to get it. That's John's expertise although David T may know 
this by now as well... And on Windows it's probably even more complicated. TBH 
I never tried manually building the gnucash documentation on that platform, so 
I can't give precise instructions. It will likely involve installing an msys 
environment.

* Step 5 confuses me:
"Experienced developers instruct that you should focus first on the modules in 
either of these two directories (found in the step 1 downloaded files): 
gnucash-docs/help/C or gnucash-docs/guide/C. "
What do you mean by this ? The "C" directories contain the documentation in 
English. All other directories contain translations of these in other 
languages. As I see it there is no need to present this as some kind of 
mythical knowledge only understood by "Experienced developers".

* The next paragraph confuses me as well. How would opening each file reveal 
errors ? This is not really clear to me.

* A bit further you suggest to add a pair of comments around your changes to 
help translators. I would propose not to do that as I believe this is 
redundant information. This is what a version management system is used for. 
One can use the git history to see what has changed since the last time one 
has worked on the translation. There are graphical tools like gitk or the 
github website that help you visualize these changes.

* "If you are adding or deleting an xml file, for example adding a new chapter 
or appendix, you also need to update files [guide|help]/[language]/gnucash-
{guide|help}.xml and [guide|help]/[language]/Makefile.am. There is no need to 
update Makefile.in as this is generated by running autogen.sh."
Perhaps here it's best to more explicitly state autogen.sh and ../configure.sh 
should be re-run.

* There is a section on testing the documentation locally on linux. I have 
slightly modified it, because parts of it were outdated. And I'm considering 
whether we shouldn't simplify it even more. For now I have stated you can run 
this test with any version of gnucash higher than 2.6.0, with the restriction 
that yelp is installed and working. The text is not too clear about that 
second part, but that is what the "linux" restriction is actually all about. 
This does reduce the cases where a full build of a development version of 
gnucash is necessary IMO. It believe this is only necessary when you want to 
test context help for features that are only in a more recent version than you 
currently have. But this begs the question whether we really need gnucash at 
all in the other cases. Only yelp suffices as explained at the end of step 
11.3. Perhaps we should make that the preferred testing method and only 
propose linux tests in case new context help should be tested. What do you 
think ?

* Lastly you describe how to format a patch. While this is certainly one of 
the accepted methods, it may be interesting to document how to make a pull 
request as well.

That's it. Again, thanks for all the effort you spent on this so far!

Regards,

Geert
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Autogen question

2017-01-17 Thread Geert Janssens 
Stephen,

It's very well possible the space in your user name matters. In our self-
written scripts I have tried to mind about this as much as possible, but lots 
of the build scripts of our dependencies assumes a linux environment in which 
spaces in paths are rather uncommon. So I expect there to be many issues 
because of this.
That's why the build instructions on Windows [1] recommend to build in c:
\gcdev or a similarly short name, which can also be on a second harddrive.

The easiest way to get all the required packages installed is to use the build 
scripts as provided in the gnucash-on-windows repository. How to use them is 
equally explained in the build instructions [1].

Hope this helps,

Geert


[1] https://github.com/Gnucash/gnucash-on-windows/blob/master/README

Op dinsdag 17 januari 2017 08:55:04 CET schreef Stephen Brown:
> Hi All
> 
> In a msys shell on a Windows 10 machine I see
> 
> ---
> Stephen Brown_2@Ace /c/gcdev/gnucash.git
> $ ./autogen.sh
> 
> **Error**: You must have `glib-gettextize' installed to compile GnuCash.
> Get the development packages of the glib-2.x library from your distribution.
> 
> **Error**: You must have `intltoolize' installed to compile GnuCash.
> Get the package 'intltool' of your distribution.
> 
> Stephen Brown_2@Ace /c/gcdev/gnucash.git
> $
> 
> -- Does the space in my windows login name matter?
> How do I install the required packages?
> 
> Stephen Grant Brown
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel


___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Autogen question

2017-01-17 Thread Stephen Brown 
Hi All

In a msys shell on a Windows 10 machine I see

---
Stephen Brown_2@Ace /c/gcdev/gnucash.git
$ ./autogen.sh

**Error**: You must have `glib-gettextize' installed to compile GnuCash.
Get the development packages of the glib-2.x library from your distribution.

**Error**: You must have `intltoolize' installed to compile GnuCash.
Get the package 'intltool' of your distribution.

Stephen Brown_2@Ace /c/gcdev/gnucash.git
$
--
Does the space in my windows login name matter?
How do I install the required packages?

Stephen Grant Brown
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel