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

On Saturday 30 September 2006 10:54, Leendert Meyer wrote:
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

That's not really a meaningful statement.

UTF-8 and UTF-16 are ways of encoding Unicode codepoint values in a data
stream or file. You could take a file holding UTF-16 (or -8) -encoded
text and view it as binary or octal or decimal or hexadecimal octets,
or as 16-bit numbers, likewise of any numeric radix of your choosing,
and it would still be UTF-16 (or -8) -encoded Unicode text you were
viewing.


Leen


Randall Schulz

--
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: 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)
  • Re: unicode in ruby
    ... doesn't support unicode strings natively? ... (When Unix filesystems can write UTF-16 as ... to use decomposed characters instead of composed characters (e.g., ... even compress repetitive text which no encoding can. ...
    (comp.lang.ruby)
  • 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)