User talk:Fell

Screenshots

It would be nice if I could replace the screenshots with translated ones, so I'll meed access rights to uploading files, or get them out there some other way... --Avma (talk) 15:35, 28 July 2021 (UTC)

Granted --Fell (talk) 17:43, 28 July 2021 (UTC)

Thanks Fell...--Avma (talk) 07:08, 29 July 2021 (UTC)

Broken Link

Hi there Fell, I noticed the Documentation link on the main page under GnuCash#Developing_the_Documentation is broken. Would have fixed it myself, but I do not have edit permissions for the main page. LeeRead (talk) 15:15, 27 July 2017 (UTC)

Thanks for the heads up. They should be fixed with https://wiki.gnucash.org/wiki/index.php?title=GnuCash&diff=12852&oldid=12849 --Fell (talk) 21:07, 27 July 2017 (UTC)

Git Edits Restored

Hi. I restored the Git page back to your last edits, and then merged in my own edits. I trust these will meet your needs. I apologize for overwriting your changes, and will watch for that in the future.

Thank you! :-)--Fell (talk) 16:37, 28 July 2017 (UTC)

No Worries! I'll proceed with my other planned steps then - trying to create the documentation or other wiki pages that allow you to remove some of the less frequent questions off the FAQ. Thanks! Matt. Any questions or issues, I'll try to be on IRC as Mattig7.

FAQ page edit

The addition of the Linux world article to the wiki is problematic insofar as this content is only available to subscribers. This may change at some time in the future, but it is not true now. Until it is generally available, it shouldn't be here.

Should the availability change, this addition would be better if it read:

{Link} includes scripts to migrate from QuickBooks to GnuCash.

Andrew Ruthven wrote on -devel: ... it'll be publicly available on the 14th.

- devel reader can use H. Thoma's link, others have the option to subscribe or wait a few days.

So, feel free to improve it 'for not subscribed people available from 2017-08-14' or similar. --Fell (talk) 21:55, 8 August 2017 (UTC)

You are editing the FAQ at the same time as I am. Why?

Fell,

I do not understand why you have decided that NOW is a good time to start working on the FAQ page. I have made it clear both on the wiki and on gnucash-devel that I am working on a major update of this page, and I am suddenly getting numerous notifications that you are tinkering around with the indentation, coding and content of a variety of sections here.

I am also wondering why you have put effort into making such edits on a question that I have already targeted as being duplicative and outdated (edit 14415). Putting your time into modifying the code on this section, which is covered in far greater detail on the Building page seems the height of duplication. It would be far more productive for both of us if you were in this case to work on ensuring that the Building page incorporates this information into it, and then either removing this entry altogether, or changing it to refer to the Building page.

Imagining fires

You added the phrase "Imagine a fire in your home." I would prefer in general not to add colloquial language like this. Instead, add a general statement of advice, e.g., "Off site backups protect your data from physical damage to your equipment." Sticking to factual statements, IMHO, is preferable in software documentation.

In general you are right, but IMHO in current days the requirement of different backups still needs drastic examples to exalt the consciousness. And I think the wiki can be less formal than the released docs. --Fell (talk) 15:40, 23 October 2018 (UTC)

Localization versus Translation

Frank, a couple of points. First, translation and localization, as I understand from the examples (US English uses 'z' in its spelling of this word,BTW) are fundamentally different actions.

Translation converts text from one language to another; localization, as indicated by the examples, consists of determining content for a particular jurisdiction. One could argue that building localization files requires no actual language skills at all.

Although I remain skeptical about the utility of encouraging people to contribute to either the account hierarchies or the tax codes (based on the lack of response to this over the last 13 years), I cede the point. However, since we have an entire page on translation, I'm going to remove detail here and refer readers to that page.

Templates

I remember, we got new or updated templates for AT, DE, IN, PT, RU and several minor fixes in 2018, probably more. Not all go over the english lists. Some were discussed e.g. on gnucash-de, most came as pull request or bugzilla attatchment.

Translation is only one part of localization (L18N), see https://en.wikipedia.org/wiki/Internationalization_and_localization, and the different parts require different skills: to create e.g. british business accounting templates does not need specific language skills, but knowledge of regional accounting rules, legal and fiscal specifics. So a qualified accountant would probably skip the sections and pages about translation.

• Contributing to GnuCash should probably become more user oriented: You want to contribute? Which skills and resources can you offer? Then you could help with ... in ascending order from 'only time' over accounting knowledge, language skills, GUI or Web design to coding, finally for that without time: donate.
• Translation has become to big. I plan to break it in parts after some reordering and rename the general part Localization or similar.

BTW you made a very good job in the other parts, special moving content from FAQ to "real pages"!--Fell (talk) 03:03, 4 February 2019 (UTC)

Bugzilla and account migration

So, you felt it was too soon to remove the note that user passwords would be reset. I felt it was enough time. Perhaps we should check with Derek and find out how many Bugzilla accounts remain ported but not accessed. It may also be that Derek has a new policy in place for those logins...

I thought of those Happy Campers, which find only every five or ten years new bugs.--Fell (talk) 14:49, 5 February 2019 (UTC)

Eclipse

Hi Frank, I don't think modern gdb's tell you any more which objects are missing source. They use 'just in time' to load when required if possible.

Chris, as you recently did a fresh install, you should update the whole eclipse page. ISTR the Galileo bugs are no longer important - remove that sections. When the page was written, we had often to go in the shell, because corresponding commands were not or faulty implemented in Eclipse or its plugins. In between you can often use the internal commands.

gdb

1. This section should talk about debug/dbg (symbol) packages, not dev[el] (header files). The check for devel packages already happens in the build process.
2. I would run a simple test:

1. uninstall 1 desired debug package
2. watch the output of gdb and update the wiki
3. reinstall the debug package.

git clone

Why do you want to override the default checkout branch [-b master]? The project owners set it on github.

Today I would suggest:

git clone --bare ${URL} #once
git worktree add <path> [<branch>] #for each desired branch

because it would save you the complete rebuild when switching between maint and master. But I did not fully test it in Eclipse.

--Fell (talk) 14:58, 6 June 2020 (UTC)

Configuration locations on Backup page

Frank, I believe it would it be better to remove all the specifics regarding configuration file locations from the Backup page, so that the information needs updating only in one place on the wiki. The focus here should be on the categories of files needing backup, rather than their specifics. I'll note that this page includes information about aqbanking configuration files, which might be better placed on the Configuration Locations page.

Oh, I tried only to improve/modernize the formatting. ;-)

David, right Aqbanking and FQ (add 'export ALPHAVANTAGE_API_KEY=…' into ~/.bashrc for gnc-fq-* commands, but that is already in the Help appendix) as 3. party components should probably get own sections/pages. But note, that .aqbanking like the old DOT_GNUCASH_DIR contains static (conf) and dynamic (logs, …) data. And we should not overload pages, better create more specific pages and link them. We have recently reordered the data exchange complex in de in 14 separate pages - also to reduce redundancy.

If you want to create a complete backup, you need to know, which directories are relevant. But the details (XDG spec) then are in Configuration Locations. At least the linking elements will always appear twice.

Tip

You can also put small chunks in templates like Template:De/2018-07-01_Bugzilla-Umzug, which was once on the main and the bugzilla page includes.

just as ideas, I have to leave for now --Fell (talk) 16:14, 19 March 2021 (UTC)

Update

David, how about changes like https://wiki.gnucash.org/wiki/index.php?title=Windows&curid=1333&diff=18676&oldid=16412? If you like it apply similar changes. If the website or the docs are recent and complete, link them.

Available Documentation

The page is locked: https://wiki.gnucash.org/wiki/GnuCash#Available_Documentation

It would be easier to follow if the first line was a sub-heading, say primary instructional documents

subsection until where?

and I'd remove/move Nightly Builts.

Why do you want to remove the most recent version?

Or move to where?

--Fell (talk) 20:53, 3 October 2023 (UTC)

Try and follow the flow. Users are reasonably directed to the more formal docs first but they are unlikely to find their way down to the wiki which is lost in the minutia.

As a general comment on the wiki, https://wiki.gnucash.org/wiki/FAQ is easy enough to find but https://wiki.gnucash.org/wiki/Using_GnuCash is not. - flywire

How about creating your suggested version of Gnucash as User:Flywire/GnuCash and we will move useful parts into the main page? --Fell (talk) 21:42, 11 October 2023 (UTC)

Good idea. Done.

btw, Is there a shortcut for the fancy timestamp? -flywire

Help:Signatures/en --Fell (talk) 19:24, 12 October 2023 (UTC)

Updated again -flywire

Merged, thanks!

--Fell (talk) 20:28, 13 October 2023 (UTC)