Re: request for help

On May 16, 3:56 pm, "jk" <aq...@xxxxxxxxx (not the q's)> wrote:
"phil chastney" <phil.hates.s...@xxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
messagenews:XRgXj.466377$uN4.260035@xxxxxxxxxxxxxxxxxxxxxxxxx



jk wrote:

Phil,

International Setting : Western ISO

I selected {enclose} from Dyalog Std and got >

plus an annoying line feed (as you might see)

The other choices are particular national charactersets

(and still the line feed)

this takes me too much time to find out

Jan -- I have managed to check out a copy of dlogttst.ttf, “Dyalog
Std TT" (internally, the version number is given as 1.000), which is
probably very similar to the one you're using

the good news is that there's nothing wrong with your Copy & Paste

the bad news is that the fault is in the font

that is a truly bizarre font

-- initial impressions are that it's an 8-bit font of 256 characters
-- except that the glyphs (the actual printable shapes) have
associated Unicode values
-- but the Unicode values are all over the shop, and mostly wrong

when you Copy & Paste, the Copy operation picks up the Unicode values
of the selected characters from the source document (and if there are
no Unicode values defined, it picks the indices of the characters'
positions within the font)

these values (Unicode values, in your example) are pasted into the
target document, and what you see then are the glyphs from the font
being used in the target document appropriate to the pasted values

OK? right, in your example you copied the "enclose" character, which
has Unicode value 0x203A in dlogttst.ttf (and ONLY in dlogttst.ttf)

that value of 0x203a was transferred to the target document

the target document displayed the glyph appropriate to Unicode value
0x203a, which happens to be SINGLE RIGHT POINTING ANGLE QUOTATION MARK
(= right pointing single guillemet)

like I said, the fault is in the font

and the oddities don’t end there
-- there are more coding errors -- for instance, right shoe is given
a Unicode value of 0x0153, which really belongs to the “oe” diphthong
-- the font is copyrighted 1995/6, but the creation date is 1997
-- the font claims to represent CP1252 (Microsoft’s variation on a
theme of Latin-1) but neither the Unicode values nor the glyphs match
CP1252 properly

if you have to use this font, be very careful when cutting from
Dyalog_std text and pasting into a different font environment -- as
you found, the glyphs may change

(there are Copy & Paste operations which transfer formatting
information like the font name, but that clearly didn't happen in your
case)

to confuse the issue further, there is another font, dysymb.ttf,
“Dyalog Symbol, version Winter Solstice 2006”, which claims to be a
Windows Symbol Font (a rather particular kind of beast, with some
strange habits) which gives Unicode values to all its glyphs, using
the range 0xF000 to 0xF0FF

this, too, may well change its appearance when Copied & Pasted

there may well be other fonts which I’ve not seen, but that’s the
symptoms explained

what you do about it is another matter . . . /phil

thanks for your extensive answer. I'll probably do nothing about it.
The software I've distributed is all in dyalogrt.exe, and I mostly use
the Causeway font (because I like the shape). The mapping of that
font is probably worse.

In the past I've done ..ty conversions APL-PC to MicroAPL, MicroAPL to
VS APL (on time sharing) VS APL to VAX-APL (EBCDIC vs ASCII) and
last VAX-APL to Dyalog, which was "the ultimate choice".
The mappings I've seen ...

*\jk

I suggest you try installing "APL385 Unicode" or Phil's own "SimPL"
and try to get msie6 to use that if you can. The only difference,
apart from style that I've encountered is that Dyalog (and Adrian who
designed "APL385 Unicode") use a different code point for Diamond than
does Phil.
.

Relevant Pages

  • Re: and symbol
    ... x3270to work with APL2 on a VM system using the APL385 unicode font. ... This is working for most things, but I am finding there are a few APL ... glyphs that are not being displayed when I select this font. ... all fonts should implement all Unicode ...
    (comp.lang.apl)
  • Re: and symbol
    ... x3270to work with APL2 on a VM system using the APL385 unicode font. ... This is working for most things, but I am finding there are a few APL ... glyphs that are not being displayed when I select this font. ... all fonts should implement all Unicode ...
    (comp.lang.apl)
  • Re: and symbol
    ... x3270 to work with APL2 on a VM system using the APL385 unicode font. ... glyphs that are not being displayed when I select this font. ... all fonts should implement all Unicode ... display either with the APL385 font in x3270. ...
    (comp.lang.apl)
  • Re: request for help
    ... the bad news is that the fault is in the font ... -- except that the glyphs have associated Unicode values ... these values are pasted into the target document, and what you see then are the glyphs from the font being used in the target document appropriate to the pasted values ...
    (comp.lang.apl)
  • Re: Font for a menu?
    ... It wouldn't be so bad if the Windows key were somewhere else on the keyboard, ... That's the one - the main problem is that Microsoft don't distribute a font ... I think the Unicode set has been ... flags exist in the set - but only flags for upward stems. ...
    (microsoft.public.vc.mfc)