user-pic

Max Maischein

  • Website: corion.net
  • About: I'm the author of various CPAN modules. I'm also one of the admins of perlmonks.org.
Subscribe to feed Recent Actions from Max Maischein

  • YAPC::Europe 2012 commented on No Accepted Perl 6 Talks at YAPC::EU 2012?

    What happened

    While choosing the talks, we voted on them to select each batch. This had the two-fold
    effect of only choosing the talks by majority vote ("All sports on TV are football")
    and also not having a close mental image of what (kinds of) talks had been accepted
    in the previous voting rounds and which were still in the hat. This unintentionally
    led to no Perl 6 talks being accepted.

    What we did

    As we did not want to reject speakers that we already accepted, we added a fourth track
    to make some more slots available in addition to th…

  • https://www.google.com/accounts/o8/id?id=AItOawlKCInGw3AtPhoc4NBTcIFE1ggZxSjXMXY commented on Unicode is 20++ years old and still a problem

    You can workaround and find any file with File::Find. Just convert file/dir names to/from bytes before/after passing to file::find.

  • xdg commented on Unicode is 20++ years old and still a problem

    How is File::Find supposed to know how file names are encoded on your particular filesystem? (Hint: not all filesystems store names as UTF-8 Unicode.)

    That said, I don't see what Text::CSV::Slurp is doing to filenames that would cause a problem. If it gets octets from File::Find, it looks like it's passing them right back to an open call.

    It's not opening files in UTF-8 mode, but that's sort of a separate problem.

  • Helmut Wollmersdorfer commented on Unicode is 20++ years old and still a problem

    How is File::Find supposed to know how file names are encoded on your particular filesystem?

    File::Find could guess the encoding via e.g. Encode::Locale with an accuracy of 99.99%. Of course the sanity must be checked during decoding, because Posix handles only bytes.

    Each module importing strings from an external representation should take care of the correct decoding, or as a minimum should document and warn about its limitations.

    That said, I don't see what Text::CSV::Slurp is doing to filenames that would cause a problem.

    I used Text::CSV::Slurp only to s…

  • vsespb commented on Unicode is 20++ years old and still a problem

    > File::Find could guess the encoding via e.g. Encode::Locale with an accuracy of 99.99%.

    So you want it to be broken by design, and write/read garbage from filesystems in some cases?
    Filesystem encodings never should not be detected with locale !
    Your proposed design leads to data loss.

Subscribe to feed Responses to Comments from Max Maischein

About blogs.perl.org

blogs.perl.org is a common blogging platform for the Perl community. Written in Perl and offering the modern features you’ve come to expect in blog platforms, the site is run by Dave Cross and Aaron Crane, with a design donated by Six Apart, Ltd.