Re: [GNC-dev] User not getting notifications [Ticket#207941]

[Pedro Albuquerque]

John,

I don't know what you did, but after 17:00 I received a bunch of
notifications from GnuCash Weblate, regarding those repository items,
parse errors for Dutch (?). Those I was not supposed to receive.

Thank you.

On 26/06/23 16:51, Pedro Albuquerque wrote:

John,

Will do, thank you again!

On 26/06/23 16:48, john wrote:

Pedro,

I think it would be better for you to interact directly with Weblate
support on the ticket.

Regards,
John Ralls


On Jun 25, 2023, at 20:38, Pedro Albuquerque  wrote:

John,

thank you so much for following this.

I attached a file with a bunch of screenshots, maybe Mr. Benjamin can
identify exactly what am I missing, because I can't.

I think the issue is GnuCash does not appear in my dashboard, even if
it is watched and with active notifications. But I don't see a way to
change that myself.

Again, thank you very much.

On 26/06/23 04:03, john wrote:




Begin forwarded message:

*From: *Benjamin Alan Jamie via Weblate Care 
*Subject: **RE: User not getting notifications [Ticket#207941]*
*Date: *June 25, 2023 at 16:00:23 PDT
*To: *jra...@ceridwen.us

Hi,

It seems that the user set his notification settings to unwanted
state. They can change that at
https://hosted.weblate.org/accounts/profile/#notifications

and read about it at
https://docs.weblate.org/en/weblate-4.18.1/user/profile.html#subscriptions


It matters if the project is Watched, etc. You as project admin
can’t change that, it’s only up to the user.

Best,
Benjamin
--
Weblate
--
You can follow us on Mastodon!https://fosstodon.org/@weblate



--
Regards,
Pedro Albuquerque




--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] User not getting notifications [Ticket#207941]

[Pedro Albuquerque]

John,

Will do, thank you again!

On 26/06/23 16:48, john wrote:

Pedro,

I think it would be better for you to interact directly with Weblate
support on the ticket.

Regards,
John Ralls


On Jun 25, 2023, at 20:38, Pedro Albuquerque  wrote:

John,

thank you so much for following this.

I attached a file with a bunch of screenshots, maybe Mr. Benjamin can
identify exactly what am I missing, because I can't.

I think the issue is GnuCash does not appear in my dashboard, even if
it is watched and with active notifications. But I don't see a way to
change that myself.

Again, thank you very much.

On 26/06/23 04:03, john wrote:




Begin forwarded message:

*From: *Benjamin Alan Jamie via Weblate Care 
*Subject: **RE: User not getting notifications [Ticket#207941]*
*Date: *June 25, 2023 at 16:00:23 PDT
*To: *jra...@ceridwen.us

Hi,

It seems that the user set his notification settings to unwanted
state. They can change that at
https://hosted.weblate.org/accounts/profile/#notifications

and read about it at
https://docs.weblate.org/en/weblate-4.18.1/user/profile.html#subscriptions

It matters if the project is Watched, etc. You as project admin
can’t change that, it’s only up to the user.

Best,
Benjamin
--
Weblate
--
You can follow us on Mastodon!https://fosstodon.org/@weblate



--
Regards,
Pedro Albuquerque




--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Release 1 week away, so string freeze.

[Pedro Albuquerque]

Hello developers,

I just finished my translation because of this message.

Strangely, I'm not receiving Weblate notifications for Gnucash, although
I receive them for the other projects I watch.

I just checked my notifications, and they are active. Is it my mistake
somewhere, or is it the project settings? Some help please.

On 18/06/23 21:48, John Ralls wrote:

Reminder for all developers: The 5.2 release is one week away so please don't 
push any commits involving translatable strings until after that release.

Regards,
John Ralls

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


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Website issues

[Pedro Albuquerque]

John,

this one is working, thank you.

On 28/03/2023 23:23, John Ralls wrote:

Pedro,

I found and I think fixed the problem with language stickiness on the website, 
please try it out athttps://code.gnucash.org/website. The normal site 
(www.gnucash.org) is still not updating.

Regards,
John Ralls


On Mar 26, 2023, at 11:24 PM, Pedro Albuquerque  wrote:

+1

On 26/03/2023 18:05, john wrote:

Pedro,

I see the language-persistence problem. I'll have a look at that after I finish 
the release, no need for a bug report.

Although Linas fixed the SSL problem onwww.gnucash.org  he hasn't yet fixed the 
update problem, so it's stuck in January.https://code.gnucash.org/website  
reflects the current website state. But there's a translation PR waiting 
including some of your changes. I'll merge that later today.

Regards,
John Ralls


On Mar 25, 2023, at 11:18 PM, Pedro Albuquerque  wrote:

Hello developers,

Congratulations on yet another great version of GnuCash.

I was checking the new release, and couldn't help noticing a couple of issues 
withhttps://www.gnucash.org/index.phtml?lang=pt_PT.

First, after choosing Portuguese as site language, when I change page via left 
side menu, the language set is not preserved, it reverts to English.

Second, even though Weblate says my translation is 100% complete and reviewed, 
I can see untranslated strings on the download page. Possibly more, didn't 
check all pages.

Do you want this in the bug tracker, or here is enough? Thank you in advance.

--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

--
Regards,
Pedro Albuquerque


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Website issues

[Pedro Albuquerque]

+1

On 26/03/2023 18:05, john wrote:

Pedro,

I see the language-persistence problem. I'll have a look at that after 
I finish the release, no need for a bug report.


Although Linas fixed the SSL problem on www.gnucash.org 
<http://www.gnucash.org> he hasn't yet fixed the update problem, so 
it's stuck in January. https://code.gnucash.org/website reflects the 
current website state. But there's a translation PR waiting including 
some of your changes. I'll merge that later today.


Regards,
John Ralls


On Mar 25, 2023, at 11:18 PM, Pedro Albuquerque  wrote:

Hello developers,

Congratulations on yet another great version of GnuCash.

I was checking the new release, and couldn't help noticing a couple 
of issues with https://www.gnucash.org/index.phtml?lang=pt_PT.


First, after choosing Portuguese as site language, when I change page 
via left side menu, the language set is not preserved, it reverts to 
English.


Second, even though Weblate says my translation is 100% complete and 
reviewed, I can see untranslated strings on the download page. 
Possibly more, didn't check all pages.


Do you want this in the bug tracker, or here is enough? Thank you in 
advance.


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel



--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Website issues

[Pedro Albuquerque]

Hello developers,

Congratulations on yet another great version of GnuCash.

I was checking the new release, and couldn't help noticing a couple of 
issues with https://www.gnucash.org/index.phtml?lang=pt_PT.


First, after choosing Portuguese as site language, when I change page 
via left side menu, the language set is not preserved, it reverts to 
English.


Second, even though Weblate says my translation is 100% complete and 
reviewed, I can see untranslated strings on the download page. Possibly 
more, didn't check all pages.


Do you want this in the bug tracker, or here is enough? Thank you in 
advance.


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Weblate Translation Program Beta

[Pedro Albuquerque]

Thank you, @jralls, My part is done.

On 24/03/2023 07:11, Pedro Albuquerque wrote:


Hello developers,

I understand we are now two days away from the great release (or 
major, or whatever you call it). But in Weblate there are still some 
strings with comments that I would like to see answered, before the 
translations are definitely integrated.


Could someone please have a look? Thank you in advance.

--
Regards,
Pedro Albuquerque


--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Weblate Translation Program Beta

[Pedro Albuquerque]

Hello developers,

I understand we are now two days away from the great release (or major, 
or whatever you call it). But in Weblate there are still some strings 
with comments that I would like to see answered, before the translations 
are definitely integrated.


Could someone please have a look? Thank you in advance.

--
Regards,
Pedro Albuquerque
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Proposal: Scheduling string freeze 2 weeks before each release

[Pedro Albuquerque]

Hi,

+1

Regards,
Pedro Albuquerque

On 01/12/20 22:08, Frank H. Ellenberger wrote:
> Dear coders and translators,
>
> watching translations often arrive short after a release is frustrating.
> But translators often do not know, when they should start tp cover all
> changes.
>
> If we schedule a string freeze 2 weeks before each release, coders have
> still two and a half month to apply changes without restrictions.
> And translators will have 2 weeks to do their work.
>
> If nobody objects, we will apply this rule for 4.3:
> Pull Requests before: Sa, 2020-12-11 00:00 UTC
> Other commits before: Sa, 2020-12-11 12:00 UTC or ask on IRC
> Then: Running checks and, if required, fixes
> Finally: Label on Github with tarball, Announcement
>
> Regards
> Frank
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel



OpenPGP_signature
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Request to move translation to Gnu Translation Project

[Pedro Albuquerque]

Hi John, Frank, all,

As usual, your help and response are excellent. To bad I'm not capable
of working decently with such great developers. I'll do my best to
maintain GnuCash updated, anyway I can. So, let's find a way.

Regarding TP, the answer was already given by Benno, since he already
removed the 'External' mark and assigned the translation to me. Being
behind one or two minor versions is a lot better than what it is right
now, so I think it will be an improvement anyway.

Regarding the other files (accounts, glossary and website), Frank, I
don't mind at all that you send me a 'pre-release archive', let's say a
week before the string freeze. I'm almost sure I can update the
translations on time and re-send them to you by email. But I think it's
not practical to you. It may work, until a better solution is found.

Weblate, or any other online service would be great and, I think, easy
for you developers to maintain. And could aggregate all files under a
same language project. Anything but Github, please.

The only remaining problem would be the documentation. I don't even know
how to find the differences between what is already translated and what
is not.

That said, thank you all again for your availability to help and for a
great software. Always at your disposal.

Regards,
Pedro

On 26/11/20 18:23, John Ralls wrote:
>
>> On Nov 26, 2020, at 7:52 AM, Frank H. Ellenberger 
>>  wrote:
>>
>>
>>
>> Am 26.11.20 um 16:28 schrieb John Ralls:
>>> Frank, I'm not sure what you mean about the string-freeze/prerelease 
>>> process. As we approach a major release we do a series of beta releases and 
>>> typically impose a string freeze after the one a month before the scheduled 
>>> major release date. TP gets all of those releases and the (3 or 4 active) 
>>> TP translators generally have updated translations ready in time for the 
>>> major release. There's no pre-release or string freeze process for minor 
>>> releases, TP or otherwise, and AFAICT the only non-TP translator who 
>>> routinely updates between minor releases is you (TP's Ukrainian and 
>>> Croatian translators have been very good at keeping up to date, albeit with 
>>> a one-release lag because of the TP's policy of working only from release 
>>> tarballs).
>> The betas help for a new major release, but not for the more frequent
>> minor releases.
>>
>> From https://translationproject.org/html/maintainers.html
>> 2. Using the Translation Project
>> :
>> Preferably you make a prerelease a week or so earlier and announce this
>> to the TP, so the translators get a chance to update their PO files
>> before the actual release of your package, so the release can go out
>> fully translated into several languages.
>>
>> Ideally we would declare string freeze 2 weeks before any release and
>> send a recent pot file to TP. So translators would have a chance to
>> update their po files before the release.
> Maybe should discuss this with Benno. I don't think it makes sense to do a 
> full release ahead of the real release. I'd think it would be sufficient to 
> make a pre-release tarball for the TP. They might even be able to work from 
> one of the Github tarballs. IIUC they don't try to build the project so they 
> wouldn't be affected by the versioning stuff. They run their own tools on it 
> and generate their own profile that they merge into their own po-file 
> repository.
>
> Regards,
> John Ralls
>
>
>
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel



OpenPGP_signature
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Fwd: Request to move translation to Gnu Translation Project

[Pedro Albuquerque]

Hi Benno, John,

thank you both for your super fast availability, as usual. I'll start
with the translation this weekend.

Regards,
Pedro

On 26/11/20 19:08, Benno Schulenberg wrote:
> Hi John and Pedro,
>
> Op 26-11-2020 om 15:58 schreef John Ralls:
>> Please change the pt translation as Pedro requests.
> Done.  Removed the 'external' mark for Portuguese,
> and assigned gnucash to Pedro.
>
> Regards,
>
> Benno



OpenPGP_signature
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Request to move translation to Gnu Translation Project

[Pedro Albuquerque]

Hello Dear Developers,

For some time now, I have tried to maintain GnuCash translation updated,
using Github and git. With lots of your help, it has worked in the past.
But it is highly unpractical for me, not being a developer.

So, being a disclaimed translator at Gnu Translation Project, I humbly
ask if you could move GnuCash translation file back to that project.
That way I could request that it is assigned to me and update the
translations regularly without making a mess with Github.

Many thanks in advance for your attention.

Kind regards,
Pedro Albuquerque


OpenPGP_0xE9A79A5C5307CE4A.asc
Description: application/pgp-keys


OpenPGP_0xE9A79A5C5307CE4A.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Request to move translation to Gnu Translation Project

[Pedro Albuquerque]

Hello Dear Developers,

For some time now, I have tried to maintain GnuCash translation updated,
using Github and git. With lots of your help, it has worked in the past.
But it is highly unpractical for me, not being a developer.

So, being a disclaimed translator at Gnu Translation Project, I humbly
ask if you could move GnuCash translation file back to that project.
That way I could request that it is assigned to me and update the
translations regularly without making a mess with Github.

Many thanks in advance for your attention.

Kind regards,
Pedro Albuquerque


OpenPGP_0xE9A79A5C5307CE4A.asc
Description: application/pgp-keys


OpenPGP_signature
Description: OpenPGP digital signature
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Translations update

[Pedro Albuquerque]

Hi Christopher,


that did it, thank you!


Pedro





Em 03/07/2019 às 12:18, Christopher Lam  escreveu:
Just an idea "Repositórios" in the path may not be acceptable to guile.
Try a simpler folder name eg "code"



On Wed, 3 Jul 2019 at 11:14, Frank H. Ellenberger
 wrote:




-- Forwarded message -
Von: Pedro Albuquerque 
Date: Mi., 3. Juli 2019 um 10:04 Uhr
Subject: Re[2]: [GNC-dev] Translations update
To: Frank H. Ellenberger 
Cc: GnuCash development list , Geert Janssens





Hi again,

thank you Geert, Frank, for your quick answer.

I was talking about both the UI and the help/guide. As far as I can tell,
there are no missing translations on the website.



So, the UI and building. I got a ninja/make error that I don´t know how to
solve. I attached the results of cmake and ninja hopping to get some help from
you.
I can add that I build Gnucash previously (with some difficulties on my end )
under MX-16 and it worked fine.

As prescribed here the command I used was:
sudo cmake -GNinja -DCMAKE_INSTALL_PREFIX=/opt/gnucash
/home/pmra/Repos/gnucash/gnucash
followed by sudo ninja.

The system is Debian based (BunsenLabs) and it's an old Toshiba 32 bit. I
first removed the other version of Gnucash.


Would it be Ok to send a compressed file with the updates via Bugzilla (since
I don't understand github)? UI is quick enough, docs will take a bit longer!


Pedro



Em 02/07/2019 às 10:04, "Frank H. Ellenberger" <
frank.h.ellenber...@gmail.com> escreveu:
>Hi Pedro
>
>Am 02.07.19 um 07:11 schrieb Pedro Albuquerque:
>> Hi Developpers,
>>
>> I just cloned the git repos to try and update the pt_PT translation,
>> but there is no .pot file.
>> Do I still have to build gnucash to create one?
>
>Are you talking about the program or the documeentation?
>
>Program:
>In theory yes, but as we are very short after the release, you can use
>https://translationproject.org/POT-files/gnucash-3.6.pot
>
>> Is there a list somewhere of the documentation changes? Or do I check
>> each file?
>
>Documentation:
>We are in preparation to convert the docs to .po, too:
>https://wiki.gnucash.org/wiki/Po_Based_Documentation_Translations
>But it still needs some work.
>
>How would I do it now:
>See https://github.com/Gnucash/gnucash-docs/commits/maint for an
>overview of changes.
>
>Then I would use 2 instances of e.g. KDiff3:
>1. Compare in C the current version with that, when you last translated
>a document.
>2. Edit your current pt docs while comparing with the current english
>version.
>
>A few notes: No hardcoded URLs in current versions. Replace them by the
>entities defined in our dtd:
>https://github.com/Gnucash/gnucash-docs/blob/maint/docbook/gnc-docbookx.dtd
>
>In case I missed something, https://wiki.gnucash.org/wiki/Translation
>should collect all important parts.
>
>> Apologies for the ignorance, best regards,
>> Pedro
>
>No problem and thanks for your work
>
>Frank


Sem vírus. www.avg.com 


---
Este e-mail foi verificado em termos de vírus pelo AVG.
http://www.avg.com
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] Translations update

[Pedro Albuquerque]

Hi again,

thank you Geert, Frank, for your quick answer.

I was talking about both the UI and the help/guide. As far as I can tell,
there are no missing translations on the website.



So, the UI and building. I got a ninja/make error that I don´t know how to
solve. I attached the results of cmake and ninja hopping to get some help from
you.
I can add that I build Gnucash previously (with some difficulties on my end )
under MX-16 and it worked fine.

As prescribed here the command I used was:
sudo cmake -GNinja -DCMAKE_INSTALL_PREFIX=/opt/gnucash
/home/pmra/Repos/gnucash/gnucash

followed by sudo ninja.

The system is Debian based (BunsenLabs) and it's an old Toshiba 32 bit. I
first removed the other version of Gnucash.


Would it be Ok to send a compressed file with the updates via Bugzilla (since
I don't understand github)? UI is quick enough, docs will take a bit longer!


Pedro



Em 02/07/2019 às 10:04, "Frank H. Ellenberger" 
escreveu:
>Hi Pedro
>
>Am 02.07.19 um 07:11 schrieb Pedro Albuquerque:
>> Hi Developpers,
>>
>> I just cloned the git repos to try and update the pt_PT translation,
>> but there is no .pot file.
>> Do I still have to build gnucash to create one?
>
>Are you talking about the program or the documeentation?
>
>Program:
>In theory yes, but as we are very short after the release, you can use
>https://translationproject.org/POT-files/gnucash-3.6.pot
>
>> Is there a list somewhere of the documentation changes? Or do I check
>> each file?
>
>Documentation:
>We are in preparation to convert the docs to .po, too:
>https://wiki.gnucash.org/wiki/Po_Based_Documentation_Translations
>But it still needs some work.
>
>How would I do it now:
>See https://github.com/Gnucash/gnucash-docs/commits/maint for an
>overview of changes.
>
>Then I would use 2 instances of e.g. KDiff3:
>1. Compare in C the current version with that, when you last translated
>a document.
>2. Edit your current pt docs while comparing with the current english
>version.
>
>A few notes: No hardcoded URLs in current versions. Replace them by the
>entities defined in our dtd:
>https://github.com/Gnucash/gnucash-docs/blob/maint/docbook/gnc-docbookx.dtd
>
>In case I missed something, https://wiki.gnucash.org/wiki/Translation
>should collect all important parts.
>
>> Apologies for the ignorance, best regards,
>> Pedro
>
>No problem and thanks for your work
>
>Frank


---
Este e-mail foi verificado em termos de vírus pelo AVG.
http://www.avg.com


gnucash-build.tar.gz
Description: Binary data
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

[GNC-dev] Translations update

[Pedro Albuquerque]

Hi Developpers,

I just cloned the git repos to try and update the pt_PT translation,
but there is no .pot file.
Do I still have to build gnucash to create one?

Is there a list somewhere of the documentation changes? Or do I check
each file?

Apologies for the ignorance, best regards,
Pedro
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: Printing report

[Pedro Albuquerque]

This is probably off topic and I haven't had the time to even try, but I  
intend to do so when on vacations.


Gnucash uses XML for data keeping. Maybe we can use Jasper Reports to  
enhance GnuCash capabilities.


Regards,
Pedro

Em Tue, 11 Apr 2017 22:55:04 -, R. Victor Klassen  
 escreveu:


The bit about lines being broken across pages is the result of adecision  
to use html as the interchange format for reports.
There is a directive in html to prevent this behaviour, however it is 
optional whether browsers/html renderers pay attention to it.


It’s been awhile since I cared, but I do recall that if I saved the 
report and then opened it in the right browser (might have been Firefox 
at the time), that problem goes away.


In general, it is difficult to get html to produce a report that would 
make a type lover/design nerd happy.


The good thing about using html is the high degree of portability it 
affords.


R. Victor Klassen
rvklas...@gmail.com
226-792-0733


On Apr 11, 2017, at 3:03 PM, ph hermes  wrote:

i'll just jump in here and say i wish there were some more choices in 
print

reports. my reports often print with page breaks right through a line of
informatio. it often just cuts the line in half. i have to export ascsv,
then change all the columns in excel... a very very long process when i
just want to print a report...

i'd love to be able to have page breaks before or after lines of type. 
i'd

also like to change fonts/ sizes as so many of the reports are big and
ungainly. i know i'm picky as i design books and love type, but still 
lines

should be all on 1 page or another.

just my 2 cents. many thanks for all you do...


~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:~:
writer ~:~ photographer ~:~ book designer
resident manager
paulahendricks.com

On Tue, Apr 11, 2017 at 5:17 AM, David Carlson 


wrote:

I recall that there were a few GnuCash releases that defaulted to A4 
page

size but more recently GnuCash has defaulted to US Letter. When it
defaulted to A4 my HP and Xerox printers would complain about not being
loaded with A4 paper and refuse to print. Since the two sizes ofpaper  
are

so close, I wondered why the printers couldn't be set to 'Shrink tofit"
and print on the opposite size paper. Those days are over for me, but 
now

this user has a problem which I also see on letter size paper wherelong
strings in the description field make the rest of the report spread out
over too much space. He is not alone. I have sometimes resorted to 
saving
reports in PDF format and importing them into Open Office or Libre 
Office
Calc where there is more flexibility with column formats in order to 
get a

better page appearance. If GnuCash had better format defaults thatextra
step would not be necessary.

If it is as simple as using File > Page Setup in GnuCash to switch toA4
paper, then this user has his solution.

David C

On Tue, Apr 11, 2017 at 5:51 AM, Geert Janssens <
geert.gnuc...@kobaltwit.be>
wrote:


On dinsdag 11 april 2017 10:47:59 CEST Francesco Castoro wrote:

-- Forwarded message --
From: Francesco Castoro 
Date: Tue, 4 Apr 2017 12:29:17 +0300
Subject: Printing report
To: gnucash-u...@gnucash.org

I recently moved gnucash from a desktop running Windows XP to a new
one with Windows 7 Professional.

Of course everything works properly, except for printing reports,

because

the
column "description" which on print-preview appears regularly,

during

the printing phase it spreads in four rows and this involves a
considerable waste, especially in the case of accounts very handled
(cash, banks, some customers etc).

I assume there is need to change fonts, spacing etc.

Thank you very much!


Hi Francesco,

It is exciting to learn gnucash is also being used in Uganda :)

As to your problem I observed the page formats of both scans are

different.
The report from the old PC looks like A4 while the report on your new 
PC

appears to be US Letter. Can you verify your printing preferences and

make

sure you are using the same (default) page format ?

Regards,

Geert
___
gnucash-user mailing list
gnucash-u...@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


___
gnucash-user mailing list
gnucash-u...@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.


___
gnucash-user mailing list
gnucash-u...@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-user
-
Please remember to CC this list on all your replies.
You can do this by using Reply-To-List or Reply-All.

Re: Missing pt section in gnucash-docs/xsl/l10n.xml

[Pedro Albuquerque]

Hi Frank

I thank you for your trouble. Please forgive my mistake. :-[
Not much to explain. I tried to checkout with the URL on that page and
it's not valid.

Regards,
Pedro.

Às 08:05 de 30/11/2016, Frank H. Ellenberger escreveu:
> Hi Pedro,
>
> Am 21.11.2016 um 07:14 schrieb Pedro Albuquerque:
>> Hi Frank,
>>
>> I attached the file here. But it's not tested. Hope those ascii codes
>> are correct.
> You forgot the closing tag: 
> Fixed and committed as  3ae3989.
> Thanks for your prompt answer!
>
>> And those instructions should really be reviewed, co address is wrong. ;)
> I don't understand, can you explain or fix it?
>
>> Thank you for all your trouble.
>>
>> Regards,
>> Pedro.
> Regards
> Frank


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

Re: Documentation translators: Changed para in ch_oview

[Pedro Albuquerque]

Às 12:10 de 09/08/2016, Frank H. Ellenberger escreveu:
> Hi Pedro,
>
> Am 09.08.2016 um 11:24 schrieb Pedro Albuquerque:
>> Hi Frank, all.
>>
>> Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt*
>> is the generic code for Portuguese, which means my translation could be
>> confused, for example, with Brazilian Portuguese whose country code is
>> *pt_BR* but is also Portuguese.
> I know this.
>
>> Let's assume someone in Brasil decides to create their own translation,
>> it would be impossible to distinguish between both if we were to use
>> only *pt*. It's like *en_US*, *en_AU*, *en_GB*, etc.
> In the moment, when someone offers a pt_BR translation, we will rename
> the directories with your files to pt_PT. But for now it is annoying:
>
> Run
> LANG=pt_BR gnucash
>
> F1 opens "Manual de ajuda do GnuCash"
> Ctrl+H opens "GnuCash Tutorial and Concepts Guide"
> instead of "Tutorial e guia de conceitos do GnuCash",
> which you get when you run
> LANG=pt_PT gnucash
>
> I am pretty shure, most brasilians would prefer to read your work
> instead of the english text. So I think we should rename the install dirs.
>
> BTW: I see outdated files gnucash-guide.epub and gnucash-guide.mobi in
> the repository. There is no need, to check them in, because they will be
> generated by the make process.
>
> Another misleading file is "COMO TRADUZIR" in help, describing how to
> use xml2po, but you translated the xml files. Are you planing to switch
> the method?
Not at all. Please, just delete whatever is unneeded.

Regards,
Pedro.
>
>> Thank you.
>>
>> Regards,
>> Pedro.
> Regards
> Frank


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

Re: Documentation translators: Changed para in ch_oview

[Pedro Albuquerque]

Às 11:03 de 09/08/2016, Geert Janssens escreveu:
> On Tuesday 09 August 2016 10:28:04 Pedro Albuquerque wrote:
>> Às 05:46 de 09/08/2016, David T. via gnucash-devel escreveu:
>>> Frank,
>>>
>>> As a git-challenged documentation contributor (I imagine my
>>> git-clutziness is well-documented), is there a non-git way you
>>> could present your change, so that I might examine it and maybe
>>> comment?
>>>
>>> To the list:
>>> Is the group hoping to move away from bugs on Bugzilla in favor of
>>> an all-git process? ISTM that recent comments on the lists hint at
>>> that direction. As I note above, this can act as a barrier to some
>>> of us technologically challenged individuals. Perhaps it is not
>>> such a big deal for code developers, but documentation involves a
>>> much different contributor base.
>> I'm definitely a proved git-ignorant so any other way to contribute
>> would make it easier for me too!  :-[
>>
> The way you handled it by adding a bug in bugzilla is perfectly fine and 
> appreciated.
>
> Thanks for your feedback :)
>
> Geert
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel

It is I who thanks you all for your excellent work and patience to deal
with my ignorance. :-)

Pedro.

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

Re: Documentation translators: Changed para in ch_oview

[Pedro Albuquerque]

Às 11:01 de 09/08/2016, Geert Janssens escreveu:
>
> On Tuesday 09 August 2016 10:24:30 Pedro Albuquerque wrote:
>
> > Hi Frank, all.
>
> >
>
> > Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt*
>
> > is the generic code for Portuguese, which means my translation could
>
> > be confused, for example, with Brazilian Portuguese whose country
>
> > code is *pt_BR* but is also Portuguese.
>
> >
>
> > Let's assume someone in Brasil decides to create their own
>
> > translation, it would be impossible to distinguish between both if we
>
> > were to use only *pt*. It's like *en_US*, *en_AU*, *en_GB*, etc.
>
> >
>
> Hi Pedro,
>
>  
>
> Thanks for your feedback. That part is well understood.
>
>  
>
> However the gnucash policy is to add the country code only when needed.
>
>  
>
> "when needed" is either of:
>
> - there are different translations for these countries. We only have
> one Portuguese translation, so this is not the case here
>
> - the translation has highly country specific information. This I
> can't judge as I don't know Portuguese, nor whether the contents of
> your translation is specific to Portugal and won't apply (for most
> part) to say Brazil.
>
>  
>
> Do you judge your translation is highly targeted at Portugal only
> (like specific wordings that are sufficiently different from Brazil,
> or rules that are very local) ?
>
>  
>
> Note this is no big deal though, just a small inconsistency with the
> other translations.
>
>  
>
> Regards,
>
>  
>
> Geert
>
Hi again.

Sorry if I misunderstood the question.

In terms of translation, of course every Portuguese speaking person will
understand the translation, no matter the country. In technical terms I
wouldn't know how to answer.
So, bottom line, yes I think you can use just *pt*.

Thank you.

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

Re: Documentation translators: Changed para in ch_oview

[Pedro Albuquerque]

Às 05:46 de 09/08/2016, David T. via gnucash-devel escreveu:
> Frank,
>
> As a git-challenged documentation contributor (I imagine my git-clutziness is 
> well-documented), is there a non-git way you could present your change, so 
> that I might examine it and maybe comment?
>
> To the list: 
> Is the group hoping to move away from bugs on Bugzilla in favor of an all-git 
> process? ISTM that recent comments on the lists hint at that direction. As I 
> note above, this can act as a barrier to some of us technologically 
> challenged individuals. Perhaps it is not such a big deal for code 
> developers, but documentation involves a much different contributor base.
I'm definitely a proved git-ignorant so any other way to contribute
would make it easier for me too!  :-[

Regards,
Pedro.

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

Re: Documentation translators: Changed para in ch_oview

[Pedro Albuquerque]

Hi Frank, all.

Yes, there is a reason. *pt_PT* is the country code for Portugal, *pt*
is the generic code for Portuguese, which means my translation could be
confused, for example, with Brazilian Portuguese whose country code is
*pt_BR* but is also Portuguese.

Let's assume someone in Brasil decides to create their own translation,
it would be impossible to distinguish between both if we were to use
only *pt*. It's like *en_US*, *en_AU*, *en_GB*, etc.

Thank you.

Regards,
Pedro.

Às 05:29 de 09/08/2016, Frank H. Ellenberger escreveu:
> Hi,
>
> I changed a para in ch_oview and used google translate. From my own
> language I know it is not perfect, but better than I would have done. ;-)
>
> So I ask you kindly, to review commit e4c8bae - Replace the confusing
> Release_Schedule link by 2.6-release-tour and website
>
> BTW, Pedro, is there some reason for installing to pt_PT instead of pt
> or is it a mistake?
>
> Regards
> Frank
> ___
> 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: Guide Documentation

[Pedro Albuquerque]

Hi,

I filed a bug with a patch, following these instructions:
http://wiki.gnucash.org/wiki/Documentation_Update_Instructions#The_Documentation_Change_Process_--_What_and_How_it_happens

Hope it's OK.

Regards,
Pedro.

Qui, 2016-03-03 às 20:09 +0100, Geert Janssens escreveu:

> On Sunday 28 February 2016 09:11:26 Pedro Albuquerque wrote:
> 
> > Hi,
> 
> > 
> 
> > like I said, it was just an idea, no need for discussion. When there
> 
> > is a plan, and if my help is needed, I'm available.
> 
> > 
> 
> > Meanwhile, I reset the reports files to their original state and run
> 
> > another make check. You can see the result in the attached file. I
> 
> > also tested C and pt with yelp and both worked fine.
> 
> > I think everything is OK now.
> 
> > 
> 
> > Have a nice Sunday,
> 
> > Pedro.
> 
> > 
> 
>  
> 
> Hi Pedro,
> 
>  
> 
> I have checked your most recent work and it passes make check now.
> 
>  
> 
> I have pushed it to our central repository after rebasing it to maint.
> 
>  
> 
> I few small items you may want to look into to further improve the
> Portuguese translation:
> 
>  
> 
> 1. I noticed the images are still not properly sized for the pdf
> version of the guide. I believe I explained earlier how you can fix
> this (for example using gimp).
> 
>  
> 
> 2. When compiling the guide as mobi, I get these errors:
> 
> Manifest item 'OEBPS/figures/loans_PrivateLoanFirstPayment.png' not
> found 
> Referenced file u'OEBPS/figures/loans_PrivateLoanFirstPayment.png' not
> found
> 
> 
> I suspect this is due to a missing image, or using the wrong image
> name in your document somewhere.
> 
>  
> 
> Regards,
> 
>  
> 
> Geert
> 


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

Re: Guide Documentation

[Pedro Albuquerque]

Hi,

like I said, it was just an idea, no need for discussion. When there is
a plan, and if my help is needed, I'm available.

Meanwhile, I reset the reports files to their original state and run
another make check. You can see the result in the attached file. I also
tested C and pt with yelp and both worked fine.
I think everything is OK now.

Have a nice Sunday,
Pedro.

Sáb, 2016-02-27 às 14:52 -0800, John Ralls escreveu:

> > On Feb 26, 2016, at 1:56 PM, Pedro Albuquerque <palbuquerqu...@gmail.com> 
> > wrote:
> > 
> > Hi
> > 
> > since reports documentation is not really available, here is an idea.
> > 
> > I think it can be consensual that reports should have a dedicated
> > section, since they affect both business and personal finances, and are
> > the only way to keep our accountants happy  ;-) .
> > 
> > So, I used the existing ch_reports.xml as base and:
> > 
> > 1 - Divided it, because it seemed to me that a single file for all
> > reports documentation would be to big. There isn't any logical reason
> > for this split.
> > 2 - The split is based on the Reports Menu it self. Apart the general
> > concepts, there is a file for each sub-menu and one for the general
> > menu.
> > 3 - Another file/section could be created for the How-to's, or they
> > could be integrated in the Example section.
> > 4 - I used the existing tables and expanded them to the list of
> > available reports. 
> > 5 - I did not create anything, except some links between tables and
> > files, and the screenshots, and even those would have to be EXIF cleaned
> > and size adjusted.
> > 6 - Nothing is finished nor complete. I used Accounts Summary Report as
> > the only example to illustrate my idea.
> > 
> > 7 - I didn't use git patch because I wouldn't know how. Please forgive
> > my ignorance, but this way is easier for me, and probably for you
> > developers.
> > I think I've made my fair share of git mistakes for you to endure with.
> > 
> > As said before, I'm available to help, but never to create unnecessary
> > discussions. It's just an idea, please do completely disregard it if it
> > is not in line with the roadmap or any other existing guidelines. Since
> > it was accepted within my translation (to be changed, if needed), here
> > is the English version with one single not pt translated example.
> > 
> > Regards,
> > Pedro.
> > 
> > P.S.: my github fork is updated, I think, so the files should be also
> > available there.
> 
> Pedro,
> 
> Thanks. I made one inline comment on your last "Still the make Check" commit; 
> with that fixed your Portuguese translation can be merged.
> 
> Unfortunately the C part fails make check, largely due to the same sort of 
> sect2 problems.
> 
> I'm afraid I don't understand what you're trying to convey in the tables. 
> Could you explain that please?
> 
> Regards,
> John Ralls
> 


