ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <pragma@wxs.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \Word broken
Date: Tue, 05 Aug 2008 22:48:44 +0200	[thread overview]
Message-ID: <4898BCAC.7080705@wxs.nl> (raw)
In-Reply-To: <48988A73.4060201@waechter.wiz.at>

Matthias Wächter wrote:
> On 8/5/2008 6:48 PM, Hans Hagen wrote:
>> Matthias Wächter wrote:
>>> On 8/5/2008 6:37 PM, Hans Hagen wrote:
>>>> Matthias Wächter wrote:
>>>>
>>>>> Do you know how this can be fixed? Is the descripion descriptive enough?
>>>> will be fixed in the next release (tomorrow we plan to do a formal release)
>>> Thanks! I am looking forward to the change as I am curious what’s the proper way of doing it.
>> you mean in lua code?
> 
> Yeah. While I survived a journey into changing some ConTeXt (MKII) functionality recently and found everything clear (texbook is your friend), I am really puzzled about attribute handling in Lua. But it’s just a couple of lines I have investigated, maybe I’ll be a wizz as soon I roll things up from bottom to top … ;-)

attributes are just a property of nodes, and characters in the input 
become nodes

in this case there is a specific attribute for casing with a value that 
tells to do Words

the tricky thing here is that when i process Word, i need to erase 
following casing attributes

at some time in the future, context mkiv will provide a mechanism for 
user attributes

(attribute processing can take place at several moments by intercepting 
the node list)

Hans


-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
      tel: 038 477 53 69 | fax: 038 477 53 74 | www.pragma-ade.com
                                              | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive  : https://foundry.supelec.fr/projects/contextrev/
wiki     : http://contextgarden.net
___________________________________________________________________________________

      reply	other threads:[~2008-08-05 20:48 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-24 18:57 \word of synonyms Matthias Wächter
2008-07-24 19:49 ` Peter Münster
2008-07-25  9:30   ` Matthias Wächter
2008-07-29 20:53     ` \Word broken Matthias Wächter
2008-07-29 21:22       ` Hans Hagen
2008-07-30  8:23         ` Matthias Wächter
2008-08-05 10:56           ` Matthias Wächter
2008-08-05 16:37             ` Hans Hagen
2008-08-05 16:44               ` Matthias Wächter
2008-08-05 16:48                 ` Hans Hagen
2008-08-05 17:14                   ` Matthias Wächter
2008-08-05 20:48                     ` Hans Hagen [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=4898BCAC.7080705@wxs.nl \
    --to=pragma@wxs.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).