notebook -- make it unicode aware

[williamstein]

On Dec 12, 2007 7:48 AM,  wrote:
> 
> Hi all,
> 
> I need to use non-english characters (in comments) in Notebook
> worksheet.
> While working, they're shown w/o problem, but if I save ("download to
> file") worksheet, then close
> SAGE, then open again and load .sws file, sometimes (!) I see just
> unicode codes (like %u4041)
> instead of my chars.
> Strange, but sometimes they're loaded correctly...
> I'm using Sage v 2.8.13 (VMware) under winXP Pro.
> 
> Am I missing something?

No, more likely I'm missing something in how that functionality
was implemened.  You're probably one of the first ever Russian uses of 
Sage, and we have had very little testing of Unicode in Sage. 
Hopefully fixing the above is for developers just a 
matter of changing a few lines in 

  SAGE_ROOT/devel/sage/sage/server/noteboook

that relate to loading and saving the file worksheet.txt. 
   

Component: notebook

Issue created by migration from https://trac.sagemath.org/ticket/1477

[williamstein]

comment:2

> Could you summarize the situation with rendering problems?  Is it as follows:
> (1) When you try to put them in input cells, they get corrupted on load/save.

To be correct, they're replaced by "non-browser"  unicode codes (like
%u0440 instead of р )

> (2) Using edit mode, unicode not in {{{}}}'s gets saved just fine.

Yes, as they are NOT processed (as I understand) and get saved "as
is".


> Oh, by the way, when you're entering html in edit mode, you can just do,
> e.g., consider $y^2 = x^3 + \sqrt{x}$ and the formula will get typeset
> using jsmath.

Thanks, can be helpful when writing my materials.

[sagetrac-mabshoff]

comment:3

Hmm, didn't we fix this by adding UTF-8 support?

Cheers,

Michael

[sagetrac-mabshoff]

comment:4

This sounds very much like #2896. It is not fixed.

Cheers,

Michael

[mwhansen]

comment:5

Sage's support for Unicode and UTF-8 in the notebook is awful. It will take a bit of work to fix this. For starters, we should be using encodeURIComponent in the Javascript instead of escape since escape fails miserably for non-ASCII characters.

I'll look into this more once the templating is done. There's too many strings floating as it is.

[sagetrac-mabshoff]

comment:7

Fixed via #4547 and #5211.

Cheers,

Michael