Making check in help
make[1]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help'
Making check in C
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/C'
xmllint --valid --noout ../../../help/C/gnucash-help.xml
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/C'
Making check in de
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/de'
xmllint --valid --noout ../../../help/de/gnucash-help.xml
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/de'
Making check in it
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/it'
xmllint --valid --noout ../../../help/it/gnucash-help.xml
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/it'
Making check in pt
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/pt'
xmllint --valid --noout ../../../help/pt/gnucash-help.xml
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help/pt'
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help'
make[2]: Nothing to be done for `check-am'.
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help'
make[1]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/help'
Making check in guide
make[1]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/guide'
Making check in C
make[2]: Entering directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/guide/C'
xmllint --valid --noout ../../../guide/C/gnucash-guide.xml
make[2]: Leaving directory 
`/home/pedro/Programas/GnucashGit/gnucash-docs/build/

Re: Reports chapter in guide

[Pedro Albuquerque]

Hi Geert, all

I'll think about a way to contribute more widely as soon as I solve my
"local" problems. But I most certainly don't want to raise a huge
discussion about the merge.

I'm trying to follow John's advices, after what I'll translate my idea
and submit it as a bug. Starting there, we'll see how (or if) can I be
useful.

Thank you for the encouragement.

Regards,
Pedro.

