Multiple mismatchs between e.g. gnucash-guide.xml and *-C.omf

[Frank H. Ellenberger]

I am currently searching a good form of olinks for referencing e.g.
between guide and help. But their parameters depend on the docbook
version. Looking in gnucash-guide I see



Might yelp be confused if I would use olinks in a form, which was
introduced in 4.2?

Also other other parameters differ. In short, our omfs are all outdated.

This would not had happen, if we had updated
more often. As you can see from

our docs are based on gnome-doc-utils-devel or it's ancestor.

WHile working on the pdf generation Geert updated gnome-doc-utils (our
xslt directory) from 1.45 to 1.75.2
but the devel part (templates, makefile ...) was not incorporated.

Otherwise the omf files would be generated dynamical with recent date,
version number, contributor list ...

So I would suggest to merge gnome-doc-utils-devel-0.20.10 or similar
before GDP drops docbook support - they now prefer their homebrew
mallard, other licenses etc.

If you agree, should we do it on maint or master, cherrypick or switch
complete? I currently have no complete overview of the divergence
between the make files.

Your thoughts?

~Frank


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

RE: Document Update Instructions have been revised

[Chris Good]

Hi David,

 

I’ve added a section 
http://wiki.gnucash.org/wiki/Documentation_Update_Instructions#Installing_make.

I assume you do need the full Xcode to build GnuCash on Mac OS X, but only need 
the command-line tools to build the documentation.

 

Regards,

 

Chris Good

Mobile 0484 001 392

Phone +61 2  0747

 

From: David T. [mailto:sunfis...@yahoo.com] 
Sent: Tuesday, 7 February 2017 9:30 PM
To: Chris Good ; 'John Ralls' 
Cc: 'Frank H. Ellenberger' ; 'GnuCash 
Developers' 
Subject: RE: Document Update Instructions have been revised

 

Chris, 

 

No. I haven't tried John's suggestion. My current mac is five years old, and I 
had already downloaded the full xcode upgrade when John made the suggestion. 
I'll note that the wiki still instructs mac users to install the full xcode 
suite. If it's no longer true, then the wiki needs correction.

 

David

 

On Tue, Feb 7, 2017 at 13:01, Chris Good

 > wrote:

From: John Ralls [mailto:jra...@ceridwen.us] 
Sent: Friday, 27 January 2017 1:40 AM
To: sunfis...@yahoo.com  
Cc: Chris Good  >; 
Frank H. Ellenberger  >; GnuCash Developers 
 >
Subject: Re: Document Update Instructions have been revised

On Jan 25, 2017, at 11:55 PM, David T.  wrote:

On Thu, Jan 26, 2017 at 8:26, John Ralls

 wrote:

Indeed. But you don't need all of it, just the command-line tools.

Regards,

John Ralls

 

I'm not sure you can get one without first getting the other. At least, I 
haven't been able to. 

Assuming that you don't already have Xcode installed, try running 

  clang foo.cpp

in Terminal. That should pop up a dialog box offering to install them for you.

 Regards,

John Ralls

 

Hi David,

 

Did you manage to install the Xcode command line tools without having to 
install the full Xcode or did you have to use John’s ‘clang foo.cpp’ method?

I think we should document this either way.

 Regards, Chris Good

 



smime.p7s
Description: S/MIME cryptographic signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Handling of xml2po based docs translations like the italian; was: gnucash-docs maint: Glossary: Transactions have at least 2 splits

[Frank H. Ellenberger]

Hi,

Am 08.02.2017 um 18:17 schrieb Geert Janssens:
> I just don't know why the entity wasn't added properly by simply calling are 
> make recipe. I assumed this was something John's make recipe was supposed to 
> do. But that may be a false assumption. I haven't dug deeper at this point.

I assume, you run make ...
Eclipse is there context sensitive: If you rightclick on C to commit it
will only mark changes below 'C' and not in 'it'.

Regards

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

Re: Handling of xml2po based docs translations like the italian

[Geert Janssens]

