From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Natural tables introduces spaces in \type
Date: Thu, 06 Nov 2014 09:58:44 +0100 [thread overview]
Message-ID: <545B3844.5000907@wxs.nl> (raw)
In-Reply-To: <CAO8LnPGcJ=9B1P8ThT0U5HJDfMH+FREZDDcgu_-p20xGmfScXQ@mail.gmail.com>
On 11/5/2014 9:50 PM, Christoph Reller wrote:
> On 11/5/2014 10:28 AM, Hans Hagen wrote:
> > On 11/5/2014 8:09 AM, Christoph Reller wrote:
> > > Thank you very much Hans!
> > >
> > > Maybe you could tell me why the following still produces a space in
> > > front of the full stop:
> > >
> > > \definetype[ctype][compact=absolute]
> > > \starttext
> > > \bTABLE
> > > \bTR \bTD \ctype{\test.txt} \eTD \eTR
> > > \eTABLE
> > > \stoptext
> >
> > because the absolute cleaner only deals with \foo { and \foo [
> >
> > > If this issue is resolved I will be glad to wikify.
> >
> > i'll add the . to the filter criteria
>
> Thank you for the explanation. I am not sure if it is a wise idea to
> add only "." (the full stop). I tried the following characters, and
> they all are preceded by a space:
>
> . - _ # % , ; @ !
>
> Basically, what I want is to write a file system path name such as
> C:\Path_to-my\file.ext. The above characters are all valid file system
> characters. Is there a better solution? Or are you willing to add all
> the above (maybe except for # and %) to the absolute cleaner?
we could have a specific filename cleaner but of course there will be
users who have paths that have spaces after the \ ... okay, we could
just not support evil paths like that
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 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 : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2014-11-06 8:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 20:50 Christoph Reller
2014-11-06 8:58 ` Hans Hagen [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-11-19 21:43 Christoph Reller
2014-11-07 13:44 Christoph Reller
2014-11-10 7:18 ` Keith Schultz
2014-11-06 15:15 Christoph Reller
2014-11-07 8:11 ` Alan BRASLAU
2014-11-05 7:09 Christoph Reller
2014-11-05 9:28 ` Hans Hagen
2014-11-03 12:47 Christoph Reller
2014-11-02 13:27 Christoph Reller
2014-11-02 13:54 ` Hans Hagen
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=545B3844.5000907@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).