[Bug 1026763] New: Locale::Maketext interpolating escaped backslashes improperly
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1026763
Bug ID: 1026763
Summary: Locale::Maketext interpolating escaped backslashes
improperly
Product: Fedora
Version: 18
Component: perl-Locale-Maketext
Assignee: ppisar(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: eggled(a)gmail.com, perl-devel(a)lists.fedoraproject.org,
ppisar(a)redhat.com, psabata(a)redhat.com
External Bug ID: CPAN 120457
+++ This bug was initially created as a clone of Bug #1025906 +++
Description of problem:
When a literal backslash is in an L10N value, it is treated nonuniformly by the
Locale::Maketext::_compile method, as patched by RH in Locale::Maketext::Guts
(per https://bugzilla.redhat.com/show_bug.cgi?id=884354). The result depends
on unrelated parts of the string.
[...]
How reproducible:
Always
Steps to Reproduce:
1. Create a language token, whose value is 'Some data\n'
2. Query the language token through Locale::Maketext ($lh->maketext($tag))
Actual results:
'Some data\\n'
Expected results:
'Some data\n'
Additional info:
The behavior changes in the following cases:
1) If the value contains a tokenized field, behavior depends on whether there
is a trailing newline:
'[_1]Some data\n' => 'Some data\n'
'[_1]Some data\n'."\n" => 'Some data\\n
'
2) If the escaped backslash is in a function call, it behaves as expected:
'Some data[sprintf,\n]' => 'Some data\n'
NOTE: All of these cases in standard perl (with Locale::Maketext v 1.13 from
CPAN) behave exactly the same as each other, and they all produce just a single
'\' before the 'n'.
--- Additional comment from Petr Pisar on 2013-11-04 12:16:19 GMT ---
The 'Some data\n' is due to back-porting the fix to perl 5.10.1.
The parameterized case behaves for me differently and is caused by the changes
in the fix. Even latest Locale::Maketext is affected.
----
All Fedoras are affected.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=BtlUasPZ1z&a=cc_unsubscribe
9 years, 10 months
[Bug 1048703] New: Module::Pluggable ignores single-letter-named package names
by Red Hat Bugzilla
https://bugzilla.redhat.com/show_bug.cgi?id=1048703
Bug ID: 1048703
Summary: Module::Pluggable ignores single-letter-named package
names
Product: Fedora
Version: 20
Component: perl-Module-Pluggable
Assignee: ppisar(a)redhat.com
Reporter: ppisar(a)redhat.com
QA Contact: extras-qa(a)fedoraproject.org
CC: perl-devel(a)lists.fedoraproject.org, ppisar(a)redhat.com
External Bug ID: CPAN 89680
Having two files:
$ cat M.pm
print join(',', M->plugins), "\n";
package M;
use Module::Pluggable search_path => [ 'M' ];
$ cat M/X.pm
package M::X;
1;
`perl M.pm' should locate M::X plug-in and print the name to standard output
like this:
$ perl -I/home/petr/Module-Pluggable/lib M.pm
M::X
However it does not.
This issue has been reported to upstream
<https://rt.cpan.org/Public/Bug/Display.html?id=89680> and fixed in commit:
commit 7872bc27ac7f828a6b53d00717abdf83f2d1866d
Author: Simon Wistow <simon(a)fastly.com>
Date: Tue Oct 22 09:32:27 2013 -0700
Allow single letter package names
All Fedoras with perl-Module-Pluggable < 5.00 are affected.
--
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=b6247j23hp&a=cc_unsubscribe
9 years, 10 months