It is trivial to display/enter fancy single glyphs for J. At least as trivial (which I personally don't consider to be trivial) as it is for APL.
Those interested (and I am definitely not) should ignore this trivial aspect of the problem and focus on the hard part which is the mapping of single unicode glyphs to J primitives. What are the glyphs for =. =: +. *. *: =: ? ?. etc.? Perhaps if I saw a complete proposal for this glyph to J mapping that had some communitiy consensus, I wouldn't be so profoundly negative on discussions like this. Keep in mind that the APL folk paid enormous attention to the appearance of the APL glyphs. A hodge podge of unicode glyphs from random parts of unicode fonts would not please anyone who loved APL. We have beaten this dead horse every year for 25 years. When will it be out of its misery? Something that people On Thu, Feb 27, 2014 at 5:10 PM, Joe Bogner <[email protected]> wrote: > On Thu, Feb 27, 2014 at 4:56 PM, Skip Cave <[email protected]> wrote: >> Just my two cents worth... >> >> As an old APL (occasional) programmer, I always wanted a way to flip a >> switch in the J editor and turn J's 2-character primitives into APL >> characters (where appropriate), and either leave J's unique verbs alone, >> have the community decide on an appropriate single glyph, or let me pick a >> symbol for those myself. Then I could always flip that switch in the editor >> back, and see the actual J code, any time I wanted. > > > It seems like it would be straightforward to create a JHS editor and > viewer that toggles between the character sets. Could it just parse > the words and replace with the APL character from a lookup table? The > editor would replace back to ASCII before evaluation. > ---------------------------------------------------------------------- > For information about J forums see http://www.jsoftware.com/forums.htm ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