Op woensdag 8 februari 2017 15:01:19 CET schreef Frank H. Ellenberger:
> ... continuation:
> 
> http://code.gnucash.org/docs/it/gnucash-guide/gnc-gloss.html
> shows another limit beneath the mixture of Italian expressions with
> English explanations.
> 
This is a drawback of using xml2po in general to do the Italian translation. 
It wouldn't matter whether the translated xml file is automatically or 
manually generated. The xml to po and back conversion program expects strings 
not to change positions.

> The alphabetical order of Italian glossary entries would not be the same
> as the English. I don't know, if there is a trick like some XSLT to get
> them in the right order.

Maybe there are. I haven't searched for this yet.

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

Re: Handling of xml2po based docs translations like the italian; was: gnucash-docs maint: Glossary: Transactions have at least 2 splits

[Geert Janssens]

Op woensdag 8 februari 2017 14:14:40 CET schreef Frank H. Ellenberger:
> Hi,
> 
> Am 08.02.2017 um 10:06 schrieb Geert Janssens:
> > Frank,
> > 
> > It looks like a second change slipped in your commit to include the
> > Glossary in the Italian translation.
> 
> That was " Bug 777891 - Guide Glossary lacks proper ID tag or mention in
> Basics …" which was commited to C after your "Update Italian guide
> translation following the merge of business chap…"
> 
I know this very well. I pushed the original commits :)
I just don't know why the entity wasn't added properly by simply calling are 
make recipe. I assumed this was something John's make recipe was supposed to 
do. But that may be a false assumption. I haven't dug deeper at this point.

> > This was apparently missing from my most recent commit. I wonder however
> > whether this should have been automatically added by running make in the
> > Italian translation's build directory ? Or was there something else I
> > should have done to get that ?
> > 
> > Geert
> 
> on Aug 10, 2016 I reverted the italian update from the last commit
> because we had decided "better obsolete and coherent than partly in
> English". But jralls committed on 14 Sep 2016 "Automate regeneration of
> the Italian xml files."
> 
> Starting from this date, if you had run make in a higher directory and
> did not unselect guide/it/gnucash-guide.xml it got updated - resulting
> in a mixture of italian and english sections.
> 
> I don't know if I missed some discussion there and if that behavior was
> intended.
> 
John can certainly correct me if I'm wrong, but I guess this was done because 
to timely catch issues like files being added/removed.

So the motivation now probably is "better a documentation that can be built 
but has English text intermixed than one that's consistent in Italian but no 
longer can be built".

Just my thought here.

Regards,

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

Re: Boost error compiling gnucash under Microsoft Windows

[Geert Janssens]

Op woensdag 8 februari 2017 12:07:08 CET schreef Geert Janssens:
> Op woensdag 8 februari 2017 11:57:56 CET schreef Geert Janssens:
> > Stephen,
> > 
> > It's confimed, I goofed :(
> > 
> > I have just commited a fix for this. If you pull the latest change in the
> > gnucash-on-windows repository you should be able to proceed.
> > 
> > Thanks for pointing this out!
> > 
> > Geert
> 
> ... and the build then fails while building gnc-timezone.cpp because of a
> integer length issue on my system. This is code John Ralls pushed almost
> half a year ago. It's surprising this fails now. It didn't when using cmake
> and ninja-build last week.
> 
> So my original advice stands, add the two variables to your custom.sh (in
> gnucash-on-windows.git). It's the environment as currently used by the
> active developers and hence you have the least issues with that setup.
> 
> Regards,
> 
> Geert

And I ran into yet another build failure that got unnoticed unless starting 
from scratch. Google Mock wasn't properly detected. To fix this I had to make 
modifications to the gnucash git repository, which I have just pushed. Should 
you get stuck on this, be sure to pull the latest commits and let us know how 
it then goes.

Regards,

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

Re: gnucash-docs maint: Bug 777891 - Guide Glossary lacks proper ID tag or mention in Basics Chapter.

[Derek Atkins]

Indeed.  No errors last night.

-derek

"Frank H. Ellenberger"  writes:

> Don't worry!
>
> It seems there was another reason:
> http://lists.gnucash.org/logs/2017/02/07.html#T13:39:06
>
> ~Frank
>
> Am 07.02.2017 um 18:53 schrieb David T. via gnucash-devel:
>> When I put this in, I accidentally committed the Overview without
>> the related Glossary change, thus creating a broken reference. I
>> caught it immediately and committed the glossary change as well in a
>> second commit. Geert “squashed” the two commits (his term) before
>> committing; is it possible that somehow the first commit went
>> through, but the second didn’t? Otherwise, it’s a pretty minor
>> change.
>> 
>> David
>> 
>>> On Feb 7, 2017, at 10:33 PM, Derek Atkins  wrote:
>>>
>>> Geert,
>>> I believe this broke the docs build; it failed last night.
>>>
>>> -derek
>>>
>>> Geert Janssens  writes:
>>>
 Updated via  https://github.com/Gnucash/gnucash-docs/commit/f8e2df0d 
 (commit)
from  https://github.com/Gnucash/gnucash-docs/commit/0c8c66f9 (commit)



 commit f8e2df0d822e4de5ed1ca2285bd00acbab30d73c
 Author: David Thomas 
 Date:   Mon Feb 6 21:31:39 2017 +0500

Bug 777891 - Guide Glossary lacks proper ID tag or mention in Basics 
 Chapter.

This patch adds the appropriate tag in the glossary, and references the 
 glossary in the Overview Chapter.
> :
>
>

-- 
   Derek Atkins, SB '93 MIT EE, SM '95 MIT Media Laboratory
   Member, MIT Student Information Processing Board  (SIPB)
   URL: http://web.mit.edu/warlord/PP-ASEL-IA N1NWH
   warl...@mit.eduPGP key available
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Handling of xml2po based docs translations like the italian

[Frank H. Ellenberger]

... continuation:

http://code.gnucash.org/docs/it/gnucash-guide/gnc-gloss.html
shows another limit beneath the mixture of Italian expressions with
English explanations.

The alphabetical order of Italian glossary entries would not be the same
as the English. I don't know, if there is a trick like some XSLT to get
them in the right order.

~Frank


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

Handling of xml2po based docs translations like the italian; was: gnucash-docs maint: Glossary: Transactions have at least 2 splits

[Frank H. Ellenberger]

Hi,

Am 08.02.2017 um 10:06 schrieb Geert Janssens:
> Frank,
> 
> It looks like a second change slipped in your commit to include the Glossary 
> in the Italian translation.

That was " Bug 777891 - Guide Glossary lacks proper ID tag or mention in
Basics …" which was commited to C after your "Update Italian guide
translation following the merge of business chap…"

> This was apparently missing from my most recent commit. I wonder however 
> whether this should have been automatically added by running make in the 
> Italian translation's build directory ? Or was there something else I should 
> have done to get that ?
> 
> Geert

on Aug 10, 2016 I reverted the italian update from the last commit
because we had decided "better obsolete and coherent than partly in
English". But jralls committed on 14 Sep 2016 "Automate regeneration of
the Italian xml files."

Starting from this date, if you had run make in a higher directory and
did not unselect guide/it/gnucash-guide.xml it got updated - resulting
in a mixture of italian and english sections.

I don't know if I missed some discussion there and if that behavior was
intended.

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

Re: Boost error compiling gnucash under Microsoft Windows

[Geert Janssens]

Op woensdag 8 februari 2017 11:57:56 CET schreef Geert Janssens:
> Stephen,
> 
> It's confimed, I goofed :(
> 
> I have just commited a fix for this. If you pull the latest change in the
> gnucash-on-windows repository you should be able to proceed.
> 
> Thanks for pointing this out!
> 
> Geert

... and the build then fails while building gnc-timezone.cpp because of a 
integer length issue on my system. This is code John Ralls pushed almost half 
a year ago. It's surprising this fails now. It didn't when using cmake and 
ninja-build last week.

