Re: [GNC-dev] Register Documentation Improvements (was Re: [GNC] Column widths again)

[John Ralls]

> On Aug 23, 2018, at 12:45 AM, Geert Janssens  
> wrote:
> 
> It would be nice if our html version of the docs would get some css love in 
> that case though. Wading through plain rendered html is an equally 2000'ish 
> experience.

I just had a look at https://github.com/Gnucash/gnucash-docs/tree/master/xsl 
. It’s pretty old, the 
docbook part is 1.75.2 from 2010 and the rest was lifted from an early Gnome 
docs beta and never updated. No wonder it looks like 2000’ish html, it *is* 
2000’ish html!

We could go Gnome [1] or we could just use the latest stylesheets [2] from 
DocBook itself (tutorial [3]). Or we could do something else. 

Regards,
John Ralls

[1] https://gitlab.gnome.org/GNOME/gnome-doc-utils 

[2] https://github.com/docbook/xslt10-stylesheets/ 
, reference docs 
https://github.com/docbook/xslt10-stylesheets/tree/master/xsl/doc 

[3] http://www.sagehill.net/docbookxsl/ 
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Documentation Version Display

[John Ralls]

> On Aug 24, 2018, at 10:35 AM, John Ralls  wrote:
> 
> Good point about the top two links. I’ve modified them to be versioned. I’ll 
> add some clarifying text after I figure out how to not break the translations 
> in the process.

I’ve added a sentence explaining that the top set of links go to the English 
HTML of the current stable version and suggesting that the reader scroll down 
for older versions and different languages and formats.

I’ve msgmerged the new string into the po files to include it.

GENERAL PLEA: Most of the website translations are pretty old and in poor shape:

po/ca.po   418 translated messages, 6 fuzzy translations, 5 untranslated 
messages.
po/de.po   385 translated messages, 3 fuzzy translations, 41 untranslated 
messages.
po/es.po 36 translated messages, 1 fuzzy translation, 392 untranslated 
messages.
po/fr.po264 translated messages, 48 fuzzy translations, 117 
untranslated messages.
po/hu.po   167 translated messages, 63 fuzzy translations, 199 untranslated 
messages.
po/it.po403 translated messages, 15 fuzzy translations, 11 untranslated 
messages.
po/ja.po220 translated messages, 56 fuzzy translations, 153 
untranslated messages.
po/nb.po 66 translated messages, 3 fuzzy translations, 360 untranslated 
messages.
po/nl.po310 translated messages, 31 fuzzy translations, 88 untranslated 
messages.
po/pl.po  72 translated messages, 2 fuzzy translations, 355 
untranslated messages.
po/pt.po403 translated messages, 15 fuzzy translations, 11 untranslated 
messages.
po/zh_CN.po  164 translated messages, 76 fuzzy translations, 189 untranslated 
messages.
po/zh_TW.po  147 translated messages, 22 fuzzy translations, 260 untranslated 
messages.

Anyone able to improve these translations, please jump in !

Regards,
John Ralls

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

Re: [GNC-dev] translation of new register helper panels

[John Ralls]

Alain,

Perhaps you are using too old a version of Poedit? I just downloaded 2.11 and 
it has no problem with that msgid.

Regards,
John Ralls

