Is 'þ' in the 256 characters? It has a unicode value of 254 but a UTF-8
numeric value of 195 190. It's literal numeric value (non-UTF-8) is invalid
when treated as UTF-8.
   # 'þ'
2
   #7 u:'þ'
1
   254{a.
�
   4 u: 254
þ
   195 190{a.
þ
   3!:0]7 u:'þ'
131072
   3!:0 'þ'
2

Although the unicode value of 'þ' is less than 256 it still must be
represented with two bytes in UTF-8. This is where it gets confusing to
view UTF-8 as literal. And why I sometimes think it would be nice if UTF-8
was a type unique from literal and unicode.
   5 16$4 u: 160+i.96
 ¡¢£¤¥¦§¨©ª«¬­®¯
°±²³´µ¶·¸¹º»¼½¾¿
ÀÁÂÃÄÅÆÇÈÉÊËÌÍÎÏ
ÐÑÒÓÔÕÖרÙÚÛÜÝÞß
àáâãäåæçèéêëìíîï
   5 16$a.{~160+i.96
����������������
����������������
����������������
����������������
����������������

'þ' acts weird when executed because literal values above 127 are special
and they should never appear in a statement. This would have to be done
differently to allow for international characters in names.


On Wed, Feb 26, 2014 at 10:30 PM, bill lam <bbill....@gmail.com> wrote:

> IFAIK APL does not allow names with non-ascii character. That will
> be an interesting extension but it also depends on locales which
> include Indic and Arabic language that I have no knowledge at all.
> It is easier if we restrict it to European international
> characters, but then I consider it not too much benefit as being a Chinese.
>
> Ср, 26 фев 2014, Don Guinn писал(а):
> > ​​
> > But it is a start to playing with APL characters as names. Some unicode
> > characters need to be treated like letters and others as words in
> > themselves for ;: . International characters should be like A-Z,a-z and
> can
> > be included in words. Other characters like Greek characters could be
> > treated as words not requiring spaces around them, like + is a word. This
> > would mean that they could not be included as parts of other words. But
> > could be used as single character names. Allowing international
> characters
> > in names would be useful without considering APL characters. And  maybe
> > this would be a step to figuring our how to handle APL characters.
> >
> > >
> > >
> > ----------------------------------------------------------------------
> > For information about J forums see http://www.jsoftware.com/forums.htm
>
> --
> regards,
> ====================================================
> GPG key 1024D/4434BAB3 2008-08-24
> gpg --keyserver subkeys.pgp.net --recv-keys 4434BAB3
> gpg --keyserver subkeys.pgp.net --armor --export 4434BAB3
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm

Reply via email to