[ruby-core:85839] [Ruby trunk Bug#14127][Rejected] (CSV) generating UTF-16LE encoded file without BOM

Issue #14127 has been updated by kou (Kouhei Sutou).

Status changed from Assigned to Rejected

nobu almost said.

You should write BOM by yourself when you use `CSV.generate`.

If you don't want to write BOM by yourself, you should use `CSV.open(..., "w:UTF-16")`:

```ruby
CSV.open("utf16.csv", "w:UTF-16:utf-8") do |csv|
  csv << ['something', 'トセナ。ト最・ナセテステ。テュテゥ']
end
```

But it generates big-endian UTF-16.


----------------------------------------
Bug #14127: (CSV) generating UTF-16LE encoded file without BOM
https://bugs.ruby-lang.org/issues/14127#change-70698

* Author: laykou (Ladislav Gallay)
* Status: Rejected
* Priority: Normal
* Assignee: kou (Kouhei Sutou)
* Target version: 
* ruby -v: 2.4.1
* Backport: 2.3: UNKNOWN, 2.4: UNKNOWN
----------------------------------------
This file should contain BOM information so that it is properly detected as UTF-16LE file.

How to generate such file:

~~~ruby
file = CSV.generate(encoding: 'UTF-16LE') do |csv|
    csv << ['something', 'トセナ。ト最・ナセテステ。テュテゥ']
end
~~~

According to `file -I file.csv` this file is recognized as `application/octet-stream; charset=binary` because it is missing the BOM information.

According to Wikipedia https://en.wikipedia.org/wiki/UTF-16 it should contain "\xFF\xFE" on the beginning of the document so that everyone knows iths UTF-16LE.

Here is someone trying to fix this in the similiar way: https://stackoverflow.com/a/22950912/1632815 I did it: manually adding that BOM information.

~~~ ruby
## Adds BOM, albeit in a somewhat hacky way.
new_html_file = File.open(foo.txt, "w:UTF-8")
new_html_file << "\xFF\xFE".force_encoding('utf-16le') + some_text.force_encoding('utf-8').encode('utf-16le')
~~~




-- 
https://bugs.ruby-lang.org/

Unsubscribe: <mailto:[e-mail]?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-core>