Files should remain ASCII. That way they are portable to folks without Unicode fonts.
A simple implementation would be to create a 3rd window type for viewing code. This would be read only and show the same content as the editing window but using Unicode. The existing "duplicate my window” and "model / view support" support might be allow side-by-side viewing and live updates (where changing the ASCII text updated the Unicode view).
Just using Unicode symbols to display an ASCII source would be significantly easier to implement. Making the display read-only, so you'd have to toggle into ASCII mode to edit the module, should be fairly easy using code from the pretty-printer. If you want to edit the view with symbols, I suggest you write a precise specification of how it should work.
Leslie
On Monday, March 28, 2016 at 10:18:32 AM UTC-7, Ron Pressler wrote: Well, there's always the (less ideal, IMO, but still very good) option of implementing this only at the presentation layer, in the toolbox only. This is an orthogonal feature, and can be implemented regardless of whether or not SANY is made to support unicode or not (although that would require adding the option of saving as unicode).
BTW, I believe Java has supported unicode since the beginning (which is already twenty years), and a Java char is a UTF-16 character, which should support all the characters we need.
Ron
--
You received this message because you are subscribed to the Google Groups "tlaplus" group.
To unsubscribe from this group and stop receiving emails from it, send an email to tlaplus+u...@xxxxxxxxxxxxxxxx.
To post to this group, send email to tla...@xxxxxxxxxxxxxxxx.
Visit this group at https://groups.google.com/group/tlaplus.
For more options, visit https://groups.google.com/d/optout.
|