|
From: | James Youngman |
Subject: | [bug-enscript] [bug #57965] the wildcard * for input files daes not work properly? |
Date: | Mon, 31 May 2021 10:18:47 -0400 (EDT) |
User-agent: | Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36 |
Follow-up Comment #9, bug #57965 (project enscript): I agree that it looks like this problem is not caused by the shell's wildcard expansion. In your newest example, it also seems to me that the file f.f is not included at all. IMO that's a bit worse than just duplicate output. I wonder if this is a problem in enscript which is only happening in cases where the locale settings have some particular property. This might be affected for example by your environment setting LC_CTYPE=es_ES.UTF-8 or by which locale data files are actually built on your system. Are you able to reproduce the problem with your locale set up for a different locale? My guess is that the enscript code is most well-tested in the C locale and some English-language US-centric locale. Try this config for example (it's not the same as my config though): $ env LANG=en_US.utf8 LANGUAGE=en_US:en LC_ALL=en_US.utf8 bash $ locale LANG=en_US.utf8 LANGUAGE=en_US:en LC_CTYPE="en_US.utf8" LC_NUMERIC="en_US.utf8" LC_TIME="en_US.utf8" LC_COLLATE="en_US.utf8" LC_MONETARY="en_US.utf8" LC_MESSAGES="en_US.utf8" LC_PAPER="en_US.utf8" LC_NAME="en_US.utf8" LC_ADDRESS="en_US.utf8" LC_TELEPHONE="en_US.utf8" LC_MEASUREMENT="en_US.utf8" LC_IDENTIFICATION="en_US.utf8" LC_ALL=en_US.utf8 $ (try to reproduce the problem here) _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?57965> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |