Hi,
AFAIK english "rebate" is much more general than german "Rabatt", which is a
special kind of discount. So I think, as split-register paired
with "Aufwendung" is the other meaning, where "Erstattung" fits better.
Frank
___
gnucash-devel mailing lis
Hi Manfred!
Thanks for the list, and my apologies for not responding more quickly. I
have added it to the Wiki
Nathan
PS: you can sign up for an account on our wiki if you want.
On 6/28/07, Manfred Usselmann <[EMAIL PROTECTED]> wrote:
>
> Hi Nathan,
>
> On Wed, 23 May 2007 10:26:09 -0400
> "Nat
On 7/10/07, Christian Stimming <[EMAIL PROTECTED]> wrote:
>
> Chris, Nathan, and all,
>
> I think we're ready for 2.2.0. We've fixed a whole number of Windows bugs;
> we
> reduced the showstoppers on Windows to a minimum; and we've fixed a
> significant number of overall bugs as well. I think we ca
"Benjamin Sperisen" <[EMAIL PROTECTED]> writes:
> So, if you've already started on one, just tell me and I'll start
> tracking it. If not, is it alright with you if I write it? It would
> probably have a prototype like:
>
> time_t gnc_parse_date(char* str, int format);
>
> where format is in an en
Thomas Baumgart <[EMAIL PROTECTED]> writes:
> You might find some more information about the problem here:
>
> http://kmymoney2.sourceforge.net/online-manual/details.impexp.qifimp.html#id2512201
Interesting. The way I'd handle it is to assume "70-99" -> 1970-1999
and "00-60" == 2000-2060. If we
Ben,
"Benjamin Sperisen" <[EMAIL PROTECTED]> writes:
> I just committed some changes that should make the lib/stf code
> compile with goffice 0.2, but if anyone still has problems, please let
> me know. For now, I've commented out the calls to functions that are
> in goffice-0.3, and I'll uncomme
Thomas,
[EMAIL PROTECTED] writes:
>> The QIF code has a decent date parser, although it's in scheme
>> right now. The regex looks like:
>>
>> "^ *([0-9]+) *[-/.'] *([0-9]+) *[-/.'] *([0-9]+).*$|^
>> *([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9]).*$"
>>
>> In other words the seperators are a dash
Chris, Nathan, and all,
I think we're ready for 2.2.0. We've fixed a whole number of Windows bugs; we
reduced the showstoppers on Windows to a minimum; and we've fixed a
significant number of overall bugs as well. I think we can go ahead and
release 2.2.0 at the next date that seems fit.
As di
Hi all,
on Tuesday 10 July 2007 12:39, Benjamin Sperisen wrote:
> Hi Chintan,
>
> I think I'm at the point with the CSV import where I would be ready to
> integrate a date parser that could be used by both the QIF and CSV
> imports, so I was just wondering how far you are as far as date
> parsing
Hi Chintan,
I think I'm at the point with the CSV import where I would be ready to
integrate a date parser that could be used by both the QIF and CSV
imports, so I was just wondering how far you are as far as date
parsing code is concerned. I'm happy to write the date parsing
function, but I thoug
Thanks for all of your comments!
Christian and I already discussed some of his email in #gnucash, but
I'll summarize that discussion here, and respond to the rest of his
comments as well as those from Derek and Thomas about the date
parsing.
On 7/8/07, Christian Stimming <[EMAIL PROTECTED]> wrote
Quoting Nikos Charonitakis <[EMAIL PROTECTED]>:
>> http://svn.gnucash.org/trac/browser/gnucash/trunk/packaging/win32/gnucash.iss.in?format=raw
>>
>> Unfortunately the file contains characters by at least two
>> different encodings
>> by now: iso-8859-1 for the German umlauts, and iso-8859-7 for
12 matches
Mail list logo
