Hi list,
i'm translating the english documentation to italian.
I would like to know which is the best way to translate the
documentation, and if someone else is translating the docs to italian.
And once completed where i can send the docs translated.
Thanks
fabrizio
Hi Fabrizio,
thank you very much for offering to help with translations. Much
documentation about the different translation areas is collected in the
file doc/TRANSLATION_HOWTO in the recent gnucash packages. But if you
start to work, you should definitely only use the current up-to-date
sour
Actually I would still prefer a gnomesupport.org-like approach of the
restriction level in the gnucash wiki: Editing allowed for every
logged-in users and everyone can create a user account for
herself/himself. No manual grant of editing permission.
Iff this attracts too much spam, we can stil
On 12/1/05, Christian Stimming <[EMAIL PROTECTED]> wrote:
Hi Fabrizio,thank you very much for offering to help with translations. Muchdocumentation about the different translation areas is collected in thefile doc/TRANSLATION_HOWTO in the recent gnucash packages. But if you
start to work, you shoul
Developers,
I'm requesting comments on the following policy change. I
believe this change would streamline GnuCash development.
* Background
For many years now, the development policy has included a
requirement to make an entry in the ChangeLog file describing the
changes made a
On Thursday 01 December 2005 9:25 pm, Chris Shoemaker wrote:
> The problems with continuing to use the existing ChangeLog
> policy are:
> - Having to write two commit descriptions increases the chance
> that both will be of lesser quality than if only one description was
> required.
On Thu, 2005-12-01 at 16:25 -0500, Chris Shoemaker wrote:
> Comments?
This change is fine with me, and sounds good.
...jsled
--
http://asynchronous.org/ - `a=jsled; b=asynchronous.org; echo [EMAIL PROTECTED]
___
gnucash-devel mailing list
gnucash-deve
Quoting Josh Sled <[EMAIL PROTECTED]>:
On Thu, 2005-12-01 at 16:25 -0500, Chris Shoemaker wrote:
Comments?
This change is fine with me, and sounds good.
Before we go ahead with this, I'd like to hear from Chris Lyttle
and Christian Stimming.. They're the ones who usually use the
ChangeLog
Chris Shoemaker <[EMAIL PROTECTED]> writes:
> The problems with continuing to use the existing ChangeLog
> policy are:
> - Having to write two commit descriptions increases the chance
> that both will be of lesser quality than if only one description was
> required.
Write one desc
Derek Atkins <[EMAIL PROTECTED]> writes:
> Personally, I like being able to grep through the changelog in order
> to see, e.g. whether a particular change made it into a particular
> release. I suppose I can always redirect the log/status command into
> a file and grep it there.
People who must
10 matches
Mail list logo
