{"action":"closed","issue":{"url":"https://api.github.com/repos/mathjax/MathJax/issues/1134","labels_url":"https://api.github.com/repos/mathjax/MathJax/issues/1134/labels{/name}","comments_url":"https://api.github.com/repos/mathjax/MathJax/issues/1134/comments","events_url":"https://api.github.com/repos/mathjax/MathJax/issues/1134/events","html_url":"https://github.com/mathjax/MathJax/issues/1134","id":63839279,"number":1134,"title":"placement of braces with \\mathscr vs. \\scr and other codes","user":{"login":"orangeplanet","id":7536637,"avatar_url":"https://avatars.githubusercontent.com/u/7536637?v=3","gravatar_id":"","url":"https://api.github.com/users/orangeplanet","html_url":"https://github.com/orangeplanet","followers_url":"https://api.github.com/users/orangeplanet/followers","following_url":"https://api.github.com/users/orangeplanet/following{/other_user}","gists_url":"https://api.github.com/users/orangeplanet/gists{/gist_id}","starred_url":"https://api.github.com/users/orangeplanet/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/orangeplanet/subscriptions","organizations_url":"https://api.github.com/users/orangeplanet/orgs","repos_url":"https://api.github.com/users/orangeplanet/repos","events_url":"https://api.github.com/users/orangeplanet/events{/privacy}","received_events_url":"https://api.github.com/users/orangeplanet/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/mathjax/MathJax/labels/Expected%20Behavior","name":"Expected Behavior","color":"3463b3"}],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":2,"created_at":"2015-03-23T21:42:51Z","updated_at":"2015-04-02T11:59:47Z","closed_at":"2015-04-02T11:59:47Z","body":"The placement of braces in MathJax appears to make a difference in \\mathscr vs. \\scr, \\mathfrak vs. \\frak, and \\mathcal vs. \\cal.   See https://jsfiddle.net/4nfo1joa/\r\n \r\nIt looks as thought \\scr has to be encased in outer grouping braces to contain it properly: {\\scr P}.  If it isn't set up this way, then all the lowercase letters that follow in the string come out as Roman and all the uppercase letters inherit the script.  \\scr{P} doesn't keep the target isolated the way {\\scr P} does.   The same pattern occurs with \\mathfrak vs. \\frak.  Almost the same thing happens with \\cal: if it isn't coded as {\\cal P}, then all the uppercase variables inherit the calligraphic setting, but the lowercase variables go to italic. \r\n\r\nIs this expected behavior for these commands or a bug? \r\n"}}