From: Floris van Manen <vm@klankschap.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Invoice Forms
Date: Thu, 14 Jun 2018 16:17:44 +0200 [thread overview]
Message-ID: <0F2F54AE-6EEB-4006-B1CC-5A5CB947207C@klankschap.nl> (raw)
In-Reply-To: <552F67D2-3012-42BD-8507-1CF1011167FE@fiee.net>
[-- Attachment #1.1: Type: text/plain, Size: 2111 bytes --]
almost…
what is \fieevis ?
\670>:letter:layer:location:fiee ... 5em \fieevis
\setuptabulate [bodyfont=s...
l.4 }
> On 14 Jun 2018, at 16:00, Henning Hraban Ramm <texml@fiee.net> wrote:
>
> Am 2018-06-14 um 12:48 schrieb Henning Hraban Ramm <texml@fiee.net>:
>
>> Am 2018-06-13 um 19:50 schrieb jdh <dhenman@gmail.com>:
>>
>>> Is there a source of context document forms for invoices, (and other documents), that have been contributed for open modifications and use? If not it would be very beneficial to people to have such a depository. Please let me know.
>>
>> Dear unknown,
>> there’s nothing out there, AFAIK.
>>
>> But I’m writing my invoices with ConTeXt, using a mixture of Shell, Python, Lua and ConTeXt, also mixed German/English:
>> * A bunch of Shell scripts call the main Python script with the right parameters.
>> * Python script/library manages customers and catalogue and fills a ConTeXt/Lua invoice template
>> * Python or Shell script calls ConTeXt, invoice calculations in Lua
>>
>> I can provide you with the ConTeXt & Lua part, the Python stuff contains too much private information.
>> There’s no documentation and I don’t claim the code to be good.
>>
>> <classy.lua><invoicelib.lua><classy.lua><invoicelib.lua>
>
> Sorry, didn’t check what I attached. Here are the missing tex files.
>
> Greetlings, Hraban
> ---
> https://www.fiee.net
> http://wiki.contextgarden.net
> https://www.dreiviertelhaus.de
> GPG Key ID 1C9B22FD
> <environment.tex><rechnung_tpl.tex>___________________________________________________________________________________
> If your question is of interest to others as well, please add an entry to the Wiki!
>
> maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
> webpage : http://www.pragma-ade.nl / http://context.aanhet.net
> archive : https://bitbucket.org/phg/context-mirror/commits/
> wiki : http://contextgarden.net
> ___________________________________________________________________________________
[-- Attachment #1.2: Message signed with OpenPGP using GPGMail --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 492 bytes --]
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-06-14 14:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 17:50 jdh
2018-06-14 10:48 ` Henning Hraban Ramm
2018-06-14 14:00 ` Henning Hraban Ramm
2018-06-14 14:17 ` Floris van Manen [this message]
2018-06-14 14:50 ` Henning Hraban Ramm
2018-06-14 13:29 ` Peter Münster
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0F2F54AE-6EEB-4006-B1CC-5A5CB947207C@klankschap.nl \
--to=vm@klankschap.nl \
--cc=ntg-context@ntg.nl \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).