The demo seems to be using APL385 Unicode font but when I copy the
chess pieces all I see are dots when that font is used.
Lucida Sans Unicode displays the chess pieces ok.
But then I am missing the APL chars
Using Arial Unicode MS I see the APLchars but the chess pieces display
sideways
Other than the chesspieces missing from the session font it is most
informative and interesting demo.
I'm not in a position to check out the demo, because Silverlight doesn't
support my processor, and you don't say what environment you are copying
to, so the following might, or might not, help:
if the text contains a character whose value corresponds to a chess
piece, and APL385 is the font chosen for your local display of that
character, then you should see the .notdef character specific to the
font, because APL385 doesn't have any glyphs for chess pieces
actually, I don't think APL385 has a .notdef character either, so the
application (browser, word processor, whatever) should supply its own
Lucida Sans Unicode doesn't have a full set of glyphs for APL, and
therefore cannot display APL -- so no surprise there
likewise, my copy of Lucida Sans Unicode doesn't have any glyphs for
chess pieces, so my best guess is that
-either- you have a more recent version,
-or- the application has used a fallback font
my version of Arial Unicode MS, however, does have glyphs for chess
pieces, and they're oriented correctly -- this one is interesting --
the only instance I can think of where text sometimes gets
unexpectedly rotated 90° is Mongolian script embedded in a left-to-right
script
does anything else get rotated in this way?
to backspace one, are you sure that what you see in the demo are
characters from a font, and not .gifs?
/phil
I was copying the chess pieces into Dyalog APL and therefore it is
interesting.
The demo seemed to be using Dyalog session as well and there the fonts
showed.
Adrian Smith updated the font late last year, adding the chess pieces
and 1/8th block drawing chars, which allow:
unibar←{⊖⍉(9↑⎕UCS 9609-⍳8)[1+8⌊0⌈-⍵∘.-8×⍳⌈8÷⍨⌈/⍵]}
unibar 40+⌈40×1○0.1×⍳63
▂▄▆▇████▇▆▅▃▁
▂▅██████████████▆▄
▄▇███████████████████▅▂
▄████████████████████████▆▂
▄████████████████████████████▆▂ ▁
███████████████████████████████▆▂ ▁▅█
█████████████████████████████████▆▂ ▂▅███
███████████████████████████████████▇▃ ▂▆█████
██████████████████████████████████████▅▂ ▂▄▇███████
█████████████████████████████████████████▆▄▂▁▁▁▁▁▂▃▅▇██████████
You can download the latest version of the font from a link near the
top of:
http://www.dyalog.com/documentation_library.htm
If you don't want to bother with the fonts, you can watch me do it at:
http://www.youtube.com/watch?v=GdG04m1IQ0A
Also worth watching:
http://www.youtube.com/watch?v=a9xAKttWgP4
And for a laugh:
That looks a bit like a whale.
What's the formula for a duck? :-)
David
Thanks for the fonts.
It is very interesting to have APL lessons/demos like this on youtube.
We should probably have a lot of those.
It makes a difference being able to watch a good demo and see what is
possible.
There are a few things I learned watching the demos.
I did not see how lines are fed into the session manager from a
script.
I would to like to get pointers where to look.
> It is very interesting to have APL lessons/demos like this on youtube.
> We should probably have a lot of those.
Yes, we should! It is a lot of hard work just to produce a minute of
quality video, though (ask John Scholes)!
> I did not see how lines are fed into the session manager from a
> script.
The lines are fed into the session manager by a "Demo" tool that is
available with Dyalog v12 as a "Spice" command. If you enable Spice
(under Options|Configure|SALT), you will get a "Spice Command Line" at
the bottom of the screen (this is a "user command input line"). Into
this box, you can type e.g.
Demo filename
Where filename is a Unicode text file (typically UTF-8 encoded, but
any encoding should be usable) containing APL statements. If you don't
provide a filename, you get a file dialog box. Spice commands are also
UTF-8 files, the Demo command itself is the file "SALT
\Spice.Demo.dyalog" (but it is just a shell, the real code is in "SALT
\Lib\RunDemo.dyalog").
Beware: If you edit these files, it has *immediate* effect :-). But it
isn't so dangerous, if you make the system crash you get the usual
tracer/debugger and any changes you make to the code from inside APL
will be written straight back to the files. You just need to beware
that if you have a simple editor like Notepad open on the files
simultaneously, it may not pick up on the fact that APL is changing
the files.
Once you have started a demo, Alt+N and Alt+P execute the next line or
move you to the previous one. Alt+I restarts - read the source code to
find out the rest :-)
The scripts that I used at Dyalog'08 are here:
http://conference.dyalog.com/2008Elsinore/Presentations/Morten%20Kromberg/Unicode%20Demo%20Scrips/
For more on SALT+SPICE, look under the "Tools" heading at
http://www.dyalog.com/documentation/
Morten
Don't have a good "formula". This is a bit of a cop-out:
⎕io←0
chars←⎕UCS 32 39 40 41 44 45 46 47 54 61 92 95 96 126
duck←13 5489 29412 30337 31361 30364 76915 2159543 7017008
7323847 3230277 128980 194837 422576 153664
chars[(6⍴14)⊤duck]
,~~.
( 6 )-_,
(\___ )=='-'
\ . ) )
\ `-' /
~'`~'`~'`~'`~
(with thanks to http://www.asciiworld.com/-Duck-.html)
WOW!!!
This is really useful!
The connection to Excel (displayed in the demo) is also very nice and
useful.
You have to tell people more about this option.
It has changed my view of Dyalog a whole lot.
I had no idea scripting was an option.
Somehow that has always escaped my attention.
You have a lot of demos available you could deliver in form of scripts
instead of as ws or books.
This scripting facility Spice is really important and it is very
similar to the J labs and demos.
If you want to learn something it would of course be great to have
videos but as you correctly say it takes a hell of a lot of time and
effort to create those.
The step of creating scripts is much easier because you have the demos
in documentations as well as in ws and it would be easy to do some cut/
paste work into Unicode files.
Over time this could become the best selling part of Dyalog APL.
Given you have good script demo/labs the work with other kind of
documentation is much less important.
A good script is much easier to test for validity as time goes by than
the other kind of documentation that easily gets outdated.
Stepping through a script any monkey can do and it is also possible to
automate the process.
You could (in theory ) stop delivering ws and just deliver scripts.
I think this is great and I really do not understand how I can have
missed this option.
There is of course also:
⎕UCS 40499 40495 ⍝ U+9E33 Male Mandarin Duck, U+9E2F Female
Mandarin Duck
鸯鸳
Above sequence apparently known as "affectionate couple".
http://www.cojak.org/index.php?function=code_lookup&term=9E33