Seg, 2016-02-22 às 10:11 +0100, Geert Janssens escreveu:

> On Sunday 21 February 2016 08:21:16 Pedro Albuquerque wrote:
> 
> > Hi again,
> 
> > 
> 
> > I read the bugs you mentioned David, and all other bugs and
> 
> > attachments related. And the wiki articles, and several Internet
> 
> > pages John, thank you for pulling my ears. ;-)
> 
> > Of course, I'm not aware of the new platform discussion, nor should
> I
> 
> > worry about that, according to Geert Janssens. Makes sense, for a
> non
> 
> > developer.
> 
> > 
> 
> > So, not being neither a developer nor an experienced Gnucash user,
> and
> 
> > not even an accountant, I can only speak as a regular computer user.
> 
> > Hope I'm not bothering to much.
> 
> > Platform independently speaking, I would rather have the help manual
> 
> > and the guide merged into one single document and then split in two
> 
> > again, one for personal finances and another for business finances.
> 
> > 
> 
> > One reason for this choice of mine and following up on a recent
> 
> > discussion on the users list, there are countries where GC can't be
> 
> > used for most businesses, so a separate document for businesses
> would
> 
> > make sense to me, living on one of those.
> 
> > 
> 
> > As for the merge, I think we all know that users seldom read the
> 
> > documentation (me included), so having to jump between two documents
> 
> > could eventually discourage them even more.
> 
> > 
> 
> > Either way, thank you for this excellent software. Took me some time
> 
> > to choose it but I'm glad I did. It's now fully translated into my
> 
> > language and I will finish just saying that I can spare some time to
> 
> > help, if you want.
> 
> > 
> 
> > Regards,
> 
> > Pedro.
> 
> > 
> 
>  
> 
> Hi Pedro,
> 
>  
> 
> Thank you for your great contribution. I'm very happy it is now fully
> translated in Portuguese.
> 
>  
> 
> And of course it would be great if you are willing to help out some
> more in the spare time you have.
> 
>  
> 
> Several people agree with you that merging all documentation into one
> would be a good thing. Perhaps you can contribute to this goal (at any
> level, like: coming up with a strategy or effectively doing the work).
> 
>  
> 
> Other than that there are several documentation bugs which you may be
> interested in tackling.
> 
>  
> 
> Or as John already proposed on your last pull request, if you added
> more documentation to the Pt version than was available in the
> original English edition, perhaps you can translate your personal
> additions back into English for inclusion.
> 
>  
> 
> All of these are just suggestions. Feel free to pick up any part you
> like. Each contribution however big or small is appreciated.
> 
>  
> 
> Regards,
> 
>  
> 
> Geert
> 


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

Re: Reports chapter in guide

[Pedro Albuquerque]

Hi,

About the merge, it's just an idea, thank you for your comment, I'll
think about that.

About the other issue, like I said, there was a previous discussion
about the use of GC in certain countries. It started, if I'm not
mistaken, with a Swedish user and their tax authority imposing the
existence of a non editable file. Here most business have to be online
with the tax authority's servers.
Both these are, to say the least, very restrictive to an official use of
GC.

Regards,
Pedro.

Seg, 2016-02-22 às 10:56 -0500, Derek Atkins escreveu:

> Hi,
> 
> Pedro Albuquerque <palbuquerqu...@gmail.com> writes:
> 
> > Platform independently speaking, I would rather have the help manual and
> > the guide merged into one single document and then split in two again,
> > one for personal finances and another for business finances.
> 
> In my opinion, the Help and the Guide serve different purposes.  The
> Help document is "I found this menu item/report/etc in the UI -- what
> does it do?" whereas the Guide is more about "I want to do X, how do I
> do it in GnuCash".
> 
> I'm not sure how you could merge those two concepts together into a
> single document.
> 
> > One reason for this choice of mine and following up on a recent
> > discussion on the users list, there are countries where GC can't be used
> > for most businesses, so a separate document for businesses would make
> > sense to me, living on one of those.
> 
> Okay, I'll bite --- why can't GnuCash be used for most businesses?
> 
> > As for the merge, I think we all know that users seldom read the
> > documentation (me included), so having to jump between two documents
> > could eventually discourage them even more.
> 
> See above for why there are two documents.
> 
> > Either way, thank you for this excellent software. Took me some time to
> > choose it but I'm glad I did. It's now fully translated into my language
> > and I will finish just saying that I can spare some time to help, if you
> > want.
> >
> > Regards,
> > Pedro.
> >
> > Sáb, 2016-02-20 às 11:46 -0500, David T. escreveu:
> >
> >> 687820
> >
> 
> -derek
> 
> > ___
> > 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: Image size for PDF documentation

[Pedro Albuquerque]

Hi,

I'll try to figure it out. GIMP will surely  have that feature.

Thank you,
Pedro.


Ter, 2016-02-16 às 16:31 +0100, Geert Janssens escreveu:

> On Tuesday 16 February 2016 15:21:15 Pedro Albuquerque wrote:
> 
> > Hi,
> 
> > 
> 
> > I build all the documentation for GC guide but the PDF images are
> 
> > awfully big (please see attachment), while all the others are
> normal.
> 
> > 
> 
> > I used the regular tools, autogen, configure --with-mobi and then
> make
> 
> > pdf. Did I forget something?
> 
> > 
> 
> > Thank you in advance,
> 
> > Pedro.
> 
>  
> 
> This usually means your images are saved in the wrong resolution
> (typically the default resolution of 72 dpi). This is fine for the
> html version of the documentation.
> 
>  
> 
> The printable documentation however requires your images to have
> physical dimension information encapsulated. Most image manipulation
> programs allow you to alter this, either by directly specifying the
> print size for the image, or indirectly by specifying a resolution in
> dpi (dots per inch).
> 
>  
> 
> The relation between pixel size, resolution and print size is this:
> 
> print_size (in inch) = pixel_size / resolution (in dpi)
> 
>  
> 
> Does this help ?
> 
>  
> 
> Regards,
> 
>  
> 
> Geert
> 


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

