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: LMTX: Space in file names
Date: Mon, 19 Aug 2019 23:07:01 +0200	[thread overview]
Message-ID: <7F29C4C5-AF09-4E48-9A52-13E3C0A59766@gmail.com> (raw)

Hi Hans,

I noticed that the lmtx beta from 2019.08.18 22:27 does not anymore accept spaces in file names, while the mkiv version does accept it.
I am aware that putting a space in a file name is a very bad habit, but I am convincing some people who were used to use MS Word in order for them to use ConTeXt, and these people have many files with names containing spaces such as « correction problème 1.tex » (and in fact this is how I noticed this new behavior of lmtx: when typesetting such a file, lmtx looks for « correction.tex »). 
That is why I think if lmtx could continue to accept spaces in file names that would be very convenient. Do you think this would be possible?

Best regards: OK

___________________________________________________________________________________
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:[~2019-08-19 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-19 21:07 Otared Kavian [this message]
2019-08-19 22:01 ` Hans Hagen
     [not found]   ` <B5B499B5-CD07-4D94-B0CB-474304F3ADF0@gmail.com>
     [not found]     ` <884b9fb5-e2a1-db40-ecf2-a4b6445f4c20@xs4all.nl>
     [not found]       ` <6638461A-B9F2-490F-A93D-3BCA6C285718@gmail.com>
     [not found]         ` <48aba6d9-67e2-1e36-5a68-ba72f6827e8d@xs4all.nl>
2019-08-20 14:17           ` Otared Kavian

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=7F29C4C5-AF09-4E48-9A52-13E3C0A59766@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).