Mark Leisher wrote: > Bruno> Certainly, yes. The one who chooses to convert anything to UTF-16 > Bruno> should know about this; and this is why the RFC is explicit about > Bruno> it. The RFC also says that you can avoid the BOM problem by using > Bruno> UTF-16LE and UTF-16BE instead of UTF-16. > > We don't specifically use UTF-16LE and UTF-16BE. That requires knowing the > endian order a priori or requires some form of markup (out-of-band info). The RFC is talking about the case where you have OOB info, for example MIME headers. - 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