So my original advice stands, add the two variables to your custom.sh (in 
gnucash-on-windows.git). It's the environment as currently used by the active 
developers and hence you have the least issues with that setup.

Regards,

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

Re: Boost error compiling gnucash under Microsoft Windows

[Geert Janssens]

Op woensdag 8 februari 2017 10:01:42 CET schreef Stephen Brown:
> Hi Geert,
> 
> In a git bash shell I do
> -
> GNUCash@ACE /c/gcdev
> $ cd gnucash-on-windows.git
> 
> GNUCash@ACE /c/gcdev/gnucash-on-windows.git (master)
> $ git pull
> Already up-to-date.
> 
> GNUCash@ACE /c/gcdev/gnucash-on-windows.git (master)
> $ cd ..
> 
> GNUCash@ACE /c/gcdev
> $ cd gnucash.git
> 
> GNUCash@ACE /c/gcdev/gnucash.git (master)
> $ git pull
> Already up-to-date.
> 
> GNUCash@ACE /c/gcdev/gnucash.git (master)
> $
> 
> In the gcdev msys shell I get
> ---
> checking for boostlib >= 1.53.0... configure: We could not detect the boost
> libraries (version 1.53 or higher). If you have a staged boost library
> (still not installed) please specify $BOOST_ROOT in your environment and do
> not give a PATH to --with-boost option.  If you are sure you have boost
> installed, then check your version number looking in .
> See http://randspringer.de/boost for more documentation.
 configure: error:
> Boost 1.53.0 or later was not found and is required to build GnuCash 
> GNUCash@Ace /c/gcdev/gnucash-on-windows.git
> $
> 
> Did my “git pull” l commands work?
> Cheers
> Stephen Brown

Stephen,

It's confimed, I goofed :(

I have just commited a fix for this. If you pull the latest change in the 
gnucash-on-windows repository you should be able to proceed.

Thanks for pointing this out!

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

RE: Boost error compiling gnucash under Microsoft Windows

[Stephen Brown]

Hi Geert,

Sent from Mail for Windows 10

From: Geert Janssens
Sent: Wednesday, 8 February 2017 8:31 PM
To: gnucash-devel@gnucash.org
Cc: Stephen Brown
Subject: Re: Boost error compiling gnucash under Microsoft Windows


Op woensdag 8 februari 2017 00:24:55 CET schreef Stephen Brown:

> In a gcdev mysys shell running install.sh I see

>

>

>

>

> checking for boostlib >= 1.53.0... configure: We could not detect the boost

> libraries (version 1.53 or higher). If you have a staged boost library

> (still not installed) please specify $BOOST_ROOT in your environment and do

> not give a PATH to --with-boost option. If you are sure you have boost

> installed, then check your version number looking in .

> See http://randspringer.de/boost for more documentation.

>

> configure: error: Boost 1.53.0 or later was not found and is required to

> build GnuCash

>



Stephen,



I have very recently changed the way Boost is detected in our Windows build 
environment. To make this work, you need to pull the appropriate commits in 
both the gnucash-on-windows.git and the gnucash.git repositories.



Can you

- open a git msys shell in both repositories

- run "git pull" in each

- rerun "install.sh" from the gnucash build environment msys shell



One tip that's not yet documented anywhere:

If you want to greatly reduce the build time of the gnucash component, I 
suggest you add the following two lines in

/c/gnucash/gnucash-on-windows.git/custom.sh:

WITH_CMAKE=yes
WITH_NINJA=yes

This will change the gnucash build to use cmake and ninja-build instead of 
traditional autotools (autoconf/automake/make), which turns out to work much 
much faster. These are used by default for our unattended nightly builds.



Regards,



Geert

Hi Geert
In a git bash shell I do
-
GNUCash@ACE /c/gcdev
$ cd gnucash-on-windows.git

GNUCash@ACE /c/gcdev/gnucash-on-windows.git (master)
$ git pull
Already up-to-date.

