Message Area
Casually read the BBS message area using an easy to use interface. Messages are categorized exactly like they are on the BBS. You may post new messages or reply to existing messages!

You are not logged in. Login here for full access privileges.

Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page
   Networked Database  Linux operating system (OS), a U...   [745 / 900] RSS
 From   To   Subject   Date/Time 
Message   Holger Granholm    Maurice Kinal   Re: Character codes   March 10, 2019
 4:15 PM *  

In a message on 03-05-19 Maurice Kinal said to Holger Granholm:

Hello Maurice,

Excuse the delay. I was in Stockholm, Sweden for the Boat Show.

 HG> OK, the code 218 128 162 that i interpreted as hyphen actually
 HG> is the longer 'dash'.

MK> I am not sure what you mean but using 218 (DA) as the leading byte
MK> means you are restricted to a 2 byte or 16 bit character and not a
MK> 24 bit character that is required for euro sign in utf8.  The way
MK> the leading byte works is like this;

I understand, but this is how the UTF codes are represented in PC8,
= 8bit ASCII, and I have come to the conclusion that I will, at least
try, to use only the two following bytes in the translation table.

That may be all that is needed but if not, I can always include the
leading byte. Kind of cut and try <BG>.

MK> The first zero shows that there are two leading ones which means
MK> there is only one trailing byte following.

MK> So that means either 218 128 and 162 is ignored.

MK> For the utf8 euro character the prefix is;

MK> dec 226 = bin 11100010
MK>                  ^

According to my interpretation of how the chracter is presented in PC8
it's  as 218 130 172. All normal umlaut characters are presented with
only two bytes, like 195 165 for the small angstrom character that is
included in your "Moose" tagline.

MK> and as you can see the first zero yields three leading ones which is
MK> three bytes or 24 bits.

I don't need more than 16-bit characters for that editor.
UTF characters ARE presented with two bytes in it.

MK> For the record 218 128 is U+0680 which we already know to be a 16
MK> bit Arabic character.

That third byte (first 218 or 226) comes only as a prefix for other
characters.

MK> Thank you.  Buenas noches mi amigo.  :-)

Gracias mi amigo.


Have a good night,

Holger


.. Computers always win because they have inside information ;o)
-- MR/2 2.30

--- PCBoard (R) v15.22 (OS/2) 2
 * Origin: Coming to you from the Sunny Aland Islands. (2:20/228)
  Show ANSI Codes | Hide BBCodes | Show Color Codes | Hide Encoding | Hide HTML Tags | Show Routing
Previous Message | Next Message | Back to Linux operating system (OS), a U...  <--  <--- Return to Home Page

VADV-PHP
Execution Time: 0.0826 seconds

If you experience any problems with this website or need help, contact the webmaster.
VADV-PHP Copyright © 2002-2024 Steve Winn, Aspect Technologies. All Rights Reserved.
Virtual Advanced Copyright © 1995-1997 Roland De Graaf.
v2.0.140505

Warning: Unknown: open(c:\Sessions\sess_i4ubiribgknef1i3g0lv490ik2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0 PHP Warning: session_start(): open(c:\Sessions\sess_i4ubiribgknef1i3g0lv490ik2, O_RDWR) failed: No such file or directory (2) in D:\wc5\http\public\VADV\include\common.inc.php on line 45 PHP Warning: Unknown: open(c:\Sessions\sess_i4ubiribgknef1i3g0lv490ik2, O_RDWR) failed: No such file or directory (2) in Unknown on line 0 PHP Warning: Unknown: Failed to write session data (files). Please verify that the current setting of session.save_path is correct (c:\Sessions) in Unknown on line 0