ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Otared Kavian <otared@gmail.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: \setvariables and database module
Date: Tue, 30 Jan 2018 18:56:06 +0100	[thread overview]
Message-ID: <6D845BC3-FD8A-4877-B6CD-00D715241AB0@gmail.com> (raw)
In-Reply-To: <5A709F5D.9000108@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1053 bytes --]

> On 30 Jan 2018, at 17:37, Wolfgang Schuster <schuster.wolfgang@gmail.com> wrote:
> 
>> […]
>> Is there a way to make the \defineseparatedlist command to be more tolerant for the filename? 
>> 
> No but you can remove the space with Lua.
> 
> \externalfigure[\cldcontext{string.collapsespaces("\getvariable{talk}{picture}")}]
> 

Thanks again! That does it.

However, it seems strange that the \externalfigure command does not accept a space in front of the file name nor after the file extension, while \input is very tolerant in that respect. Compare

\input   knuth.tex   
\input knuth.tex
\input{knuth.tex}

which are all accepted, while when there is a space after the extension,

\startplacefigure[number=no]
	\externalfigure[hacker.jpg ]
\stopplacefigure

or a space before the filename 

\startplacefigure[number=no]
	\externalfigure[ hacker.jpg]
\stopplacefigure

then ConTeXt does not recognize the file…
Maybe Hans has a reason to explain this behavior, but it is not clear to me.

Best regards: OK



[-- Attachment #1.2: Type: text/html, Size: 2866 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
___________________________________________________________________________________

  reply	other threads:[~2018-01-30 17:56 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-30 14:44 Otared Kavian
2018-01-30 14:54 ` Wolfgang Schuster
2018-01-30 15:28   ` Otared Kavian
2018-01-30 15:53     ` Otared Kavian
2018-01-30 16:37       ` Wolfgang Schuster
2018-01-30 17:56         ` Otared Kavian [this message]
2018-01-30 18:05           ` Wolfgang Schuster
2018-01-30 18:18             ` Otared Kavian
2018-01-31 16:40       ` Wolfgang Schuster
2018-01-31 16:58         ` Otared Kavian
2018-01-31 17:11           ` Wolfgang Schuster
2018-01-31 21:20             ` Otared Kavian
2018-02-02  0:47               ` luigi scarso

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=6D845BC3-FD8A-4877-B6CD-00D715241AB0@gmail.com \
    --to=otared@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).