Hi Raul,
The text based result can seem pretty complicated, but when viewed with the
right lens the reasons that it looks and behaves the way that it does become
more apparent. What is going on in the background is that a list of numbers is
being converted into characters. With UTF-8 that list is comprised of 1,2 or 3
digit code points that create the characters. What the user sees is the
characters because J does a really good job of displaying them.
224 176 157 { a. NB. an example of J's covering code points
ఝ
But when you manipulate the character array, you are actually manipulating
these numbers. The results can be very different than you expected, as J works
to create characters from the fractured code points. I did a three minute video
that shows that if you use a variable width for the display of characters based
on the underlying code point, then things stars to make a lot more sense (at
least to me!). If you haven't already, take a look at the video and see what
you think.
https://youtu.be/eN9H-rMk1No
In the end, I think the benefit is that an interface can give clarity to
complicated ideas.
Cheers, bob
> On Jul 5, 2016, at 7:36 AM, Raul Miller <rauldmil...@gmail.com> wrote:
>
> On Tue, Jul 5, 2016 at 9:55 AM, robert therriault <bobtherria...@mac.com>
> wrote:
>> The concern that I have is that when the UTF-8 is broken up that the
>> display be something that is a bit more understandable for the user.
>
> What do you want the user to understand, for that case?
>
> Thanks,
>
> --
> Raul
> ----------------------------------------------------------------------
> For information about J forums see http://www.jsoftware.com/forums.htm
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
