-
Notifications
You must be signed in to change notification settings - Fork 163
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
The tag "</p>" and "<p>" appears on the questions of MagoGenie channel on CC. #222
Comments
@rtibbles @aronasorman Can you please put a ETA on this? Its a Blocker for all the MG channel. |
Looks the Magogenie content needs to run through an HTML to Markdown parser before being put in? This package should do the trick, I think: https://pypi.python.org/pypi/html2text |
Note that the ricecooker does not support HTML, only Markdown (with embedded |
@rtibbles @aronasorman @jamalex For more clarification, will this issue be handled in ricecooker or we need to handle it in our code (i.e sushi chef). I remember @aronasorman @jayoshih had taken care of the same issue before. |
@yogeshmhaskule For security reasons, we needed to escape html tags to prevent script attacks. To maintain the paragraphs, you'll need to use \n instead |
@jayoshih @aronasorman I tried using I have attached the sample response of question in file: Check the format of answer content which is similar to question content. for your reference take a look on answer content(it's combination of text, mathml, base64) which is in the file. |
The examples in your sample text contain MathML source, but also include the images that are the rendered version of the MathML, so we can just use the images in this case. The examples you describe (e.g.
|
Summary:
After importing the MagoGenie Questions onto CC, we see that a tag "< / P >" and/or
"< p >" appears on most of the questions.
Link used:
https://contentworkshop.learningequality.org/channels/f531b1ddf64755c9be5061a922317021/edit
Channel ID: f531b1ddf64755c9be5061a922317021
Screenshot:
The text was updated successfully, but these errors were encountered: