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

Handle non printable characters in region names #21

Merged
merged 1 commit into from Jul 17, 2013

Conversation

adrien-mogenet
Copy link
Contributor

Handling regions names with non printable characters caused Hannibal
to print question marks and not route to correct region details.

This fixes #20.

Handling regions names with non printable characters caused Hannibal
to print question marks and not route to correct region details.

This fixes sentric#20.
meniku pushed a commit that referenced this pull request Jul 15, 2013
@meniku
Copy link
Collaborator

meniku commented Jul 15, 2013

I also modified the Javascript-Code to use the regionURI. However, I wonder whether it wouldn't be better if we just use the regionID-part of the regionName in our URI?

@adrien-mogenet
Copy link
Contributor Author

@meniku I think this URI-handling part deserves a tight refactoring and I agree regionID-part is a great candidate. I think all theses byte[] objects should have:

  • their raw value (to perform comparisons)
  • a pretty-printable name
  • a URI-compliant encoding

For the moment I just wanted to keep it as close as possible from the original one.

@meniku meniku merged commit 7f27a19 into sentric:master Jul 17, 2013
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.

None yet

2 participants