You misunderstood the situation. The victims of the problem never intended to use locale information in any way in their scripts, and the scripts were not written to use locale information.

Can you point me to this problem? Seems, i don't understand it throughly. My problem is that i can't rely on system locale even i use locale pragma. As far i understand, those victims were dependent of their system locale even without using locale pragma? Was it like this?

I agree, that such behaviour will break earlier code and such move needs long time to adapt before any deprecation (if needed). I need the middle way: locale does not spread without using pragma, but when using it, it should flawlessly spread.

Nġnda, WK

In reply to Re^4: Pragma to handle unicode characters by wanradt
in thread Pragma to handle unicode characters by wanradt

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.