fix center-quote shortcode when config unsafe = false

[yureiita]

when config unsafe = false, center-quote without markdown works but shortcode with markdown doesn't work.

the following doesn't work when unsafe = false:

{{% center-quote %}}
**hello** *world*
this is a center-quote shortcode example.
{{% /center-quote %}}

with this fix, the following works with markdown when unsafe = false:

{{< center-quote >}}
**hello** *world*
this is a center-quote shortcode example.
{{< /center-quote >}}

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @Lruihao on Vercel.

@Lruihao first needs to authorize it.

[Lruihao]

This is what I do on purpose, I want to keep the difference between the two ways and leave the decision to the users.

see this commit bc41ae5

[yureiita]

I see, so the only solution is to use unsafe = true? because my config is unsafe = false.

{{< center-quote >}}
**hello** *world*
this is a center-quote shortcode example.
{{< /center-quote >}}

{{% center-quote %}}
**hello** *world*
this is a center-quote shortcode example.
{{% /center-quote %}}

the result of the above code when config unsafe = false is like the picture below:

[Lruihao]

@yureiita When config unsafe = false, Hugo will omitte the raw HTML (<blockquote class="blockquote-center">...</blockquote>)

{{% center-quote %}}
**hello** *world*
this is a center-quote shortcode example.
{{% /center-quote %}}

---

However, using function .Page.RenderString will result in that original content not being output, so I haven't thought of a good solution yet.

[Lruihao]

@yureiita
FYI, think of a compromise solution, which is to create a center-quote.html under your project path layouts/shortcodes/ and fill in your changes.
In this way, the following works with markdown when unsafe = false:

{{< center-quote >}}
**hello** *world*
this is a center-quote shortcode example.
{{< /center-quote >}}

[yureiita]

Alright thanks, I'll just do that. Thanks for the suggestion.

[Lruihao]

This is what I do on purpose, I want to keep the difference between the two ways and leave the decision to the users.

see this commit bc41ae5

It's using another shortcode row to show raw markdown in v0.2.16, so this PR will be merge in to master.