ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Henning Hraban Ramm via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Henning Hraban Ramm <texml@fiee.net>
Subject: Re: Adding support for German language to the Words conversion
Date: Sat, 31 Dec 2022 17:53:20 +0100	[thread overview]
Message-ID: <c40194d9-9049-5fec-ac70-0e1d0eb79c3f@fiee.net> (raw)
In-Reply-To: <230661f4-778d-7bad-b01c-ac803f7a31e8@gmail.com>

Hi Marcus,
any news on that?
Seems like you didn’t send your work to Hans or it didn’t arrive.

Happy new year,
Hraban

Am 31.10.22 um 10:05 schrieb Wolfgang Schuster via ntg-context:
> Hi Marcus,
> 
> do you have an update on the support for german verbose numbers?
> 
> Wolfgang
> 
> 
> Hans Hagen via ntg-context schrieb am 10.10.2022 um 23:44:
>> On 10/10/2022 9:21 PM, Marcus Christopher Ludl via ntg-context wrote:
>>> Hello all,
>>>
>>> this is my first contribution to this mailing list. 😄
>>>
>>> Recently, when I posted a question on StackExchange.com regarding 
>>> adding support for another language (German) to the "Words" 
>>> conversion in ConTeXt (see here: 
>>> https://tex.stackexchange.com/questions/657534/how-to-add-support-for-another-language-german-to-the-words-conversion-in-cont), @mickep suggested that I post the patched file (core-con.lua) to the mailing list, once I have it finished, so that it can be added for all to use. So, now that I'm confident my code works well, I would like to do just that. 😄
>>>
>>> How should I proceed? Should I just send the file including my new 
>>> code as an attachement to the mailing list? Or would it be 
>>> preferrable to paste only the new parts of the code inline into an 
>>> e-mail? Is that even the correct mailing list or would it be better 
>>> to send this to dev-context@ntg.nl?
>> just mail them to me and wolfgang and we'll have a look at it
>>
>> Hans

___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!

maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage  : https://www.pragma-ade.nl / http://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : https://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2022-12-31 16:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-10 19:21 Marcus Christopher Ludl via ntg-context
2022-10-10 21:44 ` Hans Hagen via ntg-context
2022-10-31  9:05   ` Wolfgang Schuster via ntg-context
2022-12-31 16:53     ` Henning Hraban Ramm via ntg-context [this message]

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=c40194d9-9049-5fec-ac70-0e1d0eb79c3f@fiee.net \
    --to=ntg-context@ntg.nl \
    --cc=texml@fiee.net \
    /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).