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.

Sign up for GitHub

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

Jump to bottom

Issue encoding a non-ascii character preceded by an xml-unsafe one #792

Closed
GoogleCodeExporter opened this issue Mar 25, 2015 · 5 comments
Closed

Issue encoding a non-ascii character preceded by an xml-unsafe one #792

GoogleCodeExporter opened this issue Mar 25, 2015 · 5 comments
Labels
auto-migrated Platform-Pharo Priority-High Type-Defect

Comments

@GoogleCodeExporter
Copy link 

In http://lists.squeakfoundation.org/pipermail/seaside/2014-May/030878.html 
Stephan Eggermont reports:

We have an issue in default Pier with rendering/encoding.
Did I miss setting encoding somewhere?

If we enter in WAEncodingFunctionalTest the following three characters:
->ë
the text input field removes the -.

We noticed because the text area used to edit pier documents
became unusable.

Original issue reported on code.google.com by jo...@yesplan.be on 20 May 2014 at 8:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
auto-migrated Platform-Pharo Priority-High Type-Defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@GoogleCodeExporter