Site published

[Pedro Albuquerque]

Hi,

just want to say Thank you for your trouble publishing the site. Looks
great.

Have a nice Sunday everybody,
Pedro.
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Missing screen/info on tutorial

[Pedro Albuquerque]

Hi,

Tutorial first chapter, Putting it all together section, while
describing the creation a a new book, the screen regarding the New book
options is not mentioned/described.

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

Re: Missing screen/info on tutorial

[Pedro Albuquerque]

Done, thank you John.

Regards,
Pedro.

Sáb, 2016-01-23 às 07:15 -0800, John Ralls escreveu:

> > On Jan 23, 2016, at 3:27 AM, Pedro Albuquerque <palbuquerqu...@gmail.com> 
> > wrote:
> > 
> > Hi,
> > 
> > Tutorial first chapter, Putting it all together section, while
> > describing the creation a a new book, the screen regarding the New book
> > options is not mentioned/described.
> 
> Pedro,
> 
> Please check if there's a bug report on this and file one if there isn't. 
> We'll all have forgotten the mention on the mailing list in a week or two.
> 
> Regards,
> John Ralls
> 


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

Possible Bug/Suggestion

[Pedro Albuquerque]

Hi, please have a look at this image and let me know if a bug should be
created:



This is the scheduled transactions window, obviously, with the mouse
pointer on the far right. Part of the info popup disappears.
Happens under Ubuntu 14.04 LTS, 32 bit system.

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

