+++ This bug was initially created as a clone of Bug #1026763 +++ +++ 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. ---- F < 20 bundled Locale::Maketext in perl.
Created attachment 822380 [details] Upstream fix ported to perl-5.16.3
perl-5.16.3-266.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/perl-5.16.3-266.fc19
perl-5.16.3-245.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/perl-5.16.3-245.fc18
perl-5.16.3-266.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report.
perl-5.16.3-245.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.