From: Tom Link Date: 2009-02-05T17:17:40+09:00 Subject: [ruby-core:21852] [Feature #1106] Script encoding vs. default_internal: Implicitly transcode strings/regexps Issue #1106 has been updated by Tom Link. Thanks for the summary. I'm not really sure what problem the current solution is supposed to solve but it's not mine to question it. IMHO ruby should inform users about such conflicts or simply throw an error. Currently, ruby --verbose shows a warning message telling users that default_(in|ex)ternal was set. This message could be more informative. Also, it doesn't cover cases where default_internal wasn't set but two scripts have different encodings != ASCII. I think additional warning messages should be displayed when a source file's encoding doesn't match default_internal or if the script encodings are heterogenous (number of encodings != ASCII >= 2). ---------------------------------------- http://redmine.ruby-lang.org/issues/show/1106 ---------------------------------------- http://redmine.ruby-lang.org