Re: ASCII convention

On Mon, 10 Oct 2005 13:54:11 GMT, "Peter T. Daniels"
<grammatim@xxxxxxxxxxxxxxxx> wrote:

>Miguel Carrasquer wrote:
>>
>> On Mon, 10 Oct 2005 03:14:18 GMT, "Peter T. Daniels"
>> <grammatim@xxxxxxxxxxxxxxxx> wrote:
>>
>> >Miguel Carrasquer wrote:
>> >>
>> >> On Sun, 09 Oct 2005 15:53:38 GMT, "Peter T. Daniels"
>> >> <grammatim@xxxxxxxxxxxxxxxx> wrote:
>> >>
>> >> >If, however, you refer to typography where special fonts (containing
>> >> >angle brackets) are not available, and if you're clever enough to use a
>> >> >Mac, the Single Guillemets provide a very reasonable substitute (see my
>> >> >chapter in the Blackwell *Handbook of Linguistics*. Unfortunately, they
>> >> >turn into Icelandic in Windows: instead of <xyz> write Ðxyzð.
>> >>
>> >> The problem is not with Windows, it's with your browser
>
>It's with Windows fonts, which put different characters in the same
>codepoints as Mac fonts. Mac fonts don't have all those silly
>box-drawing characters, freeing up lots of space for useful stuff in
>128-255.

You're stuck in 1984, it seems.

When the Macintosh came out, there was no standard to extend
ASCII betond 7 bits, so they made up their own scheme, "Mac
Roman".

Windows fonts (except the ones made to emulate MS-DOS
["OEM"] character sets) do not have and never have had
box-drawing characters. Because Windows came later than the
Mac, it had support for the ANSI draft standard (later
ISO-8859-1) built in from the start, albeit in the Microsoft
way. The problem with the Windows "Latin-1" encoding is
that it illegally sticks characters in the 80-9F area (so
does Mac Roman).

Mac Roman is now utterly obsolete, as is Monsieur Pirard's
MacRoman to ISO-8859-1 abomination. OS X (2001) is based on
Unicode, as Windows has been since Windows NT (1993).


=======================
Miguel Carrasquer Vidal
mcv@xxxxxx
.

Relevant Pages

  • Re: Im sure glad I didnt buy a Mac Mini!
    ... George Graves wrote: ... Also if one writes a document in Word for Mac, and saves it as a current Word for Windows file, All ASCI ... Characters above 255 will be missing when the file is opened with a current version of Word on Windows. ... These incomaptibilities are mostly caused because Windows font sets are incomplete and special characters have to be accessed from a special menu. ...
    (comp.sys.mac.advocacy)
  • Re: length of char in bits differs on Win/Linux and Mac
    ... You were just lucky on Windows with your algorithm, and you used the wrong encoding for reading on the Mac. ... because Java uses Unicode for all characters. ...
    (comp.lang.java.programmer)
  • Re: Im sure glad I didnt buy a Mac Mini!
    ... in Word for Mac, and saves it as a current Word for Windows file, All ... Characters above 255 will be missing when the file is opened with a ... I'd call MS and Apple were I you. ...
    (comp.sys.mac.advocacy)
  • Re: Serial port read troubles
    ... and converting the bytes into ASCII (man readable characters). ... Mac) that I can send data to correctly, but when it sends data back, I ... Windows using the same Keyspan converter. ...
    (comp.lang.basic.realbasic)
  • Re: Im sure glad I didnt buy a Mac Mini!
    ... George Graves wrote: ... Also if one writes a document in Word for Mac, and saves it as a current Word for Windows file, All ASCI ... Characters above 255 will be missing when the file is opened with a current version of Word on Windows. ... These incomaptibilities are mostly caused because Windows font sets are incomplete and special characters have to be accessed from a special menu. ...
    (comp.sys.mac.advocacy)