Re: Documentation translators: Changed para in ch_oview

On Thursday 11 August 2016 21:19:31 David T. wrote: > Geert, > > I truly appreciate your reasonable and reasoned reply. It makes clear > even to the densest of us (me). I was not aware of Frank’s > longstanding and ongoing contributions to GnuCash, and for that I > also apologize. > > I have

Re: Documentation translators: Changed para in ch_oview

Geert, I truly appreciate your reasonable and reasoned reply. It makes clear even to the densest of us (me). I was not aware of Frank’s longstanding and ongoing contributions to GnuCash, and for that I also apologize. I have since seen Frank’s explanation as well, and I appreciate his work to

Re: Documentation translators: Changed para in ch_oview

HI, Am 10.08.2016 um 18:29 schrieb Geert Janssens: > And I can't tell why Frank chose to push this commit rather than following > your suggestion in > bug 743672. He can explain that himself if he cares to. By the way, I believe > you were on the > right track and agree even more with John we

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 21:22:36 David T. wrote: > > I think also of concern to me here is that there are now two > recommended methods for suggesting and making changes, and as I noted > here, with two avenues for change, there is the increasing likelihood > that bugs will languish in one or

Re: Documentation translators: Changed para in ch_oview

Am 09.08.2016 um 13:59 schrieb Pedro Albuquerque: > Às 12:10 de 09/08/2016, Frank H. Ellenberger escreveu: : >> 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", >>

Re: Documentation translators: Changed para in ch_oview

> On Aug 9, 2016, at 7:23 PM, Geert Janssens wrote: > > On Tuesday 09 August 2016 16:59:10 David T. wrote: > > Geert, > > > > > > Ok, I had to re-read this a couple of times to get your point. > > > > > > For some time now we are accepting changes in two ways:

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 16:59:10 David T. wrote: > Geert, > > > > Ok, I had to re-read this a couple of times to get your point. > > > > For some time now we are accepting changes in two ways: either as an > > attachment in bugzilla or as a pull request in github. The > > submitter can choose

Re: Documentation translators: Changed para in ch_oview

> On Aug 9, 2016, at 4:59 AM, David T. via gnucash-devel > wrote: > > As for the modification that Frank is offering, I will note that there is a > bug that I filed in bugzilla (743672) proposing that this section be moved in > its entirety to an appendix. Perhaps

Re: Documentation translators: Changed para in ch_oview

Geert, > On Aug 9, 2016, at 2:19 PM, Geert Janssens wrote: > > On Tuesday 09 August 2016 13:37:02 David T. wrote: > > Geert and Frank, > > > > I understand that these aspects of software development are clear and > > easy for you; suffice to say they are not for me.

Re: Documentation translators: Changed para in ch_oview

À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 >>

Re: Documentation translators: Changed para in ch_oview

À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

Re: Documentation translators: Changed para in ch_oview

À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 > > >

Re: Documentation translators: Changed para in ch_oview

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

Re: Documentation translators: Changed para in ch_oview

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

Re: Documentation translators: Changed para in ch_oview

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

Re: Documentation translators: Changed para in ch_oview

À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

Re: Documentation translators: Changed para in ch_oview

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

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 13:37:02 David T. wrote: > Geert and Frank, > > I understand that these aspects of software development are clear and > easy for you; suffice to say they are not for me. I do not wish to > start any long discussion about the mechanisms for implementing > changes to

Re: Documentation translators: Changed para in ch_oview

Geert and Frank, I understand that these aspects of software development are clear and easy for you; suffice to say they are not for me. I do not wish to start any long discussion about the mechanisms for implementing changes to GnuCash’s code and documentation; they have been hashed out many

Re: Documentation translators: Changed para in ch_oview

On Tuesday 09 August 2016 09:46:00 David T. via gnucash-devel wrote: > 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? Can you read a

Re: Documentation translators: Changed para in ch_oview

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

Documentation translators: Changed para in ch_oview

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