From: Christoph Reller <christoph.reller@gmail.com>
To: ntg-context <ntg-context@ntg.nl>
Subject: Re: Natural tables introduces spaces in \type
Date: Thu, 6 Nov 2014 16:15:36 +0100 [thread overview]
Message-ID: <CAO8LnPGTs3+jr7O2JEcxcG32dvFiLfM6p3fBWX13G0oGwJkYJg@mail.gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 991 bytes --]
On 11/6/2014 9:58 AM, Hans Hagen wrote:
> 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
A rigorous filename cleaner would have to treat a huge number of possible
Unicodes. This is overkill. I believe the best would be to have a cleaner
for all ascii "symbols". That would fit most purposes of writing file names
and URIs:
!#"$%&'*()+,-./:;<=>?@[\]^_`{|}~
Of the above characters the following are disallowed on NTFS:
"*/:<>?|
Still I think they should be included in the cleaner. If % or # pose
problems then they may be omitted.
With the current "absolute"-cleaner, a space after \ is preserved
correctly, so I don't understand your comment:
\definetype[ctype][compact=absolute]\starttext
\bTABLE\bTR\bTD \ctype{\a\ b} \eTD\eTR\eTABLE\stoptext
I would be glad if you could implement such a "ascii-symbol"-cleaner.
Thanks,
Christoph
[-- Attachment #1.2: Type: text/html, Size: 1424 bytes --]
[-- Attachment #2: Type: text/plain, Size: 485 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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
next reply other threads:[~2014-11-06 15:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-06 15:15 Christoph Reller [this message]
2014-11-07 8:11 ` Alan BRASLAU
-- 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-05 20:50 Christoph Reller
2014-11-06 8:58 ` Hans Hagen
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=CAO8LnPGTs3+jr7O2JEcxcG32dvFiLfM6p3fBWX13G0oGwJkYJg@mail.gmail.com \
--to=christoph.reller@gmail.com \
--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).