H. Peter Anvin writes: > I would say this isn't really a good idea... a BOM isn't > meaning-neutral, so if you're converting pieces of text and end up > adding BOMs in the middle, you have changed the meaning. Certainly, yes. The one who chooses to convert anything to UTF-16 should know about this; and this is why the RFC is explicit about it. The RFC also says that you can avoid the BOM problem by using UTF-16LE and UTF-16BE instead of UTF-16. Bruno - Linux-UTF8: i18n of Linux on all levels Archive: http://mail.nl.linux.org/lists/
- iconv output utf-8 -> utf-16, which one is wrong? etrapani
- Re: iconv output utf-8 -> utf-16, which one i... Mark Leisher
- Re: iconv output utf-8 -> utf-16, which one i... Edmund GRIMLEY EVANS
- Re: iconv output utf-8 -> utf-16, which o... Mark Leisher
- RE: iconv output utf-8 -> utf-16, which one i... Karlsson Kent - keka
- Re: iconv output utf-8 -> utf-16, which one i... Bruno Haible
- Re: iconv output utf-8 -> utf-16, which o... Ulrich Drepper
- Re: iconv output utf-8 -> utf-16, which one i... H. Peter Anvin
- Re: iconv output utf-8 -> utf-16, which one i... Bruno Haible
- Re: iconv output utf-8 -> utf-16, which one i... Mark Leisher
- Re: iconv output utf-8 -> utf-16, which o... Jean-Marc Desperrier
- Re: iconv output utf-8 -> utf-16, which one i... H. Peter Anvin
- Re: iconv output utf-8 -> utf-16, which one i... Bruno Haible
- Re: iconv output utf-8 -> utf-16, which one i... H. Peter Anvin
- Re: iconv output utf-8 -> utf-16, which one i... Edmund GRIMLEY EVANS
- Re: iconv output utf-8 -> utf-16, which o... Bruno Haible
- Re: iconv output utf-8 -> utf-16, which o... H. Peter Anvin
