[Bug 433260] [NEW] par2 cannot work with special characters

[ricardisimo]

Public bug reported:

Binary package hint: par2

Whether working with gpar2, pypar2 or the KDE variant (all of which rely
on par2) any files with special characters - á, é, í, ó, ú, ç, ñ, etc. -
are invisible to their corresponding parity files; par2 cannot see that
they are present at all, much less read their contents. We have been
looking for the source of the problem in this thread:

http://ubuntuforums.org/showthread.php?p=7975747

And someone discovered and posted the following:

"Yep, the PAR 1.0 spec definitely uses UTF-16 (although it does not make
that clear).

I've just had a quick look at the PAR 2.0 and I see that the main part
of the spec refers to ASCII (which is actually meaningless). The correct
current name for what used to be known as ASCII is US-ASCII (which is a
7-bit character set).

par2cmdline and QuickPar treat the filename as 8-bit but leave it up to
the OS to decide what character encoding is being used. When QuickPar
accesses a file, the filename is treated as ANSI using whatever code
page is currently selected as the default.

In the optional part of the PAR 2.0 spec where unicode is referred to,
it gives no indication at all as to what encoding is used. I would
assume that UTF-16 is intended."

This is not a minor issue, as it affects an infinite number of real and
possible files from Spanish, French, German, and any of the Western
languages outside of the US and UK. The problem renders their parity
files useless.

I thank you for any attention you can give to this problem.

** Affects: par2cmdline (Ubuntu)
     Importance: Undecided
         Status: New

-- 
par2 cannot work with special characters
https://bugs.launchpad.net/bugs/433260
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs