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

Add support for Markdown body translation #11

Closed
jeremydw opened this issue Mar 14, 2014 · 4 comments
Closed

Add support for Markdown body translation #11

jeremydw opened this issue Mar 14, 2014 · 4 comments

Comments

@jeremydw
Copy link
Member

Currently, only fields and templates can be translated.

@jeremydw
Copy link
Member Author

Markdown bodies can now be localized, but they are not extracted into messages files. HTML content bodies can make use of standard translation tags. If anyone has any suggestions for message storage or extraction of long-form Markdown documents, I'm all ears!

@WillsB3
Copy link

WillsB3 commented Jan 10, 2017

@jeremydw Did you ever get any further with this?

I have some long form copy in a documents .yaml which I'd like to render via Markdown:

$title: My Document

blurb: >
    This is some long form copy that is split into multiple paragraphs.

    Here is the second paragraph.

Is it possible to render individual fields of a document with markdown by using some built in filter in the template?

Edit: I now realise this issue is regarding translation of markdown content. Oops - Sorry. Let me know if there's a more appropriate place for this discussion..

@jeremydw
Copy link
Member Author

It is! You should be able to do {{doc.blurb|markdown|safe}}. There is a built-in markdown filter that will render its contents as markdown. Does that meet your needs?

https://grow.io/docs/templates/#markdown

@WillsB3
Copy link

WillsB3 commented Jan 11, 2017

Perfect - Thanks. Can't believe I didn't find that in the docs...

Thanks again

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

No branches or pull requests

2 participants