> On Aug 25, 2018, at 5:02 AM, Alain Sanguinetti  wrote:
> 
> Hello,
> 
> 
> Thanks for your input.
> 
> So what's happening is that PoEdit doesn't process correctly the strings 
> starting with an empty line ""
> 
> By removing the empty "" they are displayed correctly in PoEdit, otherwise i 
> just an't seem to find them in the interface.
> 
> I don't know why i couldn't find the strings in the po files, maybe a 
> settings of the search.
> 
> How do you advise me to handle this problem? Is this something related to 
> PoEdit ?
> 
> Best regards,
> 
> 
> Alain Sanguinetti
> 
> 
> On 8/18/18 12:57 AM, Frank H. Ellenberger wrote:
>> Hello Alain,
>> 
>> Am 17.08.2018 um 22:35 schrieb Alain Sanguinetti:
>>> Hello,
>>> 
>>> 
>>> I'm getting started, as of today, in helping translating to French.
>>> 
>>> I tried to round up the translation of the initial new file helper but I
>>> can't seem to find the strings corresponding to the 4th and 5th panels.
>>> 
>>> I generated the pot and merged with the existing fr.po but they don't
>>> seem to be anywhere :/
>>> 
>>> If i don't find them in fr.po, where are they ?
>>> 
>>> Thanks,
>> You checked out the maint branch of Gnucash?
>> In the directory po, not po/glossary,
>> the file fr.po as it is currently on github
>> has starting in line 7773 the section:
>> #: ../gnucash/gnome/gtkbuilder/assistant-hierarchy.glade.h:10
>> #, fuzzy
>> msgid ""
>> "\n"
>> "Select categories that correspond to the ways that you foresee you will
>> use "
>> "GnuCash. Each category you select will cause several accounts to be"
>> "created.\n"
>> "\n"
>> "Note: the selection you make here is only the starting point for
>> your "
>> "personalized account hierarchy. Accounts can be added, renamed, moved, or"
>> "deleted by hand later at any time."
>> msgstr ""
>> "\n"
>> "Sélectionnez les catégories correspondantes à votre utilisation de
>> GnuCash. "
>> "Chaque catégorie sélectionnée entrainera la création de plusieurs
>> comptes. "
>> "Choisissez les catégories vous concernant. Vous pourrez toujours créer
>> des "
>> "comptes supplémentaires manuellement plus tard."
>> 
>> The fuzzy flag says the msgid changed after the msgstr was last edited.
>> So you should compare the msgstr with the new msgid and after updating
>> the msgstr remove the "#, fuzzy" line to reenable the translation.
>> 
>> Page 5 begins in line 7819.
>> 
>> Because you have run make pot;msgmerge ...
>> The line number in your version might be slightly different, but you can
>> either search the file for the english text (=msgid) or the source,
>> here: assistant-hierarchy.glade.
>> 
>> I would be interested to read, what went wrong in your case.
>> 
>> HTH
>> Frank
>> 
> -- 
> Alain Sanguinetti
> 
> ___
> 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

Re: [GNC-dev] Documentation Version Display

[Colin Law]

On Sat, 25 Aug 2018 at 15:11, Frank H. Ellenberger
 wrote:
>
> Am 25.08.2018 um 09:39 schrieb Colin Law:
> > On Sat, 25 Aug 2018 at 02:25, David T. via gnucash-devel
> >  wrote:
> >> ...
> >> I imagine most people would search for “gnucash help” or “gnucash 
> >> tutorial.”
> >
> > Actually I think the search is very likely to be something like
> > gnucash how to reconcile account
> > which will take one straight into the middle of the tutorial, hence
> > the need for the version on each page.
>
> No, the recent stable (3.2) is the only version indexed by google. We
> disallow indexing older versions because before the version with most
> links (i.e. 1.x) was listed first.

That does not conflict with what I said, the search will take the user
to the page.  He may not be using the latest version and does not know
that only the latest is indexed, so the page should indicate which
version it is for.

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

Re: [GNC-dev] Documentation Version Display

[Frank H. Ellenberger]

Am 25.08.2018 um 09:39 schrieb Colin Law:
> On Sat, 25 Aug 2018 at 02:25, David T. via gnucash-devel
>  wrote:
>> ...
>> I imagine most people would search for “gnucash help” or “gnucash tutorial.”
> 
> Actually I think the search is very likely to be something like
> gnucash how to reconcile account
> which will take one straight into the middle of the tutorial, hence
> the need for the version on each page. 

No, the recent stable (3.2) is the only version indexed by google. We
disallow indexing older versions because before the version with most
links (i.e. 1.x) was listed first.

 I think new users may well
> search for tutorial or help but once one gets going it is much more
> likely to be a specific search, which may well be quicker than finding
> the tutorial and looking for the right section.
> 
> Colin

Frank

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

Re: [GNC-dev] translation of new register helper panels

[Alain Sanguinetti]

Hello,


Thanks for your input.

So what's happening is that PoEdit doesn't process correctly the strings 
starting with an empty line ""


By removing the empty "" they are displayed correctly in PoEdit, 
otherwise i just an't seem to find them in the interface.


I don't know why i couldn't find the strings in the po files, maybe a 
settings of the search.


How do you advise me to handle this problem? Is this something related 
to PoEdit ?


Best regards,


Alain Sanguinetti


On 8/18/18 12:57 AM, Frank H. Ellenberger wrote:

Hello Alain,

Am 17.08.2018 um 22:35 schrieb Alain Sanguinetti:

Hello,


I'm getting started, as of today, in helping translating to French.

I tried to round up the translation of the initial new file helper but I
can't seem to find the strings corresponding to the 4th and 5th panels.

I generated the pot and merged with the existing fr.po but they don't
seem to be anywhere :/

If i don't find them in fr.po, where are they ?

Thanks,