Re: Possible Bug/Suggestion

[Pedro Albuquerque]

OK, thank you.

Sex, 2016-01-22 às 12:56 +, Richard Ullger escreveu:

> They're is already an open bug for this.
> 
> 
> 
> On Fri, 22 Jan 2016 12:55 Pedro Albuquerque <palbuquerqu...@gmail.com>
> wrote:
> 
> 
> Hi, please have a look at this image and let me know if a bug
> should be
> created:
> 
> 
> 
> This is the scheduled transactions window, obviously, with the
> mouse
> pointer on the far right. Part of the info popup disappears.
> Happens under Ubuntu 14.04 LTS, 32 bit system.
> 
> Regards,
> Pedro.
> ___
> 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

Tutorial and Concepts Guide - Multi-platform Compatibility

[Pedro Albuquerque]

Hi,

the list doesn't mention Windows. Not that I'm a big fan, but...

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

Help manual suggestion

[Pedro Albuquerque]

Hi,

I've been translating the help manual and noticed something.

In the Transactions section, Inserting/Adding a transaction (both single
and multi-split), there is a description on how GC attempts to fill the
account name in alphabetical order.
That description uses the default account separator ":" (colon). But if
someone chooses another character, the description becomes invalid.

In pt_PT translation, I added a small  bringing this to the user's
attention.

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