GNUCash@ACE /c/gcdev/gnucash-on-windows.git (master)
$ cd ..

GNUCash@ACE /c/gcdev
$ cd gnucash.git

GNUCash@ACE /c/gcdev/gnucash.git (master)
$ git pull
Already up-to-date.

GNUCash@ACE /c/gcdev/gnucash.git (master)
$

In the gcdev msys shell I get
---
checking for boostlib >= 1.53.0... configure: We could not detect the boost 
libraries (version 1.53 or higher). If you have a staged boost library (still 
not installed) please specify $BOOST_ROOT in your environment and do not give a 
PATH to --with-boost option.  If you are sure you have boost installed, then 
check your version number looking in . See 
http://randspringer.de/boost for more documentation.
configure: error: Boost 1.53.0 or later was not found and is required to build 
GnuCash

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

Did my “git pull” l commands work?
Cheers
Stephen Brown
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Compiling gnucash on Windows

[Geert Janssens]

Op woensdag 8 februari 2017 00:21:57 CET schreef Stephen Brown:
> Hi All,
> 
> 
> In running install.sh from GNUCash@Ace /c/gcdev/gnucash-on-windows.git in a
> gcdev msys shell
> 
> I had to give full path name to git for it to be found.
> 
> Cheers
> 
> Stephen Brown

Hi Stephen,

This is deliberately so. Git installs its own complete msys environment which 
is incompatible with our build system. So we must ensure nothing of the git 
environment is in the standard path while running our build scripts.

For this reason I usually have two msys windows open on my windows test 
system, one regular msys shell from the gnucash build environment and a second 
one specifically for git. This second one can be opened from the Windows 
Explorer:
- vi Windows Explorerer navigate to c:\gcdev
- right-click on gnucash-on-windows.git and from the context menu you can 
select "Git Bash shell"

This will open another msys shell but from the git installation. In this shell 
you can run git commands without the full path. You can recognize this shell 
because it adds the checked out branch in the prompt.

While writing this, it occurs to me that you could also set up an alias for 
git in our own msys shell so the full path is no longer required. I haven't 
tried this myself yet.

Regards,

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

Re: documentation bug 687820

[Geert Janssens]

Op dinsdag 7 februari 2017 18:50:16 CET schreef David T.:
> Once again, Geert, you come to clarify. Indeed, I was not aware that this
> was a comma-delimited list. With only one dependency, that is not clear
> from the page.
> 
> Once again, I prove that there is nothing too simple that I can’t screw up.
> 

:D

David,

I have nothing but respect for the way you are willing to work through this 
pile of developer oriented information. And I'm happy to continue to explain 
each detail that turns out to confuse you and other non-developers. Just keep 
asking :)

Regards,

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

Re: gnucash-docs maint: Glossary: Transactions have at least 2 splits

[Geert Janssens]

Op dinsdag 7 februari 2017 18:07:22 CET schreef Frank H. Ellenberger:
> Updatedvia  https://github.com/Gnucash/gnucash-docs/commit/2cfd0249
> (commit) from  https://github.com/Gnucash/gnucash-docs/commit/0a7a95c3
> (commit)
> 
> 
> 
> commit 2cfd0249299e77853b1f851d0e765a6c60601557
> Author: fell 
> Date:   Wed Feb 8 00:07:16 2017 +0100
> 
> Glossary: Transactions have at least 2 splits
> 
> 
> 
> Summary of changes:
>  guide/C/gnc-glossary.xml   | 2 +-
>  guide/it/gnucash-guide.xml | 8 ++--
>  2 files changed, 7 insertions(+), 3 deletions(-)
> 
> ___
> gnucash-patches mailing list
> gnucash-patc...@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-patches

Frank,

It looks like a second change slipped in your commit to include the Glossary 
in the Italian translation.

This was apparently missing from my most recent commit. I wonder however 
whether this should have been automatically added by running make in the 
Italian translation's build directory ? Or was there something else I should 
have done to get that ?

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