You checked out the maint branch of Gnucash?
In the directory po, not po/glossary,
the file fr.po as it is currently on github
has starting in line 7773 the section:
#: ../gnucash/gnome/gtkbuilder/assistant-hierarchy.glade.h:10
#, fuzzy
msgid ""
"\n"
"Select categories that correspond to the ways that you foresee you will
use "
"GnuCash. Each category you select will cause several accounts to be"
"created.\n"
"\n"
"Note: the selection you make here is only the starting point for
your "
"personalized account hierarchy. Accounts can be added, renamed, moved, or"
"deleted by hand later at any time."
msgstr ""
"\n"
"Sélectionnez les catégories correspondantes à votre utilisation de
GnuCash. "
"Chaque catégorie sélectionnée entrainera la création de plusieurs
comptes. "
"Choisissez les catégories vous concernant. Vous pourrez toujours créer
des "
"comptes supplémentaires manuellement plus tard."

The fuzzy flag says the msgid changed after the msgstr was last edited.
So you should compare the msgstr with the new msgid and after updating
the msgstr remove the "#, fuzzy" line to reenable the translation.

Page 5 begins in line 7819.

Because you have run make pot;msgmerge ...
The line number in your version might be slightly different, but you can
either search the file for the english text (=msgid) or the source,
here: assistant-hierarchy.glade.

I would be interested to read, what went wrong in your case.

HTH
Frank


--
Alain Sanguinetti

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

Re: [GNC-dev] Documentation Version Display

[Colin Law]

On Sat, 25 Aug 2018 at 02:25, David T. via gnucash-devel
 wrote:
> ...
> I imagine most people would search for “gnucash help” or “gnucash tutorial.”

Actually I think the search is very likely to be something like
gnucash how to reconcile account
which will take one straight into the middle of the tutorial, hence
the need for the version on each page.  I think new users may well
search for tutorial or help but once one gets going it is much more
likely to be a specific search, which may well be quicker than finding
the tutorial and looking for the right section.

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

Re: [GNC-dev] Documentation Version Display

[Colin Law]

Some applications handle this problem by inserting a prominent warning
at the top of each page of out of date documentation, see [1] for
example.  I assume they have some automatic way of doing this rather
than editing all the pages, so whether something like this could be
done without major effort I don't know.

Colin

[1]https://docs.influxdata.com/influxdb/v1.0/introduction/installation/
On Sat, 25 Aug 2018 at 02:25, David T. via gnucash-devel
 wrote:
>
> Adrien,
>
> That seems reasonable, too, although there was recently a long discussion 
> about which online document a user was viewing, suggesting that it’s not 
> always clear.
>
> As for “search juice,” I can’t possibly imagine how there would be a major 
> negative impact by adding “Gnucash v. 3.2” immediately prior the two document 
> titles—and I can’t imagine a search where this would negatively affect 
> results. Honestly, I imagine most people would search for “gnucash help” or 
> “gnucash tutorial.” Such a search presumably would be helped by this change, 
> rather than hurt by it. Not being privy to Google’s search algorithms, I 
> can’t say with authority, or course.
>
> I am opposed to removing these links altogether. As I noted elsewhere, 
> “current stable release” is not IMHO a universally-understood term. And, 
> while I haven’t mentioned it before, I personally find the grid of cryptic 
> icons lined up next to the document titles to be difficult to understand or 
> use. On my screen, they are far too small for me to process visually; of the 
> four in use, I only immediately recognize the PDF icon. The use of a tiny 
> earth icon for HTML help is neither intuitive to me, nor clear to discern. 
> Additionally, I am admittedly unfamiliar with either the Epub or Mobi formats 
> or icons; however, if the goal is to universally communicate the availability 
> of these formats, I don’t think this is the way. But I digress!
>
> The point is, these links clearly put the user into the online documents, 
> which I think is valuable.
>
> David
>
> > On Aug 24, 2018, at 6:30 PM, Adrien Monteleone 
> >  wrote:
> >
> > David,
> >
> > I agree the pages should have both the document title (per another thread) 
> > and the version either in the header or footer.
> >
> > But I can’t fathom clicking the ‘main’ documentation link and thinking that 
> > I’m getting anything other than the most current version. If I knew I was 
> > running an older version of the software and slightly down the page I see a 
> > link for documentation for that version, I’m going to grab that one 
> > instead, making a fairly safe assumption that the main link isn’t for me.
> >
> > The only solution I can think of for this situation is to remove those two 
> > links at the top of the page and users will then click the links for their 
> > chosen version. (with each already well labeled) Adding the version to 
> > those links is, to me, unnecessary clutter. (links should be as concise and 
> > accurately descriptive as possible, and changing that link text each 
> > release will reduce search juice for those links.)
> >
> > Regards,
> > Adrien
> >
> >> On Aug 24, 2018, at 12:03 PM, David T. via gnucash-devel 
> >>  wrote:
> >>
> >> John,
> >>
> >>
> >>> On Aug 24, 2018, at 10:57 AM, John Ralls  wrote:
> >>>
> >>>
> >>>
>  On Aug 24, 2018, at 5:51 AM, David T. via gnucash-devel 
>   wrote:
> 
>  Hello,
> 
>  Today, I had the opportunity to examine the online Help text, where I 
>  saw detailed information about the Transaction Report, which has 
>  recently changed radically. The information provided on the online Help 
>  clearly references the new version of this report, which I surmise 
>  because I am still running 2.6.21, and I do not have this version of the 
>  report.
> 
>  Here is the problem: there is no indication in the online resources 
>  (either in the document itself, or on Gnucash.org ) 
>  the version of GnuCash to which the documentation refers. This could 
>  lead to user confusion, as they see help that refers to functionality 
>  that they do not have.
> 
>  I am sure that the stock answer here will be: “GnuCash is currently on 
>  release 3.2, and therefore the documentation available at Gnucash.org 
>   reflects the current release.” I respect that.
> 
>  However, at any given time, there will be people who choose for one 
>  reason or another not to upgrade to the latest and greatest version—or 
>  more problematically, are unaware that they are not running the latest 
>  version. These users would benefit from being informed *somewhere* that 
>  the documentation that they are consulting is for a particular version. 
>  Is there some way to add the version number to the header of the 
>  documentation pages? (The footer is also an option, but is less 
>  preferable online since the footer 

Re: [GNC-dev] avoid the brain dead import

[David Cousens]

William

I think the answer to your question lies in the fact that files users wish
to import don't come from a single source and don't always conform to any
well defined standard with regard to both the data format and the
information supplied.  

Importing OFX data is considerably more straightforward than importing CSV
data for this reason, as it does conform to a reasonably well defined
standard, but even then some institutions do manage to stuff it up. In most
cases users don't necessarily have any control over what another institution
includes in the files they supply. Most include transactions between the To
and From dates inclusively that you might enter when requesting a data
download but this is not guaranteed. Stupid ? Yes, but the importer has to
cope with stupid, as well as nicely well formatted and thought out files.
Not all data for a bank account includes the detail of which account you may
want the second split of a transaction to go to and even if they do it may
not match your choices in setting up your chart of accounts. If it does then
GnuCash deals with that

I am an accountant (retired) and I have imported the same file (or at least
overlapping data in different files) on more than one occasion since I have
been using GnuCash. The point of the matcher is to pick this up before you
have enterd the data into your accounts and not have to deal with the far
more laborious task of working out which transactions were duplicated in an
import and deleting them from your records one by one once they have been
imported. If you get the date format wrong relative to your locale format on
an import, it can be particularly difficult. Swapping days and years
produces some interesting results.

The matcher also has a Bayesian learning system which can allocate the
transfer account for the second split on the basis of matching information
in the description and other fields. My experience has been after I have
imported one  or two month's data, it will generally assign the transfer
account for about 60% of data in the succeeding months and handles regular
payments and deposits pretty well and it gets better still after a few
months. 

I import  a few hundred transactions a month, generally in 5-10 minutes from
OFX files with no problem. CSV importing (e.g. Paypal can be far more
problematical but the ability of the importer in v3.2 to save import
settings is a great help.

There is a recent patch (Bug 796778) which might help you shorten the
initial input before the matcher works efficiently but it is not yet
incorporated in the master branch. It implements multiple selection of rows
in the matcher e.g.. from the same vendor using Ctrl-click and Shift Click
and the rubberbanding techniques implemented in GTK and the assignment of
those rows to a single transfer account. It speeds up the initial import of
data quite a bit but is less effective once the Bayesian matching is trained
(which is possibly why it has not been implemented before now) as that tends
to pick up repeated transactions fairly well. 

The downside is of course there is always a transaction or two  from the
same vendor or customer which may have to go to a different transfer
account, i.e. you still have to check that it has been correctly assigned by
the matcher.

Keep trying. Tthe brain dead importer does get less brain dead with repeated
use.

David Cousens



-
David Cousens
--
Sent from: http://gnucash.1415818.n4.nabble.com/GnuCash-Dev-f1435356.html
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel