Timeline for answer to When can APL characters be counted as 1 byte each? by Adám
Current License: CC BY-SA 4.0
Post Revisions
29 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 26, 2018 at 16:53 | comment | added | Kevin Cruijssen | @Adám Ah, didn't knew Jelly was based on APL. I thought it was a separated language just like 05AB1E, which both have custom code pages. | |
| Oct 26, 2018 at 15:10 | comment | added | Adám | @KevinCruijssen The question is When can APL characters be counted as 1 byte each? Jelly is an APL. Maybe the question and answer should be overhauled to include all code pages, although there is probably less confusion about dedicated golfing languages using custom code pages than mainstream language doing so. Sure, Jelly isn't a mainstream language, but I included it here because the posts were specific to APL. | |
| Oct 26, 2018 at 13:18 | comment | added | Kevin Cruijssen | Since Jelly's custom code-page is part of the answer, wouldn't other answers using custom code-pages (i.e. 05AB1E) be part of the answer as well now? 05AB1E probably barely existed yet when you wrote this answer, but I see you edited it today, hence the question. | |
| Oct 26, 2018 at 9:40 | history | edited | Adám | CC BY-SA 4.0 |
add dzaima/APL
|
| Jun 12, 2018 at 8:17 | history | edited | Erik the Outgolfer | CC BY-SA 4.0 |
code page has changed
|
| May 14, 2018 at 20:06 | history | edited | Adám | CC BY-SA 4.0 |
language
|
| Dec 21, 2017 at 17:22 | vote | accept | Adám | ||
| Dec 21, 2017 at 17:22 | history | edited | Adám | CC BY-SA 3.0 |
add SBCS note
|
| Nov 28, 2017 at 13:56 | history | edited | Adám | CC BY-SA 3.0 |
remove "Win" from "APL+Win"
|
| Nov 15, 2017 at 22:53 | history | edited | Adám | CC BY-SA 3.0 |
details about glyphs not in set
|
| Dec 20, 2016 at 13:53 | history | edited | Adám | CC BY-SA 3.0 |
New glyphs for Dyalog APL 16.0, layout improvements, new link
|
| Sep 30, 2016 at 18:21 | history | edited | a spaghetto | CC BY-SA 3.0 |
added 4 characters in body
|
| Sep 15, 2016 at 15:20 | history | edited | Adám | CC BY-SA 3.0 |
Added M
|
| Aug 28, 2016 at 8:29 | comment | added | Adám | @luserdroog See Jelly Code page. | |
| Aug 28, 2016 at 8:20 | comment | added | Adám |
@luserdroog Both ¶ and newline are read as byte 7F, which makes it much easier to read code as statements may be separated by actual visual newlines, while literal newlines (inside strings) can be seen. However, Jelly considers them completely equivalent – in fact, it cannot distinguish between them at all.
|
|
| Aug 28, 2016 at 4:22 | comment | added | luser droog | What's Jelly's 257th character? How is that even possible? | |
| Jul 19, 2016 at 5:23 | comment | added | luser droog | I'm devising a new one (I linked to here of course :). | |
| Jul 11, 2016 at 10:14 | history | edited | Adám | CC BY-SA 3.0 |
Added Jelly, J, K, Q, Nial, ELI
|
| Jul 7, 2016 at 18:45 | comment | added | Alex A. Mod | Interesting. Thanks for clarifying. | |
| Jul 7, 2016 at 18:29 | comment | added | Adám |
@AlexA. No, out-of-the-box, Dyalog APL does not understand APL EBCDIC. "Classic" is basically just another extended ASCII. However, Dyalog APL has ⎕AVU which allows you to use any codepage you want. So by assigning ⎕AVU←256 Unicode points that correspond to APL EBCDIC, it does support it.
|
|
| Jul 7, 2016 at 17:42 | comment | added | Alex A. Mod | So Dyalog does not support the EBCDIC code page? Or is that what the "classic Dyalog APL encoding" is? | |
| Jun 24, 2016 at 12:17 | comment | added | jimmy23013 |
@MartinEnder So U+2227 is only because I think it is closest to that character. It's more like A+ doesn't think ^ and ∧ are different, just like the Windows console doesn't think ☺ and U+1 START OF HEADING are different, and display it like a ☺.
|
|
| Jun 24, 2016 at 12:07 | comment | added | jimmy23013 |
@MartinEnder A+ doesn't seem to be aware of the encodings at all. It has only a font of the 256 characters, where ^ looks like an inverted © in that font, which in turn looks like a ∨ in the Unicode standard.
|
|
| Jun 24, 2016 at 8:54 | comment | added | Martin Ender Mod |
An interesting follow-up question would be how the different dialects handle output encoding. Do they just output byte streams or do they output some Unicode encoding of the code points represented in the string. For instance, it appears that you can't include the ^ character in a string literal in A+ since U+5E is not on the code page. But if you use ∧ instead, would that get printed as a 0x5E byte, or as a UTF-8/16/32 encoded U+2227?
|
|
| Jun 23, 2016 at 22:01 | history | edited | Adám | CC BY-SA 3.0 |
deleted 57 characters in body
|
| Jun 23, 2016 at 22:00 | comment | added | Adám | @jimmy23013 Thanks for your hard work. I only did research and data-mangling. jimmy23013 did a full character set manually/visually! | |
| Jun 23, 2016 at 21:26 | history | edited | jimmy23013 | CC BY-SA 3.0 |
tried to guess it from the font
|
| Jun 23, 2016 at 17:33 | history | edited | Alex A.Mod | CC BY-SA 3.0 |
fixed links; added ngn/apl link
|
| Jun 23, 2016 at 17:21 | history | answered | Adám | CC BY-SA 3.0 |