Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Unicode output fixes #15

Merged
merged 2 commits into from
Jun 12, 2017
Merged

Unicode output fixes #15

merged 2 commits into from
Jun 12, 2017

Conversation

dgw
Copy link
Owner

@dgw dgw commented Jun 10, 2017

Does in fact resolve #14, based on testing the change in production this week.

dgw added 2 commits June 7, 2017 08:04
Wolfram is frankly super dumb about Unicode in its output... Why would anyone want
non-ASCII characters as '\:79d1' (a non-standard escape sequence) instead of '科'?
Sure beats me. But asking W|A for plaintext appears to make it output raw UTF-8
instead, so fine.

Should resolve #14.
@dgw dgw added the bug label Jun 10, 2017
@dgw dgw self-assigned this Jun 10, 2017
@dgw dgw added this to the v0.3.2 milestone Jun 10, 2017
@dgw dgw changed the base branch from master to v0.3.x June 11, 2017 19:38
@dgw
Copy link
Owner Author

dgw commented Jun 11, 2017

Changing the base branch made such a mess, wow. Fixed with rebase/force-push.

@dgw dgw force-pushed the unicode-output-fixes branch from 116cebf to 7fdb2be Compare June 11, 2017 19:44
@dgw dgw merged commit 7fdb2be into v0.3.x Jun 12, 2017
@dgw dgw deleted the unicode-output-fixes branch June 12, 2017 12:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant