Difference between revisions of "User talk:Fell"
(→Imagining fires) |
(→Localization versus Translation: new section) |
||
| Line 34: | Line 34: | ||
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. | 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. --[[User:Fell|Fell]] ([[User talk:Fell|talk]]) 15:40, 23 October 2018 (UTC) | :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. --[[User:Fell|Fell]] ([[User talk: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. | ||
Revision as of 01:25, 4 February 2019
Contents
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.
- 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.
