Re: Par2cmdline with non normal characters.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 14May2016 22:45, Robin Laing <MeSat@xxxxxxxxxxxxxxx> wrote:
On 14/05/16 21:55, cs@xxxxxxxxxx wrote:
However, there is a way out. Get your error message above into your
terminal, specificly by running your command again to ensure it is
exact. Then use cut/paste in your terminal to effect 4 mv commands. So,
like this:

mv *.part01.rar '<paste-filename-1-from-the-error-message-here>'

so you're:
- using the shell to match the _current_ first file with *.part01.rar
- you are typing a single quote, then pasting the filename from the
error    message, then another single quote

Provided the desired filenames' quote _is_ an apostrophe and not an
ASCII single quote, you should be ok here. This is because your terminal
has transcribed the error string from par2, and hopefully that will be
usable.

This avoids figuring out how to type a weird filename.
[...]
Well done Cameron.  Thank you.
Moving the files did help. I don't know why I didn't try that before. With everything else going on today, it must of slipped my mind. I started going in circles. I know I tried to move the files late last night but not with the paste like you suggested.

The advantage of the paste is that par2 has recited the filenames for you to your terminal, so cut/paste gets to pick them up again verbatim in whatever encoding is in play.

BTW, with the locale the utf-8 bit is what matters for this: it dictates how character codepoints are encoded when written to your terminal and, for locale aware apps, how they are encoded when filename bytes are generated. It also ditates how things like "ls" decode those bytes and decide what is printable or otherwise.

The .en-ca stuff is for higher level conventions like language, regional dictionaries, currency symbols, number separators and so forth.

This will go in my notes for future reference if it happens again.

It is funny that the par2 program had no problem seeing the repair volume files with the glyph but couldn't see the rar files with the glyph.

Is it possible you handed par2 the names of the repair files on the command line, but that par2 was getting the rar filenames from the metadata?

Cheers,
Cameron Simpson <cs@xxxxxxxxxx>
--
users mailing list
users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe or change subscription options:
http://lists.fedoraproject.org/admin/lists/users@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct
Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines
Have a question? Ask away: http://ask.fedoraproject.org



[Index of Archives]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [EPEL Devel]     [Fedora Magazine]     [Fedora Summer Coding]     [Fedora Laptop]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Desktop]     [Fedora Fonts]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Yosemite News]     [Gnome Users]     [KDE Users]     [Fedora Art]     [Fedora Docs]     [Fedora Sparc]     [Libvirt Users]     [Fedora ARM]

  Powered by Linux