Re: [SLE] easy way to enter this symbol:￥

On Saturday 30 September 2006 19:29, Jan Engelhardt wrote:
I copied the characters into a text file (kate), saved it as a
utf-16 file, opened it with Midnight Commander (mc) using 'View'
(F3), and I could discover the 16-bit unicode numbers.

Midnight Commander does not support UTF-16. So it's all UTF-8,
including Kate.

I was viewing in HEX mode. That's not utf-16 nor utf-8. :P

Cheers,

Leen

--
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@xxxxxxxx
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@xxxxxxxx

Relevant Pages

  • Re: Unicode string libraries
    ... encoding negotiation. ... old languages which have adopted Unicode without much pain. ... compatibility with too many old programs; but char as a holder for UTF-8 ... The limitations of UTF-16 ...
    (comp.programming)
  • Re: Case-sensitivity as option?
    ... Code points beyond 0x10FFFF cannot be encoded with UTF-16, ... it is unlikely that Unicode will ... Windows to UTF-8. ... encode them with normal surrogates. ...
    (comp.lang.forth)
  • Re: unicode in ruby
    ... doesn't support unicode strings natively? ... put on Unix ages ago. ... (When Unix filesystems can write UTF-16 as ... translate to UTF-8 and/or follow the nonsensical POSIX rules for native ...
    (comp.lang.ruby)
  • Re: AfxMessageBox?
    ... except that unfortunately there are now surrogate pairs in UTF-16. ... This means that any program that does string manipulation assuming each wchar_t is a single character is technically incorrect, ... Microsoft 16-bit "Unicode" no longer has the advantage that motivated its creation. ... I confess that one reason I like UTF-8 is that is backward compatible with code that assumed all ASCII characters. ...
    (microsoft.public.vc.mfc)
  • Re: Unicode Delphi Win32 - which approach
    ... I like the backwards compatibility aspects of UTF-8 vs UTF-16. ... UTF-8 encoding is different from ANSI, at least it's still byte oriented ... encoding, programmers will be forced to "think" Unicode, and not ...
    (borland.public.delphi.non-technical)