Re: Fortran and UTF-8/UNICODE

From: G.F. Thomas (gfthomas_at_sympatico.ca)
Date: 11/29/03

  • Next message: Phillip Helbig---remove CLOTHES to reply: "Re: Master and Slave and Los Angeles" 
    Date: Sat, 29 Nov 2003 14:51:12 -0500

    "Arjen Markus" <arjen.markus@wldelft.nl> wrote in message
    news:3FC70450.5523A066@wldelft.nl...
    > Hello,
    >
    > I was simply wondering about the support of UTF-8 or UNICODE
    > in Fortran: does anyone know of a library/module that actually
    > supports these character sets?
    >
    >
    > Regards,
    >
    > Arjen

    Unicode support in Fortran has been available since FPS/Windows NT days.
    It's also available in CVF. This is consistent with Windows 32 (not 95,
    98, and Me) being Unicode-based by design, ab initio. For Unicode I/O
    you'll have to use the USEROPEN specifer in the OPEN statement to get at
    the CreateFile API. You've now entered the land of C-Fortran. Actually,
    CreateFile is interfaced in CVF's kernel32 module so you can use it if
    you pass it a C-string file name. Look up Using National Language
    Support Routines in the online help index.

    BTW, it's ironic that the vintage FPS and CVF documentation's use of the
    politically incorrect term multibyte renders them more current than the
    F004 CD with it's misappropriation of the outdated multioctet . The
    F-word for English's byte is octet and it connotes eight as in 8-bits.
    If ISO was looking for a term that didn't so explicitly beget 8 as
    opposed to 7 or 9, say, then it would have done well to stick with byte.
    Instead ISO fcuked up. ISO, being a rubber-stamping clearinghouse for
    the handiwork of others, hawks the outdated Unicode v 3, with its
    regrettable adoption of octet, as its own. Unicode v 4 has acknowledged
    this fcuk up and has already reverted back to byte from octet and the
    toadying ISO will follow suit when it brings itself in line with
    Unicode's most recent advances. The term 'multioctet' is passé with
    Unicode v4, and by vitally sustaining usurpation with ISO, it having
    adopted 'multibyte' as a character set with a variable number of bytes
    per character just as Microsoft had the foresight to do a decade ago. 

    -- 
Ciao,
Gerry T.
______
"The enemy is anybody who's going to get you killed, no matter which
side he's on." -- Yossarian, in Catch 22.
  • Next message: Phillip Helbig---remove CLOTHES to reply: "Re: Master and Slave and Los Angeles"

    Relevant Pages

    • Re: Quieter glyphs than parentheses
      ... partial support for Unicode. ... agnosticism, it imposes requirements that a Unicode-supporting ... While R6RS can remain agnostic about character sets, ...
      (comp.lang.lisp)
    • Re: Unicode Support
      ... > compiler/assembler is unicode support. ... > but the fact that most assemblers, ... Most popular *editing* tools support this data format. ... Is there really a need to put unicode characters into identifiers? ...
      (alt.lang.asm)
    • Unicode text editor mined 2000 release 11
      ... Mined provides both extensive Unicode and CJK support offering many ... of terminal variations, or Han character information). ... It was the first editor that supported Unicode in a plain-text terminal. ...
      (comp.os.linux.announce)
    • Re: Unicode-based FreeBSD
      ... displaying specialised characters on the screen/tty. ... There are special Input Methods for the rest of Unicode. ... Unicode support and the FreeBSD developers see little reason to ...
      (freebsd-current)
    • Unicode text editor mined 2000 release 11
      ... are not aware of (like auto-detection features and automatic handling ... It was the first editor that supported Unicode in a plain-text terminal. ... Combining character width properties. ... Added keyboard configuration examples for Control-function key detection for rxvt and mlterm to the runtime support library. ...
      (comp.editors)
    Loading