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

Adding support for non US-ASCII encoded menu items #73

Merged
merged 1 commit into from
Mar 29, 2013

Conversation

dalyons
Copy link
Contributor

@dalyons dalyons commented Mar 28, 2013

  • Eval the menu template in the interpreter's default_external encoding,
    which will probably be utf8, or something like windows-1252 on win32
  • Added test with utf8 char in it

- Eval the menu template in the interpreter's default_external encoding,
  which will probably be utf8, or something like windows-1252 on win32
- Added test with utf8 char in it
JEG2 added a commit that referenced this pull request Mar 29, 2013
Adding support for non US-ASCII encoded menu items
@JEG2 JEG2 merged commit 85dd2b7 into JEG2:master Mar 29, 2013
@rkh
Copy link

rkh commented May 24, 2013

Can we have a release please? :)

@JEG2
Copy link
Owner

JEG2 commented May 25, 2013

1.6.19 was released on May 13. It includes this fix, doesn't it?

@rkh
Copy link

rkh commented May 26, 2013

Ah, sorry, I think I had two different encoding issues at the same time and only one of them was caused by me having an outdated highline. > 1.6.1 has not been tagged.

Keep up the good work!

@JEG2
Copy link
Owner

JEG2 commented May 27, 2013

I admit, I'm terrible about forgetting to tag releases. We'll need to get someone to locate the proper SHA's so I can add the tags.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants