Re: Unicode support

In article <nospam-5F3985.07305909052005@xxxxxxxxxxxxxxxxxx>, Richard E
Maine <nospam@xxxxxxxxxxxxx> writes:

> > Is support for unicode in filenames and character strings provided
> > intrinsically by the language (f95) or is it compiler specific?
>
> In f95, the whole subject is completely compiler specific.

> The form of valid file names is compiler specific. However,
> interestingly I had to check), I see that a file name must be of default
> character kind, even if other kinds are supported. This seems to suggest
> that you couldn't (in the standard) support unicode file names unless
> unicode was the default kind. Unicode contents is explicitly ok in f2003
> (optionally to the compiler), but doesn't look like unicode file names
> have the same level of support. Of course, if the compiler otherwise
> supports unicode, and the operating system also supports unicode in file
> names, it wouldn't surprise me to see that as a trivial extension. In
> fact, I'd be tempted to call its lack an oversight in the standard.

If course, since the Fortran character set is a subset of Unicode, if
Unicode is the default character kind then everyone is happy and it is
not an extension except in the same sense that a Fortran90 processor
which supports lower case is an extension in the sense that a processor
in Fortran90 didn't have to support lower case (if it does, it has to be
equivalent to upper case).

.

Relevant Pages

  • Re: CLisp case sensitivity
    ... it explicitly allows conforming lisps not to support ... Lisp implementation _also_ conforming with Unicode. ... >> character with a Basic Multilingual Plane character ...
    (comp.lang.lisp)
  • Re: Unicode support
    ... the whole subject is completely compiler specific. ... In f2003, the standard defines a unicode character kind (ok, it is ISO ... that you couldn't support unicode file names unless ...
    (comp.lang.fortran)
  • Re: Upcoming release and unicode
    ... > Macintosh into a Unicode-throughout suite of applications. ... > As noted below, Office 2004 for Macintosh will support the input, display, ... > and basic editing of Unicode characters associated with the following ... > compatibility and character fidelity with Office for Windows. ...
    (microsoft.public.mac.office.word)
  • Re: Attention: European C/C++/C#/Java Programmers-Call for Input
    ... ASCII files and senses when the extended character ... The same will apply to PhiText 2.0 ... Unicode you use another 21 bits to store visual information such as text ... compiler, ...
    (comp.arch.embedded)
  • 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)