Re: require fails when requiring scripts with utf-8 filenames.



Daniel Jonson wrote:
Any suggestions? isnt utf-8 filenames supported? surely it must be?

Who knows? If you can find an official spec for how Strings work in ruby
1.9, I'd love to see it. So far what I've managed to reverse-engineer
I've documented here:
http://github.com/candlerb/string19/blob/master/string19.rb

How 'require' is influenced by string encoding I've not tested. It seems
to me the logical thing would be to treat filenames as just strings of
bytes (as the OS does), but as I say, who knows.
--
Posted via http://www.ruby-forum.com/.

.



Relevant Pages

  • Re: Fizz Buzz Zoom
    ... data structure, and the code takes care of itself"). ... one or more of the strings is empty. ... s" Fizz" record spec add!: ...
    (comp.lang.forth)
  • Re: IEEE-FP 0.5.3
    ... >> The DPANS94 specification is extended to include IEEE ... >> The IEEE extension of REPRESENT aims to change the DPANS94 ... There is nothing in the spec ... > strings for nan/inf or the values for n2, ...
    (comp.lang.forth)
  • Re: XML_RPC and unicode problems
    ... >> strings it transfers are unicode and thusly tries to do conversions on ... >> unicode conversions, or is there some way for me to just pass raw data ... spec which simply removed a previous reference to ASCII: ...
    (comp.lang.python)
  • Re: Suggested coding style
    ... The whole point of zfill is that it handles signs correctly. ... Use the d format for integers and the ... strings transparently then you need to lobby to have the API changed. ... the spec works just fine as is. ...
    (comp.lang.python)
  • Re: #to_b - why isnt this one already in there?
    ... in a constructor which takes a hash. ... set of Strings - with a few additional values merged in. ... common in Ruby to use a hash as a substitute for keyword arguments to ... I think the reason it's not part of the language is that you ...
    (comp.lang.ruby)