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

No support for unicode characters in multiple choice #4

Closed
GoogleCodeExporter opened this issue Aug 14, 2015 · 1 comment
Closed

No support for unicode characters in multiple choice #4

GoogleCodeExporter opened this issue Aug 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

I wanted to make a multiple choice answer that had the Spanish word marrón in 
it, but it wasn't allowed.

Original issue reported on code.google.com by sfederwi...@google.com on 11 Jan 2013 at 11:22

@GoogleCodeExporter
Copy link
Author

This works now.

Original comment by s...@seanlip.org on 25 Feb 2013 at 7:12

  • Changed state: Fixed

BenHenning added a commit that referenced this issue Aug 26, 2015
support a training interface. Changes per code review #4.
czxcjx pushed a commit to czxcjx/oppia that referenced this issue Oct 6, 2015
…pia#4.

Implemented all changes recommended by the previous code review.
czxcjx pushed a commit to czxcjx/oppia that referenced this issue Oct 6, 2015
.

Including most of the changes recommended in the review, the following
are the most noteworthy and major changes:

- Introduce a generic customization argument validator in the base interaction
  validator service. This includes tests verifying its functionality.

- Update existing validators to use this validator for thorough customization
  argument validation.

- Improve the spacing in bsaeValidatorSpec.js.

- Improve the clarity of the multiple choice validator, in specific regards to
  the rule type equals versus any other future possible rule types.

- Alter the EndExploration validator policy to ensure it does not receive
  answer groups or a default outcome, since it does not expect either.

- Fix a few bugs which broke the protractor tests (and frontend functionality).

- Remove the isActiveRuleEditorShown function in StateRules.js and references to
  it in state_editor_rules.html. This function was being incorrectly referenced
  in the HTML file and its policy does not make sense when deciding whether to
  display a rule editor.
apb7 added a commit that referenced this issue Feb 18, 2018
seanlip pushed a commit that referenced this issue Jan 6, 2019
…6028)

* Fixes part of #4374

Updated docstrings in Python Backend code for core.storage.base_model.gae_models_test, core.storage.base_model.gae_models, core.storage.user.gae_models, core.tests.test_utils, core.tests.performance_tests.base, core.tests.performance_framework.perf_services, core.tests.performance_framework.perf_domain, core.domain.summary_services, core.domain.email_jobs_one_off_test, core.domain.visualization_registry

* Review checks

* Review checks #2

* Review checks #3

* Review checks #4

* Review Fixes #5

Minor fix

* Review checks #5

Minor fixes

* Review checks #5

Minor fixes

Merge branch 'docstrings-backend' of https://github.com/YashJipkate/oppia into docstrings-backend

* Moved a line up where it can

* linting checks

linting checks ~2

linting checks ~3

* Added missing args and return docstrings

* Address Review

* Linting fix

Linting fixes

* Reviews and linting

* Fixed missing params error

* Linting checks
kevintab95 referenced this issue in kevintab95/oppia May 26, 2020
Fix part of oppia#9132: Migrate mobile navigation.js to async/await
srijanreddy98 referenced this issue in srijanreddy98/oppia Jul 8, 2020
Merge changes from original fork
lkbhitesh07 pushed a commit that referenced this issue Apr 4, 2024
* lala

* Add WebP images

* Remove temp files
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

No branches or pull requests

1 participant