public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: BPJ <melroch-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc 3.1.2 does not expand file names correctly
Date: Thu, 27 Jul 2023 12:36:31 +0200	[thread overview]
Message-ID: <CADAJKhBmdnJc7J3803mV3dq-Acng_sQ++nGwoKX09LVWHYgMEQ@mail.gmail.com> (raw)
In-Reply-To: <62484f9c-7ab2-f8f4-f1d6-31bd8fc4bde8-FcZObrvlYduBUy7/sJONFg@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 3453 bytes --]

The safest practice is in any case not to use non-ASCII characters (nor
spaces) in file names, since above-ASCII characters are not portable
between encodings, and different operating systems may use different
encodings. If you are interested I have a Perl script which does its best
to customizably 'transliterate' filenames between other encodings (UTF-8 by
default) and ASCII, and rename files, adding a unique number in case of
conflicts in the resulting names. It can also create or add to a YAML file
mapping between transliterated names and original names, and has a mode for
'reverting' names. It does by default back up files under their original
files into a directory of your choice (by default 'renamed-TIMESTAMP' in
the current directory.)

/bpj

Den ons 26 juli 2023 02:03H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org> skrev:

> On 07/18/2023 10:08 PM, H wrote:
> > On July 18, 2023 10:06:41 PM EDT, H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org> wrote:
> >> On July 18, 2023 7:22:40 PM EDT, John MacFarlane
> >> <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
> >>> I'm not sure what you mean by "expand file names."
> >>> Are you talking about tab-completion?  That is not done by pandoc but
> >>> by the shell.
> >>>
> >>>> On Jul 18, 2023, at 3:49 PM, H <agents-FcZObrvlYduBUy7/sJONFg@public.gmane.org> wrote:
> >>>>
> >>>> Running 3.1.2 on CentOS7 and found that the CLI does not expand file
> >>> names correctly. It fails to expand file names containing 'ä' -
> >>> possibly others as well that I have not tested.
> >>>> Is this a known bug?
> >>>>
> >>>> --
> >>>> You received this message because you are subscribed to the Google
> >>> Groups "pandoc-discuss" group.
> >>>> To unsubscribe from this group and stop receiving emails from it,
> >>> send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >>>> To view this discussion on the web visit
> >>>
> https://groups.google.com/d/msgid/pandoc-discuss/2b0984b1-a157-eb8a-0e1e-8f10c4d8473e%40meddatainc.com
> .
> >> Yes, you are correct, tab-completion. It works correctly outside
> >> pandoc.
> > Let me double-check tomorrow to make sure.
>
> I had reason to use pandoc again today and could verify that when a
> filename contains 'ä' tab-completion works when used /ahead/ of this
> character but not when used /after/ the character /up until '_' occurs in
> the filename/.
>
> ls -al works correctly even when pandoc fails above.
>
> Can anyone else confirm problems with tab-completion?
>
> --
> You received this message because you are subscribed to the Google Groups
> "pandoc-discuss" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/62484f9c-7ab2-f8f4-f1d6-31bd8fc4bde8%40meddatainc.com
> .
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/CADAJKhBmdnJc7J3803mV3dq-Acng_sQ%2B%2BnGwoKX09LVWHYgMEQ%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 5196 bytes --]

      parent reply	other threads:[~2023-07-27 10:36 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-18 22:49 H
     [not found] ` <2b0984b1-a157-eb8a-0e1e-8f10c4d8473e-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-18 23:22   ` John MacFarlane
     [not found]     ` <63A5017C-517E-4202-8360-23F1C06B30BF-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-19  2:06       ` H
     [not found]         ` <FAC4F510-40C1-46BC-9C4B-0DA764A0062D-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-19  2:08           ` H
     [not found]             ` <61856054-B9CF-4BA3-B541-803C0DF78D00-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-19 14:27               ` jcr
2023-07-26  0:02               ` H
     [not found]                 ` <62484f9c-7ab2-f8f4-f1d6-31bd8fc4bde8-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-26 18:02                   ` John MacFarlane
     [not found]                     ` <3846738C-261F-40DC-9D74-E697852A89DB-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2023-07-27 15:57                       ` H
     [not found]                         ` <4ce9e402-9591-9b4c-19b7-be614af62b00-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-27 16:34                           ` Bastien DUMONT
2023-07-27 16:48                             ` 'William Lupton' via pandoc-discuss
     [not found]                               ` <CAEe_xxiDLUsDBP=1S6jrY4Tb9AAXZTQWPdcJyCa12mXF3DiQAg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-27 17:15                                 ` H
     [not found]                                   ` <e9dc67e5-1614-d5e4-ca90-0509c9d02397-FcZObrvlYduBUy7/sJONFg@public.gmane.org>
2023-07-27 18:39                                     ` 'William Lupton' via pandoc-discuss
     [not found]                                       ` <CAEe_xxgs5B7h8W8tOcHvvA=oT=mBtFKSxGhxsXfJRAHtKJ2VXw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-07-27 19:25                                         ` H
2023-07-27 10:36                   ` BPJ [this message]

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=CADAJKhBmdnJc7J3803mV3dq-Acng_sQ++nGwoKX09LVWHYgMEQ@mail.gmail.com \
    --to=melroch-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /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).