Convert file from UTF8 (no BOM) to UTF16 (with BOM)

recode UTF8..UTF-16LE linux-utf8-file.txt
Convert file from the UTF8 encoding used on Linux (has no "EF BB BF" byte order mark at the start) to the UTF-16 encoding used on Windows (has an "FF FE" byte order mark at the start). Thanks to commenter: previous iconv command was the obsolete way to do it.

0
By: greppo
2009-06-04 08:53:51

What Others Think

That seems overly complicated. I prefer recode: recode utf8..utf16 <in.txt >out.txt That command does the same, producing UTF16 with BOM in big-endian byte order. If you need little-endian byte order, simply append "/s" (meaning "swap bytes"): recode utf8..utf16/s <in.txt >out.txt
inof · 527 weeks ago

What do you think?

Any thoughts on this command? Does it work on your machine? Can you do the same thing with only 14 characters?

You must be signed in to comment.

What's this?

commandlinefu.com is the place to record those command-line gems that you return to again and again. That way others can gain from your CLI wisdom and you from theirs too. All commands can be commented on, discussed and voted up or down.

Share Your Commands



Stay in the loop…

Follow the Tweets.

Every new command is wrapped in a tweet and posted to Twitter. Following the stream is a great way of staying abreast of the latest commands. For the more discerning, there are Twitter accounts for commands that get a minimum of 3 and 10 votes - that way only the great commands get tweeted.

» http://twitter.com/commandlinefu
» http://twitter.com/commandlinefu3
» http://twitter.com/commandlinefu10

Subscribe to the feeds.

Use your favourite RSS aggregator to stay in touch with the latest commands. There are feeds mirroring the 3 Twitter streams as well as for virtually every other subset (users, tags, functions,…):

Subscribe to the feed for: