Difference between revisions of "User talk:Jralls"

From GnuCash
Jump to: navigation, search
(Bugs/support for "unsupported" tool Bayes.perl: Tip)
(Response)
Line 14: Line 14:
 
Thank you again for your dedication. I appreciate GnuCash very much. [[User:Jim DeLaHunt|Jim DeLaHunt]] ([[User talk:Jim DeLaHunt|talk]]) 19:16, 11 February 2016 (UTC)
 
Thank you again for your dedication. I appreciate GnuCash very much. [[User:Jim DeLaHunt|Jim DeLaHunt]] ([[User talk:Jim DeLaHunt|talk]]) 19:16, 11 February 2016 (UTC)
 
: Jim, if you open the history of the Bayes page, you can see the author [[User:YeOldHinnerk]]. How about contacting him? --[[User:Fell|Fell]] ([[User talk:Fell|talk]]) 22:26, 11 February 2016 (UTC)
 
: Jim, if you open the history of the Bayes page, you can see the author [[User:YeOldHinnerk]]. How about contacting him? --[[User:Fell|Fell]] ([[User talk:Fell|talk]]) 22:26, 11 February 2016 (UTC)
 +
: And BTW he's been in the past a regular contributor to gnucash-users, though he hasn't posted anything there in a year.
 +
 +
No, don't file a bug report for a Wiki page. Change the Wiki Page. We don't use Talk pages much. Frank and I camp out on the Recent_Changes page so that we can revert and block spammers, so we see the changes. I don't think that anyone else ever looks, so your complaints would be unheard. Much better to either change the page itself, to post about it on gnucash-user, or both.
 +
 +
FWIW a cursory look at the code shows that it has no facility for handling a compressed file and that it loops through the file once, processing the first import-map-bayes element that it finds and then exiting. It's working with the XML as raw text so it has the potential to mess up your file and make it unreadable. A simple XSLT stylesheet would do a better job more safely.

Revision as of 23:18, 11 February 2016

Hello John, please explain your revert at the talkpage of Roadmap. Otto (talk) 14:11, 29 June 2015 (UTC)

Hi John, you took out the word alias from your last edit of the Editing Git page but I think you forgot to replace it with something better. Regards Chris Good

Chris, Thanks for noticing. Fixed.

Bugs/support for "unsupported" tool Bayes.perl

Hello, Jralls, many thanks for all your work on GnuCash. Your diligence includes monitoring the Wiki, and noticing the bugs I documented in Talk:Bayes. You deleted those notes, and pointed me to gnucash-user@gnucash.org to request support there.

Fair enough. I want to contribute in the correct way to help GnuCash forward. Still, the issues I was noting are for a Perl script at Bayes, and it says there, "The GnuCash team is not responsible for it and it is provided as-is and you can use it at your own risk." Do you really want traffic on gnucash-user for a "not responsible" bit of code? Do you also want bugs on this utility to be filed at bugzilla.gnome.org? If so, then is it all right if I add this after the "not responsibile" sentence in Bayes?

Thank you again for your dedication. I appreciate GnuCash very much. Jim DeLaHunt (talk) 19:16, 11 February 2016 (UTC)

Jim, if you open the history of the Bayes page, you can see the author User:YeOldHinnerk. How about contacting him? --Fell (talk) 22:26, 11 February 2016 (UTC)
And BTW he's been in the past a regular contributor to gnucash-users, though he hasn't posted anything there in a year.

No, don't file a bug report for a Wiki page. Change the Wiki Page. We don't use Talk pages much. Frank and I camp out on the Recent_Changes page so that we can revert and block spammers, so we see the changes. I don't think that anyone else ever looks, so your complaints would be unheard. Much better to either change the page itself, to post about it on gnucash-user, or both.

FWIW a cursory look at the code shows that it has no facility for handling a compressed file and that it loops through the file once, processing the first import-map-bayes element that it finds and then exiting. It's working with the XML as raw text so it has the potential to mess up your file and make it unreadable. A simple XSLT stylesheet would do a better job more safely.